Dane Springmeyer

@artemp to prepare for @davidtheclark testing this I tried node-mapnik master with latest mapnik master but I'm seeing: ``` 624 passing (7s) 1 pending 3 failing 1) mapnik.Feature should output...

@davidtheclark: quick update: @artemp and I worked today to get the latest Mapnik core version (needed for his fix for you) working against latest node-mapnik. Still a few things needed...

@davidtheclark - dug into this issue just now. There is some other bug lurking so it is not as simple as updating the Mapnik core version like I thought (which...

@artemp as part of testing this (https://gist.github.com/springmeyer/5f9ad5831402587c258116f1e627895c) I also noticed that: ``` "data": { "foo": "bar" } ``` Is round tripping as `"data":"{foo:\"bar\"}"` in mapnik v3.0.12 but `"data":"{\"foo\":\"bar\"}"` in mapnik...

@davidtheclark In my mind what still stands here is the problem of null reporting. Mapnik creates (as it parses features) a "context". This "context" is a map of every property...

Can you explain a little more about your use-case? How exactly will unioned water geometries help you/how are they a problem right now? Supporting working with vector tile geometries in...

Thinking out loud: As far as the `brew install` I'm thinking that I'll provide a pull request to homebrew to make the homebrew package build against gdal, postgis, and cairo...

Yes, it did. And before the 2.0.0 release all parameters were made to use consistent dashes (instead of underscores), so its now `font-directory`, and it can be passed a directory...

Yes, a bug in the bindings resulting from the oddity of this parameter. Basically, `font-directory` only matters at the time the xml is loaded so it did not make sense...

hmm, forgot that I actually did away with this support (https://github.com/mapnik/mapnik/commit/ea5a46f2302e7706149c2bef91dc48d06163e71c#diff-bc721da090a4fdd48972b8aad7f14ec8). So, `font-directory` is not able to be round tripped and there is no way to add it via python.