Dane Springmeyer

> In which case, I think the best way forward is for an official mapnik release. Having a release means we can update mapnik-reference, and move over to node-mapnik 4.x...

If a key exists inside the `Feature.properties` object named `id` Mapnik respects it and round-trips it correctly. If a property named `id` exists at `Feature.id` then Mapnik ignores this, like...

@davidtheclark btw, you can play around with the Mapnik behavior with a script like: ``` var mapnik = require('mapnik'); var expected = { type: "Feature", id: "will be ignored", properties:...

Yes, and good call on +async too.

:-1: on adding SRID info the the WKB. We should not support EWKB - only supporting WKB output I think is fine. If programs want WKB (like PostGIS) then adding...

/cc @artemp can you take a look at this?

note while the `grid_renderer` in Mapnik is available in C++ the actual encoding to json with utf8 characters is currently done in python/node.js and still needs a pure C++ api:...

> The ticket is still open - has all the code landed in Mapnik 3.0.0, or is it planned for 3.1? @pnorman Yes the code has landed. The ticket is...

Interested in providing a patch for this? If so trying to get more to the bottom of #213 would be good - I tend to not recommend people use regex...

> Has any thought been given to what the syntax for creating this structure would look like in carto? Not that I am aware, so I'm you are planning on...