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
This public comment is respectfully submitted by the Web Service Technical Panel (WSTP) of the Defence Geospatial Information Working Group (DGIWG). This comment is specifically directed toward 23-000 OGC SENSORML ENCODING STANDARD. GeoJSON is not mentioned at all in this document. Given the significant relationship of GeoJSON with other current, relevant, and emerging OGC standards, it may prove valuable to clearly define the relationship of this standard with GeoJSON or explain the rationale for a lack thereof.
The text was updated successfully, but these errors were encountered:
Will add GeoJSON to the list of Normative references.
Maybe also clarify somewhere that GeoJSON is an option for providing sensor position and deployment geometry.
Maybe add a note in the JSON encoding req class to say that a SensorML Process/System is NOT a GeoJSON feature because GeoJSON implementations don't deal well with complex nested structures.
This public comment is respectfully submitted by the Web Service Technical Panel (WSTP) of the Defence Geospatial Information Working Group (DGIWG). This comment is specifically directed toward 23-000 OGC SENSORML ENCODING STANDARD. GeoJSON is not mentioned at all in this document. Given the significant relationship of GeoJSON with other current, relevant, and emerging OGC standards, it may prove valuable to clearly define the relationship of this standard with GeoJSON or explain the rationale for a lack thereof.
The text was updated successfully, but these errors were encountered: