Hi, thank you for pictures, I've moved the slider a bit more and I do agree, sometimes
you can accidentally :) hit a native tile scaling such that the tiles are displayed perfectly..
though most of the time one gets poor picture, because there is so much more real numbers :)
I wonder, wouldn't it be easier (and better for readability) to make the map just to jump between those
discrete scalings (like it is porbalby done in other programs such as OSMtracker etc)?
Instead of that interpolation scaling you mentioned in your first post...
unfortunately, in my phone the text is never visible, no matter what is the position of the zoom slider.
As far as I understand it, the problem is that some basic scale coefficient the tiles are shown with
is not good for QVGA.
The tiles are 256x256 pixels. They look OK if they are displayed in native resolution 1:1 scale (I checked)
Probably, Run.GPS by default tries to fit about 480/256 = 1.875 tiles per VGA screen width,
in order to display them in NATIVE resolution (one tile pixel per one screen pixel).
This fails on QVGA (width 240) where the tiles look too small in the result..
OpenStreetMap (and Google) Maps are normally available in 18 zoom levels. If you move the zoom slider in Run.GPS to a value so that the scale of the displayed map is between two of these zoomlevels the image has to be scaled.
There are several ways to do this scaling. Two simple possibilities are:
1. Take the higher zoomlevel image and scale the image up
2. Take the lower zoomlevel image and scale the image down
Run.GPS always uses the second method so if you have adjusted your zoomslider to a value between two OSM zoomlevel then the image will be scaled down and text is not readable any more. I think even on a VGA screen you can't read the text.
You can only try to hit a setting for the zoomslider thats near an OSM zoomlevel so the map image gets not scaled very much.
I have asked the programmers a few times to encance this behavior but until now they refused in changing it. I asked for an option so Run.GPS uses the first method for scaling but they said that the image then looks blurry. But I think a blurry image is better than an image where you can't read the text.
Even better would be an option which makes the cut in the middle of to zoomlevels.
Unfortunately for me, the problem persists with every kind of maps, including the google maps..
I think it stems from the simple fact that Run.GPS has been optimized for a screen resolution better
than mine.. Still it would be nice to be able to adjust it to QVGA..
12.01.2010 22:17:48 UTCgeändert am 12.01.2010 22:18:04 UTC
Hi,
i think this is not a problem with Run.GPS. OpenStreetMap delivers these pictures.
Perhaps you can use GoogleMaps instead of OpenStreetMaps.
Just have a look there http://www.gps-sport.net/forums/thread/1327-0/kartenmaterial
12.01.2010 20:13:46 UTCgeändert am 12.01.2010 20:15:43 UTC
maps zoom levels vs and screen size
Dear Run.GPS community.
I've come across a slight annoyance using Run.GPS (though overall is it great software, and I'm considering to by a license once my trial expires), and I wonder if anyone can suggest anything.
I have an htc touch phone with QVGA screen, and the maps (openstreet, google all of them) always appear
at a zoom level not comfortable for reading. In fact it is not even possible to read street names, because the lettering is too small. I presume that these zoomlevels would look OK on the higher-resolution screen.