-
-
Notifications
You must be signed in to change notification settings - Fork 82
Migrate POI kind and kindDetail assigment from plain Java to MultiExpression rules #537
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
Migrate POI kind and kindDetail assigment from plain Java to MultiExpression rules #537
Conversation
…some kind=other slipping through
wipfli
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this pull request. At first sight it looks good. Do you also plan to move the minZoom to the MultiExpressions?
| Expression.or( | ||
| with("landuse", "forest"), | ||
| Expression.and(with("boundary", "national_park"), with_operator_usfs), | ||
| Expression.and( | ||
| with("boundary", "national_park"), | ||
| with("protect_class", "6"), | ||
| with("protection_title", "National Forest") | ||
| ), | ||
| Expression.and( | ||
| with("boundary", "protected_area"), | ||
| with("protect_class", "6"), | ||
| with_operator_usfs | ||
| ) | ||
| ), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not though about this use case for the with function. But if it works I guess it is very convenient! cc @msbarry
Yes, I have a followup PR in the works for zooms but it’s much larger so I wanted to be sure that the basic ideas in this one are correct before proposing it. |
|



Migrate from plain Java conditionals to MultiExpression rules when applying POI
kindandkindDetail. Removes some dense logic fromprocessOsm(), passes all existing tests with no changes required.