Coordinate System Axis: `rangeMeaning` is not getting extracted, `maxValue` and `minValue` may or may not be

[strogonoff]

• rangeMeaning can be “exact” or “wraparound”, if maxValue and minValue are present
• maxValue and minValue can be missing (null), but need to check they are migrated if they exist
• extract maxValue and minValue as strings

[stefanomunarini]

None of the entries in https://geodetic.isotc211.org/register/geodetic/CoordinateSystemAxis shows data for rangeMeaning, maxValue and minValue. The database dump also does not have any data for those fields (see image below).

Is this an actual issue?

[stefanomunarini]

@strogonoff forgot to mention this while on the call with Mike, but maybe you had the chance on the call on Monday, or has anything been mentioned about it?

[stefanomunarini]

I have included rangeMeaning as a required property (https://github.com/isogr/register-system-transition/pull/24/files and https://github.com/isogr/registry/pull/21/files)

As for now, all of the coordinate-sys-axis entries do not contain a minValue, maxValue or rangeMeaning (as for https://github.com/isogr/register-system-transition/issues/14#issuecomment-1884773426), thus all those fields values are None.

[strogonoff]

Thank you. I think this is not a priority for the time being.

[strogonoff]

For transition period, we’ll focus on issues assigned to milestones…

[stefanomunarini]

@ribose-jeffreylau I'm not sure if you closed this by mistake? Relevant PR is still open .

[ribose-jeffreylau]

@stefanomunarini Apologies, yes I did close it by mistake :p

Thanks for spotting it... otherwise it would have gone unnoticed!

[stefanomunarini]

Merged relevant PR. Closing this