<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>OK everyone I am currently editing the LGA shapefiles for QLD so
no one should attempt as to not create conflicts (although I'm not
currently working on the suburbs file).</p>
<p>The PSMA data isn't good IMO. And requires a lot of fixing to be
imported, lots of problems with overlapping ways.</p>
<p>But the biggest problem is that the names are all caps! Does
anyone know a way to automatically convert all of these properly
so that "BRISBANE" is "Brisbane"? <br>
</p>
<div class="moz-cite-prefix">On 6/10/18 12:07 pm, Joel H. wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1de18080-e085-c736-ea1c-065c15b1d2a2@disroot.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Hi cleary (and everyone),</p>
<p>This is excellent news, I wasn't aware of this. I think this is
great and would be interested in importing Queensland's</p>
<p>My first though is to add a fixme notice (in similar fashion to
the NSW import), that tells us to reconsider the place label
node already in OSM, and to integrate it with the boundary data.</p>
<p>I'm going to check the shapefiles, but in the meantime, what
other considerations need to be made?</p>
<p><br>
</p>
<p>--Joel<br>
</p>
<div class="moz-cite-prefix">On 5/10/18 11:42 am, cleary wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1538703721.2652663.1531383336.46589BD3@webmail.messagingengine.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">A month ago, we celebrated the
news that OSM now has approval to use the PSMA Administrative
Boundaries and there was some discussion, including the need
for a proper import process. I am willing to start adding
some boundaries in areas with which I am familiar/interested
but I am waiting for the proper import process to be
determined. I am not aware if anything has been done in regard
to a plan to import this data. If so, please guide me. If not,
I propose the following:<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">Individual mappers download most
recent data from <a
href="https://data.gov.au/dataset/psma-administrative-boundaries"
moz-do-not-send="true">https://data.gov.au/dataset/psma-administrative-boundaries</a>
and add/check data in their areas of interest and/or when they
have time. (Andrew Harvey has provided a script <span
class="text-gray-dark mr-2">to assist working with PSMA
Administrative Boundaries Data</span> and there is a link on
<a
href="https://wiki.openstreetmap.org/wiki/Australian_Data_Catalogue"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Australian_Data_Catalogue</a>)<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">Administrative boundaries in
NSW, SA, VIC and ACT be modified instance-by-instance if there
are discrepancies that require updating. Where there are
discrepancies, the most recent data is usually preferred . If
there are concerns about accuracy of the most recent data,
further consultation with other mappers or relevant government
boundary authorities would be appropriate.<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">In QLD, WA, TAS and NT : LGA
and Suburb/Locality boundaries be added one at a time,
integrating with existing data where appropriate. Previous
data from unauthorised sources be deleted or the authorised
source be added if the data is accurate.<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">LGA Boundaries continue to be
tagged as admin_level=6<br>
</div>
<div style="font-family:Arial;">Suburb/Locality boundaries be
tagged as admin_level=10<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">In both instances
source=PSMA_Admin_Boundaries_August_2018 <br>
</div>
<div style="font-family:Arial;">(or whichever date is applicable
to the most recent data being used)<br>
</div>
<div style="font-family:Arial;">This source information may seem
unwieldy but provides accuracy and completeness of
information.<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">Administrative boundaries NOT be
attached to other ways such as creeks, rivers, roads, etcetera
so that the other features can be modified as needed without
affecting the administrative boundaries which are generally
static.<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">Multiple administrative
boundaries (including national_parks and government approved
protected_areas or state forests) be mapped on a single way,
where appropriate, and with multiple relations attached to
that single way i.e. a single way could form the boundaries
for localities, LGAs and a national park, if appropriate in
the particular location.<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">Electoral boundaries NOT be
added at this time.<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">Other boundaries which have been
discussed, such as regions and indigenous areas, NOT be added
as part of this particular project unless they are LGAs or
Suburbs/Localities (some indigenous areas may be identified as
protected areas or defined localities or LGAs, in which case
they are added and identified on that basis). Mapping of
regions could be further discussed separately if required.
They are usually not defined by legislation and therefore
usually not "administrative" in the way that LGAs and
Suburbs/Localities are legislated.<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div style="font-family:Arial;">Comments and feedback, please.<br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div><br>
</div>
<div style="font-family:Arial;"><br>
</div>
<div><br>
</div>
<div>On Fri, Aug 31, 2018, at 4:23 PM, Andrew Harvey wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>The Department of Industry,
Innovation and Science which
manages <a
href="http://data.gov.au"
moz-do-not-send="true">data.gov.au</a>
have just completed the OSMF CC
BY waiver allowing the PSMA
Administrative Boundaries[1] to
be used within OpenStreetMap[2].<br>
</div>
<div><br>
</div>
<div>Quoting their email, "The
Australian Government received
great encouragement from PSMA
Australia Limited to make the AB
[Administrative Boundaries] data
more accessible. Many thanks to
OSM for your ongoing global open
data efforts."<br>
</div>
<div><br>
</div>
<div>Others more active in working
with admin boundaries in OSM
might be able to comment further
on my analysis, but I've taken a
look at the current OSM data
from a planet extract[3], using
osmium tool to extract
administrative boundaries[4]:<br>
</div>
<div><br>
</div>
<div> osmium tags-filter
australia-latest.osm.pbf
nwr/boundary=administrative -o
osm-admin-boundaries.osm.pbf<br>
</div>
<div><br>
</div>
<div>Then converted to GeoPackage
to open in QGIS to compare to
PSMA boundaries:<br>
</div>
<div>
<div><br>
</div>
<div> ogr2ogr -f GPKG
osm-admin-boundaries.gpkg
osm-admin-boundaries.osm.pbf<br>
</div>
</div>
<div><br>
</div>
<div>The admin_level values for
Australia are defined as[5]:<br>
</div>
<div><br>
</div>
<div>3 n/a<br>
</div>
<div>4 State or Territory<br>
</div>
<div>5 n/a (but used in Victoria
for regions[6])<br>
</div>
<div>6 Local Government Area (eg
Shire/Council)<br>
</div>
<div>7 District or Region (e.g
Perthshire, Fitzroy, Canning,
Greater Sydney, Greater
Melbourne, etc.)<br>
</div>
<div>8 Postcode<br>
</div>
<div>9 Suburb and Locality<br>
</div>
<div>10 Suburb and Locality<br>
</div>
<div><br>
</div>
<div>(not sure why the split
across 9 and 10...? but it looks
like no data for 9 and all
suburb/localities are marked as
10, a seperate discussion but
perhaps they should be 9 and
smaller neighbourhoods be in
10?)<br>
</div>
<div><br>
</div>
<div>PSMA Admin Boundaries provide
(for Australia wide Shapefiles
see [7] built from [8])<br>
</div>
<div><br>
</div>
<div>Commonwealth Electoral
Boundaries (I don't think should
be included in OSM)<br>
</div>
<div>State Electoral Boundaries (I
don't think should be included
in OSM)<br>
</div>
<div>State Boundaries<br>
</div>
<div>Local Government Areas<br>
</div>
<div>Suburbs / Localities<br>
</div>
<div>Town Points<br>
</div>
<div>Wards<br>
</div>
<div><br>
</div>
<div>admin_level 6 LGAs<br>
</div>
<div>It looks like NSW, VIC have
complete LGA coverage already
aside a few minor differences,
but NT is patchy and TAS, QLD,
WA are almost non-existent (ACT
doesn't really have LGAs it's
all managed by the Territory).
SA is missing a few LGAs which
exist in the PSMA data.<br>
</div>
<div><br>
</div>
<div>admin_level 7 is a mixed bag,
but the PSMA data won't help
here<br>
</div>
<div><br>
</div>
<div>suburbs/localities<br>
</div>
<div>NSW, VIC, SA all have pretty
much complete data in OSM but
there are a number of
differences with the PSMA data
which should warrent
investigation and correction.<br>
</div>
<div><br>
</div>
<div>ACT I think has good existing
data (in the PSMA data in
suburb/localities there are both
levels, eg. Canberra Centre and
Parkes), but the districts have
a slightly different name
format.<br>
</div>
<div><br>
</div>
<div>All other states are empty in
OSM.<br>
</div>
<div><br>
</div>
<div>Keeping in mind that we have
state data for admin boundaries
in VIC (VicMap), NSW (Spatial
Services), ACT (ACTmapi) and SA
(<a href="http://data.sa.gov.au"
moz-do-not-send="true">data.sa.gov.au</a>)
already.<br>
</div>
<div><br>
</div>
<div>So there does appear to be a
lot of data missing in OSM,
which licensing wise we could
bring in to OSM. So I guess the
question is should we and how
should we do that. Is anyone
interested in working on this?
If people are, I think it should
go through the proper import
process (discuss first, identify
the process and then execute).<br>
</div>
<div><br>
</div>
<div>[1] <a
href="https://data.gov.au/dataset/psma-administrative-boundaries"
moz-do-not-send="true">https://data.gov.au/dataset/psma-administrative-boundaries</a><br>
</div>
<div>[2] <a
href="https://wiki.openstreetmap.org/wiki/File:Department_of_Industry_Innovation_and_Science_ODbl_permission_Administrative_Boundaries.pdf"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/File:Department_of_Industry_Innovation_and_Science_ODbl_permission_Administrative_Boundaries.pdf</a><br>
</div>
<div>[3] <a
href="http://download.openstreetmap.fr/extracts/oceania/"
moz-do-not-send="true">http://download.openstreetmap.fr/extracts/oceania/</a><br>
</div>
<div>[4] <a
href="https://osmcode.org/osmium-tool/manual.html#filtering-by-tags"
moz-do-not-send="true">https://osmcode.org/osmium-tool/manual.html#filtering-by-tags</a><br>
</div>
<div>[5] <a
href="https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative#10_admin_level_values_for_specific_countries"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative#10_admin_level_values_for_specific_countries</a><br>
</div>
<div>[6] <a
href="https://en.wikipedia.org/wiki/Regions_of_Victoria"
moz-do-not-send="true">https://en.wikipedia.org/wiki/Regions_of_Victoria</a><br>
</div>
<div>[7] <a
href="https://tianjara.net/data/psma-admin-bdys/"
moz-do-not-send="true">https://tianjara.net/data/psma-admin-bdys/</a><br>
</div>
<div>[8] <a
href="https://github.com/andrewharvey/psma-admin-bdys-data"
moz-do-not-send="true">https://github.com/andrewharvey/psma-admin-bdys-data</a><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div><u>_______________________________________________</u><br>
</div>
<div>Talk-au mailing list<br>
</div>
<div><a href="mailto:Talk-au@openstreetmap.org"
moz-do-not-send="true">Talk-au@openstreetmap.org</a><br>
</div>
<div><a
href="https://lists.openstreetmap.org/listinfo/talk-au"
moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-au</a><br>
</div>
</blockquote>
<div style="font-family:Arial;"><br>
</div>
<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" moz-do-not-send="true">Talk-au@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-au" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-au</a>
</pre>
</blockquote>
<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>