Re: [Talk-us] Common names of highways do not match road signs.

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

Re: [Talk-us] Common names of highways do not match road signs.

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

[Talk-us] Code Sprint at State of the Map US

Look forward to seeing many of you at SotM US! Monday will have Code Sprints. I'm planning to focus on analysis, but would also love to delve into some core infrastructure topics.Who's planning on going? Have any more ideas of what you'd like to work on?

Re: [Talk-us] Common names of highways do not match road signs.

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.

Re: [Talk-us] Common names of highways do not match road signs.

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

Re: [Talk-us] Common names of highways do not match road signs.

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

Re: [Talk-us] Common names of highways do not match road signs.

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

Re: [Talk-us] Common names of highways do not match road signs.

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

Re: [Talk-us] Common names of highways do not match road signs.

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. >

[Talk-us] Common names of highways do not match road signs.

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