Kevin Morgan writes:
>
>
> Here is an idea. An additional tag is added called signage. The tag use
the following format name;ref;text. Each item is added to the tag if the
information is in clued on road signs. The tag has the following sub tags
color, icon, description, direction and text. Th
On Sun, 2016-07-10 at 12:07 -0400, Kevin Morgan wrote:
> Here is an idea. An additional tag is added called signage. The tag
> use the following format name;ref;text. Each item is added to the tag
> if the information is in clued on road signs. The tag has the
> following sub tags color, icon, des
I think this would be great for point-based data in order to help others
properly determine the correct name=* tag. However, given the
circumstances, I tend to also use source:name or name:source (not sure
which is correct) citing the state law renaming the road, since that's
verifable and canonic
Here is an idea. An additional tag is added called signage. The tag use
the following format name;ref;text. Each item is added to the tag if
the information is in clued on road signs. The tag has the following sub
tags color, icon, description, direction and text. The text sub tag is
used to add a
On Sun, Jul 10, 2016 at 5:47 AM, Richard Fairhurst
wrote:
> Greg Troxel wrote:
> > When converting to garmin format with mkgmap, and I think with osmand,
> > I will tend to hear both the name and the ref. That's a big lengthy, but
> > there's no real pattern on which to leave out.
>
> For cycle.
Greg Troxel wrote:
> When converting to garmin format with mkgmap, and I think with osmand,
> I will tend to hear both the name and the ref. That's a big lengthy, but
> there's no real pattern on which to leave out.
For cycle.travel's directions in the US, I've started post-processing the
name a
Paul Johnson writes:
> On Thu, Jul 7, 2016 at 9:32 PM, Kevin Morgan
> wrote:
>
>> It is confusing to use open street maps in my area(Central Ohio) for
>> driving directions since the "common names" of high ways do not match
>> road signs. The common names are used by open map chest for road nam
There are many parts here: road signs in the real world, names which might not
match those, data in OSM, and presentation by "stacks"
(hardware/software/network) of those data. The first two can be captured with
proper tagging in the third. If the fourth does not meet your needs, it MAY be
t
Paul Johnson writes:
>
> On Thu, Jul 7, 2016 at 9:32 PM, Kevin Morgan
wrote:It is confusing
to use open street maps in my area(Central Ohio) for
> driving directions since the "common names" of high ways do not match
> road signs. The common names are used by open map chest for road names.
> Fo
On Fri, Jul 8, 2016 at 9:22 AM, Andy Townsend wrote:
> I've tended to use "name:signed=no" and/or "ref:signed=no" if there's a
> name or ref that is agreed to be "correct" but not useful for navigation.
This is where things get *exceedingly* complicated in my region. Signage
can be *highly* i
On 08/07/2016 15:45, Jeffrey Ollie wrote:
... According to the Iowa DOT, it's official name is
"Interstate Highway 235" but ...
As Paul has already said, that sounds like a "ref" to me, not a "name".
If something doesn't have a name, you don't need to create one for OSM...
Cheers,
Andy
_
On Fri, Jul 8, 2016 at 9:22 AM, Andy Townsend wrote:
>
> In the UK we've also had a problem with some (generally armchair) mappers
> thinking that "all roads must have a name" and "any name is better than no
> name" so they've been adding "names" that might have been in a news report
> ages ago al
I've tended to use "name:signed=no" and/or "ref:signed=no" if there's a
name or ref that is agreed to be "correct" but not useful for
navigation. It's not used much:
http://taginfo.openstreetmap.org/keys/name%3Asigned
but it does mean that you can exclude "non-useful names" from maps made
wi
It's been a long time since I've messed much with turning OSM data
into Garmin maps, but even back then the main problem was mapping the
OSM data model to the Garmin data model, what kind of data to retain,
what data to leave out, what data needed to be massaged before being
included etc. It's more
On Thu, Jul 7, 2016 at 9:32 PM, Kevin Morgan
wrote:
> It is confusing to use open street maps in my area(Central Ohio) for
> driving directions since the "common names" of high ways do not match
> road signs. The common names are used by open map chest for road names.
> For example when turning o
It is confusing to use open street maps in my area(Central Ohio) for
driving directions since the "common names" of high ways do not match
road signs. The common names are used by open map chest for road names.
For example when turning on to State Route 315 with OpenMapChest loaded
on my GPS I am
16 matches
Mail list logo
