You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To our understanding, while OGC-API Features has been validated as an INSPIRE Download Service via the OAPIF Good Practice (GP) there is currently no way to validate JSON encoded data (GP on JSON encoding in INSPIRE, no validator).
Which would seem to imply that, to utilize OAPIF within INSPIRE, this API MUST provide GML encoded data is order to claim validity of the payload vis a vis the DataSpecifications
What does this mean pertaining to STA, as this standard only supports JSON encoding? The STA GP includes the mapping from the original GML model to STA encoded JSON, so to our reading, pertaining to STA the JSON encoding should be covered.
What's the official stance on this issue?
The text was updated successfully, but these errors were encountered:
To our understanding, while OGC-API Features has been validated as an INSPIRE Download Service via the OAPIF Good Practice (GP) there is currently no way to validate JSON encoded data (GP on JSON encoding in INSPIRE, no validator).
Which would seem to imply that, to utilize OAPIF within INSPIRE, this API MUST provide GML encoded data is order to claim validity of the payload vis a vis the DataSpecifications
What does this mean pertaining to STA, as this standard only supports JSON encoding? The STA GP includes the mapping from the original GML model to STA encoded JSON, so to our reading, pertaining to STA the JSON encoding should be covered.
What's the official stance on this issue?
The text was updated successfully, but these errors were encountered: