Modify

Opened 10 years ago

Last modified 4 years ago

#9895 new enhancement

checking correct use of noexit

Reported by: skyper Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: noexit Cc:

Description (last modified by skyper)

There was/is some dicussion about noexit=* on talk-de@osm and tagging@osm.
The wiki was changed as one result.

Major points are:

  1. only use noexit=yes on nodes
  2. only useful value is yes (use fixme=continues instead of noexit=no) (done r15954)
  3. only tag it on end nodes without any other connection (or ways with one unconnected end node)

Now validator checks for these three rules would be nice. Thanks

Attachments (0)

Change History (14)

comment:1 by skyper, 10 years ago

Description: modified (diff)

comment:2 by pieren, 10 years ago

This subject is controversial, please don't try to impose your opinion thourgh JOSM tracking.

comment:3 by Don-vip, 10 years ago

Are all the points controversial or can we implement something everyone agrees?

comment:4 by skyper, 10 years ago

Description: modified (diff)

I did add the links to the discussion. Please make up your own opinion, but be careful with the wiki and have a look at its recent history.

comment:5 by pieren, 10 years ago

have a look at its recent

I did. Currently, the wiki says : "Use the noexit=yes tag on the node at the end of a highway=* or on the way itself ..."

comment:6 by Don-vip, 10 years ago

With 120k ways tagged as such, I agree with Pieren, we won't implement rule 1.

Rule 2: why not
Rule 3: nodes or ways without connections

We could also check noexit is only used with highways

in reply to:  6 comment:7 by skyper, 10 years ago

Replying to Don-vip:

With 120k ways tagged as such, I agree with Pieren, we won't implement rule 1.

Well, I tried my best, on the discussion but I am tired to repeat myself and other arguments and one person just says, This does not convince me but without other arguments. The wiki page was a real mess for some years but cleaning up and writing down what more than 95% of all persons, taking part on the discussions in German and English, said, gets reverted by one person all the time.

Please, do not allow this tag on ways in Germany or even German-speaking area, as we only accept it on the end node of way without any other connections to this node.

Rule 2: why not
Rule 3: nodes or ways without connections

Well, exactly at this point it gets complicated, if used on ways.

We could also check noexit is only used with highways

Better use allow it also for *ways (eg. water,rail). I found some rails ending without a buffer_stop.

I did not mention this ticket on any mailing list but if you do not want to read/foolow the discussion, we could start another one here and tell more people about voting on tickets.

comment:8 by skyper, 10 years ago

Guess rule 1 must wait until the other rules and the changed wiki pages will show some effects. As it explicitly should not be used on waterways a check for railway/highway would make sense.

comment:9 by skyper, 7 years ago

Any plans to add rule 2 and 3 for the whole planet and rule 1 for at least Germany and elsewhere other communities agree with this rule ?

comment:10 by skyper, 4 years ago

Rule one is in the Germany specific rules.

Rule two and three are useful globally.

comment:11 by Klumbumbus, 4 years ago

In 15954/josm:

see #9895 - Warn about values of noexit other than yes

comment:12 by Klumbumbus, 4 years ago

rule 3 would need to check other highway/railway ways only, else it would end in false positives if the highway/railway ends e.g. at a landuse area way. (While this tagging style is controversial that discussion does not belong here in this ticket.)

comment:13 by skyper, 4 years ago

Description: modified (diff)

comment:14 by skyper, 4 years ago

According to the wiki [osmwiki/Key:noexit] noexit is not allowed for any object type but nodes for years, now. Any chance, to have a warning in core excluding the countries where it is controversial or still accepted with ways?

Version 0, edited 4 years ago by skyper (next)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to skyper.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.