[talk-au] vicmap data licensing

[Ian Sergeant]

I see there are two ways we can approach this.  One is to make the
data available in OSM form.  People can use information to
trace/import to complete the map as they go about their daily mapping.

Secondly, we can have a complete plan as to how we import bits that we
know come from good sources and should complement/replace existing OSM
data.

If we import LGA and postcodes, we immediately need to consider things
like what happens when these align with coastlines, or with each
other, or with suburb boundaries?  Probably other things too.

Worst case is, as has been done on some occasions in the past, is for
the import to be done and to leave hundreds of thousands of "fixmes"
scattered around the country.

Ian.



On 14 October 2013 08:21, Nyall Dawson <nyall.dawson at gmail.com> wrote:
> Maybe a good approach would be to start with the easy things first. It
> should be quite straightforward to import the boundary information like
> postcodes and LGA borders. Unless I'm mistaken, these boundaries are
> basically non-existent in Victoria OSM at the moment.
>
> Property boundaries would be another good candidate like this - there should
> be very little existing information we'd need to worry about.
>
> Nyall
>
>
>
> On 11 October 2013 07:37, Li <me at lixia.co> wrote:
>>
>> Does anyone have experience on importing data? In particular avoiding
>> duplicates?
>>
>> Li.
>>
>> On 10 Oct 2013, at 5:16 pm, Ben Kelley <ben.kelley at gmail.com> wrote:
>>
>> Hi.
>>
>> I guess the thing to consider is how you would handle a second import if
>> someone had edited the data in OSM in between.
>>
>> I think this kind of conflict would be very difficult to resolve. You
>> could either plan to do a 1-off import, or maybe include a tag on the
>> imported data matching a unique identifier for the same feature in the
>> vicmap data. The US Tiger import did something like this.
>>
>>   - Ben Kelley.
>>
>> On 10 Oct 2013 17:12, "Li Xia" <me at lixia.co> wrote:
>>>
>>> Hi everyone,
>>>
>>> I'm meeting Vicmap and data.gov staff tomorrow to get their blessing on
>>> importing vicmap data into OSM.
>>>
>>> Once the licensing is squared away, we can move onto discussing
>>> techniques of importing the data. "Snapshot" data in shp format is available
>>> from data.vic.gov.au. Alternatively a vicmap provides a live feed to weekly
>>> data diffs directly. Any advice on how to import this data is much
>>> appreciated.
>>>
>>> Li
>>>
>>> _______________________________________________
>>> Talk-au mailing list
>>> Talk-au at openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-au
>>>
>>
>> _______________________________________________
>> Talk-au mailing list
>> Talk-au at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-au
>>
>
>
> _______________________________________________
> Talk-au mailing list
> Talk-au at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au
>