2017-03-20 19:23 GMT+01:00 yo paseopor :
> whether the node is independent or part of one or more ways depends on the
>> situation and mapper. Even if the node is now part of just one way, in the
>> future this might change and it can become member of more ways (e.g. if the
>> way it is on is spli
On Mon, Mar 20, 2017 at 9:57 AM, Martin Koppenhoefer wrote:
>
> whether the node is independent or part of one or more ways depends on the
> situation and mapper. Even if the node is now part of just one way, in the
> future this might change and it can become member of more ways (e.g. if the
> wa
On Mon, Mar 20, 2017 at 9:46 AM, Topographe Fou
wrote:
> Hi,
>
> I put stops, give ways and traffic light where the car has to stop/yield
> which can be far from the position of the sign (for instance in the US
> where the light is after the junction, thus may not be crossed if you
> turn). Also
Since nodes lack direction, but relations do... seems like a stop sign
relation would be ideal, with multiple ways for the "from" role and the
node where it applies as the "to" role, with the actual stop sign locations
as the "device" role, similar to how enforcement is tagged.
On Mar 19, 2017 14:
On Mon, Mar 20, 2017 at 3:39 PM, Paul Johnson wrote:
> Since nodes lack direction, but relations do... seems like a stop sign
> relation would be ideal, with multiple ways for the "from" role and the node
> where it applies as the "to" role, with the actual stop sign locations as
> the "device" ro
2017-03-19 20:55 GMT+01:00 yo paseopor :
> Why you accept a line and not a dot in the same place knowing the
> information of the way the node it is [5]?
because a line/way has a direction, a node hasn't. It is simple as that.
You can continue to insist in mapping directions on nodes, and it m
2017-03-19 20:55 GMT+01:00 yo paseopor :
> In OSM mappers assume something until this thing has become more important
> and then need to redefine the way the key is applied with subkeys and other
> values.Think about bus stops for example [2]
For bus stops, nothing has really changed in the pas
2017-03-19 20:55 GMT+01:00 yo paseopor :
> but the way the node is in yes it does. Node it is not independent. It is
> in a way.
whether the node is independent or part of one or more ways depends on the
situation and mapper. Even if the node is now part of just one way, in the
future this migh
age original
De: t...@fitchdesign.com
Envoyé: 17 mars 2017 11:26 PM
À: tagging@openstreetmap.org
Répondre à: tagging@openstreetmap.org
Objet: Re: [Tagging] The direction=* tag
If micro mapping, then the stop sign is usually not in the center of the
traveled way (though I have occasionally seen so
On Sun, Mar 19, 2017 at 8:30 PM, Tod Fitch wrote:
> Unfortunately, I’ve not been able to make the Kendzi3D JOSM plug-in work
> for me. I’ll continue to poke at it from time to time as it looks
> intriguing.
>
I have told Kendzi now it is not working (with version 11425 it does) , but
as you can
This has the added complication that the way may have two-way traffic, but
the sign doesn't apply to both directions. In fact, most signs don't apply
to both sides of a roadway; instead, there will usually be a separate sign
for both directions of travel.
On March 19, 2017 2:56:02 PM yo pase
>
> yes, it is important to be able to understand to which way (and traveling
> direction) a sign applies, but nodes do not have a forward or backward
> direction
but the way the node is in yes it does. Node it is not independent. It is
in a way. with a specific direction (you can revert the dire
Unfortunately, I’ve not been able to make the Kendzi3D JOSM plug-in work for
me. I’ll continue to poke at it from time to time as it looks intriguing. I did
not feel confident in tagging lanes, especially turn lanes, until I found the
JOSM plug-in that allowed me to visualize and check the taggi
sent from a phone
> On 17 Mar 2017, at 22:47, yo paseopor wrote:
>
> I don't agree with this: marking the direction of the traffic sign is not
> noise, for a driver can be VITAL, also with the meaning of the traffic sign
> (the main purpose of a traffic sign).
yes, it is important to be ab
>
> But at present I am pretty sure that map rendering can’t use
> “direction=forward | backward”. It can (and my rendering does) use the
> compass points and/or degrees values for rotating icons in the point
> symbolizer.
As you can see Kendzi3D plug-in [1] and a style for JOSM [2] do it with
f
On 03/17/2017 05:24 PM, Tod Fitch wrote:
> The “highway=stop | give_way” tag on a node on way might be used by
> map rendering, which probably doesn’t care if it has forward or
> backward tagging.
OsmAnd does a callout for highway=stop but unfortunately ignores the
direction=* tag as of the versio
If micro mapping, then the stop sign is usually not in the center of the
traveled way (though I have occasionally seen some there). For micro mapping,
place a node for the sign where it exists on the side of the road and then use
the compass direction to indicate how it is facing. As it is detac
I don't agree with this: marking the direction of the traffic sign is not
noise, for a driver can be VITAL, also with the meaning of the traffic sign
(the main purpose of a traffic sign).
Why? Because in a way with two directions we need to know to what direction
traffic sign it is for. It is not t
Thank you for the insight. I don’t know that it is off topic though as any
tagging scheme should be both achievable by a typical mapper and useful to any
anticipated data consumers. Something that is easy for taggers but not useful
to data consumers is just noise. Something that is useful for a
On the routing engine side these tags will be translated to turn penalties
for specific turns, so the matching equivalent would probably be
from,via,to relations. Which is not a feasible modelling in OSM
realistically speaking. Simple stop signs could go on ways, but fail to
capture more complex si
From a data consumer point of view, what type of tagging would be reasonable to
indicate the, for lack of a better work, direction of travel a stop, give way
or traffic light has effect?
> On Mar 17, 2017, at 3:54 AM, Daniel Hofmann wrote:
>
> Jumping in here to give a perspective from a routi
Jumping in here to give a perspective from a routing engine (OSRM,
https://github.com/Project-OSRM/osrm-backend#open-source-routing-machine).
We do not handle direction tags on nodes which indicate a property for a
way or a turn at an intersection. The example with stop signs and give
yield signs i
On 2017-03-16 04:13, Tod Fitch wrote:
The “direction” tag [1] has different uses that seem disjoint to me.
2. To specify direction (clockwise/counterclockwise) around a
roundabout (not sure why this is needed as it should be apparent
from local laws or specified with a “oneway=yes”).
2017-03-16 5:13 GMT+01:00 Tod Fitch :
> The “direction” tag [1] has different uses that seem disjoint to me.
>
>1. To specify the orientation (compass point or degrees from north) of
>an object (adit or cave entrance, etc.).
>
>
"orientation" would have been a better descriptor IMHO, but t
Hi,
Am 2017-03-16 um 05:13 schrieb Tod Fitch:
> The “direction” tag [1] has different uses that seem disjoint to me.
> To specify the orientation (compass point or degrees from north) of an object
> (adit or cave entrance, etc.).
> To specify direction (clockwise/counterclockwise) around a round
Hi,The second use should not be encouraged IMHO as it is redundant with the direction of the way.Reguarding the third use, you can use either traffic_signals:direction or direction but the first form will explicitly apply to the traffic_signals while the second may apply to different tags of the
Am 16.03.2017 05:13, schrieb Tod Fitch:
It seems to me that the first and the third definitions should be
split into separate tags with the second definition deprecated.
I agree that this situation is suboptimal. The second meaning has
nothing to do with a direction but with a sense of rotation.
27 matches
Mail list logo
