I am testing out the new Add Geometry to Indoors Positioning Dataset tool released with 3.6 and overall, it has drastically improved the accuracy of our IPS (yay!) but I keep getting an error for some entrance/exit transitions and cannot seem to figure out why.
The error is: WARNING 250084: Entrance / Exit Features with the following Object IDs are not within any valid Level Feature and will not be processed: 7, 8, 9, 10, 11.
All of those transition features are on the second level of a building that opens up to an outdoor paseo. For context, the building is on a hill, so the east side "ground level" is floor 2, and the west side ground level is floor 1. The building is also split on the second floor, with a paseo that runs through it. Here is the second level floorplan for reference. Blue units are indoors, and the gray with black border area is the level feature.
There are also a couple doors/transitions on the first floor, just below the ones on the second floor, and those process correctly. We also have a similar situation in another building, where the west entrance is on the first floor and the east entrance is on the second floor, just no split in the building/level, and those both processed properly as well.
Here is the output of the tool I am getting:
Floor 1: works as expected
Floor 2: fails to create a transition
I first thought it was because the level feature edge was too far from the transition, so I reshaped the level to only include the interior of the building, but that did not help. I have checked the Z values and made a 3D scene to ensure the level, IPS areas and transitions are all on the same plane and they are. All the attributes seem to be correct, and I cannot find any difference between the areas that work and the areas that do not work.
I know this is a new tool but does anyone have any ideas on what is happening?
Hi Molly,
A Product Engineer in IPS team here. Can you share the values of:
- VERTICAL_ORDER_FROM and VERTICAL_ORDER_TO for the Entrance/Exit features that are and are not being processed
- LEVEL_ID and VERTICAL_ORDER for your Level feature class
The tool compares the vertical_order_from values in the Entrance/Exit features with the vertical_order values of the Levels. It could be that the features you are passing have the same Level_ID but different vertical_order_from value, hence some of them are skipped.
Hi @Patrycja_Religa ,
Thanks for responding. The vertical order to and from for the transitions are all 1. The level_ID for the levels layer is HLC_2000.LV2 and the vertical order is also 1. Here a screenshot of the table with the relevant features.
Can you please also show the same for the transitions that are processed?
Highlighted are the problem transitions, the rest processed properly.
I am going to try adjusting the Levels and Transitions geometry. We have been playing around with the idea of moving the Transition line to closer to edge of the facility instead of right at the door threshold, and treating the paseo as more of an interior space than exterior. That way when people are just walking through the paseo to go from one side of building to another, it does not have to try to switch between IPS and GPS (which cause a lag and possible confusing when navigating) and instead will only switch to GPS once you have left the building as if you are walking to another building. Something like shown here, current transitions are in pink, but new ones would be the orange lines.
I don't think that is causing my particular issue but it's something we want to try anyway, so I will report back on if I have the same issue with these new transitions or not.
Would you mind sharing the data with me to debug it on my end (preliga@esri.com)? I’m not seeing anything wrong with the attributes you provided.
Hi Molly, any update on this?