[Imports] Australia / Victoria / Melbourne - VicMap Property

[Andrew Harvey]

On Sun, 1 Sep 2019 at 10:02, Simon Jackson <simon.robin.jackson at gmail.com>
wrote:

> *Short Version:*
> https://arcg.is/0Tu8Tb
> Start a discussion on incorporating the VicMap Property dataset into OSM.
>

Sorry I can't see that link without an ESRI login.


> *The Data*
> The VicMap dataset consists of a number of layers that have been made
> available as open data under a creative commons license.
>

CC BY licensing alone is still not suitable for use in OSM due to
https://blog.openstreetmap.org/2017/03/17/use-of-cc-by-data/. However the
good news is VicMap data's owner has completed the required waiver, as
noted at https://wiki.openstreetmap.org/wiki/Australian_Data_Catalogue.


> There are a couple of layers that as an OSM user, I would would be of
> value to consider for an initial bulk import
> <https://wiki.openstreetmap.org/wiki/Import> of data, and then
> potentially looking at workflows to sync the importing of the incremental
> deltas through periodically.
>
> *VicMap Property:*
> https://discover.data.vic.gov.au/dataset/property-view-vicmap-property
>
>
https://wiki.openstreetmap.org/wiki/Parcel gives a good overview of
cadastre data for use in OSM, in short there is no clear consensus on if we
should import it or not.

I'm a bit torn for both sides, on one hand it's very easy for downstream
consumers to combine parcel boundaries with OSM data to form a map, I do
this all the time. On the other hand having this data in OSM can help map
features more accuratly to those boundaries. I see this being done on an ad
hoc basis, where editors can pull in a few boundaries at a time as you're
mapping things like residential landuse, parks etc. not a mass import.

I would be against a mass import, simply because you'd end up with too many
duplicates based on things already mapped which would make almost
impossible.

Are you suggesting to import all boundaries, or only certain kinds? What
tags would you use? I'm keen to see a more concrete plan of what you're
proposing. Property boundaries aren't in the default OSM style, not to say
that's any reason not to do this, but just something to keep in mind.

On one hand we're already snapping features like parks, landuse, and a
variety of amenity tags to the property boundaries (based on aerial
imagery), how would you reconcile what's in OSM already vs what you propose
to import?


> *VicMap Address:*
> https://discover.data.vic.gov.au/dataset/address-vicmap-address


Again, I think these would be useful, but again I'd like to see a well laid
out plan on the import. eg. resolving conflicts, avoiding duplicates. Then
there's consideration as to where the address be mapped, on a lone node, on
a building, on the amenity feature or all of the above?

What about addresses which don't exist on the ground, should these be in
OSM or not?

>
>    - I use OSM as a basemap and for network analysis, but I have not
>    contributed to OSM (I plan to do a small area of VicMap Property on my
>    street after this email using the ArcGIS OSM tools).
>
> I'd suggest you do some contributing to OSM first, to gain the mapper's
perspective, since you mentioned you've not contributed before. I think
this is important to have that understanding before thinking about an
import.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20190901/65427383/attachment-0001.html>