Instead of downloading a specific GeoJson file manually from data grand lyon, we could simply point to the equivalent data GrandLyon homepage page instead. We then should be able to programaticaly find a compatible datasource if any (via API if there is one or with custom logic if required).
The provide URL could also beside the dataset description (on the about page) as the "data source" accessible by a human.
Interesting suggestion, which will make life easier for our users (even if the process is not that complicated).
I especially see an interest in the reference to the data page in the "About"
Instead of downloading a specific GeoJson file manually from data grand lyon, we could simply point to the equivalent data GrandLyon homepage page instead. We then should be able to programaticaly find a compatible datasource if any (via API if there is one or with custom logic if required). The provide URL could also beside the dataset description (on the about page) as the "data source" accessible by a human.