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

mapcss2osmose: support for multi-element rules (parent selectors and such) #2425

Open
Famlam opened this issue Dec 28, 2024 · 2 comments
Open

Comments

@Famlam
Copy link
Collaborator

Famlam commented Dec 28, 2024

Currently our mapcss only supports "single element"-rules. Rules with e.g. parent/child/link selectors (e.g. way[x] > node[y]), containment selectors (e.g. node[x] ∈ area[y]), connection pseudo-classes (e.g. :unconnected) or parent/child-expressions (e.g. parent_tag(...)) are all ignored at the moment.

It would be great to also support them in Osmose. Most likely this'll have to be via SQL queries.

The biggest challenges I'd expect:

  • efficiency
  • connection with class selectors (which may also be shared with single-element rules, e.g.
node[some_selector] {set x;}
way[z] > node!.x {throwWarning: "X";}

Just filing this issue to also have it on the issue tracker.

@frodrigo
Copy link
Member

I already have a partial implementation of that some where...

@frodrigo
Copy link
Member

I already have a partial implementation of that some where...

I found it in /home/fred/osmose-backend/mapcss/mapcss2osmose-osmosis.py on osm110

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants