Jun 10, 2020, 23:17 by [hidden email]:
Reverted. _______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
In reply to this post by Jack Armstrong Dancer@sprynet.com
On Wed, Jun 10, 2020 at 1:55 PM Jack Armstrong <[hidden email]> wrote:
Reading the wiki page on one feature per OSM element, it starts off with Ideally, every OSM element or object should be tagged with only one main feature tag, to represent a single on-the-ground feature. I read this as there are exceptions. Unfortunately when this was written, sidewalks as separate ways weren't even thought of. However at the time of the writing of the wiki, level_crossings were. Looking at the discussion history, this issue never came up. Please note that I didn't go back to look at the mailing list conversation. Clearly level crossings tag would appear to violate the policy. I'm happy to read that ideally there should be one main feature tag to describe a feature but there are exceptions. I would suggest that the one feature per element page needs to include a couple of exceptions to the rule. Best, Clifford _______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
sent from a phone > On 10. Jun 2020, at 23:28, Clifford Snow <[hidden email]> wrote: > > I would suggest that the one feature per element page needs to include a couple of exceptions to the rule. the rule is mostly pointless, because it depends what you define as a feature. In the crossing example there is no infraction of the rule: there is one feature which is a pedestrian crossing (footway of type crossing) and there is a crossing node where a crossing footway crosses the highway way (different feature). Cheers Martin _______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
Jack - can you live with Martin's point? On Wed, Jun 10, 2020 at 2:36 PM Martin Koppenhoefer <[hidden email]> wrote:
_______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
In reply to this post by Clifford Snow
On Thu, 11 Jun 2020 at 06:30, Clifford Snow <[hidden email]> wrote:
(Not having a go at you, Clifford, just using your comment as an example! :-)) "Recently" (2019?), iD has also started pointing out / suggesting / demanding that all crossings (be they road - footway, driveway - footway, footway - footway / cycleway, road - road etc) eg https://www.openstreetmap.org/edit#map=19/-28.08457/153.44892 (if the "error" doesn't show, please click on either side of Second Avenue), also be marked as a crossing. When you go ahead & "fix" it, it inserts a highway=crossing at that point: https://www.openstreetmap.org/edit#map=21/-28.07834/153.44686. Good luck with telling them they're "wrong"!
Thanks Graeme _______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
Às 19:29 de 10/06/2020, Graeme
Fitzpatrick escreveu:
That's an obvious error. The ways must cross somewhere (that's what the warning states) , but it doesn't tell you to add a crossing. _______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
In reply to this post by Clifford Snow
On Wed, 10 Jun 2020 at 14:27, Clifford Snow <[hidden email]> wrote:
> To help me understand, below are three schemes for crossings. Which one(s) best describe your suggested way of mapping. > > ... > 2. With no crossing ways, just a node on the highway to mark the type of crossing https://mycloud.snowandsnow.us/index.php/s/4ad5wLzMNcE3sNo Mateusz has already pointed this out, but just to reinforce, this scheme would break pedestrian routing and require a wholesale rewrite of all routers to be able to jump between nearby ways. An analogy would be having a break in a minor road where it intersects the roadway of a major road. --Jarek _______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
Jun 11, 2020, 01:10 by [hidden email]:
And that rewrite would introduce unfixable routing bugs in cases where nearby footways are not allowing pedestrain movement. Also, that rewrite would be quite hard to implement without cratering performance.
_______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
In reply to this post by Jack Armstrong Dancer@sprynet.com
From: Clifford Snow Actually, I'm very flexible with just about anything. My only goal in bringing this up was to clean up the wiki page so that mappers have clear guidance. The way the wiki was written seemed confusing. After I brought up the subject I learned about the sidewalk proposal from 2011 and it seemed the proposal and the wiki were clearly at odds. I don't feel strongly either way about it. Again, I'd just like to see the proposal, the wiki and the OSM community agree on something that mappers can use as a common guideline. I'm easy. Cheers :) _______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
In reply to this post by Jack Armstrong Dancer@sprynet.com
Hello,
Le 10.06.20 à 04:03, Jack Armstrong a écrit : > Users have been adding pedestrian crossing tags on ways I don't see 2 crossing. I only see 1 crossing https://www.openstreetmap.org/node/7598863281 between a footway https://www.openstreetmap.org/way/813492687 and a tertiary road https://www.openstreetmap.org/way/558176641 Regards, Marc _______________________________________________ Tagging mailing list [hidden email] https://lists.openstreetmap.org/listinfo/tagging |
Free forum by Nabble | Edit this page |