![]() |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
After last CSSU Cloud GPS don't work in portrait.
I was trying to blacklist as other programs but it didn't help. Do you know how to blacklist it properly or any work around? |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
Quote:
Start it while in landscape mode. After this, it runs also in portrait. |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
Quote:
You can as I have done, create a directory in /opt for your maps and have it mounted at '/home/.maps' when you boot/plug, unplug the usb. |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
@vi_
yes it maybe a solution, but keep in mind that one tif of 40Mbytes converted for zooms from 8 to 16 needs about 500-600 Mbytes of free space... Considering zooms from 8 to 15, about 200 Mbytes.... |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
You may repartition Your eMMC to gain more space on /home (second partition, ext2) and loose some on MyDocs (first part., FAT).
Personally I would prefer that now (but still have standard layout). Or, look here: http://talk.maemo.org/showthread.php?t=74415 and create a storage file on MyDocs, keeping all Your map data (max. 4GB). This is, what I have now (a 4 GB file on MyDocs, formatted as FAT with 512 kB cluster size). One may also consider, that one file per map provider is possible. So mounting takes places NOT on /home/user/MyDocs/.maps BUT on /home/user/MyDocs/.maps/OSM I (e.g.) Whatever solution You choose, the standard eMMC (with 64kB cluster size) is the worst. |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
Quote:
|
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
@hardkorek
please check the latest cssu updates and pay attention to the ini files changes (the update procedure asks if you want replace them - you should..). On mine n900 cloudgps rotates perfectly with no black screen. |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
Quote:
My source maps do not overlap, but because of the map borders, there are multiple versions of some tiles generated. I couldn't get tiles_merge to work for me, so I hacked up some python to do the same job. It copies all the generated source files into one destination tree. If the destination file already exists, then the two tiles are joined with ImageChops.lighter(im1, im2) from PIL. This seems to give a reasonable join, but there may be a better method. Of course, if your source maps overlap, it's going to be more difficult. |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
My maps are offroad maps with white border with coord info and some date and producer detail...
So the white border covers an area already described by another map which i have already converted in another tile store folder.... I'm sorry but i can't understand the purpose of ImageChops.lighter(im1, im2) where im1 im2 are pieces of maps..... maybe that your images are black with white lines? Now i'm writing something to compare the size of the tiles before overwrite (the white one is smaller) |
Re: [WIP] CloudGPS 0.4.8 - smoothest maps for N900
Because my maps don't overlap, if I generate two tiles for the same location, then each one is transparent where there is no map information. Using lighter just uses the brightest pixel from either image (transparent registers as dark).
Since your source maps overlap, the problem is a little different. The png file size seems to depend on the number of colours and the amount of detail, so file size is probably a good guide to detecting which on is the 'better' tile to keep. |
| All times are GMT. The time now is 04:58. |
vBulletin® Version 3.8.8