Skip to main content
Solved

ArcGIS Indoors to IMDF transformation - openings not processed

  • June 9, 2021
  • 4 replies
  • 24 views
I

Hi,

​

I am hoping someone in the community can help me with the issue I am experiencing during ArcGIS Indoors to IMDF transformation. Openings features, which are part of the Details FC in my ArcGIS indoors information model, are not being picked up during the FME transformation process - meaning the output does not contain openings.geojson file at all.

​

FME transformation phase that extracts the openings from Details features seems to be passing as expected. Feature geometry checks are also passed, but then the FeatureTypeFilter leaves them Unfiltered.

The reason for this might be in the fact that assigned IMDF category for these features is set as pedestrian (which I understand is one of the allowed IMDF subcategories for Openings).

 

I would appreciate if anyone can offer some assistance.

 

Thanks

Best answer by daveatsafe

Hi @daveatsafe​,

thanks for a quick reply.

The features seem to have been output as expected from the first FeatureTypeFilter (see image).

I realised my mistake was in the mapping table which had a wrong value for the openings in the IMDF_category (I must have wrongly set to "pedestrian"). Changed it to "opening" now but this had no effect to the outcome of that FeatureTypeFilter in question - it still processes them as Unfiltered features.

Hi @indoorstester​,

 

The first FeatureTypeFilter catches the openings through the AIIM/Details port, but the second FeatureTypeFilter has an 'opening' port instead of AIIM/Details. Please edit the second FeatureTypeFilter and replace 'openings' with 'AIIM/Details', then reconnect the output to the Opening section.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • 1637 replies
  • June 9, 2021

Hi @indoorstester​,

 

Please have a look at the fme_feature_type attribute of the Unfiltered output to see why they did not exit from the Details port. Were these features output properly from the previous FeatureTypeFilter?

I
  • indoorstester
  • Author
  • 2 replies
  • June 10, 2021

Hi @daveatsafe​,

thanks for a quick reply.

The features seem to have been output as expected from the first FeatureTypeFilter (see image).

I realised my mistake was in the mapping table which had a wrong value for the openings in the IMDF_category (I must have wrongly set to "pedestrian"). Changed it to "opening" now but this had no effect to the outcome of that FeatureTypeFilter in question - it still processes them as Unfiltered features.

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • 1637 replies
  • Best Answer
  • June 10, 2021

Hi @daveatsafe​,

thanks for a quick reply.

The features seem to have been output as expected from the first FeatureTypeFilter (see image).

I realised my mistake was in the mapping table which had a wrong value for the openings in the IMDF_category (I must have wrongly set to "pedestrian"). Changed it to "opening" now but this had no effect to the outcome of that FeatureTypeFilter in question - it still processes them as Unfiltered features.

Hi @indoorstester​,

 

The first FeatureTypeFilter catches the openings through the AIIM/Details port, but the second FeatureTypeFilter has an 'opening' port instead of AIIM/Details. Please edit the second FeatureTypeFilter and replace 'openings' with 'AIIM/Details', then reconnect the output to the Opening section.

I
  • indoorstester
  • Author
  • 2 replies
  • June 11, 2021

that worked! imdf submitted to review by apple

 

thanks a lot for your help @daveatsafe​ ! hopefully, no additional fixes will be needed.

Community Stats

32,070
Posts
121,771
Replies
39,698
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.