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
Describe the bug
The Mapeo Territory fork of iD editor utilizes generic geometry point/line/area presets, as a fallback for when configurations change and a category is no longer available.
Solution:
Hide these presets by hiding their unique class identifiers preset-point preset-line preset-area using CSS. Doing so will accomplish two things:
The generic geometry presets are no longer available as a category option for mapping when creating a feature.
If a feature does get reclassified into one of the generic geometry presets as a fallback due to the original category no longer being available in the config, the generic presets will not be available in the list when changing the category. This forces a user to reclassify the data using only available categories in the config, which is a desirable behavior.
The text was updated successfully, but these errors were encountered:
Describe the bug
The Mapeo Territory fork of iD editor utilizes generic geometry point/line/area presets, as a fallback for when configurations change and a category is no longer available.
Issue originally raised : https://www.notion.so/digidem/Hiding-generic-geometry-presets-in-Territory-74f3c6784f2c459ea3376e4e6699f05d#7820d5d2c7994eff9f8a242c82ae8a72
All details : https://www.notion.so/digidem/Hiding-generic-geometry-presets-in-Territory-74f3c6784f2c459ea3376e4e6699f05d
Solution:
Hide these presets by hiding their unique class identifiers preset-point preset-line preset-area using CSS. Doing so will accomplish two things:
The generic geometry presets are no longer available as a category option for mapping when creating a feature.
If a feature does get reclassified into one of the generic geometry presets as a fallback due to the original category no longer being available in the config, the generic presets will not be available in the list when changing the category. This forces a user to reclassify the data using only available categories in the config, which is a desirable behavior.
The text was updated successfully, but these errors were encountered: