Use ODbL licenced data from Rivermap

[tim-lloyd]

I suggest not using the map interface file. We will change it eventually.
It would be better to use the licenced data extract files intended for the purpose.
https://www.rivermap.ch/public/ODBL/extract.json
https://www.rivermap.ch/reuse.php

[fparrel]

Thanks for your remark, a clear license is better than juridical blur of screen-scraping. I will modify it when I resume with this project, probably during Christmas holidays. Regards

…

On Tue, Dec 15, 2020 at 8:50 PM tim-lloyd ***@***.***> wrote: I suggest not using the map interface file. We will change it eventually. It would be better to use the licenced data extract files intended for the purpose. https://www.rivermap.ch/public/ODBL/extract.json https://www.rivermap.ch/reuse.php — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEUOY4HJUSAP6KFLJJ2BCTSU64ZNANCNFSM4U44HKSA> .

-- http://outofoffice.regepe.com

[fparrel]

Hello, I've written a new importer: e70a911#diff-da3f23426fcadd3d6f1a6e7c5416f74339b44c909655414ee8dcabbd4415355f
But I have an issue about the waterflow stations, in your exported data, there is just an uuid. Is there anyway to get the URL of the station?

[tim-lloyd]

The station information is not in the ODbL extract because we don't regard it as 'our' information to set licence terms. We do make the station information available via an api. There we document the sources and any licence terms if we know of. Please email the project to request an api key and documentation. It may be useful to know that not all source water authorities provide linkable station pages. But where we know them, the information is in the api. Also, you should expect the urls to change from time to time. We have about 50+ sources and there is always something going on. Cheers /T

…

On Thu, 21 Jan 2021 at 16:16, fparrel ***@***.***> wrote: Hello, I've written a new importer: e70a911 #diff-da3f23426fcadd3d6f1a6e7c5416f74339b44c909655414ee8dcabbd4415355f <e70a911#diff-da3f23426fcadd3d6f1a6e7c5416f74339b44c909655414ee8dcabbd4415355f> But I have an issue about the waterflow stations, in your exported data, there is just an uuid. Is there anyway to get the URL of the station? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB7XCFU4SPLVXXRLQNAPMH3S3BAOTANCNFSM4U44HKSA> .

[tim-lloyd]

More simply, we could consider providing a service to translate a uuid into a station page. I'm not sure and it depends what you need. Contact me privately to discuss this.

…

On Thu, 21 Jan 2021 at 16:56, Tim Lloyd ***@***.***> wrote: The station information is not in the ODbL extract because we don't regard it as 'our' information to set licence terms. We do make the station information available via an api. There we document the sources and any licence terms if we know of. Please email the project to request an api key and documentation. It may be useful to know that not all source water authorities provide linkable station pages. But where we know them, the information is in the api. Also, you should expect the urls to change from time to time. We have about 50+ sources and there is always something going on. Cheers /T On Thu, 21 Jan 2021 at 16:16, fparrel ***@***.***> wrote: > Hello, I've written a new importer: e70a911 > #diff-da3f23426fcadd3d6f1a6e7c5416f74339b44c909655414ee8dcabbd4415355f > <e70a911#diff-da3f23426fcadd3d6f1a6e7c5416f74339b44c909655414ee8dcabbd4415355f> > But I have an issue about the waterflow stations, in your exported data, > there is just an uuid. Is there anyway to get the URL of the station? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#1 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB7XCFU4SPLVXXRLQNAPMH3S3BAOTANCNFSM4U44HKSA> > . >