Conversation
There was a problem hiding this comment.
It builds and it works - I can't complain!
A couple of interesting things though.
- Compared to the binary you sent yesterday, this takes almost twice as long to build the same maps. The binary yesterday completely maxed out my CPU, this newer build doesn't.
- Compared to the binary from yesterday, the output is different with the same input map. I realise there are some changes to bring more tags in to the output (so would expect changes to the metadata files). But there are many changes to the reference and geometry files too. Is this because of the changes to the road classes that are being processed?
Is there any motivation to try and update the dependencies to more recent ones? Since this is just a one-off building process for the maps, I'd say no as we don't need it to be super optimised and up to date.
This is likely because of the xmx parameter (java max heap size) and I put the default to 2G.
I made two PRs, here is the one that did some changes to the processing. I can merge this and rebase the other PR and if you are then able to check if we get same results? |
|
Also notice that in the last 'force-push' I unified the behaviour of |
Local
Build
Generate tiles
Docker
Build
Generate tiles