![]() |
Re: Plans for Maemo Mapper v2.0
Quote:
|
Re: Plans for Maemo Mapper v2.0
Here is an idea.
Make in the db where you want to keep the map tiles two tables. one coordinates and CRC of the image tile and in the second table the CRC of the image and the image. This way you can exclude duplicates, we'll have only one tile that is blue... or white... or whatever. you make the CRC as a unique key in the images table. when you insert, you insert in both tables, in the image table the insert will fail (if the CRC is already there). this way you won't have to check if the image is already in the table before inserting. What do you think? -ioan |
Re: Plans for Maemo Mapper v2.0
Quote:
|
Re: Plans for Maemo Mapper v2.0
Maemo Mapperi is great because as far as I know it is currenlty the only available native WMS-client for maemo platform. And WMS allows me to serve my own maps quite easily. Plans for db-utilization sound great, expect that features of PostGIS are perhaps too far from here.
WFS-support for MM would be nice :rolleyes: |
Re: Plans for Maemo Mapper v2.0
Quote:
Or, if there's some fast way to detect if an image is just a single color one while retrieving it, avoid storing it in the database and store just the corresponding color information. So, imagine a table with fields: coordinates | display "display" is a short string: when it does begin with "#", the value is considered as a color (to render a monocolor tile for that coordinates), otherwise it is considered as the id of the image to render (picking it from a second table with fields: id | image). |
Re: Plans for Maemo Mapper v2.0
I did a test with creating a table just for the tile image and the crc32, the table looks like this:
CREATE TABLE testtable ([crc32] VARCHAR (8) PRIMARY KEY UNIQUE, [maptile] BLOB COLLATE NOCASE); I didn't do anything for coordinates, nothing special to see there. I ran the test on 213304 map tiles, and at the end, in the database I had 135417 unique tiles (77887 were duplicates!). The 213304 tiles on my computer use 897MB (size on disk), and the database, after excluding the duplicates is about 290 MB. I used sqlite3. -ioan |
Re: Plans for Maemo Mapper v2.0
Quote:
|
Re: Plans for Maemo Mapper v2.0
Quote:
http://ioanghip.googlepages.com/crc.jpg the caption shows the number of processed files, the list, first field is the size, the second how many duplicates with that size... I suppose on windows we have 106 bytes not 103. -ioan |
Re: Plans for Maemo Mapper v2.0
Any plans for adding a Golf Course GPS program that would allow for course maps to be built, shared or downloaded from a respository? Possibly a program similar to Sky Caddie. This would be a superb mapping application.
I really appreciate your present Maemo Mapper program and look forward to version 2.0 |
Re: Plans for Maemo Mapper v2.0
Quote:
Google Streets: 103 bytes Virtual Earth Streets: 106 bytes Virtual Earth Satellite or Hybrid: 1652 bytes Among my Google Satellite downloads, I have a lot of duplicate 1755 byte files, which in fact are NOT maps, even though they commonly appear clustered in featureless ocean areas. (Some of the true satellite map files are actually smaller.) Opening these files as text reveals the following HTML error page, saved under the target JPG filename: Code:
<html> |
| All times are GMT. The time now is 09:22. |
vBulletin® Version 3.8.8