Properties of GeometryCollection children not being added to Polygons about geojson-google-maps HOT 6 CLOSED

But GeoJSON geometry objects don't need a properties member do they? Are you thinking of a Feature?

from geojson-google-maps.

Looks like this might be a "feature" of TopoJSON, which doesn't support GeoJSON features. The topojson.object function attaches properties to GeoJSON geometry objects.

For context, as a proof of concept, I'm generating GeoJSON from Esri Shapefiles (Natural Earth) using GDAL, converting the GeoJSON to TopoJSON for serving, converting back to GeoJSON in the browser, and using GeoJSON.js to generate the google.maps.Polygons for rendering.

Perhaps better to fork for this use case?

from geojson-google-maps.

Interesting. I'd be interested in seeing the exact files you're working with. Can you easily set up something reproducible with JSFiddle or something like http://bl.ocks.org/4554134 ?

from geojson-google-maps.

Code at:
https://github.com/saxman/google_maps/tree/master/natural_earth

If you take a look at the ne_10m_admin_0_countries.topojson.js file, you can see the properties in the GeometryCollection.

More context on why topojson does this:
topojson/topojson#7

from geojson-google-maps.

Yeah, I guess I just have reservations about honoring something that's not in the GeoJSON spec here. If we start checking for a properties member of a geometry, what's keeping us from honoring any other random key value pairs in a geometry?

from geojson-google-maps.

Or maybe I'm not looking at things correctly and topojson/topojson#7 puts these properties in a proper Feature and not the geometry.

from geojson-google-maps.