[OSM-talk] [RFC] Deprecating the use of Tag:highway=stop in favour of Key:stop

[John Smith]

--- On Wed, 26/8/09, James Livingston <doctau at mac.com> wrote:

> This brings up an interesting question, when you're
> "finding the  
> nearest junction" to use for stop key on a node, what
> counts as a  
> junction? It's going to be a node which belongs to the
> current way and  
> at least one other way satisfying certain conditions, but
> what are  
> those conditions? If we are to use the stop key, I think
> those  
> conditions will need to be explicitly spelt out, so that
> you can  
> process the data.

Which is tagging for routing software, if you aren't supposed to tag for rendering software why should router software be different?

Anything that needs to know which junction a stop sign applies to will know what junctions are what because they need to already for generating routing already.
 
> One obvious possibility would be ways that have highway=*
> tags -  
> should footway/cycleway/path crossing count as junctions?

These are usually before the junction, routing software usually should ignore these since cars can't go on foot paths, and cyclists/pedestrians have their own signage etc. 

> If we're going to automagically determine which junction
> the Stop  
> applies to, why do we even need a new key with yes/both/-1
> values?

Exactly.

> Surely we could just say that if the existing highway=stop
> tag is  
> applied to a node belonging to a single way (and not an
> intersection,  
> which has the current meaning), then the Stop applies to
> traffic on  
> the current way approaching the closest junction.

That's exactly what I've been saying :)