[Talk-us] (Was) How is Scout?

[Paul Johnson]

On Fri, Jul 18, 2014 at 8:49 PM, Tod Fitch <tod at fitchdesign.com> wrote:

> Probably because I wasn't looking for it when searching for how to tag
> lanes and because there is no link to the placement:*=* proposal page from
> the turn:*=* page in the wiki. Do any data consumers (map renderers,
> navigation displays, etc.) use this key?


I don't know...Osmand has it planned.  I would hope Scout does.  Just
because nobody's using it yet doesn't mean we shouldn't try to get that
data there.  My current project is to make all roads in Oklahoma at State
Highway level and higher (State Turnpike, US Highway, Interstate Highway)
entirely reviewed from the TIGER import, properly aligned, with lanes and
placements, with route relations.  In an effort to benefit the most people
soonest if someone does implement lane guidance based off this data, I'm
ordering this in descending order of population by county (Oklahoma, Tulsa,
Cleveland, Comanche...) then descending order of priority by network
(Interstate first, state highway last), ascending ref (35, 40, 235,
240...).  This also gets the hardest cases out of the way earliest, plus
usually causes me to find data that needs some serious fixing on the
crossing ways in the vicinities, so I'm probably going to be generating at
least a few notes per mapping session (probably the most will be in the OKC
and Lawton areas, I've more or less got Tulsa to a point where I'm just
adding detail, since in the Tulsa area, we've got alignment correct down to
the median crossing location level on almost all of the section line roads,
and even maxspeed=* included and accurate on ~90+% of Tulsa County's
highway=* ways).

At the risk of going longwinded and derailing this, I'm a little
disappointed I didn't get to reach every county in Oklahoma at least once,
if only to at least get the base speed limit off the sign at the county
line, since that would at least make it possible to retag the county's
highways so you at least get some warning if you're going faster than the
basic rule in that county, since it varies.  And would obviate missing
speeds on roads posted higher than the basic speed.

I realize this is slightly overkill when I group tag every vehicle-capable
highway=* public way that isn't already maxspeed=* tagged, but given that,
in any given county but Tulsa and OKC, there's typically fewer than a dozen
ways with explicitly posted speed limits...it's better than trying to
individually scout out a bazillion miles of totally signless tracks signed
as county roads...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20140718/7fc16616/attachment.html>