![]() |
Re: WhoGo Maps
Quote:
|
Re: WhoGo Maps
Quote:
Quote:
|
Re: WhoGo Maps
Quote:
|
Re: WhoGo Maps
Quote:
We would have to think about how much time we should invest into Mapbox QML if "Developer offering will see many improvements in 2018-2019. We are planning to open Qt Location after Qt upgrade 5.9" [http://www.merproject.org/logs/%23me...4-19T08:13:56] will happen. I don't mind maintaining and developing QML bindings further, but then it has to be used by applications. Right now, QML Mapbox bindings are relatively "easy" to maintain, although there are some issues filed that will have to be addressed. Adopting new gesture area would be somewhat harder and this work will have to be weighted against the time it will be used. In this sense, we would have to compare APIs and think what will be used in 2019. In addition to APIs, there are differences in update paths and control that is possible to get over it, but looks like Qt is making a major exception and making significant updates in Mapbox component in stable releases and Mapbox is developing within Qt 5.9 as well. |
Re: WhoGo Maps
I see two-finger rotation as a nice to have thing, but not really all that relevant, or relevant only in rare use cases, so if it looks like a lot of work, it's likely not worth the trouble. And if there is indeed an up-to-date Mapbox GL in SFOS 3, I'll likely switch to that, but that depends on the details and remains to be seen.
|
Re: WhoGo Maps
5 Attachment(s)
Quote:
Before: Attachment 39878 After (it looks like I took the shot before the map fully rendered, sorry about that): Attachment 39879 After, once the navigation started: Attachment 39880 I am also attaching the patch file (rremove the txt extension) and the RPM if anyone is interested. Install manually and then enable or disable in Patchmanager. I am not uploading it in Warehouse just yet. |
Re: WhoGo Maps
1 Attachment(s)
A funny observation. As mentioned earlier, I had some surprising routing results. So I tried it again, to route me to Edinburgh. It's not like there are dozens of them to choose from. But, surprise surprise, I got routed somewhere completely off:
Once I zoomed in, it turned out I got routed to a Duke of Edinburgh pub in a village on the other side of the country. To confirm, I tried Search and indeed, I got a list of results with said pub right at the top, so it looks like in ambiguous search results, a) the list is not ordered in any meaningful way (e.g. by relevance) b) the app just picks the first item from the list as the destination. I found that the solution was to search for ", , Edinburgh", to follow the "<house number>, <street>, <town>" format with the first two entries empty. Now I see why commercial satnavs want you to enter the town, street and house number as separate entries ;) I also had a few OOM issues when I was trying to route to a location half of Europe away. Some of them so serious that any application I tried starting afterwards was killed instantly. The only remedy was a reboot. Come to think of it, that sounds more like the server problem: WhoGo was killed but the server still kept the memory allocated, not leaving enough for anyone else. The last question, how can I navigate to given geo coordinates? I tried for example "geo:55.149,-3.189" but received "no search results". |
Re: WhoGo Maps
I wonder how difficult would it be to use some sort of heuristics to order the hitlist with better relevancy?
Do the search results include some sort of description of the target; if so, then it would make sense to value a city over a shop for example. |
Re: WhoGo Maps
Quote:
But I think it could be even simpler than that. If you type in a single entry (for example "Frankfurt am Main", to give an example of a single entry that is not a single word), assume that it is a town. So the app can do the ", ," conversion automatically. |
Re: WhoGo Maps
Quote:
|
All times are GMT. The time now is 21:26. |
vBulletin® Version 3.8.8