Redundant spatial element state affects parameters

[longt61]

I am working with Revit Schedule for room  and other spatial elements in general, and I have noticed that a spatial element can several states during their lifetime in Revit when you delete them in model, place them outside of closed boundary etc..etc.. . After a quick look at the link below, I can determine the state of a spatial element, which includes Placed, Not Placed, Not enclosed, Redundant.

https://thebuildingcoder.typepad.com/blog/2016/04/how-to-distinguish-redundant-rooms.html 

However, the problem is that I am working with Revit schedule and the state of spatial element affects some of the element 's parameters. Each affected parameter can display different text on schedule and this text is completely irrelevant to its actual value retrieved by API. 

For example: a redundant room can make its:

    - Perimeter displays "Redundant" in schedule view, but return "0" in API

    - Level displays "level_name" in schedule view, but return null/ Invalid level ID in API

Since Revit API need parameter value for sorting/grouping and filtering operation, which is what I am currently working on to determine which element belongs to which schedule row, the inconsistent of display value and actual  value is a problem that need to be solved. I think there are a few options for me though:

1. Determine if a parameter if affected by the spatial element placing state.

2. Find a connection between the display value and the actual value retrieved by API 

3. Hardcode all the parameters and move on with other problems, which seems to be acceptable at a certain degree, but it leads to 2 other question:

    3.1. Is there any other element that can be affected like this beside room, area and space (which are noted in Spatial element API)?

    3.2. Is there other parameter that can be affected by state of element beside Level and Perimeter (project parameter, shared parameter ....)

Any suggestion is much appreciated.