Closed philipbelesky closed 3 years ago
Note: this also provides a defacto means to search for matches with an AND
style query rather than an OR
style query. E.g. searching for items with operator=yarra-trams
and railway=station
might be desirable, but if those were provided as the feature input parameter it would return items with either tag.
Upcoming in 0.13.0
Often you would want to do further filtering upon the data extracted from the Nodes/Ways/Buildings components. This might include filtering based on more precise metadata that is not in the defined features/subfeatures list. It also might include filtering by particular metadata ranges, e.g.
surface
isasphalt
orconcrete;
maxspeed<=
50`. This can be achieved with standard Grasshopper components, per the examples file, but is cumbersome.A dedicated component could also provide better affordances, such as providing a Selection-Component-like UI to list all possible metadata that could be the basis of further filtering.