Well, one of the main reasons I brought this up is because I've noticed another
user changing some relations from "forward/backward" to
"west/east"/"south/north" without discussing this here on talk-us. That user
would happen to be KristenK. This user has been doing this since the 11th at
lea
can someone post on IRC?
https://plus.google.com/events/crt026uc10l7i1oetvquep466eo
( I hope this is the right link...G+)
--
Martijn van Exel
http://oegeo.wordpress.com/
http://openstreetmap.us/
___
Talk-us mailing list
Talk-us@openstreetmap.org
ht
Re the comment by Nathan: “I'm still confused as to why the consumers of a
relation can't use the forward/backward roles…” The forward/backward roles only
make sense on one-way roads. Other than that, which way is forward and which
way is backward? Depends on which way you’re driving down the r
They're not at all hard to find in the US. I would wager that fewer than 50% of
the actual on the ground road routes in the US have any divided segment
whatsoever.
What exactly is captured by two relations that is not captured by one, however?
That's the part I'm not understanding. We have tool
Hi,
As a meta comment. I have been trying to follow all of the US
route/shield discussions over the past couple of months. I don't feel
confident that I understand the consensus on how to map these
routes+shields and do not feel comfortable editing them. When the dust
settles, could somebody that
2013/11/18 Nathan Mills
> I'm still confused as to why the consumers of a relation can't use the
> forward/backward roles of the ways referenced therein rather than requiring
> completely separate relations. Why do we need two or more relations plus a
> super relation per road route even for undi
When you find a suspicious edit, try to be part of the solution,
What a really well-written post. Thank you, Richard!
SteveA
California
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
I'm still confused as to why the consumers of a relation can't use the
forward/backward roles of the ways referenced therein rather than requiring
completely separate relations. Why do we need two or more relations plus a
super relation per road route even for undivided highways? Even for a some
2013/11/18 Richard Weait
> Repair or revert data that is incorrect. Get help from a
> more-experienced mapper if you haven't done this before.
>
Thank you Richard for this post. Very true that every single mapper can try
to make contact with other mappers in his surroundings and find a solution
On Mon, Nov 18, 2013 at 10:52 AM, Paul Johnson wrote:
> Not a fan. It greatly complicates things for information that can either
> be gleaned obviously or is a "nice to have." Having 3+ relations for
> something that isn't fully divided just complicates things, with the
> exception edge case of
When you find a suspicious edit, try to be part of the solution,
rather than merely a reporting system. :-)
If you are experienced enough, attempt to determine which account
introduced the suspicious data. Contact that account through the user
mail system. Presume good faith; they may well be a
Not a fan. It greatly complicates things for information that can either
be gleaned obviously or is a "nice to have." Having 3+ relations for
something that isn't fully divided just complicates things, with the
exception edge case of a relation that starts or ends on a divided highway.
On Sun,
12 matches
Mail list logo
