Artem Pavlenko
Artem Pavlenko
@mathisloge - font installation to match expected layout e.g fonts in `/mapnik-install-dir/lib/mapnik/fonts/`
Add support for c++20 Currently fails due to http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1423r2.html
Currently we support `not [field] is {val}` but we don't support `[field] is not {val}`. As we added support for `is null` (#794) this grows in utility.
While digging into compiler warnings I noticed we're still using mapnik-vector-tile 2.2.1 in https://github.com/mapnik/node-mapnik/blob/master/package.json#L39 Latest master has some important fixes and builds cleanly (no warnings) for me, shouldn't we upgrade?...
```c++ #define TOSTR(obj) (*v8::String::Utf8Value((obj)->ToString())) ``` Would it make sense to not always create `std::string` from `char const*`? For example ```c++ p.parse(TOSTR(info[0]); ``` ^ this call can be expensive as `info[0]`...
Good bindings should strive to expose as much of the underlying library functionality as reasonable. This issue is to track progress adding missing properties and methods available in https://github.com/mapnik/mapnik ###...
When built in `Release` mode `import mapnik` is causing a segfault (Ubuntu 22.04 + clang 14). `Debug` build is OK.
when I run python demo, an error like that: File "rundemo.py", line 58, in provpoly_lyr.datasource = mapnik.Shapefile(file=path.join(root,'../data/boundaries'), encoding='latin1') File "/usr/local/lib/python2.7/dist-packages/mapnik-0.1-py2.7-linux-x86_64.egg/mapnik/init.py", line 370, in Shapefile return CreateDatasource(keywords) TypeError: No to_python (by-value)...
ref https://github.com/mapnik/mapnik/issue/4045
We should have something like ```python im=mapnik.Image(256,256) im(0,0)=mapnik.Color("red").packed() ``` or ```python im[0,0]=mapnik.Color("red").packed() ```