You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, iD has a mechanism for matching a feature to one and only one preset. It's straightforward for new contributors to add new presets since they are easily defined in JSON.
However, a single preset does not fully define a feature. Features can be sorted into multiple "groups" based on their tags and geometry. iD now defines these variously in code, for example:
Toggle-able Map Data layers
Routable features
Implied one-way features
We should move these to JSON files as part of #6483 and #5326.
Each group can have rules that define what features to include and qualities that specify what the features have in common. iD can then match each feature into a number of groups and adjust behaviors based on them.
The text was updated successfully, but these errors were encountered:
Currently, iD has a mechanism for matching a feature to one and only one preset. It's straightforward for new contributors to add new presets since they are easily defined in JSON.
However, a single preset does not fully define a feature. Features can be sorted into multiple "groups" based on their tags and geometry. iD now defines these variously in code, for example:
We should move these to JSON files as part of #6483 and #5326.
Each group can have
rules
that define what features to include andqualities
that specify what the features have in common. iD can then match each feature into a number of groups and adjust behaviors based on them.The text was updated successfully, but these errors were encountered: