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
The base property is oddly named as a reference to a 3D model. Could that be something like model?
However, it is not clear how referencing a 3D model is within scope of this Moving Features API.
Could a separate API or conformance class perhaps add this capability?
The ability to reference 3D models from point geometry is also something being considered for OGC API - 3D GeoVolumes, with a /models/{modelId} end-point, where the content-type can be negotiated using an Accept: header, rather than being available in a single format (OGC API Web Guideline Principle 9).
The text was updated successfully, but these errors were encountered:
The
base
property is oddly named as a reference to a 3D model. Could that be something likemodel
?However, it is not clear how referencing a 3D model is within scope of this Moving Features API.
Could a separate API or conformance class perhaps add this capability?
The ability to reference 3D models from point geometry is also something being considered for OGC API - 3D GeoVolumes, with a
/models/{modelId}
end-point, where the content-type can be negotiated using anAccept:
header, rather than being available in a single format (OGC API Web Guideline Principle 9).The text was updated successfully, but these errors were encountered: