Re: [OSM-talk-be] Importing Villo! API data

2017-11-05 Thread CedB12
Hi Glenn, I will respond to some of your points because they are relevant to my contributions in this thread. At the end of this email I also comment on a survey I made today of six stations in order to evaluate the quality of the API data. As far as I can tell from my survey, the station names

Re: [OSM-talk-be] Importing Villo! API data

2017-11-04 Thread CedB12
Hello again, Sorry for taking so much time after my last message. I guess I can now share a concrete proposal for name tag changes to continue the discussion. I have put everything in a few different formats in the following repository: https://github.com/cedb12/villo-names My main

Re: [OSM-talk-be] Importing Villo! API data

2017-10-17 Thread CedB12
Hello Yves, Thank you for sharing your thoughts. I agree with you on the problem of importing locations in bulk. Still, I think it is safe to use the API data to clean up the names and reference numbers of the stations we have already mapped. As far as I know, the API "name" values match

[OSM-talk-be] Importing Villo! API data

2017-10-15 Thread CedB12
Hello all, Lately I have been looking at the Villo! dataset from the JCDecaux API at [1], which is released under the Etalab Open License (see also [2]). I want to consult the community about the use of this data to improve the tagging of the stations we have already mapped. I would also like to