Overview map for Africa
Hi List, while testing the latest patches I found something strange: I created a map for Africa with default style using java -Xmx6000m -jar mkgmap.jar --max-jobs --nsis --precomp-sea=f:\osm\sea_20130308.zip -c template.args When I open this map in Basecamp I just see white rectangle. I have to zoom in multiple times to see anything. Wouldn't it be better to change the default so that we display at least the boundaries off continents on very low resolutions? Ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
No, definitely not. There should rather be work on a real overview map. There is a branch for it, but it lacks it's own style. We will need a separate style for the overview map. This will greatly help overview in Basecamp/Mapsource/Qlankdarte GT. On the device any map lower than resolution 18, is bad, because the background map is much better and 16 or 14 (speed!). If the map goes down to 14 or 16, than too many tiles have to be opened, in order to draw it, hence a hefty slowdown. Same on desktop. A multi-level overview map - say 12,14,16 is what we really need. There is a good description about overview maps also here: www.*maptk*.dnsalias.com/*MapTk*/*MapTk*_en.pdf -- scroll to page 20. On 25.03.2013 09:31, GerdP wrote:
Hi List,
while testing the latest patches I found something strange: I created a map for Africa with default style using java -Xmx6000m -jar mkgmap.jar --max-jobs --nsis --precomp-sea=f:\osm\sea_20130308.zip -c template.args
When I open this map in Basecamp I just see white rectangle. I have to zoom in multiple times to see anything. Wouldn't it be better to change the default so that we display at least the boundaries off continents on very low resolutions?
Ciao, Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi Felix, I'm confused. You start with clear no, but the rest sound like a big yes ? Since I did not suggest any solution: What was the "no" for? Gerd Felix Hartmann-2 wrote
No, definitely not. There should rather be work on a real overview map. There is a branch for it, but it lacks it's own style. We will need a separate style for the overview map. This will greatly help overview in Basecamp/Mapsource/Qlankdarte GT. On the device any map lower than resolution 18, is bad, because the background map is much better and 16 or 14 (speed!). If the map goes down to 14 or 16, than too many tiles have to be opened, in order to draw it, hence a hefty slowdown. Same on desktop. A multi-level overview map - say 12,14,16 is what we really need.
There is a good description about overview maps also here: www.*maptk*.dnsalias.com/*MapTk*/*MapTk*_en.pdf -- scroll to page 20.
On 25.03.2013 09:31, GerdP wrote:
Hi List,
while testing the latest patches I found something strange: I created a map for Africa with default style using java -Xmx6000m -jar mkgmap.jar --max-jobs --nsis --precomp-sea=f:\osm\sea_20130308.zip -c template.args
When I open this map in Basecamp I just see white rectangle. I have to zoom in multiple times to see anything. Wouldn't it be better to change the default so that we display at least the boundaries off continents on very low resolutions?
Ciao, Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754629.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
It means, resolutions below 18 are great, but in a separate overview map, not part of the normal *.img files. Even better would be, if we could create the overview map in advance - maybe not even based on OSM material. There should be very simple overview maps - (first level - sea/land - maybe some major cities, only useful for continent maps, or country maps of Canada, Russia, China, and other huge countries, second level - add all capitals, add country borders, third level - add motorways, add cities with population >1 Mio (depending on the country). This could save processing time I imagine - by having the overview map, or at least the data used for it prebuilt, like the bounds and the sea files. If we add a lower resolution to the main branch now, it should clearly only be an intermediary step to real overview maps. Overview maps are not transferred to Garmin GPS units, as they come with a preloaded world map, which offers decent performance when zooming out. If on the other hand we create maps with resolution 12 or 14, and no overview map, we make the GPS units painfully slow when zooming out and rely on the caching mechanism of Basecamp/Mapsource in order to get any kind of performance on the desktop (e.g. open a map of Asia, and grab a coffee until you can pan around well...). On 25.03.2013 14:18, GerdP wrote:
Hi Felix,
I'm confused. You start with clear no, but the rest sound like a big yes ? Since I did not suggest any solution: What was the "no" for?
Gerd
Felix Hartmann-2 wrote
No, definitely not. There should rather be work on a real overview map. There is a branch for it, but it lacks it's own style. We will need a separate style for the overview map. This will greatly help overview in Basecamp/Mapsource/Qlankdarte GT. On the device any map lower than resolution 18, is bad, because the background map is much better and 16 or 14 (speed!). If the map goes down to 14 or 16, than too many tiles have to be opened, in order to draw it, hence a hefty slowdown. Same on desktop. A multi-level overview map - say 12,14,16 is what we really need.
There is a good description about overview maps also here: www.*maptk*.dnsalias.com/*MapTk*/*MapTk*_en.pdf -- scroll to page 20.
On 25.03.2013 09:31, GerdP wrote:
Hi List,
while testing the latest patches I found something strange: I created a map for Africa with default style using java -Xmx6000m -jar mkgmap.jar --max-jobs --nsis --precomp-sea=f:\osm\sea_20130308.zip -c template.args
When I open this map in Basecamp I just see white rectangle. I have to zoom in multiple times to see anything. Wouldn't it be better to change the default so that we display at least the boundaries off continents on very low resolutions?
Ciao, Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754629.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
+1 Would be nice to have an overview map with only a rough coastline, rough borderlines, major capitals.
Hi Gerd I've often wondered how 'easy' it is to also include major roads / motorways in the overview map , as seen in many TOPOs at zoom level &15. As Felix is hinting , this could be an option ? At the moment, I'm having to extract such data separately as an mp file and include them in the 'final' basemap/overview.mp and thus create the img ..Nick -- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754680.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
as far as I know, that should be pretty simple. The overview map is in principle just a normal .img, plus the references. Hence the main work, should be the additional style-files for it. (be it part of the normal lines/polygons/pois files, or in completly separate lines_overview, polgons_overview, poi_overview files)... On 25.03.2013 23:13, n Willink wrote:
w 'easy' it is to also include major roads / motorways in the overview map , as seen in many TOPOs at zoom level &15. As Felix is hinting , this could be an option ? At the moment, I'm having to extract such data separately as an mp file and include them in the 'final' basemap/overview.mp and thus create the img
..Nick
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi all, thanks for the input. Today I tried the solution implemented by Steve in the overview branch , and although the code is more that two years old it seems to do what I suggested, so I wonder why it wasn't merged into the trunk. africa_overview.png <http://gis.19327.n5.nabble.com/file/n5754697/africa_overview.png> If I got this right, Steve sees two possible uses: 1) Create the img files with the normal style and create the overview map using the data from these img files 2) Create two sets of img files, one with the normal style, one with an "overview" style. Create the overview map with the 2nd set and combine it with the 1st set of img files. I don't know if 2) would work? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754697.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Gerd wrote:
Today I tried the solution implemented by Steve in the overview branch , and although the code is more that two years old it seems to do what I suggested, so I wonder why it wasn't merged into the trunk. africa_overview.png <http://gis.19327.n5.nabble.com/file/n5754697/africa_overview.png>
Hi Gerd If I look at your overviewmap the coastline seems still very detailed. How many tiles is this overview map (just one?). Is it possible to use another shape for the continent(s) or maybe a filtered osm coastline that throws away all the small details like islands and stuff? Is it possible to update this branch version so we can experiment a bit with the overview map?
Minko-2 wrote
If I look at your overviewmap the coastline seems still very detailed. How many tiles is this overview map (just one?). Is it possible to use another shape for the continent(s) or maybe a filtered osm coastline that throws away all the small details like islands and stuff?
Is it possible to update this branch version so we can experiment a bit with the overview map?
It is one tile with < 5 Mb. The branch is r1666 and t1659 was merged with trunk, so I can try to merge current trunk with the old code, but first I'd like to know why development was stopped. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754712.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
I don't really know why it stopped, but to what I know, there was one main problem to make it useful: Only one level in the overview map (the lowest resolution), and therefore no way to make it really useful. The overview map needs to have several levels too, and the very least needed is the ability to specify which resolution goes into the overview map, and which into the main map. BTW: I don't know what resolution is used in your 5MB overview map. If that is resolution 16, it's kinda okay. If that is resolution 14 - it's not okay, because an overview map consisting of resolution 12,14,16 would then simply be too big to fit into one tile. Also depending if you have a detailed basemap on your GPS, or not (usually European GPS devices have detailed Europe basemap, rest of the world less detailed. American have America more detailed, and so on. While the newer generation have such a detailled basemap, that clearly resolution 18 would best be used in the overview map too, and the detailed (mkgmap) map starting only at resolution 19. Overall much heavier filtered/non OSM data would be better suited for an overview map, I assume. e.g. the following could be used in the options file: # The levels specification for this style # levels = 0:24, 1:22, 2:20, 3:19, 4:18 # the level specification for the overview map # overviewmap_levels = 0:16, 1:14, 2:12 On 26.03.2013 10:56, GerdP wrote:
Minko-2 wrote
If I look at your overviewmap the coastline seems still very detailed. How many tiles is this overview map (just one?). Is it possible to use another shape for the continent(s) or maybe a filtered osm coastline that throws away all the small details like islands and stuff?
Is it possible to update this branch version so we can experiment a bit with the overview map? It is one tile with < 5 Mb. The branch is r1666 and t1659 was merged with trunk, so I can try to merge current trunk with the old code, but first I'd like to know why development was stopped.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754712.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
BTW: here is the old thread about the overview map branch: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2010q3/008700.html And there is clearly a second huge problem. The branch only used the created .img files in order to make a new overview map. However that defeats it's purpose. The resulting overview map is used, and yes, it probably (though I'm not even sure about it) speeds up Mapsource/Basecamp/Qlandkarte GT when zoomed out, but the main problem remains. With all that low resolutions in the actual normal .img files, there is no speedup for the GPS device, where those low resolutions are a PITA. So there needs to be a clear separation of overview map, vs normal map in the resolution levels. Also it would be great, if for subsequent mkgmap runs with different input data, the overview map data could be reused, and simply tiles added without adding information. (e.g. you create one map, and want to have it a) including contourlines b)without contourlines - so you need to separate overview maps, one referencing the contourlines .img files, one not referencing them. At the same time the map data of both overview maps, should be the same of course and it would be a waste of time running mkgmap twice just because now the overview map is not created from the standard *.img files anymore). On 26.03.2013 10:56, GerdP wrote:
Minko-2 wrote
If I look at your overviewmap the coastline seems still very detailed. How many tiles is this overview map (just one?). Is it possible to use another shape for the continent(s) or maybe a filtered osm coastline that throws away all the small details like islands and stuff?
Is it possible to update this branch version so we can experiment a bit with the overview map? It is one tile with < 5 Mb. The branch is r1666 and t1659 was merged with trunk, so I can try to merge current trunk with the old code, but first I'd like to know why development was stopped.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754712.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi Felix, I don't understand what problem you see with "all that low resolutions": I created the overview map with those tiles that were produced with the default style. Gerd Felix Hartmann-2 wrote
BTW: here is the old thread about the overview map branch: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2010q3/008700.html
And there is clearly a second huge problem. The branch only used the created .img files in order to make a new overview map. However that defeats it's purpose. The resulting overview map is used, and yes, it probably (though I'm not even sure about it) speeds up Mapsource/Basecamp/Qlandkarte GT when zoomed out, but the main problem remains. With all that low resolutions in the actual normal .img files, there is no speedup for the GPS device, where those low resolutions are a PITA. So there needs to be a clear separation of overview map, vs normal map in the resolution levels.
Also it would be great, if for subsequent mkgmap runs with different input data, the overview map data could be reused, and simply tiles added without adding information. (e.g. you create one map, and want to have it a) including contourlines b)without contourlines - so you need to separate overview maps, one referencing the contourlines .img files, one not referencing them. At the same time the map data of both overview maps, should be the same of course and it would be a waste of time running mkgmap twice just because now the overview map is not created from the standard *.img files anymore).
On 26.03.2013 10:56, GerdP wrote:
Minko-2 wrote
If I look at your overviewmap the coastline seems still very detailed. How many tiles is this overview map (just one?). Is it possible to use another shape for the continent(s) or maybe a filtered osm coastline that throws away all the small details like islands and stuff?
Is it possible to update this branch version so we can experiment a bit with the overview map? It is one tile with < 5 Mb. The branch is r1666 and t1659 was merged with trunk, so I can try to merge current trunk with the old code, but first I'd like to know why development was stopped.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754712.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754733.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
well the original branch, just copied the content from the lowest resolution from the .img file, into the overview map. However that principle is flawed. Content should be either in the overview map, or in the .img map. Not in both. So depending on which levels/resolutions are in your 5MB africa overview map (I don't know), 5MB is a good size, or a far too big size... On 26.03.2013 12:47, GerdP wrote:
Hi Felix,
I don't understand what problem you see with "all that low resolutions": I created the overview map with those tiles that were produced with the default style.
Gerd
Felix Hartmann-2 wrote
BTW: here is the old thread about the overview map branch: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2010q3/008700.html
And there is clearly a second huge problem. The branch only used the created .img files in order to make a new overview map. However that defeats it's purpose. The resulting overview map is used, and yes, it probably (though I'm not even sure about it) speeds up Mapsource/Basecamp/Qlandkarte GT when zoomed out, but the main problem remains. With all that low resolutions in the actual normal .img files, there is no speedup for the GPS device, where those low resolutions are a PITA. So there needs to be a clear separation of overview map, vs normal map in the resolution levels.
Also it would be great, if for subsequent mkgmap runs with different input data, the overview map data could be reused, and simply tiles added without adding information. (e.g. you create one map, and want to have it a) including contourlines b)without contourlines - so you need to separate overview maps, one referencing the contourlines .img files, one not referencing them. At the same time the map data of both overview maps, should be the same of course and it would be a waste of time running mkgmap twice just because now the overview map is not created from the standard *.img files anymore).
On 26.03.2013 10:56, GerdP wrote:
Minko-2 wrote
If I look at your overviewmap the coastline seems still very detailed. How many tiles is this overview map (just one?). Is it possible to use another shape for the continent(s) or maybe a filtered osm coastline that throws away all the small details like islands and stuff?
Is it possible to update this branch version so we can experiment a bit with the overview map? It is one tile with < 5 Mb. The branch is r1666 and t1659 was merged with trunk, so I can try to merge current trunk with the old code, but first I'd like to know why development was stopped.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754712.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754733.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi Felix, you can try on your own. See the first post regarding my mkgmap parms, I did not apply any patches or changes to create that overview, I just compiled the branch version and ran it with --tdbfile and the existing *.img files. Gerd Felix Hartmann-2 wrote
well the original branch, just copied the content from the lowest resolution from the .img file, into the overview map. However that principle is flawed. Content should be either in the overview map, or in the .img map. Not in both.
So depending on which levels/resolutions are in your 5MB africa overview map (I don't know), 5MB is a good size, or a far too big size... On 26.03.2013 12:47, GerdP wrote:
Hi Felix,
I don't understand what problem you see with "all that low resolutions": I created the overview map with those tiles that were produced with the default style.
Gerd
Felix Hartmann-2 wrote
BTW: here is the old thread about the overview map branch: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2010q3/008700.html
And there is clearly a second huge problem. The branch only used the created .img files in order to make a new overview map. However that defeats it's purpose. The resulting overview map is used, and yes, it probably (though I'm not even sure about it) speeds up Mapsource/Basecamp/Qlandkarte GT when zoomed out, but the main problem remains. With all that low resolutions in the actual normal .img files, there is no speedup for the GPS device, where those low resolutions are a PITA. So there needs to be a clear separation of overview map, vs normal map in the resolution levels.
Also it would be great, if for subsequent mkgmap runs with different input data, the overview map data could be reused, and simply tiles added without adding information. (e.g. you create one map, and want to have it a) including contourlines b)without contourlines - so you need to separate overview maps, one referencing the contourlines .img files, one not referencing them. At the same time the map data of both overview maps, should be the same of course and it would be a waste of time running mkgmap twice just because now the overview map is not created from the standard *.img files anymore).
On 26.03.2013 10:56, GerdP wrote:
Minko-2 wrote
If I look at your overviewmap the coastline seems still very detailed. How many tiles is this overview map (just one?). Is it possible to use another shape for the continent(s) or maybe a filtered osm coastline that throws away all the small details like islands and stuff?
Is it possible to update this branch version so we can experiment a bit with the overview map? It is one tile with < 5 Mb. The branch is r1666 and t1659 was merged with trunk, so I can try to merge current trunk with the old code, but first I'd like to know why development was stopped.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754712.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754733.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754746.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Minko, I think I managed to migrate the changes in the overview branch into the current trunk version. Attached is the patch, the compiled binary is available here: http://files.mkgmap.org.uk/download/95/mkgmap.jar overview_v1.patch <http://gis.19327.n5.nabble.com/file/n5754899/overview_v1.patch> I have added two options: --x-overview-add-lines --x-overview-add-polygons If you add both, you get the result as with the branch version. If prefer adding only the polygons to see the shape of the continent. By the way, the full img file for Africa has ~ 1.3 Mb. So, feel free to play with it and suggest changes. Gerd Minko-2 wrote
Gerd wrote:
Today I tried the solution implemented by Steve in the overview branch , and although the code is more that two years old it seems to do what I suggested, so I wonder why it wasn't merged into the trunk. africa_overview.png <http://gis.19327.n5.nabble.com/file/n5754697/africa_overview.png>;
Hi Gerd
If I look at your overviewmap the coastline seems still very detailed. How many tiles is this overview map (just one?). Is it possible to use another shape for the continent(s) or maybe a filtered osm coastline that throws away all the small details like islands and stuff?
Is it possible to update this branch version so we can experiment a bit with the overview map? _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754899.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Thanks Gerd! I already made a "quick and dirty"test with Nick's suggestion to use an mp image file. See https://dl.dropbox.com/u/64716698/OSM/mkgmap/overview1.jpg and https://dl.dropbox.com/u/64716698/OSM/mkgmap/overview2.jpg To make this overview map, I filtered the Germany extract from everything except admin_level=2 and place=city & population>300.000 I ran mkgmap with precomp-sea and just only one level (13). With gpsmapedit I merged the resulting img with an already made overview map of a Germany test map (just a few tiles in the corners). Saved the merged map as mp file and converted back to img with mkgmap. I used this map for the overview img. The result is that if you zoom all the way out, you see overview1.jpg, not a blank map anymore but a normal one with borders, view cities and sea. If you zoom in, the normal map appears (except where there are no tiles, then you see the overview map underneath). I'll try your patched version later and let you know the results. Should be another big improvement of mkgmap! Gerd wrote:
I think I managed to migrate the changes in the overview branch into the current trunk version. Attached is the patch, the compiled binary is available here: http://files.mkgmap.org.uk/download/95/mkgmap.jar
overview_v1.patch <http://gis.19327.n5.nabble.com/file/n5754899/overview_v1.patch>
I have added two options: --x-overview-add-lines --x-overview-add-polygons If you add both, you get the result as with the branch version. If prefer adding only the polygons to see the shape of the continent.
By the way, the full img file for Africa has ~ 1.3 Mb.
So, feel free to play with it and suggest changes.
Gerd
I think the precompiled sea will be able to provide special polygons for the overview map. Jochen Topf provides simplified shapes on the page openstreetmapdata.com. It should be easy to use them for the overview map. WanMil
Thanks Gerd! I already made a "quick and dirty"test with Nick's suggestion to use an mp image file. See https://dl.dropbox.com/u/64716698/OSM/mkgmap/overview1.jpg and https://dl.dropbox.com/u/64716698/OSM/mkgmap/overview2.jpg
To make this overview map, I filtered the Germany extract from everything except admin_level=2 and place=city & population>300.000 I ran mkgmap with precomp-sea and just only one level (13). With gpsmapedit I merged the resulting img with an already made overview map of a Germany test map (just a few tiles in the corners). Saved the merged map as mp file and converted back to img with mkgmap. I used this map for the overview img. The result is that if you zoom all the way out, you see overview1.jpg, not a blank map anymore but a normal one with borders, view cities and sea. If you zoom in, the normal map appears (except where there are no tiles, then you see the overview map underneath).
I'll try your patched version later and let you know the results. Should be another big improvement of mkgmap!
Gerd wrote:
I think I managed to migrate the changes in the overview branch into the current trunk version. Attached is the patch, the compiled binary is available here: http://files.mkgmap.org.uk/download/95/mkgmap.jar
overview_v1.patch <http://gis.19327.n5.nabble.com/file/n5754899/overview_v1.patch>
I have added two options: --x-overview-add-lines --x-overview-add-polygons If you add both, you get the result as with the branch version. If prefer adding only the polygons to see the shape of the continent.
By the way, the full img file for Africa has ~ 1.3 Mb.
So, feel free to play with it and suggest changes.
Gerd
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi WanMil, yes, this could be useful for some kind of a precompiled overview map. I'd like to collect some input first, but I think a nice overview map could contain large cities, level 2 boundaries, coastlines, and maybe also large rivers. I don't know if this collection of data is already available for download somewhere? Ciao, Gerd
Date: Wed, 27 Mar 2013 13:26:01 +0100 From: wmgcnfg@web.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Overview map for Africa
I think the precompiled sea will be able to provide special polygons for the overview map. Jochen Topf provides simplified shapes on the page openstreetmapdata.com. It should be easy to use them for the overview map.
WanMil
Thanks Gerd! I already made a "quick and dirty"test with Nick's suggestion to use an mp image file. See https://dl.dropbox.com/u/64716698/OSM/mkgmap/overview1.jpg and https://dl.dropbox.com/u/64716698/OSM/mkgmap/overview2.jpg
To make this overview map, I filtered the Germany extract from everything except admin_level=2 and place=city & population>300.000 I ran mkgmap with precomp-sea and just only one level (13). With gpsmapedit I merged the resulting img with an already made overview map of a Germany test map (just a few tiles in the corners). Saved the merged map as mp file and converted back to img with mkgmap. I used this map for the overview img. The result is that if you zoom all the way out, you see overview1.jpg, not a blank map anymore but a normal one with borders, view cities and sea. If you zoom in, the normal map appears (except where there are no tiles, then you see the overview map underneath).
I'll try your patched version later and let you know the results. Should be another big improvement of mkgmap!
Gerd wrote:
I think I managed to migrate the changes in the overview branch into the current trunk version. Attached is the patch, the compiled binary is available here: http://files.mkgmap.org.uk/download/95/mkgmap.jar
overview_v1.patch <http://gis.19327.n5.nabble.com/file/n5754899/overview_v1.patch>
I have added two options: --x-overview-add-lines --x-overview-add-polygons If you add both, you get the result as with the branch version. If prefer adding only the polygons to see the shape of the continent.
By the way, the full img file for Africa has ~ 1.3 Mb.
So, feel free to play with it and suggest changes.
Gerd
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I can't get it working Gerd, it crashes everytime with a NullPointerException: Exception in thread "main" java.lang.NullPointerException at uk.me.parabola.mkgmap.combiners.OverviewBuilder.addMapCoverageArea(OverviewBuilder.java:185) at uk.me.parabola.mkgmap.combiners.OverviewBuilder.readFileIntoOverview(OverviewBuilder.java:113) at uk.me.parabola.mkgmap.combiners.OverviewBuilder.onMapEnd(OverviewBuilder.java:75) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:429) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:127) at uk.me.parabola.mkgmap.main.Main.main(Main.java:111)
I think I managed to migrate the changes in the overview branch into the current trunk version. Attached is the patch, the compiled binary is available here: http://files.mkgmap.org.uk/download/95/mkgmap.jar
overview_v1.patch <http://gis.19327.n5.nabble.com/file/n5754899/overview_v1.patch>
Hi Minko, strange. It seems that you run it with an input *.img that doesn't contain the required bounds info. What options are you using for mkgmap? Gerd Minko-2 wrote
I can't get it working Gerd, it crashes everytime with a NullPointerException:
Exception in thread "main" java.lang.NullPointerException at uk.me.parabola.mkgmap.combiners.OverviewBuilder.addMapCoverageArea(OverviewBuilder.java:185) at uk.me.parabola.mkgmap.combiners.OverviewBuilder.readFileIntoOverview(OverviewBuilder.java:113) at uk.me.parabola.mkgmap.combiners.OverviewBuilder.onMapEnd(OverviewBuilder.java:75) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:429) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:127) at uk.me.parabola.mkgmap.main.Main.main(Main.java:111)
I think I managed to migrate the changes in the overview branch into the current trunk version. Attached is the patch, the compiled binary is available here: http://files.mkgmap.org.uk/download/95/mkgmap.jar
overview_v1.patch <http://gis.19327.n5.nabble.com/file/n5754899/overview_v1.patch>;
mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754946.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, I ve these options in my mkgmap.args file product-id: 1 draw-priority: 20 country-name: Europe country-abbr: EU style-file: Full name-tag-list: name,int_name,name:en,name:nl,name:de,name:fr,place_name generate-sea: land-tag=natural=background precomp-sea: Sea\sea_20130308.zip bounds: bounds_20130308.zip location-autofill: is-in,nearest x-housenumbers tdbfile latin1 code-page: 1252 show-profiles: 1 ignore-maxspeeds remove-short-arcs min-size-polygon: 4 reduce-point-density=1 reduce-point-density-polygon=3 merge-lines add-pois-to-areas add-pois-to-lines preserve-element-order keep-going net route index nsis java command: java -Xmx1250m -jar %MKGMAP% --output-dir=%date% --family-id=%FID% --overview-mapname=OFM_%mapname% --x-overview-add-lines --x-overview-add-polygons --series-name="OFM (%mapname%v%date%)" --family-name="OFM (%mapname%)" --area-name="OFM_%mapname%(%date%)" -c %argsfile% --description="OFM_%mapname%(%date%)" %typfile% 2>log.txt %argsfile% = mkgmap.args *.img I have also tried it with *.o5m files or an .osm file but they all crash. Using the default style didnt help too.
strange. It seems that you run it with an input *.img that doesn't contain the required bounds info. What options are you using for mkgmap?
Gerd
Hi Minko, I think the problem is caused by the last two parms ... --description="OFM_%mapname%(%date%)" %typfile%) I think the patched mkgmap tries to create an overview map for this. Gerd Minko-2 wrote
Hi Gerd, I ve these options in my mkgmap.args file
product-id: 1 draw-priority: 20 country-name: Europe country-abbr: EU style-file: Full name-tag-list: name,int_name,name:en,name:nl,name:de,name:fr,place_name generate-sea: land-tag=natural=background precomp-sea: Sea\sea_20130308.zip bounds: bounds_20130308.zip location-autofill: is-in,nearest x-housenumbers tdbfile latin1 code-page: 1252 show-profiles: 1 ignore-maxspeeds remove-short-arcs min-size-polygon: 4 reduce-point-density=1 reduce-point-density-polygon=3 merge-lines add-pois-to-areas add-pois-to-lines preserve-element-order keep-going net route index nsis
java command:
java -Xmx1250m -jar %MKGMAP% --output-dir=%date% --family-id=%FID% --overview-mapname=OFM_%mapname% --x-overview-add-lines --x-overview-add-polygons --series-name="OFM (%mapname%v%date%)" --family-name="OFM (%mapname%)" --area-name="OFM_%mapname%(%date%)" -c %argsfile% --description="OFM_%mapname%(%date%)" %typfile% 2>log.txt
%argsfile% = mkgmap.args *.img
I have also tried it with *.o5m files or an .osm file but they all crash. Using the default style didnt help too.
strange. It seems that you run it with an input *.img that doesn't contain the required bounds info. What options are you using for mkgmap?
Gerd
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754954.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, It was the typ file option that was causing it. Without type file it generates an overview map but it doesn't do what I want. There is no sea, no coastline, but everything turns into 0x0b polygon (hospital) as background. Also no borderlines.
Hi Minko,
I think the problem is caused by the last two parms ... --description="OFM_%mapname%(%date%)" %typfile%)
I think the patched mkgmap tries to create an overview map for this.
Gerd
Correction to my previous post, the sea was covered by a "hospital" background, 0xb. So there must be a bug in the patch. If I make this "hospital" transparent, the sea and coastline are visible. Only the borders disappear, despite the fact that I render them at the lowest level, but this is maybe a style file issue (maybe garmin dont render 0x1001e at very low zoomlevels, or the mkgmap patch doesnt know I'm using this line type).
There is no sea, no coastline, but everything turns into 0x0b polygon (hospital) as background. Also no borderlines.
Hi Minko, yes, the code changed the background type 0x4b to 0x0b. I find this also in the trunk version and in the current code of the display tool, so I am not sure why this happens. In fact, I don't yet see how the code that reads the img files should be able to read the extended type. Working on it ... Gerd
Date: Wed, 27 Mar 2013 22:38:02 +0100 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Overview map for Africa
Correction to my previous post, the sea was covered by a "hospital" background, 0xb. So there must be a bug in the patch.
If I make this "hospital" transparent, the sea and coastline are visible. Only the borders disappear, despite the fact that I render them at the lowest level, but this is maybe a style file issue (maybe garmin dont render 0x1001e at very low zoomlevels, or the mkgmap patch doesnt know I'm using this line type).
There is no sea, no coastline, but everything turns into 0x0b polygon (hospital) as background. Also no borderlines.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Thanks Gerd, Could you also look why the typ file isn't processed, no matter where I put the option, it gives a NullPointerException
yes, the code changed the background type 0x4b to 0x0b. I find this also in the trunk version and in the current code of the display tool, so I am not sure why this happens. In fact, I don't yet see how the code that reads the img files should be able to read the extended type. Working on it ...
Gerd
Hi Minko, yes, that is caused by a missing if statement: if (!finfo.isImg()) return; Gerd
Date: Thu, 28 Mar 2013 09:24:02 +0100 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Overview map for Africa
Thanks Gerd, Could you also look why the typ file isn't processed, no matter where I put the option, it gives a NullPointerException
yes, the code changed the background type 0x4b to 0x0b. I find this also in the trunk version and in the current code of the display tool, so I am not sure why this happens. In fact, I don't yet see how the code that reads the img files should be able to read the extended type. Working on it ...
Gerd
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Gerd wrote:
yes, that is caused by a missing if statement: if (!finfo.isImg()) return;
Thanks, And how about points, like big cities, country and sea names, are they copied too to the overview map? I think a special style file for generating the overview map is better. If possible with a few zoomlevels, like Felix suggested. If no such style is present, mkgmap will look at the items in the lowest level that is present, like the patch now does.
Hi Minko, I think the function implemented in the current patch ignores points completely. This has to be implemented as well as the support for data with extended types. Regarding the special style: I am not sure how this has to be done. The current implementation works only with the data in the *.img files, so this would require a completely different logic, but afaik it should be possible. Gerd
Date: Thu, 28 Mar 2013 09:39:00 +0100 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Overview map for Africa
Gerd wrote:
yes, that is caused by a missing if statement: if (!finfo.isImg()) return;
Thanks,
And how about points, like big cities, country and sea names, are they copied too to the overview map? I think a special style file for generating the overview map is better. If possible with a few zoomlevels, like Felix suggested. If no such style is present, mkgmap will look at the items in the lowest level that is present, like the patch now does. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Minko,
And how about points, like big cities, country and sea names, are they copied too to the overview map?
attached is version 2 of the patch. I've corrected the known errors and added the methods to copy points. You have to add option --x-overview-add-points for that. The three --x-overview-add-xxx options could probably be combined to e.g. --x-overview-add-features=n where n is a sum of points = 1 ,lines = 2 ,polygons = 4, but I leave that for later. The compiled binary is here: http://files.mkgmap.org.uk/download/96/mkgmap.jar Gerd
Forgot to mention that data with extended types is still ignored. I don't know if this is supported in overview maps ? If I got this right we have no existing code to read that kind of data, so it will require much more coding and testing. Gerd From: gpetermann_muenchen@hotmail.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 28 Mar 2013 10:48:10 +0100 Subject: Re: [mkgmap-dev] Overview map for Africa Hi Minko,
And how about points, like big cities, country and sea names, are they copied too to the overview map?
attached is version 2 of the patch. I've corrected the known errors and added the methods to copy points. You have to add option --x-overview-add-points for that. The three --x-overview-add-xxx options could probably be combined to e.g. --x-overview-add-features=n where n is a sum of points = 1 ,lines = 2 ,polygons = 4, but I leave that for later. The compiled binary is here: http://files.mkgmap.org.uk/download/96/mkgmap.jar Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Thanks Gerd, I did a quck test with my combined Benelux & Germany map, the v2 patch works fine: https://dl.dropbox.com/u/64716698/OSM/mkgmap/overview3.jpg At the moment don't worry about the extended types. I can do it with some workarounds by adjusting my styles a bit. At the moment my lowest map resolution is 16, but with a working overview map this could be set to 18. Then I can use 16 (or 17?) for the map details that needs to be set in the overview map (it renders too many items now), and for the moment without extended line and polygon types. I think this will render the maps definitely quicker than now.
Forgot to mention that data with extended types is still ignored. I don't know if this is supported in overview maps ? If I got this right we have no existing code to read that kind of data, so it will require much more coding and testing.
Gerd
About some data for the overview map, maybe this could be a good source: http://www.naturalearthdata.com/downloads/
I copied / pasted line type 0x1001e (purple border, https://dl.dropbox.com/u/64716698/OSM/mkgmap/overview2.jpg) with gpsmapedit into the overviewmap and it worked, so I don't think it is not supported.
Forgot to mention that data with extended types is still ignored. I don't know if this is supported in overview maps ? If I got this right we have no existing code to read that kind of data, so it will require much more coding and testing.
Gerd
The three --x-overview-add-xxx options could probably be combined to e.g. --x-overview-add-features=n where n is a sum of points = 1 ,lines = 2 ,polygons = 4, but I leave that for later.
Please remember that all options (at least the new ones) should be deniable with "no-xxx". Using numbers as parameters is also non intuitive. So I vote for leaving the three options as they are.
Gerd wrote:
yes, that is caused by a missing if statement: if (!finfo.isImg()) return;
Thanks,
And how about points, like big cities, country and sea names, are they copied too to the overview map? I think a special style file for generating the overview map is better. If possible with a few zoomlevels, like Felix suggested. If no such style is present, mkgmap will look at the items in the lowest level that is present, like the patch now does.
What about the following ideas: 1. Retrieve the data from the highest instead of the lowest level. The lowest level often contains fragmentary data, e.g. have a look a the boundaries in your example image http://gis.19327.n5.nabble.com/file/n5754697/africa_overview.png The data could be merged so that long ways are created that do not fall through the filters (DouglasPeucker etc.). The MapReader.linesForLevel and other methods must have filters that returns only selected garmin id types. 2. Use a separate overview style file and fetch the Garmin ids out of it. Then use these Garmin ids to build the overview map. I think the overview map should be configurable (one likes to see motorways, others like to see rivers etc.) Maybe it would also be possible to add a special overview statement or use special overview levels in the normal style files to achieve the same. 3. In case --precomp-sea parameter is set the data from an additional file in the precompiled sea folder is used. WanMil
WanMil wrote
What about the following ideas:
1. Retrieve the data from the highest instead of the lowest level. The lowest level often contains fragmentary data, e.g. have a look a the boundaries in your example image http://gis.19327.n5.nabble.com/file/n5754697/africa_overview.png The data could be merged so that long ways are created that do not fall through the filters (DouglasPeucker etc.). The MapReader.linesForLevel and other methods must have filters that returns only selected garmin id types.
Sounds reasonable and should be easy to implement. WanMil wrote
2. Use a separate overview style file and fetch the Garmin ids out of it. Then use these Garmin ids to build the overview map. I think the overview map should be configurable (one likes to see motorways, others like to see rivers etc.) Maybe it would also be possible to add a special overview statement or use special overview levels in the normal style files to achieve the same.
I sill have no clear idea what we need. I think at least a list of wanted types for each class (point,line,polygon). Or maybe more complex to allow the creation of multiple levels in the overview map. WanMil wrote
3. In case --precomp-sea parameter is set the data from an additional file in the precompiled sea folder is used.
You mean this additional file could provide all wanted info like level2- boundaries, rivers, etc.? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5755050.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
WanMil wrote
3. In case --precomp-sea parameter is set the data from an additional file in the precompiled sea folder is used. You mean this additional file could provide all wanted info like level2- boundaries, rivers, etc.?
No, only sea data. I think that we don't need the other stuff. It is contained in the img files. Of course the problem will be to handle them appropriately, e.g. the "Bodensee" might be split into several small polygons that might need to be reassembled for the overview map. Yes, the sea data is also contained in the img files but we don't need to invent a new type of precompiled data and therefore it is quite easy to get high quality data. WanMil
Sounds good Wanmil, a separate style file for generating the overview map is also a good thing. I have succesfully updated the overview maps for my Europe maps with the patch, it is already an improvement to see no blank maps anymore when zooming out! Wanmil wrote:
What about the following ideas:
1. Retrieve the data from the highest instead of the lowest level. The lowest level often contains fragmentary data, e.g. have a look a the boundaries in your example image http://gis.19327.n5.nabble.com/file/n5754697/africa_overview.png The data could be merged so that long ways are created that do not fall through the filters (DouglasPeucker etc.). The MapReader.linesForLevel and other methods must have filters that returns only selected garmin id types.
2. Use a separate overview style file and fetch the Garmin ids out of it. Then use these Garmin ids to build the overview map. I think the overview map should be configurable (one likes to see motorways, others like to see rivers etc.) Maybe it would also be possible to add a special overview statement or use special overview levels in the normal style files to achieve the same.
3. In case --precomp-sea parameter is set the data from an additional file in the precompiled sea folder is used.
WanMil
A more detailed basemap is also more preferable should you want to add a window restriction to Mapsource .When you drag the map,anything outside the frame gets shown as a basemap. www.pinns.co.uk/osm/osm/basemapframe.jpg The map is created using mkgmap, not the tdb file, as it requires a higher tdb version , ie 4.09+ ..Nick -- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606p5754939.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (6)
-
Felix Hartmann -
Gerd Petermann -
GerdP
-
Minko -
n Willink -
WanMil