Richard Fairhurst

Ok. The .proto contains `lats` and `lons` - https://github.com/systemed/tilemaker/blob/master/include/osmformat.proto#L203 - so if `protoc` is compiling the .proto correctly, `lats_size` should be in there. I wonder if maybe you have an...

Did you get this resolved, @Nakaner?

Yep. The current approach (v2.1 onwards) taken by the OMT-compatible schema is that tilemaker notes which ways are members of boundary relations (`type=boundary, boundary=administrative`) using `relation_scan_function`. It then writes out...

Could be reprojection artefacts, or a difference in validity tests between JTS/GEOS (as used by QGIS) and Boost.Geometry (as used by tilemaker). They're only warnings - you can safely ignore...

Thanks. I'm not going to have a chance to look at this immediately but that's helpful.

There have been a few changes recently that might fix this - I haven't tried it out with this dataset but you might want to have a look.

(In particular, the Boost version might be relevant here.)

I don't know the first thing about Docker, I'm afraid. Leaving this open in case anyone does.

This is really informative: thank you. I'd be interested to hear what ideas people have for reducing memory consumption. Two I've thought of: - [x] Use an attribute dictionary across...

No reason not to use mmap or perhaps stxxl as an option, it's just not something that I've implemented. But I'd very happily receive a pull request as long as...