Dane Springmeyer

In my experience the most useful and easy thing to do is to turn on logging at the database level.

Hi @craigds - right, I think the statically compiled GDAL linked into the plug-in is likely the limitation. My understanding is that VSI needs curl and linking curl statically would...

try checking out the 'win-binary' branch of buffertools at https://github.com/springmeyer/node-buffertools. If that works for you I will check with @bnoordhuis about creating a pull request with the gyp file and...

@toddharrison - #23 added a new, better approach for windows. So, ideally you could build yourself following the new instructions: https://github.com/TooTallNate/node-buffertools/commit/914f50676083debd1f02955fa4196e451949cb4c

@toddharrison - as a stopgap you could due `npm install ldapjs --force` and then manually place the `https://github.com/springmeyer/node-buffertools/tree/win-binary` into your node_modules folder.

I also rarely use Windows. I only use it to package http://tilemill.com. But, I've pushed a new windows binary of node-buffertools to my branch at https://github.com/springmeyer/node-buffertools/tree/win-binary. I also removed the...

@igorpupkinable - that looks fine. The `C++ exception` warnings would be a problem if node-buffertools was using C++ exceptions, but it is not.

@nebulon42 - that is great you are interested in working on the group-symbolizer support. Also, with further thought I agree that it likely makes sense to land in mapnik-reference first....

👍 @talaj - Agree that anything in Mapnik should be visible in `mapnik-reference` irregardless of its binding in `carto`

note the `placement-type` parameter also applies to the shield symbolizer and was added in ec739c8709c92438013235a94627fe7be0d5be61. But, the `list` type is still held back because we do not currently have a...