OpenAtlas

Since a georeferenced image should always use the same coordinates, maybe it is better to store somehow the coordinates directly linked to the image, and each entity which is linked to that image uses automatically the coordinates. For entities without map, this wouldn't change anything, and for entities with map it is most likely the wanting behavior.

Yes, the possibility to use GeoTIFFs (https://www.ogc.org/standard/geotiff/) might be a partial solution. However, from former conversations with Stefan I recall, that that might be difficult to do, also, already uploaded images would still face this problem. Or do you already have a solution in mind?

• image_id
• place_id
• link_id
• bounding_box

We could remove place_id and link_id to make this information independent from a place and also make image_id unique just to be save.
Regarding existing data, because image_id should now be unique but there might be already multiple entries (for different places) I would suggest to just take the first entry and delete all others because they should be the same anyway.

• Write an SQL update script for web.map_overlay
  • Remove place_id and link_id
  • Delete multiple image_id (keep one)
  • Make image_id unique
• Adapt views to use overlay if overlay data is available (and is enabled in profile)
• Adapt links and views to set/change overlay data (place_id is still needed for navigation to redirect back to the place view)

Sorry, I didn't mean in the image, because reading GeoTIFFs would be another big feature. Yesterday I had no further time to explain it.

• Link image 1 to place 1
• Set overlay coordinates at place 1
• Link image 1 to place 2
• Set overlay coordinates at place 2
• Link image 1 to place 3
• Set overlay coordinates at place 3

• Link image 1 to place 1
• Set overlay coordinates at place 1
• Link image 1 to place 2 (image 1 automatically an overlay)
• Link image 1 to place 3 (image 1 automatically an overlay)

• Upload image 1
• At image detail view, click a button "Set coordinates"
• Set coordinates
• Link image 1 to place 1 (image 1 automatically an overlay)
• Link image 1 to place 2 (image 1 automatically an overlay)
• Link image 1 to place 3 (image 1 automatically an overlay)

In the database, we can drop the columns place_id and link_id from web.map_overlay, since the link is enough.

Yes, I missed that we can drop the link_id too (I edited my former comment accordingly) but would argue to leave the view location as is (your first approach).
It would be less rewriting, users are already familiar with this workflow and I think it is more accessible/needed at the place view anyway.

Bernhard Koschiček-Krombholz wrote in #note-7:

I'm currently working on it and it looks promising.
Since all duplicated entries will be deleted, we checked your data and it looks good. Only one file has an issue, that the coordinates are not the same for all the linked places:
https://thanados.openatlas.eu/entity/198570
@Roland Filzwieser can you resolve this issue?

SQL to detect duplicate entries with different coordinates:
[...]

It should be resolved. All four linked places had basically the same coordinates, only one had more decimal places than the others. An excellent example for a possible issue with this, that is now resolved ;)

That is nice, thank you.
I will update Thanados next week. Because it involves a database upgrade, I need to approve, that everything will be fine with your presentation sites.

Thanados is updated.