search

usdot-jpo-ode / wzdx

The Work Zone Data Exchange (WZDx) Specification aims to make harmonized work zone data provided by infrastructure owners and operators (IOOs) available for third party use, making travel on public roads safer and more efficient through ubiquitous access to data on work zone activity.
Creative Commons Zero v1.0 Universal
92 stars 62 forks source link

Allow GeoJSON Bounding Box on the WZDxFeed and RoadEventFeature objects #142

Closed j-d-b closed 3 years ago

j-d-b commented 3 years ago

Background

From the GeoJSON specification section 5:

A GeoJSON object MAY have a member named "bbox" to include information on the coordinate range for its Geometries, Features, or FeatureCollections.... The "bbox" values define shapes with edges that follow lines of constant longitude, latitude, and elevation.

Currently, the WZDx schema defines custom FeatureCollection (WZDxFeed) and Feature (RoadEventFeature) objects which are instances of the GeoJSON versions, but more restricted. They do not currently allow for the GeoJSON bbox property.

However, the geometry of a road event references the GeoJSON MultiPoint and LineString geometries for structure and thus bbox is allowed there.

Proposed solution

Adding the optional bbox property to the WZDxFeed and RoadEventFeature would be a simple, backwards compatible change that would allow producers to specify a bounding box if desired and keeps WZDx closer to GeoJSON. This provides consistency with being able to provide it at the geometry level.

DeraldDudley commented 3 years ago

+1

j-d-b commented 3 years ago

Addressed in #145.