-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add scale and distance to spatial section #189
Comments
the parameter is already parsed on OWSLib Suggestion would be to introduce these in pygeometa (note that usually either scale or resolution is provided):
|
pvgenuchten
added a commit
to pvgenuchten/pygeometa
that referenced
this issue
Dec 20, 2022
resolves geopython#189
pvgenuchten
added a commit
to pvgenuchten/pygeometa
that referenced
this issue
Dec 20, 2022
resolves geopython#189
pvgenuchten
added a commit
to pvgenuchten/pygeometa
that referenced
this issue
Nov 9, 2023
resolves geopython#189
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
scale and/or distance (resolution) are 2 common fields in many iso19139 oriented metadata profiles, such as https://geonovum.github.io/Metadata-ISO19115/#resolutie. I suggest to include these properties in either the spatial or content section of pygeometa, and return them as part of the iso19139 generation in the relevant fields
identificationInfo[1]//spatialResolution//equivalentScale//denominator and identificationInfo[1]//spatialResolution/*/distance
The text was updated successfully, but these errors were encountered: