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

How to avoid duplicate processing of OSM object #730

Open
caerandir opened this issue Jul 6, 2024 · 0 comments
Open

How to avoid duplicate processing of OSM object #730

caerandir opened this issue Jul 6, 2024 · 0 comments

Comments

@caerandir
Copy link

First of all: Thanks for providing tilemaker! Very cool piece of software!

Is there a way to avoid that the same OSM object is processed twice because it matches more than one condition in node_keys and/or way_keys?

Here's an example - imagine node_keys = {"building", "amenity", "tourism=attraction", "man_made"}. Now there's an observation tower with a shop that sells ice cream, which in OSM has the keys man_made=tower, tourism=attraction, building=yes and amenity=ice_cream. It will now turn up four times for processing in node_function(), and I currently try to counter this by checking for such combinations, but I am wondering if there's a more elegant way. If not, I'd propose something where you could - like with the Id()-function that returns the OSM ID - have Id_processed() or Processed(Id()) which returns true or false if the object was already processed or added to a layer.

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

1 participant