search

opengeospatial / OGC-ISG-Sprint-Sep-2020

3 stars 5 forks source link

OGC API Features encoding #10

Open volkercoors opened 4 years ago

volkercoors commented 4 years ago

one limitation of OGC API Features is the supported encodings that are not suited for 3D. However, at the 3DPS SWG meeting last week, Josh pointed out that one of the encodings is mandatory and other encodings can be implemented instead. One idea for future work is to explore the path to extend OGC API Features with encodings as bounding volume hierarchies.

http://docs.opengeospatial.org/is/17-069r3/17-069r3.html

8 Requirements classes for encodings 8.1. Overview This clause specifies four pre-defined requirements classes for encodings to be used by a OGC API Features implementation. These encodings are commonly used encodings for spatial data on the web:

HTML GeoJSON Geography Markup Language (GML), Simple Features Profile, Level 0 Geography Markup Language (GML), Simple Features Profile, Level 2

None of these encodings are mandatory and an implementation of the Core requirements class may also implement none of them but implement another encoding instead.

jeffharrison commented 4 years ago

Interesting idea...

'One idea for future work is to explore the path to extend OGC API Features with encodings as bounding volume hierarchies'

Best Regards, Jeff