overview2 branch
Hi, I think r2616 is ready for trunk, but I will probably not have time to work on any errors during the next 10 days. So, I think it is better to give all some time for testing. @Steve: I have updated the doc, but I see some error warnings and creation of pdf fails. Reg. the open question about merge-lines: I have no preference here. I can add public boolean isSimilar(MapLine other){ if (direction != other.direction) return false; return isSimilar((MapElement) other); } to MapLine.java, it looks "more correct", but it increases the img size a little bit with the default style. Gerd
On Fri, May 17, Gerd Petermann wrote:
Hi,
I think r2616 is ready for trunk, but I will probably not have time to work on any errors during the next 10 days. So, I think it is better to give all some time for testing.
I think there is a bug in the documentation: + levels = 0:24, 1:22, 2:20, 3:18 + overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12 This are 9 levels, but in the other document it is stated, that only 8 levels are allowed, including the overview levels. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Hi Thorsten, my understanding is that we can have 8 levels in the normal map and another 8 in the overview map. Where did you find the wrong docu? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5761507.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, On Fri, May 17, GerdP wrote:
Hi Thorsten,
my understanding is that we can have 8 levels in the normal map and another 8 in the overview map.
Where did you find the wrong docu?
Ok, then I misunderstand the "Again, up to 8 levels are allowed.". I thought this means normal and overlay levels together. But for some reasons, I don't get an overview map generated. Maybe it's because I'm using the level keyword in my style file and not resolution? But in that case, "level 3" in the style, what does this mean now? That it is level 3 in the normal map and level 3 in the overview map? I used now 0-6 for the normal map and 7 vor the overview map, but there is still no overview map visible in mapsource. Need to do more tests over the weekend. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
levels continue. So you need to specify via options file, or commandline at which level to switch from nomal map to overview map. It all depends on the overview-levels option, where a level appears.. You need to continue counting levels, not start again at 0. max is 0-7 for normal map plus 8-15 for overview map (if you use all levels possible in both). On 17.05.2013 10:05, Thorsten Kukuk wrote:
Hi Gerd,
On Fri, May 17, GerdP wrote:
Hi Thorsten,
my understanding is that we can have 8 levels in the normal map and another 8 in the overview map.
Where did you find the wrong docu? Ok, then I misunderstand the "Again, up to 8 levels are allowed.". I thought this means normal and overlay levels together.
But for some reasons, I don't get an overview map generated. Maybe it's because I'm using the level keyword in my style file and not resolution? But in that case, "level 3" in the style, what does this mean now? That it is level 3 in the normal map and level 3 in the overview map? I used now 0-6 for the normal map and 7 vor the overview map, but there is still no overview map visible in mapsource.
Need to do more tests over the weekend.
Thorsten
On Fri, May 17, Felix Hartmann wrote:
levels continue. So you need to specify via options file, or commandline at which level to switch from nomal map to overview map. It all depends on the overview-levels option, where a level appears..
You need to continue counting levels, not start again at 0. max is 0-7 for normal map plus 8-15 for overview map (if you use all levels possible in both).
Not possible: Error in style: Error: Level number too large, max=7 Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Hi Thorsten, I am not sure: Do you still have this problem? I was not able to reproduce it with the your style files in the git repo (commit f6e5f5404048e043499a7c299886ac7d2d3fd263) Gerd
Date: Fri, 17 May 2013 17:30:19 +0200 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] overview2 branch
On Fri, May 17, Felix Hartmann wrote:
levels continue. So you need to specify via options file, or commandline at which level to switch from nomal map to overview map. It all depends on the overview-levels option, where a level appears..
You need to continue counting levels, not start again at 0. max is 0-7 for normal map plus 8-15 for overview map (if you use all levels possible in both).
Not possible: Error in style: Error: Level number too large, max=7
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, On Mon, May 27, Gerd Petermann wrote:
Hi Thorsten,
I am not sure: Do you still have this problem? I was not able to reproduce it with the your style files in the git repo (commit f6e5f5404048e043499a7c299886ac7d2d3fd263)
Which git repo? I don't use git... I only need one level for the overview map, and I had level 7 free, so I used only that. But I assume that, if you use level 8 or higher in the style file, you will get the same error message. But haven't looked in the mkgmap code yet. Thorsten
Gerd
Date: Fri, 17 May 2013 17:30:19 +0200 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] overview2 branch
On Fri, May 17, Felix Hartmann wrote:
levels continue. So you need to specify via options file, or commandline at which level to switch from nomal map to overview map. It all depends on the overview-levels option, where a level appears..
You need to continue counting levels, not start again at 0. max is 0-7 for normal map plus 8-15 for overview map (if you use all levels possible in both).
Not possible: Error in style: Error: Level number too large, max=7
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ 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
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Hi Thorsten,
I am not sure: Do you still have this problem? I was not able to reproduce it with the your style files in the git repo (commit f6e5f5404048e043499a7c299886ac7d2d3fd263)
Which git repo? I don't use git...
sorry, I confused the nick names. I tested with https://github.com/aighes/RadReiseKarte It contains an options file with these settings: levels=0:24, 1:23, 2:22, 3:21, 4:20, overview-levels=5:18, 6:16, 7:14, 8:12, 9:11 and e.g. this line in the polygons file: natural=sea { add mkgmap:skipSizeFilter=true } [0x32 level 8] Gerd
I only need one level for the overview map, and I had level 7 free, so I used only that.
But I assume that, if you use level 8 or higher in the style file, you will get the same error message. But haven't looked in the mkgmap code yet.
Thorsten
Gerd
Date: Fri, 17 May 2013 17:30:19 +0200 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] overview2 branch
On Fri, May 17, Felix Hartmann wrote:
levels continue. So you need to specify via options file, or commandline at which level to switch from nomal map to overview map. It all depends on the overview-levels option, where a level appears..
You need to continue counting levels, not start again at 0. max is 0-7 for normal map plus 8-15 for overview map (if you use all levels possible in both).
Not possible: Error in style: Error: Level number too large, max=7
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ 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
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Jepand it is working as expected. There is only a problem with international cycle-routes in level 7 (res 14). They are not rendered completely, but I'm investigating it. So don't know jet if it's a problem in mkgmap or in style or in osm-relation (maybe to many subrelations) Henning Am 27.05.2013 09:29, schrieb Gerd Petermann:
Hi Thorsten,
I am not sure: Do you still have this problem? I was not able to reproduce it with the your style files in the git repo (commit f6e5f5404048e043499a7c299886ac7d2d3fd263)
Which git repo? I don't use git...
sorry, I confused the nick names. I tested with https://github.com/aighes/RadReiseKarte
It contains an options file with these settings: levels=0:24, 1:23, 2:22, 3:21, 4:20, overview-levels=5:18, 6:16, 7:14, 8:12, 9:11
and e.g. this line in the polygons file: natural=sea { add mkgmap:skipSizeFilter=true } [0x32 level 8]
Gerd
I only need one level for the overview map, and I had level 7 free, so I used only that.
But I assume that, if you use level 8 or higher in the style file, you will get the same error message. But haven't looked in the
mkgmap code
yet.
Thorsten
Gerd
Date: Fri, 17 May 2013 17:30:19 +0200 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] overview2 branch
On Fri, May 17, Felix Hartmann wrote:
levels continue. So you need to specify via options file, or commandline at which level to switch from nomal map to overview map. It all depends on the overview-levels option, where a level appears..
You need to continue counting levels, not start again at 0. max is 0-7 for normal map plus 8-15 for overview map (if you use all levels possible in both).
Not possible: Error in style: Error: Level number too large, max=7
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ 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
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ 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
Hi Thorsten, I tested with level in rules, but not after the last changes of the levels handling. Maybe it doesn't work anymore. Gerd Thorsten Kukuk wrote
Hi Gerd,
On Fri, May 17, GerdP wrote:
Hi Thorsten,
my understanding is that we can have 8 levels in the normal map and another 8 in the overview map.
Where did you find the wrong docu?
Ok, then I misunderstand the "Again, up to 8 levels are allowed.". I thought this means normal and overlay levels together.
But for some reasons, I don't get an overview map generated. Maybe it's because I'm using the level keyword in my style file and not resolution? But in that case, "level 3" in the style, what does this mean now? That it is level 3 in the normal map and level 3 in the overview map? I used now 0-6 for the normal map and 7 vor the overview map, but there is still no overview map visible in mapsource.
Need to do more tests over the weekend.
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5761519.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
On Fri, May 17, GerdP wrote:
Hi Thorsten,
I tested with level in rules, but not after the last changes of the levels handling. Maybe it doesn't work anymore.
Ok, I played a little bit more and now I have the overview map. Don't know what the difference is that it works now, but I will find out ;) The polygons are completly broken, so I need to play more with it, but the lines are fine. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Maybe something to improve: If you feed mkgmap with img tiles (*.img) it will also index the ovm_*.img files which result in a crash in Mapsource. So I had to specify which tilenumbers I would like to process, for instance -c mkgmap.args 10*.img 49*.img When I started with the higher tile numbers first, like 49*.img 10*.img this also made the search index crash. Is this a known issue?
Hi Minko, it is quite easy to exclude the ovm_* files, but you can have similar problems with other files like the default overview file osmmap.img. I am not sure what to do in this case, as the name is configurable. @Steve: Is there a simple way to identify an img file that contains the overview map? Gerd
Date: Sun, 19 May 2013 10:29:15 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] overview2 branch
Maybe something to improve:
If you feed mkgmap with img tiles (*.img) it will also index the ovm_*.img files which result in a crash in Mapsource. So I had to specify which tilenumbers I would like to process, for instance -c mkgmap.args 10*.img 49*.img
When I started with the higher tile numbers first, like 49*.img 10*.img this also made the search index crash. Is this a known issue? _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, Well, the point is that a default overview file has to be made out of those img's, so it wont be there yet.
it is quite easy to exclude the ovm_* files, but you can have similar problems with other files like the default overview file osmmap.img. I am not sure what to do in this case, as the name is configurable.
@Steve: Is there a simple way to identify an img file that contains the overview map?
Gerd
Hi Minko, it might be there if you execute mkgmap twice, once with *.osm as input, next time with *.img I am not sure yet if the other combiner options like --gmapsupp, --index etc. have problems with this. Gerd Minko-2 wrote
Hi Gerd,
Well, the point is that a default overview file has to be made out of those img's, so it wont be there yet.
it is quite easy to exclude the ovm_* files, but you can have similar problems with other files like the default overview file osmmap.img. I am not sure what to do in this case, as the name is configurable.
@Steve: Is there a simple way to identify an img file that contains the overview map?
Gerd
mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5762858.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Yes, I agree this will lead to problems and it would be better if mkgmap also recognize and skips processing the overview img and other index img's (*_mdr.img) before compiling img tiles.
it might be there if you execute mkgmap twice, once with *.osm as input, next time with *.img I am not sure yet if the other combiner options like --gmapsupp, --index etc. have problems with this.
Gerd
Minko-2 wrote
Hi Gerd,
Well, the point is that a default overview file has to be made out of those img's, so it wont be there yet.
it is quite easy to exclude the ovm_* files, but you can have similar problems with other files like the default overview file osmmap.img. I am not sure what to do in this case, as the name is configurable.
@Steve: Is there a simple way to identify an img file that contains the overview map?
Gerd
mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5762858.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
Hi Gerd, Here is an example where I combine several img's, for instance to merge Lambertus img tiles into one big map or to add contour lines or hiking routes: http://www.openfietsmap.nl/downloads/osm_combi I have to filter out the index img's and overview img's with several batch files, so if mkgmap can recognize them automatically, the scripts would be more simple.
Yes, I agree this will lead to problems and it would be better if mkgmap also recognize and skips processing the overview img and other index img's (*_mdr.img) before compiling img tiles.
it might be there if you execute mkgmap twice, once with *.osm as input, next time with *.img I am not sure yet if the other combiner options like --gmapsupp, --index etc. have problems with this.
Gerd
Hi Minko, I did not try your batch file, but r2623 will ignore ovm_* files specified as command line args. It will still put the overview map into the gmapsupp if you use something like mkgmap --gmapsupp *.img Gerd
Date: Mon, 27 May 2013 12:05:11 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] overview2 branch
Hi Gerd, Here is an example where I combine several img's, for instance to merge Lambertus img tiles into one big map or to add contour lines or hiking routes: http://www.openfietsmap.nl/downloads/osm_combi
I have to filter out the index img's and overview img's with several batch files, so if mkgmap can recognize them automatically, the scripts would be more simple.
Yes, I agree this will lead to problems and it would be better if mkgmap also recognize and skips processing the overview img and other index img's (*_mdr.img) before compiling img tiles.
it might be there if you execute mkgmap twice, once with *.osm as input, next time with *.img I am not sure yet if the other combiner options like --gmapsupp, --index etc. have problems with this.
Gerd
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Thanks Gerd, r2623 ignores now ovm files as expected. Could you implement the commit from mkgmap-r2606 into the overview branch, because the non routable lines are still deleted? And in the points style file I would suggest to replace (place=capitol | place=capital) with place=city from the line (place=capitol | place=capital) & population > 999999 & name=* {set cityxx=yes} [0x0100 resolution 12 continue with_actions] And remove totally (place=capitol | place=capital) & cityxx!=yes & name=* {set cityxx=yes} [0x0100 resolution 14 continue with_actions] because -place=capitol/capital is a not a valid osm tag -capitals are mostly big cities -very small capitals like Vaduz, San Marino dont have to be rendered too early -capital=yes could also be captal from a region Bigger cities which are capitals are rendered early anyway See also the discussion earlier last week.
Hi, I've committed r2624 in the overview2 branch: -merged with trunk and applied changes suggested below. I want to find the cause for the polygon type 0x4a errors before I merge it back into trunk. Ciao, Gerd Minko-2 wrote
Thanks Gerd,
r2623 ignores now ovm files as expected.
Could you implement the commit from mkgmap-r2606 into the overview branch, because the non routable lines are still deleted?
And in the points style file I would suggest to replace (place=capitol | place=capital) with place=city from the line
(place=capitol | place=capital) & population > 999999 & name=* {set cityxx=yes} [0x0100 resolution 12 continue with_actions]
And remove totally
(place=capitol | place=capital) & cityxx!=yes & name=* {set cityxx=yes} [0x0100 resolution 14 continue with_actions]
because -place=capitol/capital is a not a valid osm tag -capitals are mostly big cities -very small capitals like Vaduz, San Marino dont have to be rendered too early -capital=yes could also be captal from a region
Bigger cities which are capitals are rendered early anyway
See also the discussion earlier last week. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5762916.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
On 27/05/13 08:43, Gerd Petermann wrote:
@Steve: Is there a simple way to identify an img file that contains the overview map?
I suspect that there should be, but we don't do anything special in any of the headers for an overview map as far as I recall. You can probably make a good guess since the first level of an overview map will normally be greater than 1. ..Steve
Am 28.05.2013 22:55, schrieb Steve Ratcliffe:
On 27/05/13 08:43, Gerd Petermann wrote:
@Steve: Is there a simple way to identify an img file that contains the overview map? I suspect that there should be, but we don't do anything special in any of the headers for an overview map as far as I recall. You can probably make a good guess since the first level of an overview map will normally be greater than 1. Sounds like a hack for me, because it would be possible, that level=1 is on overview-map.
What about using <id>.ovm as file-name for overview-tiles? Henning
Hi Henning, I want to identify the overview map itself, not the ovm_*.img work files . Reg. <id>.ovm: The work files are correct img files, so I think that we should use the *.img extension to allow double clicks for opening. (<id>.ovm would require new associations) Gerd Henning Scholland wrote
Am 28.05.2013 22:55, schrieb Steve Ratcliffe:
On 27/05/13 08:43, Gerd Petermann wrote: I suspect that there should be, but we don't do anything special in any of the headers for an overview map as far as I recall. You can probably make a good guess since the first level of an overview map will normally be greater than 1. Sounds like a hack for me, because it would be possible, that level=1 is on overview-map.
What about using <id> .ovm as file-name for overview-tiles?
Henning
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5763119.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, Can you use the overview mapname/number parameter if this is given in the mkgmap call? --overview-mapname=name If --tdbfile is enabled, this gives the name of the overview .img and .tdb files. The default map name is osmmap. --overview-mapnumber=8 digit number If --tdbfile is enabled, this gives the internal 8 digit number used in the overview map and tdb file. The default number is 63240000. And the filename_mdr.img is always the same as the filename.tdb and also the same as overview-mapname or overview-mapnumber?
I want to identify the overview map itself, not the ovm_*.img work files . Reg. <id>.ovm: The work files are correct img files, so I think that we should use the *.img extension to allow double clicks for opening. (<id>.ovm would require new associations)
Gerd
Hi Minko, don't think so. I want to detect the case where a user runs mkgmap like this: mkgmap --tdbfile *.img in a directory that already contains an overview map created by a previous call of mkgmap. Gerd Minko-2 wrote
Hi Gerd, Can you use the overview mapname/number parameter if this is given in the mkgmap call?
--overview-mapname=name If --tdbfile is enabled, this gives the name of the overview .img and .tdb files. The default map name is osmmap. --overview-mapnumber=8 digit number If --tdbfile is enabled, this gives the internal 8 digit number used in the overview map and tdb file. The default number is 63240000.
And the filename_mdr.img is always the same as the filename.tdb and also the same as overview-mapname or overview-mapnumber?
I want to identify the overview map itself, not the ovm_*.img work files . Reg. <id> .ovm: The work files are correct img files, so I think that we should use the *.img extension to allow double clicks for opening. ( <id> .ovm would require new associations)
Gerd
mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5763129.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Steve, Steve Ratcliffe wrote
On 27/05/13 08:43, Gerd Petermann wrote:
@Steve: Is there a simple way to identify an img file that contains the overview map?
I suspect that there should be, but we don't do anything special in any of the headers for an overview map as far as I recall. You can probably make a good guess since the first level of an overview map will normally be greater than 1.
well, the first level is also 0, but the high resolutions are probably missing. That should be good enough to issue a warning. Seems the only special thing are the 0x4a polygons. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5763118.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
On 29/05/13 08:05, GerdP wrote:
well, the first level is also 0, but the high resolutions are probably missing.
Oh, well it shouldn't be ;) With the default overview-levels of 4:17, 5:16, 6:15, 7:14, 8:12 then the first level is 4 and it should be writen as 4 in the file. I see that mkgmap subtracts the first level so that it starts at 0. This is not how any other map works though. In Garmin and cgpsmapper produced maps the overview map always starts at a level greater than 0. ..Steve
Steve Ratcliffe wrote
On 29/05/13 08:05, GerdP wrote:
well, the first level is also 0, but the high resolutions are probably missing.
Oh, well it shouldn't be ;) With the default overview-levels of 4:17, 5:16, 6:15, 7:14, 8:12 then the first level is 4 and it should be writen as 4 in the file.
I see that mkgmap subtracts the first level so that it starts at 0. This is not how any other map works though. In Garmin and cgpsmapper produced maps the overview map always starts at a level greater than 0.
OK, so it seems I am mixing levels and zoom levels. I have to look at this again. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5763245.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Steve, need your help here. See screenshot from Felix at http://gis.19327.n5.nabble.com/Overview2-branch-options-file-typo-tp5759855p... How do you think should the values look like for a configuration with - say 10 - levels, 5 in the normal maps and 5 in the overview map? And what do I have to change? I don't know how to produce an overview map with other tools, and afaik I don't have one from Garmin. Gerd
Date: Wed, 29 May 2013 12:06:15 +0100 From: steve@parabola.me.uk To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] overview2 branch
On 29/05/13 08:05, GerdP wrote:
well, the first level is also 0, but the high resolutions are probably missing.
Oh, well it shouldn't be ;) With the default overview-levels of 4:17, 5:16, 6:15, 7:14, 8:12 then the first level is 4 and it should be writen as 4 in the file.
I see that mkgmap subtracts the first level so that it starts at 0. This is not how any other map works though. In Garmin and cgpsmapper produced maps the overview map always starts at a level greater than 0.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd
need your help here. See screenshot from Felix at http://gis.19327.n5.nabble.com/Overview2-branch-options-file-typo-tp5759855p...
How do you think should the values look like for a configuration with - say 10 - levels, 5 in the normal maps and 5 in the overview map?
It should look like it does in the screenshot, with Zoom0=5, rather than Zoom0=0. But if you can't have a level greater than 8, then it would not be possible to have 10 levels in that case.
And what do I have to change?
I think that the overview map levels should just be LevelInfo.createFromString(levelSpec) but I see that used to be the case and then you changed it in r2592, so presumably some part of the code didn't deal with it properly. Can you recall the reason the change was made?
I don't know how to produce an overview map with other tools, and afaik I don't have one from Garmin.
A Garmin map that I own has the equivalent of levels = 0:23, 1:21, 2:19 overview-levels = 2:17, 3:15, 4:13 The overview map also has two empty levels above those, rather than the usual one empty level. http://files.mkgmap.org.uk/download/124/Selection_025.png ..Steve
Hi Steve, I changed it because of that screenshot and the remarks from Felix: http://gis.19327.n5.nabble.com/Overview2-branch-options-file-typo-tp5759855p... I wanted to have up to 8 levels for both the normal img and the overview map, and I found no problem with the overview map starting at level 0. I guess it would not be a problem for anyone to go back to the limit of 8 levels? Gerd Steve Ratcliffe wrote
Hi Gerd
need your help here. See screenshot from Felix at http://gis.19327.n5.nabble.com/Overview2-branch-options-file-typo-tp5759855p...
How do you think should the values look like for a configuration with - say 10 - levels, 5 in the normal maps and 5 in the overview map?
It should look like it does in the screenshot, with Zoom0=5, rather than Zoom0=0. But if you can't have a level greater than 8, then it would not be possible to have 10 levels in that case.
And what do I have to change?
I think that the overview map levels should just be LevelInfo.createFromString(levelSpec) but I see that used to be the case and then you changed it in r2592, so presumably some part of the code didn't deal with it properly. Can you recall the reason the change was made?
I don't know how to produce an overview map with other tools, and afaik I don't have one from Garmin.
A Garmin map that I own has the equivalent of
levels = 0:23, 1:21, 2:19 overview-levels = 2:17, 3:15, 4:13
The overview map also has two empty levels above those, rather than the usual one empty level.
http://files.mkgmap.org.uk/download/124/Selection_025.png
..Steve _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5763284.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Steve, maybe. I have installed Ubuntu 12.04 LTS, don't know what asciidoc version it uses. Gerd Steve Ratcliffe wrote
Hi
@Steve: I have updated the doc, but I see some error warnings and creation of pdf fails.
It works for me, so perhaps a version difference with one of the tools?
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5761803.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd
maybe. I have installed Ubuntu 12.04 LTS, don't know what asciidoc version it uses.
I forgot to ask what the error was? Is it only when creating pdf, or for the basic html output too? I'd like to make it work with standard packages if possible. I happen to use a reasonably recent checked out version, I can't remember exactly why. I use: hg clone https://asciidoc.googlecode.com/hg/#7c0bc8eacba9 And for PDF generation it is used with FOP 1.1: http://mirror.ox.ac.uk/sites/rsync.apache.org/xmlgraphics/fop/binaries/fop-1... ..Steve
Hi Steve, make without parms gives this and the generated htm file looks okay. asciidoc -a data-uri -a icons -a iconsdir=../resources/common-images/icons -b html5 style-manual.txt asciidoc: WARNING: rules.txt: line 285: missing style: [blockdef-open]: listing asciidoc: WARNING: rules.txt: line 306: missing style: [blockdef-open]: listing asciidoc: WARNING: rules.txt: line 319: missing style: [blockdef-open]: listing asciidoc: WARNING: <stdin>: line 7: missing style: [blockdef-open]: literal asciidoc: WARNING: rules.txt: line 439: missing style: [blockdef-open]: WARNING asciidoc: WARNING: rules.txt: line 695: missing style: [blockdef-open]: NOTE asciidoc: WARNING: creating.txt: line 55: missing style: [blockdef-open]: example make pdf shows these messages: a2x --xsl-file=../resources/docbook-xsl/fo.xsl --fop --icons --icons-dir=../resources/common-images/icons --asciidoc-opts='--conf-file=../resources/asciidoc/local-docbook45.conf' -a pubdate="$(date +'%d %B %Y')" style-manual.txt a2x: ERROR: fop -fo /home/sid/mkgmap-ov2/doc/styles/style-manual.fo -pdf /home/sid/mkgmap-ov2/doc/styles/style-manual.pdf returned non-zero exit status 127 make: *** [style-manual.pdf] Fehler 1 asciidoc --version shows asciidoc 8.6.6 Gerd
Date: Sun, 19 May 2013 20:55:41 +0100 From: steve@parabola.me.uk To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] overview2 branch
Hi Gerd
maybe. I have installed Ubuntu 12.04 LTS, don't know what asciidoc version it uses.
I forgot to ask what the error was? Is it only when creating pdf, or for the basic html output too?
I'd like to make it work with standard packages if possible.
I happen to use a reasonably recent checked out version, I can't remember exactly why.
I use: hg clone https://asciidoc.googlecode.com/hg/#7c0bc8eacba9
And for PDF generation it is used with FOP 1.1:
http://mirror.ox.ac.uk/sites/rsync.apache.org/xmlgraphics/fop/binaries/fop-1...
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 23/05/13 13:56, Gerd Petermann wrote:
Hi Steve,
make without parms gives this and the generated htm file looks okay.
asciidoc -a data-uri -a icons -a iconsdir=../resources/common-images/icons -b html5 style-manual.txt asciidoc: WARNING: rules.txt: line 285: missing style: [blockdef-open]: listing asciidoc: WARNING: rules.txt: line 306: missing style: [blockdef-open]: listing asciidoc: WARNING: rules.txt: line 319: missing style: [blockdef-open]: listing asciidoc: WARNING: <stdin>: line 7: missing style: [blockdef-open]: literal asciidoc: WARNING: rules.txt: line 439: missing style: [blockdef-open]: WARNING asciidoc: WARNING: rules.txt: line 695: missing style: [blockdef-open]: NOTE asciidoc: WARNING: creating.txt: line 55: missing style: [blockdef-open]: example
OK thanks. I have committed an extra config file that makes these warnings go away and improve the output. I don't know what the problem with pdf generation is and adding -v to a2x is the only way to find out what happens there. Unfortunatly the above fix for html makes pdf fail due to, I believe, an asciidoc bug in 8.6.6. So I will remove it for pdf. However that also means that the examples are not shaded. But better that than nothing. Actually the problem looks like the explicit labeling of paragraphs: [literal] -- stuff here -- is not supported properly in 8.6.6, but changing to the non-labeled way is fine: ---- stuff here ---- So I will just use the older better supported syntax. ..Steve
Hi Steve, thanks, warning are gone now. The problem with make pdf was simply a missing package: fop The message produced with a2x -vv showed that much clearer :O Gerd Steve Ratcliffe wrote
On 23/05/13 13:56, Gerd Petermann wrote:
Hi Steve,
make without parms gives this and the generated htm file looks okay.
asciidoc -a data-uri -a icons -a iconsdir=../resources/common-images/icons -b html5 style-manual.txt asciidoc: WARNING: rules.txt: line 285: missing style: [blockdef-open]: listing asciidoc: WARNING: rules.txt: line 306: missing style: [blockdef-open]: listing asciidoc: WARNING: rules.txt: line 319: missing style: [blockdef-open]: listing asciidoc: WARNING: <stdin> : line 7: missing style: [blockdef-open]: literal asciidoc: WARNING: rules.txt: line 439: missing style: [blockdef-open]: WARNING asciidoc: WARNING: rules.txt: line 695: missing style: [blockdef-open]: NOTE asciidoc: WARNING: creating.txt: line 55: missing style: [blockdef-open]: example
OK thanks. I have committed an extra config file that makes these warnings go away and improve the output.
I don't know what the problem with pdf generation is and adding -v to a2x is the only way to find out what happens there.
Unfortunatly the above fix for html makes pdf fail due to, I believe, an asciidoc bug in 8.6.6. So I will remove it for pdf. However that also means that the examples are not shaded. But better that than nothing.
Actually the problem looks like the explicit labeling of paragraphs:
[literal] -- stuff here --
is not supported properly in 8.6.6, but changing to the non-labeled way is fine:
---- stuff here ----
So I will just use the older better supported syntax.
..Steve _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/overview2-branch-tp5761475p5762830.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (7)
-
Felix Hartmann -
Gerd Petermann -
GerdP
-
Henning Scholland -
Minko -
Steve Ratcliffe -
Thorsten Kukuk