Bílý vrch
icon TrekBuddy
www.trekbuddy.net
Outdoor companion.
  • internal / bluetooth / simulator GPS
  • offline raster maps
  • smart GPX / raw NMEA logs
  • waypoints and simple navigation
  • custom views
  • MIDP and Symbian phones
  • Blackberry
  • Android
Visit wiki to see all features, guides and howtos. Project tracker.
Trekbuddy is on Github now

Partners:    (Polish/Polski)(Polski) Compass mapy      (Polish/Polski)(Polski) Galileos mapy      (Polish/Polski)(Polski) CartoMedia      (Czech/Èesky)(Èesky) Eaglesoft trasy      (Polish/Polski)(Polski) ExpressMap     

 FAQFAQ   SearchSearch   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
zooming of maps
Goto page Previous  1, 2, 3, 4, 5, 6, 7  Next
 
Post new topic   Reply to topic    TrekBuddy Forum Index -> WishList
View previous topic :: View next topic  
Author Message
kruch
Site Admin


Joined: 02 Jul 2006
Posts: 5676

PostPosted: Mon Mar 05, 2012 11:12 pm    Post subject: Reply with quote

Ranger wrote:
Probably flag to zoom in or not should be set for all maps in layer one time and removed for all too.


I agree. It should work well for atlases created as they were meant to be, where a layer is a set of maps with the same scale and dpi.
Back to top
View user's profile Send private message
billy06



Joined: 01 Oct 2008
Posts: 434
Location: Lowestoft U.K

PostPosted: Mon Mar 05, 2012 11:46 pm    Post subject: Reply with quote

works very well Very Happy
_________________
Nexus 5X, Nexus 5, Nexus 7 3G, HTC Sensation, nokia 5800. web:www.thetrekbuddies.co.uk . Twitter:http://twitter.com/TheTrekbuddies
Back to top
View user's profile Send private message Visit poster's website
Ranger



Joined: 12 Dec 2006
Posts: 6030

PostPosted: Tue Mar 06, 2012 12:23 am    Post subject: Reply with quote

kruch wrote:
I agree. It should work well for atlases created as they were meant to be, where a layer is a set of maps with the same scale and dpi.

Maybe it should be for all layers too. If ie layer 1:100k is zoomed in, it have scale 1:50k, so it is possible to have order of scales inverted for next not zoomed 1:75k layer, etc.
Back to top
View user's profile Send private message
guest



Joined: 08 Oct 2006
Posts: 5032

PostPosted: Tue Mar 06, 2012 10:04 am    Post subject: Reply with quote

Ranger wrote:
There are two problems to solve.
First is to have map readable at all from different sources - for such think rather Desktop setting with initial magnification factor is better think (to have map rescaled to 100% of screen ppi or near from natural map picture ppi).
Zooming map itself is just different think, ie to have some predefined factors like 75%, 125%, 150% etc, depending on kind of zooming possible (if any is).
So another desktop setting - use available map zooms first in layer and next switch layer in repeated model (means use both) is an usage option too. This way keys 7/9 will work almost the same way, only depending on desktop settings.
Layer selection from list is still usable when many of them are in atlas for fast jump to another scale or map type.
Fire short push is now rather used to synchronize gps position, can be a bit confusing if instead of that map scale will jump ...



Hi Ranger,
I am sorry, but there is no need for any calculation from "map ppi" to "display ppi"
The correlation map to display is very simple:
1 pixel of map = 1 pixel of display.
On high resolution screens you get a sharp, but small picture and thats the problem.
to zoom it, you have to multiply every pixel by an integer e.g. x2 x3 x4 ....
e.g. x 2: every map pixel results in 4 screen pixels (both dimensions).

Other zoom factors ar not possible (on an easy manner), because there are no "broken" pixels possible.

thats why kruch has now implemented a factor of 2, what in most cases is the best compromise.

Very Happy Very Happy Very Happy Thank you kruch !!! Very Happy Very Happy Very Happy
Back to top
View user's profile Send private message Visit poster's website
Ranger



Joined: 12 Dec 2006
Posts: 6030

PostPosted: Tue Mar 06, 2012 10:11 am    Post subject: Reply with quote

Yep,
So as explanation three samples showing what is good and wrong in map zooming Smile
First sample shows what some apps are trying to do (from 1:100k to 1:200k and 1:50k)
Maps are unreadable or over-readable if zoomed too much Wink
Second one shows what zooming shouldn't do (from 1:100k to 1:50k vs true 1:50k map), exception is ppi changing.
Generalization is better think than zooming.
Last one shows what zooming just can't do (atlas of maps 1:100k, 1:75k, 1:50k) Smile
I propose to implement precise magnification factor for systems where it is possible for ppi correction and just simple one for others Smile



TrekBuddy_no_zooming.png
 Description:
 Filesize:  154.67 KB
 Viewed:  11218 Time(s)

TrekBuddy_no_zooming.png



TrekBuddy_zooming.png
 Description:
 Filesize:  145.62 KB
 Viewed:  11218 Time(s)

TrekBuddy_zooming.png



Locus_zooming.png
 Description:
 Filesize:  148.78 KB
 Viewed:  11218 Time(s)

Locus_zooming.png


Back to top
View user's profile Send private message
guest



Joined: 08 Oct 2006
Posts: 5032

PostPosted: Tue Mar 06, 2012 2:59 pm    Post subject: Reply with quote

works really great with nokia 5230 !! Very Happy Very Happy
Back to top
View user's profile Send private message Visit poster's website
guest



Joined: 08 Oct 2006
Posts: 5032

PostPosted: Wed Mar 07, 2012 10:03 pm    Post subject: Reply with quote

Ranger wrote:
Yep,
So as explanation three samples showing what is good and wrong in map zooming Smile
First sample shows what some apps are trying to do (from 1:100k to 1:200k and 1:50k)
Maps are unreadable or over-readable if zoomed too much Wink
Second one shows what zooming shouldn't do (from 1:100k to 1:50k vs true 1:50k map), exception is ppi changing.
Generalization is better think than zooming.
Last one shows what zooming just can't do (atlas of maps 1:100k, 1:75k, 1:50k) Smile
I propose to implement precise magnification factor for systems where it is possible for ppi correction and just simple one for others Smile


We have to distimguish between the best solution without any restrictions and what is possible .

an ideal solution could be:
continues zooming in or zooming out (say in 1% steps from 25 to 300%) by holding a key pressed until the view is reached, that a user decides its the best for himself.
Every setting is saved for each map and restored at the next use of this map even at restart of the program.

additional a presetting somewhere in settings, for a reasoable start condition
settable from 25 % to 300% with 1% resolution.

But thats illusion.

In reality we have hardware and software restrictions who s not allow that all.
Furthermore there are many different platforms and systems with much different capabilities and trekbuddy should work on all of them.

However, a zoom of pixelbased map cannot replace a change to a higher mapzoom e.g. 14 to 16 because the more details of the higher level. what you promised in another post ("more views, less maps"....)

I am sure, kruch is aware of all that and makes the best possible solution.

At the moment I am very happy with the implementation of the x2 zoom.
Back to top
View user's profile Send private message Visit poster's website
kruch
Site Admin


Joined: 02 Jul 2006
Posts: 5676

PostPosted: Wed Mar 07, 2012 10:33 pm    Post subject: Reply with quote

A bit improved implementation over the existing will be:

- config option for default prescale option from 1 to 3 by 0.05 (or maybe more user friendly will be percent, ie. 100%-300%), applied to all maps
- x2 magnifier turned on/off when needed (as it is now)

So, for example, with prescale 150% and x2 turned on, I can get 300%. Memory consumption will be crazy, but as for math behing scaling, I guess it might not be too affected by scaling factor.
Also readability of maps not scaled by integer number, or scaled high like x3 is unknown. (Android can do filtering, but it may have negative impact on consumed memory and definitely performance).

I'll try to implemen the above, and we will test it Smile
Back to top
View user's profile Send private message
kruch
Site Admin


Joined: 02 Jul 2006
Posts: 5676

PostPosted: Thu Mar 08, 2012 8:20 am    Post subject: Reply with quote

btw I tried x2 on old SonyEricsson C510 and it worked quite well Smile
Back to top
View user's profile Send private message
Ranger



Joined: 12 Dec 2006
Posts: 6030

PostPosted: Thu Mar 08, 2012 11:31 am    Post subject: Reply with quote

Yep, x2 moves well maps from services near mainstream phone displays. Not for most of high-res yet ...


x2_sample.png
 Description:
 Filesize:  101.96 KB
 Viewed:  11101 Time(s)

x2_sample.png


Back to top
View user's profile Send private message
Cactus



Joined: 14 Dec 2007
Posts: 214
Location: Fife, Scotland

PostPosted: Thu Mar 08, 2012 1:07 pm    Post subject: Reply with quote

That makes UK OS maps so much easier to read on my Nokia 5230. Thanks! Very Happy
_________________
Nokia Lumia 635, Windows Phone 10
Nokia Lumia 520, Windows Phone 8.1
Back to top
View user's profile Send private message
kruch
Site Admin


Joined: 02 Jul 2006
Posts: 5676

PostPosted: Fri Mar 09, 2012 8:50 pm    Post subject: Reply with quote

link removed

- default pre-scale option Settings->Desktop->Map prescale (current map reload required after change)
- x2 magnifier global (=for all layers/maps in atlas)
- filtered scaling, on by default; if you don't like fuzzy images or have performance problems, uncheck Settings->Misc->Tweaks - filterede scaling


Last edited by kruch on Fri Mar 09, 2012 9:46 pm; edited 1 time in total
Back to top
View user's profile Send private message
billy06



Joined: 01 Oct 2008
Posts: 434
Location: Lowestoft U.K

PostPosted: Fri Mar 09, 2012 9:32 pm    Post subject: Reply with quote

Android , filtered scaling was not on by default when selected and saved error process net trekbuddy midlet has stopped, the same happens when you uncheck and save, this also happens when saving pre default pre scale.
setting / location gives show menu error IllegalArgumentException



alogcat.2012-03-09-21-33-06+0000.txt
 Description:

Download
 Filename:  alogcat.2012-03-09-21-33-06+0000.txt
 Filesize:  67.74 KB
 Downloaded:  2 Time(s)


_________________
Nexus 5X, Nexus 5, Nexus 7 3G, HTC Sensation, nokia 5800. web:www.thetrekbuddies.co.uk . Twitter:http://twitter.com/TheTrekbuddies
Back to top
View user's profile Send private message Visit poster's website
kruch
Site Admin


Joined: 02 Jul 2006
Posts: 5676

PostPosted: Fri Mar 09, 2012 9:45 pm    Post subject: Reply with quote

Damn...

You are right, filtered scaling was off by default. Will check the crash.
Back to top
View user's profile Send private message
billy06



Joined: 01 Oct 2008
Posts: 434
Location: Lowestoft U.K

PostPosted: Fri Mar 09, 2012 10:00 pm    Post subject: Reply with quote

what does filtered scaling do? i did not notice any change
_________________
Nexus 5X, Nexus 5, Nexus 7 3G, HTC Sensation, nokia 5800. web:www.thetrekbuddies.co.uk . Twitter:http://twitter.com/TheTrekbuddies
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    TrekBuddy Forum Index -> WishList All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7  Next
Page 4 of 7

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group