Skip to main content

Hello everybody,

I exported AIXM datafile from FME and I tried to validate it here: https://swim.m-click.aero/validator/ with profile "AIXM, GML Aviation Profile, no Business Rules". Validation result told me that tag "srsdimension" is not correct for AIXM (exact form is "attribute 'srsDimension' is not declared for element 'ElevatedPoint'"). AIXM writer automatically puts SRSDimension tag to exported datafile. So I wanna ask, where is problem - in validator or FME has wrong schema definition for AIXM?

I attached sample of my export.

Thank You!

Lubo

Hello @lazarlubomir,

After taking a look at the sample you sent along with the 5.1 schemas. It looks to be that the SRS might be a red herring so to speak. The validator FME uses which is based on Apache Xerxes open source library, reports the following as the incorrect value.

value 'BRR' does not match any member types of the union

If we changed the value BRR to one of the values mentioned in the schema such as DME - then the FME validator passes.

I'm not quite sure why the online validator fails with the srsDimension.

I hope that helps!


Hello @lazarlubomir,

After taking a look at the sample you sent along with the 5.1 schemas. It looks to be that the SRS might be a red herring so to speak. The validator FME uses which is based on Apache Xerxes open source library, reports the following as the incorrect value.

value 'BRR' does not match any member types of the union

If we changed the value BRR to one of the values mentioned in the schema such as DME - then the FME validator passes.

I'm not quite sure why the online validator fails with the srsDimension.

I hope that helps!

Hello @trentatsafe,

 

 

yes, I know about BRR incorrect value, it is my pseudo-value. But more problematic for us is srsdimension issue. Please, can You check GML definition for AIXM there: https://www.opengeospatial.org/docs/discussion-papers? It looks like AIXM should not contain srsdimension tag.

 

 

Please, can Safe software consider this issue?

 

Thank You so much!


Hello @lazarlubomir

Thank you for the documentation link. Based on the OGC doc, it does appear we are incorrect in our output. As such I have filed an issue to correct this. FMEENGINE-60185 can be used to track this change, and I will post here once it has been fixed.

 

Thank you again for your assistance!

Hello @lazarlubomir

Thank you for the documentation link. Based on the OGC doc, it does appear we are incorrect in our output. As such I have filed an issue to correct this. FMEENGINE-60185 can be used to track this change, and I will post here once it has been fixed.

 

Thank you again for your assistance!

Hello @trentatsafe,

Where can I track the FMEENGINE-60185. Is this issue solved already? If yes in which FME version?

Can you suggest any solution/workaround on how to get rid of srsDimention attribute from AIXM in FME 2017?

Thank you!

Zaneta


Hi @zaneta.mark,

 

This was fixed in 2019.1+. You can find downloads for both 2019 and 2020 from here: https://www.safe.com/support/support-resources/fme-downloads/

 

 

 

I don't believe there was a workaround found at the time.

Hello @trentatsafe,

Where can I track the FMEENGINE-60185. Is this issue solved already? If yes in which FME version?

Can you suggest any solution/workaround on how to get rid of srsDimention attribute from AIXM in FME 2017?

Thank you!

Zaneta

Hi @zaneta.mark,

 

This was fixed in 2019.1+. You can find downloads for both 2019 and 2020 from here: https://www.safe.com/support/support-resources/fme-downloads/

 

 

 

I don't believe there was a workaround found at the time.

Reply