I'm interested in understanding the relative merits of using GeoJSON or shapefile formats for handling geo-spatial data, particularly in an open-source, Python (CKAN project), web-development context.

GeoJSON is well supported in the CKAN data management python project (through Open Layers), but our clients seem to work with shapefiles. I'm trying to understand whether I should just ask clients to run their shapefiles through a simple GeoJSON convertor (perhaps even implement this myself upon file upload), or whether there is a good reason to keep their data stored in shpaefile format.

Struggling to find a decent technical comparison of the file formats. Anyone care to break it down for me?

closed as primarily opinion-based by Vince, Ian Turton Aug 13 at 16:06

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.