CSDGM Reader - Altitude Units Missing

[dwalt]

Altitude Units (altunits) from CSDGM input is not translating to mdJSON: schema{ } > metadata{ } > resourceInfo{ } > extent[ ] > object{ } > geographicExtent[ ] > object{ } > boundingBox{ } > unitsOfAltitude

[timothypage]

@dwalt I'm able to get unitsOfAltitude to import with the following CSDGM

both "minimumAltitude" and "maximumAltitude" are required to be present on writing mdJson to CSDGM, but it doesn't look like the reverse is true, it will just throw a warning

boundingBox-alititude.xml.zip

[timothypage]

I didn't see any altitude stuff in mdEditor, so crafted the above xml by hand

[dwalt]

@timothypage mdEditor does not support Bounding Box Altitude, but mdJSON does: schema{ } > metadata{ } > resourceInfo{ } > extent[ ] > object{ } > geographicExtent[ ] > object{ } > boundingBox{ } > unitsOfAltitude

In this example, a CSDGM file containing Altitude was imported into mdJSON. The altitude unit tags do not appear in the mdJSON file, even though altitude min, max and units existed in the source file.

[timothypage]

@dwalt ahhhh, it's altunit in the fgdc reader, changing to altunits

[dwalt]

Still not working. Tag is now writing, but data still null.

"boundingBox": { "westLongitude": -148.87, "eastLongitude": -148.35, "southLatitude": 63.95, "northLatitude": 64.24, "minimumAltitude": 20, "maximumAltitude": 40, "unitsOfAltitude": "" },

[timothypage]

@dwalt I can't seem to find any csdgm records that have spdom/bounding/boundalt defined, I suppose if we had one that would be the definitive test 😄

I incorrectly created the above boundingBox-alititude.xml.zip based on the code with altunit but the standard says altunits, which I think is the origin of the issue.

This one should be implemented correctly: boundingBox-alititude 2.xml.zip

[hmaier-fws]

closed by #250