[gdal-dev] Time for a new GeoJSON driver?

[Sean Gillies]

Hi all,

The GeoJSON WG's draft-ietf-geojson,
https://datatracker.ietf.org/doc/draft-ietf-geojson/, is in the RFC Editor
queue and will be published soon. I'm considering whether adoption of the
updated GeoJSON (registered media type: application/geo+json) and support
for the older GeoJSON format (no registered media type) might be helped by
creating an entirely new driver.

A separate driver would keep the existing driver from becoming even more
complicated, yes? We would also have an opportunity to remove unnecessary
configuration options and support for other JSON formats that aren't really
GeoJSON.

Does anyone feel that the existing driver code *would not* be a good place
to start and that we shouldn't arrive at a new driver by copying the
existing GeoJSON driver and removing unneeded code?

What to call the new driver is another question. "geo+json" or "RFCxxxx"
(number yet to be determined) seem like good candidates to me.

-- 
Sean Gillies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20160725/7006064f/attachment.html>