Some of our partners include a properties field inside the geometry object. This seems to be OK GeoJSON spec-wise, but seems to break at least two Java parsing libraries (sigh). Add a function that cleans up GeoJSON on the "edges" of Peripleo, so that we only ingest GeoJSON where the geometry object has only the two mandatory fields type and coordinates.
Some of our partners include a properties field inside the geometry object. This seems to be OK GeoJSON spec-wise, but seems to break at least two Java parsing libraries (sigh). Add a function that cleans up GeoJSON on the "edges" of Peripleo, so that we only ingest GeoJSON where the geometry object has only the two mandatory fields
typeandcoordinates.