Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate LineStrings for railways in default OpenMapTiles config ? #773

Open
laem opened this issue Oct 28, 2024 · 2 comments
Open

Duplicate LineStrings for railways in default OpenMapTiles config ? #773

laem opened this issue Oct 28, 2024 · 2 comments

Comments

@laem
Copy link
Contributor

laem commented Oct 28, 2024

Hi, it looks to me like this line is the culprit that produces duplicate shapes for railways (train, tram, subway) in my output tiles.

Layer("transportation", false)

Per the doc,

Layer(layer_name, is_area): write this node/way to the named layer. This is how you put objects in your vector tile. is_area (true/false) specifies whether a way should be treated as an area, or just as a linestring.

This way will be added twice, once with this Layer invocation, another time with the write_to_transportation_layer. The first one will be a LineString with no class that I highlighted in this capture as red thick lines.

image

When I inspect my tiles, this is what I get :

image

The top object in the popup is just an no-tag version of the objects below, I believe.

Can someone confirm that the issue is in the default process.lua ? I couldn't find another online .pmtiles file produced with the default process to compare.

I'm using a modified version of these settings in my project https://github.com/laem/gtfs/blob/master/tilemaker/resources/process-openmaptiles.lua.

@systemed
Copy link
Owner

Yes, I think you're right - it looks like that line has been erroneously left in after the code was refactored to include write_to_transportation_layer. If you delete that line it should fix it, I think.

laem added a commit to laem/tilemaker that referenced this issue Oct 28, 2024
Remove duplicate untagged railway lines, see systemed#773
@laem
Copy link
Contributor Author

laem commented Oct 28, 2024

it looks like that line has been erroneously left in after the code was refactored to include write_to_transportation_layer

Yes, that was my guess. Looks fixed without any side effect. PR proposed

systemed pushed a commit that referenced this issue Oct 28, 2024
Remove duplicate untagged railway lines, see #773
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants