Problem with map repositioning
I actually noticed this ages ago and forgot - but now I finally get around to write it down here:
I have an offline map in OruxMaps format (it's Switzerland) and a track, which is outside of what the offline map contains (Japan, to be precise).
To start, I centered Locus some place within the map. Now I go to Tracks, choose the track and tap its icon - which jumps to the location of the track. As expected, there is no map shown there, but surprisingly also no track. Now I change the map to one that includes the whole world (e.g. just switch to Google Maps) - and I see why: I'm not in Japan, but somewhere in Iran.
This doesn't happen when coming from a Vector map of Switzerland. Something seems to be messed up with Locus' location calculation.
The same problem 
Hello Ingo,
oki, fine. Please tell me how should I test and fix something like this when i don't have problematic map and even not a problematic track? :)
Anyway ... all maps needs to be placed from 3D earth into 2D paper. This is called projection. Most of global maps use some global projection for a whole world. Negative of such global projection is deformation of map - what you see is not how it looks in real - more global projection = worst deformation - when I tell it simply.
So it is highly probable, that your offline map use some local projection. This cause, that map should be really precise, but away from area where is projection defined, deformation may grow to really huge numbers. And because Japan is far away from Europe, deformation may be huge and it's close to impossible to compute logical coordinates for your track.
Solution for this? Hmm ... can image in best case just a warning, that track is out of range of map projection. Not sure anyway, if it will be always possible compute this correctly. We may try it if you wants.
Hello Ingo,
oki, fine. Please tell me how should I test and fix something like this when i don't have problematic map and even not a problematic track? :)
Anyway ... all maps needs to be placed from 3D earth into 2D paper. This is called projection. Most of global maps use some global projection for a whole world. Negative of such global projection is deformation of map - what you see is not how it looks in real - more global projection = worst deformation - when I tell it simply.
So it is highly probable, that your offline map use some local projection. This cause, that map should be really precise, but away from area where is projection defined, deformation may grow to really huge numbers. And because Japan is far away from Europe, deformation may be huge and it's close to impossible to compute logical coordinates for your track.
Solution for this? Hmm ... can image in best case just a warning, that track is out of range of map projection. Not sure anyway, if it will be always possible compute this correctly. We may try it if you wants.
Hi Menion!
Yeah, I know - the reason is, I could've shared the track, but the map in question is >7G...
I was just thinking there is perhaps a general problem with OruxMaps maps or the like. I wasn't aware of the computational problems (well, I know it's not simple, but I expected it to be independent of the map used, as it's just tiles...).
So with your explanation I'm fine and you can close this.
Thanx!
Hi Menion!
Yeah, I know - the reason is, I could've shared the track, but the map in question is >7G...
I was just thinking there is perhaps a general problem with OruxMaps maps or the like. I wasn't aware of the computational problems (well, I know it's not simple, but I expected it to be independent of the map used, as it's just tiles...).
So with your explanation I'm fine and you can close this.
Thanx!
Thanks for understanding. What you wrote generally IS a problem, because Locus should handle it better (maybe some notification to user that content on a map is out of map range, or something like this).
Anyway it's little bit complicated to compute some logical value what is already out of map bounds and what isn't. Hope this want happen to often to You or other users :).
Thanks for understanding. What you wrote generally IS a problem, because Locus should handle it better (maybe some notification to user that content on a map is out of map range, or something like this).
Anyway it's little bit complicated to compute some logical value what is already out of map bounds and what isn't. Hope this want happen to often to You or other users :).
Replies have been locked on this page!