<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>The thing is, it is -actually- no longer 2010 and the task of
collecting data while moving faster than walking speed has been
solved. Street-side imagery, that is with Mapillary, KartaView and
so on, with post-recording ML supported analysis so that it is
easy to find the interesting bits. This is safe, doesn't suffer
from all the issues pressing any kind of buttons while moving has,
and the major platforms are well supported in all major editors.<br>
</p>
<p>If there is need for development in this area then, IMHO, it
should be for a multi-platform recording app, that is one app that
supports uploading to Mapillary, KartaView, GeoVisio and so on<br>
</p>
<p> Simon<br>
</p>
<div class="moz-cite-prefix">Am 06.08.2022 um 12:47 schrieb Ilya
Zverev:<br>
</div>
<blockquote type="cite"
cite="mid:12c1b527-7270-4b02-8533-921897900e06@www.fastmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title></title>
<style type="text/css">#qt p.qt-MsoNormal{margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;font-size:11pt;font-family:"Calibri", sans-serif;}#qt a:link{color:rgb(5, 99, 193);text-decoration-line:underline;text-decoration-style:solid;text-decoration-color:currentcolor;text-decoration-thickness:auto;}p.MsoNormal,p.MsoNoSpacing{margin:0}p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
<div>Hi Jean, it's great the OSM Tracker would have some
development.<br>
</div>
<div><br>
</div>
<div>I've read the form, and it feels like instead of catering to
OSM Tracker's strengths, once again you want to make it like a
dozen other apps already existing on the market. Same POI
collection and polluting the volunteer notes space with traces
and notes.<br>
</div>
<div><br>
</div>
<div>OSM Tracker is unique, and while currently its usefulness is
limited, it can be made into an amazing tool for mappers. You
just need to find its niche and dig into it.<br>
</div>
<div><br>
</div>
<div>As I see it, OSM Tracker is great on recording stuff you see
on the way, moving at a speed higher than of a pedestrian: on a
bike, or in a car. Otherwise you've got tons of editors that you
can take your time with, e.g. StreetComplete. These editor would
be better than anything you can hope to make OSM Tracker into.<br>
</div>
<div><br>
</div>
<div>Now, having established that, look into prior art:<br>
</div>
<div><br>
</div>
<div>* Surveying plugin for JOSM: <a
href="https://wiki.openstreetmap.org/wiki/JOSM/Plugins/Surveyor"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.openstreetmap.org/wiki/JOSM/Plugins/Surveyor</a><br>
</div>
<div>* NanoLog, a program for data collection at 60 kmh: <a
href="https://wiki.openstreetmap.org/wiki/NanoLog"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.openstreetmap.org/wiki/NanoLog</a><br>
</div>
<div>* OpenSurveyor, a failed app like OSM Tracker: <a
href="https://vimeo.com/73281384" moz-do-not-send="true"
class="moz-txt-link-freetext">https://vimeo.com/73281384</a>
(the design doc is in Russian, alas)<br>
</div>
<div><br>
</div>
<div>I'd suggest starting with installing the app, then boarding a
bus, and seeing how much can you map at the speed. Which
decisions you can and cannot make. Then riding a bike with the
app and seeing what you want and won't map on the way. The
choice of features changes drastically when there's a deadline
for all your decisions.<br>
</div>
<div><br>
</div>
<div>You will find that sub-menus do not work, that deciding
between highway=primary and highway=motorway is not what you do,
that most fuel stations are already mapped, while marking
parking spots is useless, and that post-processing is
unavoidable.<br>
</div>
<div><br>
</div>
<div>And post-processing would be the most imporant — and tedious
— step. Most mapping parties I've help end up with a lot of
filled walking papers and GPX traces, but with no map. You need
to think how to make post-processing fun. Fast. Like, improving
the accuracy of collected waypoints. Making a JOSM plugin or a
dedicated iD editor fork. Or a tile layer from a central
database to which all the collected traces and points are sent.
Choosing data to collect that does not require looking elsewhere
for confirmation or detailing. Doing away with audio and photo
notes.<br>
</div>
<div><br>
</div>
<div>It's not 2010, forget sending data to email and uploading to
OSM notes. Make it better.<br>
</div>
<div><br>
</div>
<div>Finally, go into the field again. Collect data. Ask people to
collect data: both experienced mappers and novices. Iterate.
Make better presets. Map. And map again. Working on a tool for
surveying means you need to be surveying every other day.
Otherwise this would be another academic work not applicable to
real mapping, quickly forgotten.<br>
</div>
<div><br>
</div>
<div>I hope this helps, and of course I can help test improved
versions of the app.<br>
</div>
<div><br>
</div>
<div>Ilya<br>
</div>
<div><br>
</div>
<div>On Sat, 6 Aug 2022, at 02:51, Jean Marco Rojas Umana wrote:<br>
</div>
<blockquote type="cite" id="qt" style="overflow-wrap:break-word;">
<div class="qt-WordSection1">
<p
style="margin-right:0cm;margin-bottom:12pt;margin-left:0cm;"><span
style="color:black;" lang="EN-US"><span class="font"
style="font-family:"Arial", sans-serif;">Hello,
I am Jean Marco Rojas, a student at the Technological
Institute of Costa Rica (Public University), in the
Computer Engineering career, I am currently doing
professional practice in the </span></span><a
href="https://www.tec.ac.cr/grupo-investigacion/laboratorio-experimental/"
moz-do-not-send="true"><span style="color:rgb(17, 85,
204);background-color:white;background-position-x:0%;background-position-y:0%;background-repeat:repeat;background-attachment:scroll;background-image:none;background-size:auto;background-origin:padding-box;background-clip:border-box;"
lang="EN-US"><span class="font"
style="font-family:"Arial", sans-serif;">Laboratorio
Experimental.</span></span></a><span
style="color:black;" lang="EN-US"><span class="font"
style="font-family:"Arial", sans-serif;"> My
practice consists of proposing and developing an
improvement to the OSMTracker. We have created a very
short form to validate the necessity to implement a
functionality to upload tracked traces to a shared
folder. The form has only 7 questions, most of them are
“Yes” or “No” questions, so it will take you less than 5
minutes to complete. Thank you very much. Your
contribution is valuable for improving the tool.</span></span><span
lang="EN-US"></span><br>
</p>
<p class="qt-MsoNormal"><span style="color:black;"
lang="EN-US"><span class="font"
style="font-family:"Arial", sans-serif;">Form
link: </span></span><a
href="https://forms.gle/yqgnCWT8E12Dh2L59"
moz-do-not-send="true"><span style="color:rgb(17, 85,
204);" lang="EN-US"><span class="font"
style="font-family:"Arial", sans-serif;">https://forms.gle/yqgnCWT8E12Dh2L59</span></span></a><span
lang="EN-US"></span><br>
</p>
</div>
<div>_______________________________________________<br>
</div>
<div>talk mailing list<br>
</div>
<div><a href="mailto:talk@openstreetmap.org"
moz-do-not-send="true" class="moz-txt-link-freetext">talk@openstreetmap.org</a><br>
</div>
<div><a href="https://lists.openstreetmap.org/listinfo/talk"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.openstreetmap.org/listinfo/talk</a><br>
</div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk">https://lists.openstreetmap.org/listinfo/talk</a>
</pre>
</blockquote>
</body>
</html>