Search - no overlay of results?

Off-Track1234 · September 11, 2026, 06:41:50 AM

Has anyone else noticed that the capacity to show (mapforge poi) search results as a map overlay has been removed from OM 12.0.5 (NG)? It works for me in OM 7.4.28. In NG, the overlay icon at top-right does not even appear (tried with default profile - same result). Instead a user can select one result to show at map center (or create a user waypoint, or direct to); or we can select all - but do no more with them. It seems like this function is incomplete. Is it intended, or a bug?

Tronpo · September 11, 2026, 11:13:32 AM

Quote from: Off-Track1234 on September 11, 2026, 06:41:50 AMHas anyone else noticed that the capacity to show (mapforge poi) search results as a map overlay has been removed from OM 12.0.5 (NG)? It works for me in OM 7.4.28. In NG, the overlay icon at top-right does not even appear (tried with default profile - same result). Instead a user can select one result to show at map center (or create a user waypoint, or direct to); or we can select all - but do no more with them. It seems like this function is incomplete. Is it intended, or a bug?

On the contrary, it has improved. After doing the search and selecting that you want to show the operation valid. Then he will offer you his options to use as a superposition or as a track. Later with the overlay manager you can export the file

Off-Track1234 · September 11, 2026, 12:59:02 PM

Thanks Tronpo, I had to watch your video 6 times to work out the trick at the end - after "select all" click the tick symbol again!

So there is no bug, just no overlay symbol; and no instructions; so we need a bright soul like yours to tell us that now the tick does double duty and we must click it again later.

Maybe that is an improvement? In any case, it works like a dream once we know the trick. I wonder how many users will find it for themselves? Thanks for the demo.

IMHO the big/solid new (bigger and more solid OSM-like?) icons for search results get in the way at some zoom levels (the classic waypoint icons were better to show locations, as they were hollow and had a point at the location) but keep zooming in and they flick back and forth, then they are fine for location at high zoom.

Tronpo · September 11, 2026, 01:10:14 PM

Well, mine is more for proof and error than for innate intelligence.... You learn more from a mistake than from a thousand successes:) . If I agree, I already reported that the icons are very coasse, the size would have to be refined.

Off-Track1234 · September 12, 2026, 01:09:58 AM

And what could in OM 7.4.28 be done in 4 clicks (WPT > Search [some text] > Tick > Overlay) now (in OM 12.0.5) needs 8 clicks (WPT > Search Tools > Search [some text] > Tick > Menu > Select all > Tick > Overlay). The steep price of progress?

The new icons can be good. For example, search "fire" and fire stations will be distinct from other icons. But the icons are big and solid, so the locations are obscured at some zooms. A mixed blessing? Thanks for already reporting.

Tronpo · September 12, 2026, 08:42:01 AM

Quote from: Off-Track1234 on September 12, 2026, 01:09:58 AMAnd what could in OM 7.4.28 be done in 4 clicks (WPT > Search [some text] > Tick > Overlay) now (in OM 12.0.5) needs 8 clicks (WPT > Search Tools > Search [some text] > Tick > Menu > Select all > Tick > Overlay). The steep price of progress?

The new icons can be good. For example, search "fire" and fire stations will be distinct from other icons. But the icons are big and solid, so the locations are obscured at some zooms. A mixed blessing? Thanks for already reporting.

I see that you have not paid for the GP version prior to NG, the search already had these extra steps. You can add a button on the button panel if it is a tool of regular use for you, it gives you faster access saving some clicks

Off-Track1234 · September 13, 2026, 01:23:52 AM

A button in 12.0.5 would save the first 3 clicks, but for anyone who uses "hide buttons" to avoid map clutter it will add 2 clicks; so not much saving and still way behind 7.4.28 efficiency.

Of course 7.4.28 was not free, but donation; and (unacknowledged) donations were often much more than the "price" of versions via Google. Evidently not enough people donated.

Thanks for the reminder that GP is no better than NG. No point buying both from Google, much better to donate directly to the developer and hope he will recover some of the old features.

Tronpo · September 14, 2026, 08:04:33 AM

Quote from: Off-Track1234 on September 13, 2026, 01:23:52 AMA button in 12.0.5 would save the first 3 clicks, but for anyone who uses "hide buttons" to avoid map clutter it will add 2 clicks; so not much saving and still way behind 7.4.28 efficiency.

Of course 7.4.28 was not free, but donation; and (unacknowledged) donations were often much more than the "price" of versions via Google. Evidently not enough people donated.

Thanks for the reminder that GP is no better than NG. No point buying both from Google, much better to donate directly to the developer and hope he will recover some of the old features.

Hello everyone.
First of all, I'd like to make clear that my intention is not to start an argument

Over time I've seen that OruxMaps brings together very different types of users, and our developer tries to keep a balance so the app remains useful for everyone, which is not always easy.

That said, to access the offline POI search screen and perform a search, both version 7.4.28 and NG require the same number of steps.
The differences appear afterwards.

Version 7.4.28:
It allows working with a single node (create WP / show on map / go to) or with all nodes as a layer.
There are no further options: one or all.
This raises a practical question: what happens if a search returns 380 results and I only want to use 5?

Version NG:
1. Before searching, it allows switching the database if we don't want to use the current one.
2. After the search, it allows freely selecting how many results we want to use, selecting all, inverting the selection, or filtering by categories.
In my opinion, these options make handling the results much easier and allow optimizing the final layer the user wants to work with.
3. Possibility to perform a new search.
4. Display the results as a layer or over the active route, offering two different ways of use.

The developer has always shown willingness to improve the application, and I believe that presenting proposals focused on improving usability without removing features —and without harming other types of users— is the best way to move forward.

Would you be up for it?