Open philam opened 3 years ago
Hi, philam,
Thank you for raising this issue and concern. We have made an instant analysis of the issue. We could see that in the area of Melbourne, we have 5,721 tram-highway crossings in total. A new tag that is introduced in 2020 is used in 99 cases. 119 cases were wrongly tagged (by the old tagging scheme).
As we are regularly using QA tools which include KeepRight, Osmose, etc. KeepRight reported such issues, and we tried to fix them most logically at that time. I can't tell you whether the new tag was completely introduced at that time.
However, my team produced 36 issues of 119. They were using an old tagging scheme.
Do you propose to fix all of these 119 issues by adding a new tag, or do you prefer to remove tags from the nodes completely?
Thank you once again, Nemanja
I've noticed a couple of changesets over the past year where Microsoft contributers are incorrectly tagging intersections between tram tracks and other ways around Melbourne.
For example, these ones on Wattletree Road in Malvern have been tagged as railway=level_crossing when this is not the case at all.
Changeset: https://www.openstreetmap.org/changeset/92228449
These intersections of on-road tram tracks (which is ~95% of Melbourne's tram network) with paths, roads, etc. do not require this tag.
There are a bunch of others that have been done around the city so I'd appreciate if Microsoft could check all that have been done on all railway=tram ways in all parts of Melbourne, thanks.