Rmap files in subdirectories

ppiter shared this idea 8 years ago
Completed

Locus store the maps in locusmaps directory. User can create subdirectory like locusmapsmymaps. Locus finds sqlite maps in this subdirectory but no rmap maps. I have a couple of rmap maps and I would like to organize them in subdirectories. Is it possible for locus to read rmap maps in subdirectory as well?


Thanks

Comments (11)

photo
0

@ppiter Question- Does Locus recognize your Rmaps in directory


locusmaps ,before you move them to locusmapsmymaps ?

photo
0

I`m sure it did ...


interesting idea. Workaround for this, is to create some directory with maps (and subdirectories) somewhere on card and define these directories in locus manually


Anyway I`m changing this topic to Idea, because it`s not an issue or bug in current locus version

photo
0

Hi Starman,


yes, Locus did recognize rmap before.

photo
0

Hi ppiter-


Curious. Did Menion`s suggestion work for you?

photo
0

yes, that would i need too

photo
0

yes, this would be great. I have a lot rmap files

photo
0

implemented

photo
0

thanks :)

photo
0

Seems to work nicely in latest testing version 2.5.1.9, but only for one subdirectory level. A map like /emcc/Maps/Europe/France/IGN-Provence.rmap is ignored. Personally, I think that one subdirectory level is enough. But I still wanted to mention it :)

photo
0

good you think it, because when not, I`ll have to decline it :)


One offtopic question, is pinch zoom and works with map (that contain some points & tracks) works faster then in last Pro version? Even if this is not hardware accelerated version, it should be much faster even on your phone

photo
0

I bet there will be other requests for multi-level sub directories in the future. We`ll all be carrying >100GB around pretty soon, so it does make sense to have the whole world in your pocket. And the whole world will not fit into one subdir level nicely :).


Anyway... regarding the offtopic-thingy: I am quite happy with general pinch & zoom performance now. It is snappy, even with a track visible. However... Locus still gets very slow (about 3 fps instead of >50 fps) when I have multiple tracks selected. For example, select 50 Tracks all over Europe and zoom your map to some place else. Even though all the tracks are very far away from visibility, they still slow down zooming/scrolling to a crawl.


I do not understand why offscreen tracks can have such an impact on performance. In theory, basic visibility checking should only be 1 to 4 integer comparisons. Those can happen in no-time, even without funky optimizations (eg sorting track list according to distance from map center or r-trees). Maybe something else gets in the way, like expensive database queries?


Also, I noticed that Locus really only uses one cpu core while scrolling and zooming. Can you do graphics in one thread and points/tracks in another maybe?