[OSM-talk] FW: [EXTERNAL] Re: ODbl concerns

Thu Aug 24 02:18:58 UTC 2023

Thank you John for your correspondence.

We are going through a similar journey.

Are you able to share how the OSM community accepted that their data could be used and then offered for public use under a different licence arrangement without the need to "Share-alike"?
Also are you able to provide clarity on what your role is in negotiating this understanding?

Thank you again in advance for your contribution and engagement.

Kind regards,
George

George Boulos
DTP Data Governance Manager
Strategy - Mobility and Insights - Policy, Precincts and Innovation
Department of Transport & Planning
Level 4, 1 Spring Street
Melbourne, VIC  3000
M: +61 (0)428 470 301
George.Boulos at roads.vic.gov.au<mailto:George.Boulos at roads.vic.gov.au>
transport.vic.gov.au<https://transport.vic.gov.au/>
[cid:image001.png at 01D9D0FB.5CE23E80]

________________________________
From: john whelan <jwhelan0112 at gmail.com<mailto:jwhelan0112 at gmail.com>>
Sent: Monday, 3 July 2023 10:26 AM
To: Robert C Potter (DTP) <Robert.Potter at roads.vic.gov.au<mailto:Robert.Potter at roads.vic.gov.au>>
Cc: OpenStreetMap talk mailing list <talk at openstreetmap.org<mailto:talk at openstreetmap.org>>
Subject: [EXTERNAL] Re: [OSM-talk] ODbl concerns

If you are releasing data under an open government license then .odbl etc shouldn't come into it.

Have a look at the Canadian Federal government license 2.0

https://open.canada.ca/en/open-government-licence-canada<https://urldefense.com/v3/__https://open.canada.ca/en/open-government-licence-canada__;!!C5rN6bSF!G2U6Zb2seMiuNJs_FPf8peH3kbw_V9vrfuT-k_JX_EqAy3V9uDNyeVpGKdcL1u_uGXsKeWmOqzoEBE27J2c6xfLouWXR-KVz$>

This took a number of years to thrash out and has been formally accepted by OSM etc.

Cheerio John

On Sun, Jul 2, 2023, 20:13 Robert C Potter (DTP) via talk <talk at openstreetmap.org<mailto:talk at openstreetmap.org>> wrote:
Hi OSM,

Representing the state transport authority (Department of Transport and Planning) we have made the strategic decision to use OSM as our foundational mapping data source.  We are confident that this is a decision will be of value to both ourselves improving the management of the networks (road, Train, Bus, tram) and adding significantly to the citizens of the state.

Our intended use of OSM is built on an extract being done then validating that extract for the gazetted/official place and road names. The resultant validated dataset will be shared that via our Opendata portal.  Our state government has a strong commitment to sharing all data openly.  We are currently developing that process and should be in production by the end of the year.

Alas, there has been concern from our distribution partners with the ODbl license requirement to "Share alike".  You know these companies; Google, Here, Tomtom and Apple.

The information we would share, and all shared as ODbl;

  *   Disruptions
  *   Heavy vehicles
  *   Bicycles routes
  *   Public transport routes and timetables
I am wondering how we, can continue engage with these partners and use and improve OSM.

If you have any further queries, please do not hesitate to contact me.

Regards,

Robert Potter

Helping people use the power of location to make better decisions

Manager, Spatial Data Strategy
Department of Transport and Planning

1 Spring Street

MELBOURNE 3000

M 0402 484 739

F 03 9935 4111
E Robert.Potter at roads.vic.gov.au<mailto:Robert.Potter at roads.vic.gov.au>
W dtp.vic.gov.au<http://dtp.vic.gov.au/>
[cid:16f05bdc-8c23-42fb-9db6-2304edffd042]

I acknowledge the Traditional Aboriginal Owners of Country throughout Victoria and pay my respect to Elders past and present and emerging and to the ongoing living culture of Aboriginal people.

DISCLAIMER

The following conditions apply to this communication and any attachments: VicRoads reserves all of its copyright; the information is intended for the addressees only and may be confidential and/or privileged - it must not be passed on by any other recipients; any expressed opinions are those of the sender and not necessarily VicRoads; VicRoads accepts no liability for any consequences arising from the recipient's use of this means of communication and/or the information contained in and/or attached to this communication. If this communication has been received in error, please contact the person who sent this communication and delete all copies.
_______________________________________________
talk mailing list
talk at openstreetmap.org<mailto:talk at openstreetmap.org>
https://lists.openstreetmap.org/listinfo/talk<https://urldefense.com/v3/__https://lists.openstreetmap.org/listinfo/talk__;!!C5rN6bSF!G2U6Zb2seMiuNJs_FPf8peH3kbw_V9vrfuT-k_JX_EqAy3V9uDNyeVpGKdcL1u_uGXsKeWmOqzoEBE27J2c6xfLoue1oyxqE$>

DISCLAIMER

The following conditions apply to this communication and any attachments: VicRoads reserves all of its copyright; the information is intended for the addressees only and may be confidential and/or privileged - it must not be passed on by any other recipients; any expressed opinions are those of the sender and not necessarily VicRoads; VicRoads accepts no liability for any consequences arising from the recipient's use of this means of communication and/or the information contained in and/or attached to this communication. If this communication has been received in error, please contact the person who sent this communication and delete all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20230824/a0dada2b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10375 bytes
Desc: image001.png
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20230824/a0dada2b/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-mvfhf5xf.png
Type: image/png
Size: 13028 bytes
Desc: Outlook-mvfhf5xf.png
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20230824/a0dada2b/attachment-0003.png>