<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 25/02/2016 17:04, Nick Whitelegg
wrote:<br>
</div>
<blockquote
cite="mid:VI1PR07MB15825EC40687EEE5E2C3AFCBA6A60@VI1PR07MB1582.eurprd07.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><br>
</p>
<p>One thought I've had for a long time (and have probably
mentioned in the past) is a walkers' editor (app rather than
web-based). To be used something like:</p>
<p><br>
</p>
<p>User goes for walk and records GPX trace, following this sort
of pattern.</p>
<p><br>
Each time the type of right of way changes, the user selects a
high level type ("Public Footpath", "Public Bridleway" etc in
the UK) together with optional surface tags.</p>
<p><br>
</p>
<p>User can also enter relevant POIs like stiles, gates etc when
they are encountered.</p>
<p><br>
</p>
<p>When user returns home, track simplification algorithm used
to make a way from the GPX trace and tags it with the tags
equivalent to the ROW type.</p>
<p><br>
</p>
<p>User downloads data from OSM and algorithms are used to
auto-join the user's new ways to existing ways where
appropriate (or alternatively, the user does this manually)</p>
</div>
</blockquote>
<br>
That's not a million miles from the way that I map right now, albeit
without the benefits of an "app" as such:<br>
<br>
I record a GPS trace (on a Garmin) with numbered waypoints in it.
The symbols for the Garmin waypoints "mean" something, so the "boat
ramp" symbol means "public right of way". If it's a bridleway I'll
add "BR" to the comment on the Garmin. If more text is needed (e.g.
the name of a shop I've created a waypoint for) I'll create an line
in an email to myself, the start of which is the Garmin waypoint
number and the rest of which is the comment.<br>
<br>
When I get home I'll split the individual traces out
programmatically, merge the comments from the email into the GPX
file (likewise) and upload to OSM.<br>
<br>
I'll then edit in OSM using the uploaded trace directly (using P2 -
JOSM can't process waypoints in a way that's useful to me). Usually
the combination of new GPS trace, previous GPS traces, Bing imagery,
OS OpenData StreetView imagery and my recollection is enough to
figure out where the path should go, but none of those (unless there
are really _lots_ of old GPS traces) are good enough on their own.<br>
<br>
On an introductory level, I can definitely see the benefits of
something that can suggest to people "here are the other attributes
of $thing that you've just added", like iD does, and like Kort
does/used to do (see <a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/Kort_Game">http://wiki.openstreetmap.org/wiki/Kort_Game</a> ).<br>
<br>
Cheers,<br>
<br>
Andy<br>
<br>
<br>
</body>
</html>