-
-
Notifications
You must be signed in to change notification settings - Fork 65
handler_for_filtered not behaving as expected. #293
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
Comments
This is intended behaviour. The FileProcessor will initially forward every single object it encounters in the file to the body of the for loop. When you add a filter, then some objects are dropped. The If you know that you are only interested in ways and nodes, use an EntityFilter to filter out relations right away:
|
So my use case is that I want to modify a file, but I only care about modifying ways & nodes, and just want to pass through relations. With your last example will adding a |
Please read the code I provided. |
Ok - I see now, I was getting confused about what was being filtered in vs being filtered out. Thanks. |
If I have code like the following:
I would have expected that the relations would just get passed through to the output via the
handler_for_filtered
method, however this is not the case. I need to add something with a filter that filters everything in order to get them to show, like:This feels unexpected - is this a bug, or intended, or am I just missing passing a parameter somewhere? If intended is it possible to configure this behavior, so you don't need to add spurious filters?
The text was updated successfully, but these errors were encountered: