<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I have an updated plan, what does everyone think?</p>
<p>- Obtain processed address dataset open in JOSM</p>
<p>- Download existing addr:housenumber in a separate layer (using
overpass turbo)</p>
<p>- Inspection in JOSM. Areas with no existing address data can be
uploaded in one go.</p>
<p>- Areas which already have considerable amounts of address data
will be moved into separate files</p>
<p>- The big import will be completed under an import account.<br>
</p>
<p><br>
</p>
<p>I am planning on distributing the leftover data so that others
can help with the conflation process.<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 14/1/19 10:38 am, David Wales wrote:<br>
</div>
<blockquote type="cite"
cite="mid:69c004a5-1992-91e1-6a33-4896f185612b@disroot.org">
<pre class="moz-quote-pre" wrap="">Hi Joel,
I have had a quick look at the address data file in JOSM, and it looks
pretty good. When you split it by suburb / region, will you share the
smaller region files so other mappers can help with the review /
conflation / upload process?
Regards,
David Wales
On 13/1/19 11:13 pm, Joel H. wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Here is my processed OSM file
<a class="moz-txt-link-freetext" href="https://github.com/zayuim/osm-misc/blob/master/BrisbaneAddressesOfficialOnly.osm.xz">https://github.com/zayuim/osm-misc/blob/master/BrisbaneAddressesOfficialOnly.osm.xz</a>
The BCC dataset has issues with overlapping nodes and dupe addresses, I
ended up removing all other address types and only getting the official
ones (as opposed to the alternates).
And now the data is a lot better.
My plan is to split the data either by suburb or as squares.
-Joel
On 13/1/19 6:24 pm, Andrew Harvey wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Another option is take the CSV export from OpenAddresses
<a class="moz-txt-link-freetext" href="http://results.openaddresses.io/sources/au/qld/brisbane_city_council">http://results.openaddresses.io/sources/au/qld/brisbane_city_council</a>
and use <a class="moz-txt-link-freetext" href="https://github.com/openaddresses/oa2osm">https://github.com/openaddresses/oa2osm</a> to convert it to .osm.
It has options for title case, remapping tags, it already combines the
road name and road type together, and converts to WGS84.
But if you've already done it, best post the processed .osm file you
plan on importing and the procedure you're planning on using.
On Sun, 13 Jan 2019 at 15:46, Joel H. <a class="moz-txt-link-rfc2396E" href="mailto:joelh@disroot.org"><joelh@disroot.org></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi no need. I figured out all I needed with a simple python script I found online and LibreOffice Calc.
On 13/1/19 12:59 pm, David Wales wrote:
If you create a repository for your import scripts, and create some
issues, I'm happy to help out.
Have a look at Dion Moult's import repository for the NSW LPI Address
data for some ideas. We are importing suburb by suburb, and putting
changesets up for review on the repository before uploading them.
<a class="moz-txt-link-freetext" href="https://gitlab.com/dionmoult/osm-nsw-address-import">https://gitlab.com/dionmoult/osm-nsw-address-import</a>
This Brisbane import should be *much* more straightforward than the NSW
LPI import, because you have access to all the data upfront.
On 13/1/19 1:52 pm, <a class="moz-txt-link-abbreviated" href="mailto:forster@ozonline.com.au">forster@ozonline.com.au</a> wrote:
- What does the "ADDRESS USE TYPE" field mean? And should it be
preserved?
Hi, just guessing, when a property fronts onto two roads, 'Uprn
(official location)' is where their mail is delivered and 'Alternate' is
the other frontage.
Tony
_______________________________________________
Talk-au mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-au@openstreetmap.org">Talk-au@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-au">https://lists.openstreetmap.org/listinfo/talk-au</a>
_______________________________________________
Talk-au mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-au@openstreetmap.org">Talk-au@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-au">https://lists.openstreetmap.org/listinfo/talk-au</a>
_______________________________________________
Talk-au mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-au@openstreetmap.org">Talk-au@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-au">https://lists.openstreetmap.org/listinfo/talk-au</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-au mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-au@openstreetmap.org">Talk-au@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-au">https://lists.openstreetmap.org/listinfo/talk-au</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
Talk-au mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-au@openstreetmap.org">Talk-au@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-au">https://lists.openstreetmap.org/listinfo/talk-au</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-au mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-au@openstreetmap.org">Talk-au@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-au">https://lists.openstreetmap.org/listinfo/talk-au</a>
</pre>
</blockquote>
</body>
</html>