Curbs API raw data is not easily usable in GIS software.

[jacobmalleau]

Is your feature request related to a problem? Please describe.

When pulling Curb Zones/Spaces/Areas data files in json format, these files do not work on GIS software by default. They need to be adjusted so that they can be uploaded to these common tools.

Describe the solution you'd like

Either a better format or a publicly available conversion script users can have to use CDS more easily on GIS software.
This could be as simple as shifting the geometry attributes to above properties to match geojson format.

Is this a breaking change

• No, not breaking

Impacted Spec

For which spec is this feature being requested?

• Curbs

Describe alternatives you've considered

Additional context

Is this an issue with MDS as well? Curious how this has been resolved.

[gonzalo0512]

To expand on this issue: it mainly affects zones, areas, and spaces, which are the three CDS curbs files that contain geometries.

A straightforward way to make these files GIS-compatible is to lift the "geometry" attribute up one level, converting the JSON structure into a valid GeoJSON FeatureCollection. This is the approach we’ve been using at CurbIQ to open CDS curbs files directly in GIS software.

The resulting structure follows the standard GeoJSON format:

{
  "type": "Feature",
  "properties": [ ]  // other CDS attributes
  "geometry": [ ]   // feature coordinates
}

You can see an example of a GIS-compatible zones file here:

sample_zones_gis_compatible.zip