Jiri Drbalek

Results 97 comments of Jiri Drbalek

> isn't this the same as increasing chunk size I must say that I'm not sure. > Since chunks are instantly sent down the wire when the callback is called...

> what's that mean? That probably means you have older version of Harfbuzz than 1.0.5, but your Mapnik was compiled against Harfbuzz of version at least 1.0.5, [see this](https://github.com/mapnik/mapnik/blob/9e58c890430db6f0b6f1f7a1690877c9d913d92a/include/mapnik/text/harfbuzz_shaper.hpp#L199-L203) or...

Where do you have boost-python libs installed? I don't have OS X, but on Debian, for example, I see these files: ```console $ ls -1 /usr/lib/x86_64-linux-gnu/libboost_python* /usr/lib/x86_64-linux-gnu/libboost_python.a /usr/lib/x86_64-linux-gnu/libboost_python-py27.a /usr/lib/x86_64-linux-gnu/libboost_python-py27.so /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.62.0...

There is `features=true` parameter of `encode` method which should encode additional info into the grid JSON, [see](https://github.com/mapnik/python-mapnik/blob/faf53cde1a6023b8c22e801bd0b7978a5e1ea90e/src/mapnik_grid.cpp#L77). This might be helpful.

> But that's a boolean. How do I set the data? The data should be already collected [in the grid object](https://github.com/mapnik/mapnik/blob/f13848e2108c4863da2adb243284392a3a157885/include/mapnik/grid/grid.hpp#L69). You will not get layer index or name directly,...

Can you please try to set `export BOOST_PYTHON_LIB=boost_python` before build with mason?

> Should that possibly be documented in the readme? Shall I make a PR? I think this is a bug in setup.py in the first place, but some general advice...

I think those `limit 0` queries in the log are fine. Their purpose is to collect some metadata during initialization. See [here](https://github.com/mapnik/mapnik/blob/1d06afeea2370b29f130c93be406197e4cacb689/plugins/input/postgis/postgis_datasource.cpp#L353).

Are you building python-mapnik from Master? You need [v3.0.x](https://github.com/mapnik/python-mapnik/tree/v3.0.x) branch to build against mapnik 3.0.17.

Maybe try to build python-mapnik from [v3.0.x](https://github.com/mapnik/python-mapnik/tree/v3.0.x) branch. This branch keeps compatibility with 3.0.x versions of Mapnik.