Map search on destination coordinates

[lbo]

the "Select Circle" and "Select Polygon" options in the "Find" menu of the Map Panel should have a switch whether to use "camera coordinates" or "destination coordinates".

See the attached image of a track of aerial photography in an urban area. The camera position is not helpful to find the images showing a specific place.

I could try a coordinate filter specifying a rectangular area, but it's way more work to get the four coordinates.

Mario, if you point me to the right place, I can also try to modify the map app myself.

Oliver

[Mario]

Don't modify any of the standard apps. Your changes will be overwritten when the next IMatch update is installed.
You can clone/make your own map app in the user apps folder and then run it as a normal app in an app panel or as a dialog.

I'm not in the details of the map app or the integrated polygon search anymore at this time. There are separate implementations for Google and OSM because of different concepts.
The endpoint would be v1/search/geoarea but this endpoint does not support destination coordinates. To implement such a feature I would have to extend this endpoint and everything it uses internally. Add more options to the UI etc. Quite a bit of work, actually.

You can of course always perform your own search instead, retrieving the GPS data of the files you want to search in your app and then do the math on the destination coordinates instead of the standard coordinates.

You have placed this in General Discussion, but it sounds more like a feature request to me. Maybe you want to post a feature request? If there is more than one user who needs to search for destination coordinates, I can add an enhancement to the Map app. Telemetry tells me that not many users are currently working with destination coordinates so this is still a 'specialist' topic and feature.

[lbo]

Don't modify any of the standard apps. Your changes will be overwritten when the next IMatch update is installed.

You can clone/make your own map app in the user apps folder and then run it as a normal app in an app panel or as a dialog.

of course. I'm able to either to copy the app or to deal with (semi-automatic) patches.

I'm not in the details of the map app or the integrated polygon search anymore at this time. There are separate implementations for Google and OSM because of different concepts.
The endpoint would be v1/search/geoarea but this endpoint does not support destination coordinates.

That's too bad. I hoped it would be possible just to switch some variable names.

You have placed this in General Discussion, but it sounds more like a feature request to me. Maybe you want to post a feature request?

Yup, since it seems to be hard to do it myself, I posted now a request in "Feature Requests".

If there is more than one user who needs to search for destination coordinates, I can add an enhancement to the Map app. Telemetry tells me that not many users are currently working with destination coordinates so this is still a 'specialist' topic and feature.

I have addressed this issue in my proposal.

Finding the right images in my growing archive was the main reason chosing IMatch. For geocoding, the IMatch Map Panel is much more powerful than Geosetter. I can chose among three data sources, more map styles etc.

An anecdote on the sidelines: JEITA's original intention of "dest" coordinates likely was not to indicate the coordinates of the object shown but the destination coordinates programmed in a navigation system. But MWG decided to (ab)use this field as "Location Shown" coordinate (strange idea, isn't it?). I'm much more happy with the MWG idea.

Oliver