search

Geonovum / uml2json

Best Practise for OGC - UML to JSON Encoding Rules
https://geonovum.github.io/uml2json/document.html
0 stars 1 forks source link

Comparison with INSPIRE requirements for JSON encoding #49

Closed PB-GNM closed 4 months ago

PB-GNM commented 1 year ago

I have compared the document describing the outcome of Action 2017.2 on alternative encodings for INSPIRE data with the document as set up in this repository.

The only significant difference that I found was with basic types Measures and Length and how to deal with unit of measurement.

INSPIRE requires Measures and Lenght to be converted to doubles. Secondly it requires to add a property named x with an unit of measurement to be mapped to an extra property with the name x.uom.

The UML2JSON document as setup in this repository gives 2 options: option 1: It stays or becomes a Measure object with “value” (number) and “uom” (string) as properties and option 2: use keyword "unit" like "type" to describe the property.

jechterhoff commented 4 months ago

@PB-GNM and @PalmJanssen: This issue looks more like a statement of fact, and not an actual issue. Can we close it?

PalmJanssen commented 4 months ago

This document is based on and extends the results of OGC Engineering report UGAS-2020 regarding JSON Schema encoding rules. This is someting else then the Inspire UML-to-GeoJSON document developed in the Inspire context.

Both documents have more differences then mentioned. In general the UGAS and the evolved UML to JSON doc is more detailed and profound and aligned with OGC Api Features and of cource includes also JSON-FG.

The differences are considered as noted and are not part of the requirements set for this document.