Thanks you for the confirmation about GeoJSON import, does it support export too? Do I understand that the API and UI Import/Export yet have to fully support the import/export?
SQL only feature now?
GeoJSON is now a IETF RFC: https://tools.ietf.org/html/rfc7946.
We are using it mainly as a part of a workflow where GeoJSON is both imported and exported.
We use Leaflet as a UI frontend and SQL Spatial 2016, Azure DocumentDB and MongoDB (AWS) as backend, all which can store and index JSON readily.
We also use OSRM for routing, which is producing millions of routes daily, OSRM only communicates via JSON REST services.
The whole Hadoop ecosystem also support JSON very well, we will grow into that moving forward when we get into millions/billions of individual JSON objects.
GeoJSON pretty much dominate the web mapping and have taken over from KML as the 'standard' interchange format as it's much more versatile and extensible.
TopoJSON is not a direct extension of GeoJSON, if you drop the topology information, you have a hard time to restore the actual data. If I understand it correctly the TopoJSON actually translate the geographical coordinates to edge/arc references + local transformation and scaling. I don't think that if you treat is as GeoJSON the result will come out as intended, it requires quite alot of logic to reconstitute the original geographical shapes. https://github.com/topojson/topojson/wiki/Introduction
TopoJSON is to GeoJSON what E00 is to SHP.
It is also a very good data transfer format as it's around 4x smaller as each edge/node is only saved once and referenced by any polygon sharing the edge/node.
As Tjhb said, import/ingest a webservice would be a great feature where GeoJSON could be supported, for ESRI, Mapbox and OSM/QGIS/GDAL users like us. Making it easy for us to expose as a webservice would be excellent, maybe that's a feature for Manifold9 IMS...
Not sure if Radian support streamed import and export, that would be an excellent future capability, when I can use Radian as a processing engine in my workflows, to act like as CEP or ETL: Informatica/FME/SSIS/Flume/Spark is used today. The world of data is moving more to streaming data, with IOT and mobile devices driving the data collection. Most of our project data is from such sources, and by saving and importing/exporting from disk based files we lose agility and performance.
I would prioritize GeoJSON before TopoJSON as it's more widely used, but the benefits of TopoJSON is undeniable.
For now I use OGR/QGIS for all import/export of GeoJSON/TopoJSON files, but as I think they will be even more important as key formats in the Big Data world, I would hope Manifold add them both as first class import as well as export formats in UI and API.