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
On a call with CoST West Lombok (notes in CRM-7083#note-15) they asked for examples of how to represent different geometry types in locations/geometry.
The worked example in the OC4IDS documentation contains only a Point geometry, so I showed the LineString example in the Location extension documentation, but this caused some confusion due to being nested under tender.
Since location data is important for infrastructure projects and since the GeoJSON docs don't provide examples, we should add examples of at least LineString and Polygon to the OC4IDS worked example.
The text was updated successfully, but these errors were encountered:
On a call with CoST West Lombok (notes in CRM-7083#note-15) they asked for examples of how to represent different geometry types in
locations/geometry
.The worked example in the OC4IDS documentation contains only a
Point
geometry, so I showed theLineString
example in the Location extension documentation, but this caused some confusion due to being nested undertender
.Since location data is important for infrastructure projects and since the GeoJSON docs don't provide examples, we should add examples of at least
LineString
andPolygon
to the OC4IDS worked example.The text was updated successfully, but these errors were encountered: