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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: jrreid[at]ucalgary.ca [Submitted to the original trac issue database at 4.05pm, Saturday, 29th September 2007]
If you select a node that has more then 4 tags on it, when you select anything else, or simply deselect it, some of the values stay in place. This arises for GNS imported data, and some TIGER imports as well (see around 49.057244186871834, -111.94035878865704 for example, the placename POI is GNS, the motorway is from tiger)
The text was updated successfully, but these errors were encountered:
Author: richard[at]systemeD.net [Added to the original trac issue at 4.47pm, Thursday, 4th October 2007]
The issue isn't with 12+ tags, it's actually a known bug with any tag containing a colon.
A proper resolution to this requires completely rewriting the tag editing code (planned for a future Potlatch) but there should be a workaround in Potlatch 0.4.
Reporter: jrreid[at]ucalgary.ca
[Submitted to the original trac issue database at 4.05pm, Saturday, 29th September 2007]
If you select a node that has more then 4 tags on it, when you select anything else, or simply deselect it, some of the values stay in place. This arises for GNS imported data, and some TIGER imports as well (see around 49.057244186871834, -111.94035878865704 for example, the placename POI is GNS, the motorway is from tiger)
The text was updated successfully, but these errors were encountered: