Skip to content

Add latest Geneva orthophoto (2024) (4cm)#2905

Open
alkino wants to merge 4 commits into
osmlab:gh-pagesfrom
alkino:new_geneva
Open

Add latest Geneva orthophoto (2024) (4cm)#2905
alkino wants to merge 4 commits into
osmlab:gh-pagesfrom
alkino:new_geneva

Conversation

@alkino

@alkino alkino commented Feb 15, 2026

Copy link
Copy Markdown
Contributor

This ortho has been published in 2026.
This is the best we got: 4cm !!!
Geneva is a city surrounded by France. So for this version (and the previous one) they worked with French services (IGN) so the imagery does not stop at the border!

{
"type" : "Feature",
"properties" : {
"license_url" : "https://ge.ch/sitg/media/sitg/files/documents/conditions_generales_dutilisation_des_donnees_et_produits_du_sitg_en_libre_acces_-_revision_09.2020.pdf",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that the correct link? For me it just redirects to https://sitg.ge.ch/

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm unable to find a proper URL for license.
It is written "Accès libre" (free access), with the definition of what it means in the following "privacy policy url"

@simonpoole

Copy link
Copy Markdown
Contributor

This should likely get the best flag set to true.

The swisstopo imagery was last updated in 23/24 so we should revisit that towards the end of the year/early 27 as then swisstopos three year cycle would indicate that they will have new coverage for Geneva.

@alkino

alkino commented Mar 25, 2026

Copy link
Copy Markdown
Contributor Author

This should likely get the best flag set to true.

The swisstopo imagery was last updated in 23/24 so we should revisit that towards the end of the year/early 27 as then swisstopos three year cycle would indicate that they will have new coverage for Geneva.

Done

@andrewharvey

Copy link
Copy Markdown
Collaborator

Looks good, but I'm finding it hard to determine if the license is compatible, since as part of the review, we need to verify each added source can be used to derive features for OSM, I can see from https://sitg.ge.ch/actualites/nouvelle-orthophoto-du-canton-de-geneve-mars-2024 that it is under "Accès libre" per https://sitg.ge.ch/ressources/conditions-utilisation-donnees

It seems to be listed at https://wiki.openstreetmap.org/wiki/Switzerland/Datasources as compliant, but it doesn't really say why, only pointing out an agreement was obtained, but no link to the agreement, and the mailing list link being broken. http://lists.openstreetmap.ch/pipermail/talk-ch/2014-February/002580.html

@simonpoole If you have any thoughts on how we can improve the situation regarding validating license approvals as part of the PR reviews, I'm keen to hear.

@alkino

alkino commented Apr 18, 2026

Copy link
Copy Markdown
Contributor Author

What can we do? All the previous version are already added and have the same license.

@simonpoole

simonpoole commented Apr 20, 2026

Copy link
Copy Markdown
Contributor

https://wiki.openstreetmap.org/wiki/SITG_WMS would indicate that using the imagery is permitted, which has been my understanding for a long time. That seems to have been added by @rbuffat BTW. I've checked my personal mail archive and the one on lists.openstreetmap.ch and couldn't find a smoking gun, but IMHO the wiki entry would seem to be good enough.

As everything on openstreetmap.ch is run by a private individual it isn't particularly good as an archive of important documents, so a lot of the old stuff might vanish just like that. In any case @andrewharvey I've long suggested (long as starting with the pre-licence change work) that how we document permissions, contacts and terms for 3rd party sources is completely broken, see for example https://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2017/Project_Ideas#Third_Party_Source_Management_System_2 for a better way.

@andrewharvey

Copy link
Copy Markdown
Collaborator

In any case @andrewharvey I've long suggested (long as starting with the pre-licence change work) that how we document permissions, contacts and terms for 3rd party sources is completely broken, see for example https://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2017/Project_Ideas#Third_Party_Source_Management_System_2 for a better way.

Completely agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants