Hi I have started to implement adding features into the overview map. You can find ready built jar files on the download page and in the 'overview' branch in subversion. It creates the overview map from the .img (as before) and so it is very quick to try out even on a set of tiles covering a whole country. There is no configuration yet, it just takes everything (lines and polygons) that is in the least detailed layer of the detailed maps and adds it into the overview. You will immediately notice a big problem in that the overview map shows up even when the detailed maps are being displayed, so you get ugly jagged lines across the top of the map. I remember this happening the last time we has an overview map and I wonder if anyone can remember if there was a solution then? I'm going to start by trying the (so-called) POI flags, as one of those has been noted to be set differently on detail and base maps before. ..Steve
Steve Ratcliffe (steve@parabola.me.uk) wrote:
Hi
I have started to implement adding features into the overview map. You can find ready built jar files on the download page and in the 'overview' branch in subversion.
It creates the overview map from the .img (as before) and so it is very quick to try out even on a set of tiles covering a whole country.
There is no configuration yet, it just takes everything (lines and polygons) that is in the least detailed layer of the detailed maps and adds it into the overview.
You will immediately notice a big problem in that the overview map shows up even when the detailed maps are being displayed, so you get ugly jagged lines across the top of the map.
I remember this happening the last time we has an overview map and I wonder if anyone can remember if there was a solution then?
I'm going to start by trying the (so-called) POI flags, as one of those has been noted to be set differently on detail and base maps before.
..Steve
Sounds intriguing. What precisely is the overview map for? -- Charlie
Hi
Sounds intriguing. What precisely is the overview map for?
It shows the whole area covered by a set of detailed maps. It is needed by mapsource. We have always produced an overview map (its called osmmap.img by default), but it has been empty. It should contain the sea polygons and main roads etc so that you can see the whole area when zoomed right out. ..Steve
On 7/26/2010 5:06 PM, Steve Ratcliffe wrote:
Sounds intriguing. What precisely is the overview map for? It shows the whole area covered by a set of detailed maps. It is needed by mapsource.
We have always produced an overview map (its called osmmap.img by default), but it has been empty. It should contain the sea polygons and main roads etc so that you can see the whole area when zoomed right out.
I have always wondered what was the osmmap.img for. BTW I do not think it is packaged if you use the --nsis option. Thanks, N.
On 10/08/10 21:11, Nakor wrote:
I have always wondered what was the osmmap.img for. BTW I do not think it is packaged if you use the --nsis option.
It is, it wouldn't work otherwise. you call it baseFilename and then you assign it to MAPNAME and then the overview map and tdb file are included via that name later in the file. baseFilename = args.get("overview-mapname", "osmmap"); pw.format(Locale.ROOT, "!define MAPNAME \"%s\"\n", baseFilename); pw.format(Locale.ROOT, " File \"${MAPNAME}.img\"\n"); ..Steve
On 8/10/2010 6:03 PM, Steve Ratcliffe wrote:
On 10/08/10 21:11, Nakor wrote:
I have always wondered what was the osmmap.img for. BTW I do not think it is packaged if you use the --nsis option. It is, it wouldn't work otherwise.
you call it baseFilename and then you assign it to MAPNAME and then the overview map and tdb file are included via that name later in the file.
baseFilename = args.get("overview-mapname", "osmmap"); pw.format(Locale.ROOT, "!define MAPNAME \"%s\"\n", baseFilename); pw.format(Locale.ROOT, " File \"${MAPNAME}.img\"\n");
Oh wait. Am I mixing up things here? After mkgmap runs I have: 00000001.img 00000002.img ... North_america.img North_america.tdb osmmap.img osmmap.tdb Which is the overview map? the North_america one the osmmap one? BTW osmmap.img is quite small and does not seem to be packaged by NSIS.
On 10/08/10 23:08, Nakor wrote:
On 8/10/2010 6:03 PM, Steve Ratcliffe wrote:
On 10/08/10 21:11, Nakor wrote:
I have always wondered what was the osmmap.img for. BTW I do not think it is packaged if you use the --nsis option. It is, it wouldn't work otherwise.
you call it baseFilename and then you assign it to MAPNAME and then the overview map and tdb file are included via that name later in the file.
baseFilename = args.get("overview-mapname", "osmmap"); pw.format(Locale.ROOT, "!define MAPNAME \"%s\"\n", baseFilename); pw.format(Locale.ROOT, " File \"${MAPNAME}.img\"\n");
Oh wait. Am I mixing up things here?
After mkgmap runs I have:
00000001.img 00000002.img ... North_america.img North_america.tdb osmmap.img osmmap.tdb
Which is the overview map? the North_america one the osmmap one?
Possibly both but only one at a time. Assuming that you did --overview-mapname=North_america then North_america.img will be. If you do more than one run of mkgmap, then you will have to make sure that you always use the same --overview-mapname option otherwise you will create an extra osmmap.img and/or package the wrong file. So that is worth bearing in mind. ..Steve
Is there a switch to enable? If not am I right in assuming the most useful command would look like java -ea -jar mkgmap.jar --index --location-autofill=1 --description=bla --country-name=%country% --mapname=%FID%0000 --family-id=%FID% --product-id=1 --series-name=bla --family-name=bla --overview-mapname=mapset --area-name=bla %FID%*.img Using .img tiles as input instead of using osm? The problem that I see is that if we resuse the .img, then we will end up with the double lines. Now that we have a overview map (they can have up to 3 levels I think) would be to have: 24,22,20,18,16 as default levels in the img. and 16/14/12/11/10 (unsure if we can input data into 10) as default levels for the overview map. I think that overview map and normal map .img should only overlap with empty maplevel. (Garmin uses 17/15/13/12/11/10 in their overview maps as default levels on City Navigator -- however 12/11/10 all being empty). On some Topo maps, there are however levels which really overlap (meaning objects in both basemap and normal .img inside the same resolution) An alternative to that would be, if mkgmap could simply delete the reused levels of the overview map in each .img map (and then of course create new mdr/tdb/....)
On 25/07/10 12:58, Felix Hartmann wrote:
Is there a switch to enable?
No
If not am I right in assuming the most useful command would look like java -ea -jar mkgmap.jar --index --location-autofill=1 --description=bla --country-name=%country% --mapname=%FID%0000 --family-id=%FID% --product-id=1 --series-name=bla --family-name=bla --overview-mapname=mapset --area-name=bla %FID%*.img
Using .img tiles as input instead of using osm?
Well you can use either, but the osm files are converted into img first and then the overview map is created from the img. So its the same either way.
The problem that I see is that if we resuse the .img, then we will end up with the double lines. Now that we have a overview map (they can have up to 3 levels I think) would be to have:
Why would there be double lines? So OK there are double lines now, but I am sure that is fixable. I've since discovered that it may just be missing the background polygon. ..Steve
okay, creating the overview map from existing .img does not seem to work. Or I am missing something.
On 25/07/10 20:41, Felix Hartmann wrote:
okay, creating the overview map from existing .img does not seem to work. Or I am missing something.
Not sure, it works just like before, except that there is more in the overview map. If there is only one file on the command line you need --tdbfile to generate the overview map, but that has always been the case. ..Steve
On 25.07.2010 23:25, Steve Ratcliffe wrote:
On 25/07/10 20:41, Felix Hartmann wrote:
okay, creating the overview map from existing .img does not seem to work. Or I am missing something.
Not sure, it works just like before, except that there is more in the overview map. If there is only one file on the command line you need --tdbfile to generate the overview map, but that has always been the case.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev Ups, sorry checked out a wrong branch by mistake. This was the commandline (against 5 tiles in .img format): java -ea -jar mkgmap.jar --index --location-autofill=1 --description=overview_ch_%date% --country-abbr=ch --country-name=switzerland --mapname=63270000 --family-id=6327 --product-id=1 --series-name=overview_ch_%date% --family-name=ovmap_ch_%date% --overview-mapname=mapset --area-name="switzerland_%date%_openmtbmap.org" 6327*.img
However now I get the following: D:\Garmin\0mtb\mtbswitzerland>start /low /b /wait java -ea -jar -Xmx1300M mkgmap.jar --index --location-autofill=1 --description=overview_ch_26.07.2010 --country-abbr=ch --country-name=switzerland --mapname=63270000 --family-id=6327 --product-id=1 --series-name=overview_ch_26.07.20 10 --family-name=ovmap_ch_26.07.2010 --overview-mapname=mapset --area-name="switzerland_26.07.2010_openmtbmap.org" 6327*.img Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 62 at uk.me.parabola.imgfmt.app.BitReader.get(BitReader.java:46) at uk.me.parabola.imgfmt.app.BitReader.sget2(BitReader.java:70) at uk.me.parabola.imgfmt.app.trergn.RGNFileReader.readBitStream(RGNFileReader.java:306) at uk.me.parabola.imgfmt.app.trergn.RGNFileReader.readLineCommon(RGNFileReader.java:229) at uk.me.parabola.imgfmt.app.trergn.RGNFileReader.linesForSubdiv(RGNFileReader.java:158) at uk.me.parabola.imgfmt.app.map.MapReader.linesForLevel(MapReader.java:128) at uk.me.parabola.mkgmap.combiners.MdrBuilder.addStreets(MdrBuilder.java:206) at uk.me.parabola.mkgmap.combiners.MdrBuilder.onMapEnd(MdrBuilder.java:115) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:384) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:124) at uk.me.parabola.mkgmap.main.Main.main(Main.java:124) (against both 1662 and 63) this only happens if I use --index. If I drop --index then it works (though I would like to have more levels in the overview map, and less in the actual .img). So there seems to be something broken on the index creation.
--area-name="switzerland_26.07.2010_openmtbmap.org" 6327*.img Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 62 at uk.me.parabola.imgfmt.app.BitReader.get(BitReader.java:46) at uk.me.parabola.imgfmt.app.BitReader.sget2(BitReader.java:70)
(against both 1662 and 63)
this only happens if I use --index. If I drop --index then it works (though I would like to have more levels in the overview map, and less in the actual .img). So there seems to be something broken on the index creation.
OK that's a bit strange as the same code is being run against the same files in both overview and index creation. I'm not immediately able to reproduce the problem, so may take a bit of time to track down. ..Steve
On 26.07.2010 23:08, Steve Ratcliffe wrote:
--area-name="switzerland_26.07.2010_openmtbmap.org" 6327*.img Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 62 at uk.me.parabola.imgfmt.app.BitReader.get(BitReader.java:46) at uk.me.parabola.imgfmt.app.BitReader.sget2(BitReader.java:70)
(against both 1662 and 63)
this only happens if I use --index. If I drop --index then it works (though I would like to have more levels in the overview map, and less in the actual .img). So there seems to be something broken on the index creation. OK that's a bit strange as the same code is being run against the same files in both overview and index creation. I'm not immediately able to reproduce the problem, so may take a bit of time to track down.
..Steve It's happening on Win32, with the following maps: http://openmtbmap.x-nation.de/maps/mtbswitzerland.exe
The actuall command is: java -ea -jar -Xmx1300M mkgmap.jar --index --description=overview_ch_%date% --country-abbr=ch --country-name=switzerland --mapname=63270000 --family-id=6327 --product-id=1 --series-name=overview_ch_%date% --family-name=ovmap_ch_%date% --overview-mapname=mapset --area-name="switzerland_%date%_openmtbmap.org" 6327*.img If I add --index than it fails. Without --index it is working.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Thanks Felix, I am able to reproduce now. Only seems to happen with routa ble maps. ..Steve
Well it's a long time since the last commit to the overview branch, but it would be very great if we could get a working overview map... Why is there a need for it? - Well currently most people build mkgmap maps down to resolution 16, using map information, else in Mapsource/Basecamp/Qlandkarte there is simply not enough zoomout/speed possible for maps covering bigger regions. However, on the GPS this means, that the much quicker loading and better suited overview map will be used too late (with mkgmap trunk default style, I'm not sure if it is used at all, because there is no "empty" resolution). Also this would help everyone who is running out of levels, and hence has to make a compromise in the number of levels - as the max number of 8 levels (0-7) is not really enough if you would like to show a nice map when zoomed out very far on the desktop. The old overview branch, had, IMHO the main problem, of not being configurable. It would be great if the overview map could be created using the following scheme: 1. a)Create a completly new lines, polygons, points, relations and options style-file so one can specify what goes into the overview map. e.g. lines.overview; polygons.overview; or b) alternatively, just change the format of the options file to something like: levels = 0:24, 1:22, 2:21, 3:20, 4:19, 5:18, 6:16 levels_overview= 0:16, 1:14, 2:12, 3:10 I think b) is more practical, as it allows to more quickly change the level of detail for the overview map as it shouldn't become too big. So e.g. if you create a map of Europe you use the above figures, but if you create a map of a small country/region like e.g. Austria, you could change it to levels = 0:24, 1:22, 2:21, 3:20, 4:19, 5:18 levels_overview= 0:18, 1:16, 2:14, 3:12, 4:10 2. Add an additional parameter for the douglas-peucker algorythm. As for the overview map, there neeeds to be very strong filtering - though I don't know the size limit for an overview map. 3. Maybe, as for the coastline/sea and boundary information, mkgmap could use a drastically reduced dataset, to help speed up the map creation, and make it easier to fix things. ------------ A nice example of an overview map, is included in the Topo Hispania. It has the following levels: 0:16, 1:15, 2:14, 3:13, 4:11, 5:10 (with level 5 being empty) -- the normal map files have 0:24, 1:23, 2:22, 3:21, 4:18, 5:16, 6:14 (with level 6 being empty) Even though it is only 186KB big, it has quite a lot of information of Spain in it. For everyone not wanting to download the full topohispania (v2) I uploaded it to openmtbmap.org/topohispania.img It would be great, if mkgmap could produce something similar (though of course it will be more difficult, with changing data - though point 3 could help to give us the same quality). (note tophispania.img may not be used commercially/sold) On 25.07.2010 13:35, Steve Ratcliffe wrote:
Hi
I have started to implement adding features into the overview map. You can find ready built jar files on the download page and in the 'overview' branch in subversion.
It creates the overview map from the .img (as before) and so it is very quick to try out even on a set of tiles covering a whole country.
There is no configuration yet, it just takes everything (lines and polygons) that is in the least detailed layer of the detailed maps and adds it into the overview.
You will immediately notice a big problem in that the overview map shows up even when the detailed maps are being displayed, so you get ugly jagged lines across the top of the map.
I remember this happening the last time we has an overview map and I wonder if anyone can remember if there was a solution then?
I'm going to start by trying the (so-called) POI flags, as one of those has been noted to be set differently on detail and base maps before.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (5)
-
charlieï¼ cferrero.net -
Felix Hartmann -
Felix Hartmann -
Nakor -
Steve Ratcliffe