<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Upps sorry that that this went out twice.</p>
<p>One aspect that I forgot to mention was if you have open address
data available in GeoJSON format this can be displayed as an
overlay. This is mainly useful if you are taking a combined
survey/reference data approach. 15.2 (not released yet) supports
creating OSM objects directly out of suitable GeoJSON which could
be used as an alternative data entry strategy.</p>
<p>Simon <br>
</p>
<div class="moz-cite-prefix">Am 23.01.2021 um 11:20 schrieb Simon
Poole:<br>
</div>
<blockquote type="cite"
cite="mid:2039bef4-0fb0-a993-c44c-879c5ef2b301@poole.ch">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>I don't quite understand why, outside of a specialized
keyboard, you are reinventing the wheel (and fragmenting
available development resources, OK, I suppose that is one of
the hallmarks of OSM development which unluckily get rewarded
time and time again). Vespucci:</p>
<p>- allows you to directly enter address for upload, aka enter
once, no 2nd pass needed at home<br>
</p>
<p>- automatically will download data (so that you don't
accidentally duplicate existing addresses)</p>
<p>- can highlight missing tags, for example addresses</p>
<p>- has all the background and overlay layers from ELI available
<br>
</p>
<p>- has address prediction that will automatically detect odd /
even address schemes and increment and is street side aware</p>
<p>- allows you to configure which address tags should be set on
addresses (this tends to be a question of national preference)</p>
<p>- handles addr:street and addr:place <br>
</p>
<p>- seeds address tags values from existing data<br>
</p>
<p>- and many other things like conflict resolution and so on.</p>
<p>All since more than half a decade (actually 7 years).<br>
</p>
<p>Yes, as said, it is true that it doesn't have a specialized
keyboard, but as you typically only have to type in a small
number of numbers per street, if any at all, the pain isn't
really large enough to offset the complexity caused by i18n
support that would be required. But we even have an issue for
that <a class="moz-txt-link-freetext"
href="https://github.com/MarcusWolschon/osmeditor4android/issues/574"
moz-do-not-send="true">https://github.com/MarcusWolschon/osmeditor4android/issues/574</a>
and if somebody wants to put the effort (see i18n problems) a PR
would be gladly accepted.</p>
<p>Simon<br>
</p>
<p> <br>
</p>
<div class="moz-cite-prefix">Am 22.01.2021 um 12:25 schrieb
ipswichmapper--- via talk:<br>
</div>
<blockquote type="cite" cite="mid:MRdpptz--3-2@tutanota.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div>Hello openstreetmap community, <br>
</div>
<div><br>
</div>
<div>I have been writing an android application that should make
it significantly easier to collect housenumbers. <br>
</div>
<div><br>
</div>
<div>Now, finally, I have released an apk on Github (you'll find
it under the "assets" tab):<br>
</div>
<div><br>
</div>
<div><a
href="https://github.com/IpswichMapper/SwiftAddress/releases"
moz-do-not-send="true">https://github.com/IpswichMapper/SwiftAddress/releases</a><br>
</div>
<div><br>
</div>
<div>
<div>Make sure you check the releases page because I'll be
releasing updates that improve functionality and fix bugs.<br>
</div>
<div><br>
</div>
</div>
<div>I have written about the app in more detail in my diary
entry:<br>
</div>
<div><br>
</div>
<div><a
href="https://www.openstreetmap.org/user/IpswichMapper/diary/395413"
moz-do-not-send="true">https://www.openstreetmap.org/user/IpswichMapper/diary/395413</a><br>
</div>
<div><br>
</div>
<div>The app starts up as a simple OSMdroid map. The way you
place housenumbers is by moving the crosshair (which is in the
middle of the screen) above the building outline of the
housenumber you are trying to map. You then add the
housenumber using the keypad.<br>
</div>
<div><br>
</div>
<div>The advantage of this is that the housenumbers are already
in the right place when surveying. There is no need to clean
up the messy data (like with Keypad Mapper 3) or draw
housenumbers (like with Streetcomplete). All that needs to be
done is to load the data into JOSM and then upload. (In the
future direct upload might be supported). <br>
</div>
<div><br>
</div>
<div>Of course, most times building outlines aren't drawn in
OSM, so you can't tell from OSM imagery where the postition of
the building/house is. For this I plan on implementing
satellite background imageries into the app, so that you can
use that to find the position of the house. (I need to know
how to implement that first, however, and what imagery/tms I
can use)<br>
</div>
<div><br>
</div>
<div>You can also has a few more features, for example,
auto-incrementing, and the ability to take notes. I have
described the app in more detail in the diary entry. <br>
</div>
<div><br>
</div>
<div>Thanks,<br>
</div>
<div>IpswichMapper<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org" moz-do-not-send="true">talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></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>