[Talk-GB] NaPTAN and ODbL

[Peter Miller]

On 3 April 2012 10:26, Andy Robinson <ajrlists at gmail.com> wrote:

> Peter, re NapTAN the only scenario I can see that might need checking
> would be a decliner who has merged a NaPTAN node with an existing bus stop
> for instance and all the data now is on a node to be deleted (or at least
> part amended)  rather than the original NaPTAN node.
>

Thanks Andy. Not fussed by the odd loss. My main concern was that someone
somewhere was currently busy removing every bus stop from the UK from OSM
because the wiki was out of date!

Fyi, we are about to add some new tools to ITO Map to allow people to
compare the positions of bus stops in OSM between current NaPTAN data and
OSM and also to highlight where stops are missing, duplicated or are
missing ATCO codes etc.


Regards,



Peter


> ****
>
> ** **
>
> Cheers****
>
> Andy****
>
> ** **
>
> *From:* Peter Miller [mailto:peter.miller at itoworld.com]
> *Sent:* 03 April 2012 10:20
> *To:* Talk-GB at openstreetmap.org
> *Subject:* [Talk-GB] NaPTAN and ODbL****
>
> ** **
>
>
> I received an email a few days ago from a contributor asking if the NaPTAN
> dataset was compatible with ODbL. It is, and it is now available from
> data.gov.uk using an Open Government License. The wiki page was very
> out-of-date and I have now updated the wiki. I have seen no evidence or
> suggestion that any NaPTAN data would be removed from OSM during the switch
> over. Are we safe on that?
>
> Also... for clarification, the OS Locator tiles from ITO say 'ccbysa',
> however people can read that as 'OGL' or equivalent and I can confirm that
> it is compatible with ODbL. We originally used ccbysa on the tiles because
> the service was introduced prior to OGL being finalised and before the OSM
> switch over to ODbL was very serious. We will update the text at a suitable
> time.
>
>
> Regards,
>
>
>
> Peter Miller
> ITO World Ltd
>
>
>
>  ****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-gb/attachments/20120403/d239acf5/attachment.html>