Re: [mkgmap-dev] Missing sea and coastline while using Splitter
Hi, My way is more easy, and changes or experiments are easy to run : 1. rename the template.args (produced from splitter) to alaska_template.args, to avoid overwriting by the next run. 2. write all options in the alaska_template.args. Each option is one line. use a texteditor (not Word ) to do so. save in .txt format. It looks for example like this : /latin1// //family-id=24983// //name-tag-list=name:en,int_name,name// //gmapsupp// //description="Alaska"// //country-name=USA// //country-abbr=USA// //series-name=MyOwnAlaskaMap// //index// //location-autofill="is_in,nearest" // //copyright-message="Dave //Swarthout"// //link-pois-to-ways// //add-pois-to-areas// //reduce-point-density=4// //reduce-point-density-polygon=8// //merge-lines// //route// //drive-on=right// //net// //housenumbers// //x-split-name-index// //check-roundabouts// //check-roundabout-flares// //process-destination// //process-exits// //poi-address// //style-file="C:\Users\alask\Dropbox\Mapping\DJS_styles" //precomp-sea="C:\Users\alask\Downloads\Maps\sea.zip" //bounds="C:\Users\alask\Downloads\Maps\bounds" /# C:\Users\alask\Dropbox\Mapping\24983djs.TYP" # i don't know how to include typfiles/ #max-jobs reduces runtime on 2 cores prozessors //max-jobs=// //output-dir=//C:\Users\alask\Downloads\Maps\// // //# Following is a list of map tiles. Add a suitable description// //# for each one.// // //mapname= 63240001// //#give it a usefull name// //description= Nord// //# adjust your path here !! Fullpath is recommended // //input-file=D:\splitter\63240001.osm.pbf // // //mapname= 63240002// //description= Middle// //input-file=\splitter\63240002.osm.pbf// // //mapname= 63240003// //description= South// //input-file=\splitter\63240003osm.pbf/ 3: start mkgmap : java -Xmx1000m -jar mkgmap.jar *-c "C:\Users\Alask\Documents\splitter\alaska_template.args" . *that is all .* * regards Thomas Am 12.04.2017 um 01:37 schrieb Dave Swarthout: java -Xmx1000m -jar mkgmap.jar *-c "C:\Users\Alask\Documents\splitter\template.args"* --latin1 --family-id=24983 --name-tag-list=name:en,int_name,name --gmapsupp --description="Alaska" --country-name=USA --country-abbr=USA --index --location-autofill="is_in,nearest" --copyright-message="ODbL by OSM contributors" --link-pois-to-ways --add-pois-to-areas --reduce-point-density=4 --reduce-point-density-polygon=8 --merge-lines --route --drive-on=right --net --housenumbers --x-split-name-index --check-roundabouts --check-roundabout-flares --process-destination --process-exits --poi-address *--generate-sea=land-tag=natural=background --style-file="C:\Users\alask\Dropbox\Mapping\DJS_styles" --precomp-sea="C:\Users\alask\Downloads\Maps\sea.zip" --bounds="C:\Users\alask\Downloads\Maps\bounds" "C:\Users\alask\Dropbox\Mapping\24983djs.TYP"* * * Is the placement or order of the arguments important? Any other ideas or suggestions much appreciated.* * Thanks for your help, Dave -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Missing sea and coastline while using Splitter
Hi, I have been compiling my own maps of my local areas (<600 mB) for a couple of years now but the other day for the first time I had to use splitter to divide a large .osm file. It took several tries to get everything working to the point that a useful map emerged from the process. However, my directives are not being processed so the map I get is a plain vanilla version The sea and coastline are invisible in the finished product. In addition, some of my custom lines are missing, for example, the ones used for unpaved roads and waterway direction. Inexplicably, most of my custom styles for both highways and POIs are visible. Th simple splitter command line I'm using is here: [code]java -Xmx1000m -jar ..\splitter\splitter.jar "C:\Users\alask\Downloads\Maps\Alaska.osm" --output-dir=..\splitter > ..\splitter\splitter.log [/code] I've seen examples of a splitter command that uses the *--precomp-sea="C:\Users\alask\Downloads\Maps\sea.zip" *argument in its call but iI tried that and it made no difference in the result. Anyway, this generates three .osm files (63240001, 2, and 3) which I then process with mkgmap and the following command line. This exact comand line (but without the template.args parameter) runs perfectly and creates a map containing all my styles and shows the coastline and sea properly: java -Xmx1000m -jar mkgmap.jar *-c "C:\Users\Alask\Documents\splitter\template.args"* --latin1 --family-id=24983 --name-tag-list=name:en,int_name,name --gmapsupp --description="Alaska" --country-name=USA --country-abbr=USA --index --location-autofill="is_in,nearest" --copyright-message="ODbL by OSM contributors" --link-pois-to-ways --add-pois-to-areas --reduce-point-density=4 --reduce-point-density-polygon=8 --merge-lines --route --drive-on=right --net --housenumbers --x-split-name-index --check-roundabouts --check-roundabout-flares --process-destination --process-exits --poi-address *--generate-sea=land-tag=natural=background --style-file="C:\Users\alask\Dropbox\Mapping\DJS_styles" --precomp-sea="C:\Users\alask\Downloads\Maps\sea.zip" --bounds="C:\Users\alask\Downloads\Maps\bounds" "C:\Users\alask\Dropbox\Mapping\24983djs.TYP"* Is the placement or order of the arguments important? Any other ideas or suggestions much appreciated. Thanks for your help, Dave -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] (no subject)
Hi, I have been compiling my own maps of my local areas (<600 mB) for a couple of years now but the other day for the first time I had to use splitter to divide a large .osm file. It took several tries to get everything working to the point that a useful map emerged from the process. However, my directives are not being processed so the map I get is a plain vanilla version The sea and coastline are invisible in the finished product. In addition, some of my custom lines are missing, for example, the ones used for unpaved roads and waterway direction. Inexplicably, most of my custom styles for both highways and POIs are visible. Th simple splitter command line I'm using is here: [code]java -Xmx1000m -jar ..\splitter\splitter.jar "C:\Users\alask\Downloads\Maps\Alaska.osm" --output-dir=..\splitter > ..\splitter\splitter.log [/code] I've seen examples of a splitter command that uses the *--precomp-sea="C:\Users\alask\Downloads\Maps\sea.zip" *argument in its call but iI tried that and it made no difference in the result. Anyway, this generates three .osm files (63240001, 2, and 3) which I then process with mkgmap and the following command line. This exact comand line (but without the template.args parameter) runs perfectly and creates a map containing all my styles and shows the coastline and sea properly: java -Xmx1000m -jar mkgmap.jar *-c "C:\Users\Alask\Documents\splitter\template.args"* --latin1 --family-id=24983 --name-tag-list=name:en,int_name,name --gmapsupp --description="Alaska" --country-name=USA --country-abbr=USA --index --location-autofill="is_in,nearest" --copyright-message="ODbL by OSM contributors" --link-pois-to-ways --add-pois-to-areas --reduce-point-density=4 --reduce-point-density-polygon=8 --merge-lines --route --drive-on=right --net --housenumbers --x-split-name-index --check-roundabouts --check-roundabout-flares --process-destination --process-exits --poi-address *--generate-sea=land-tag=natural=background --style-file="C:\Users\alask\Dropbox\Mapping\DJS_styles" --precomp-sea="C:\Users\alask\Downloads\Maps\sea.zip" --bounds="C:\Users\alask\Downloads\Maps\bounds" "C:\Users\alask\Dropbox\Mapping\24983djs.TYP"* Is the placement or order of the arguments important? Any other ideas or suggestions much appreciated. Thanks for your help, Dave -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Address search on device with --x-split-name-index option
Hi Steve, r3893 creates now the same mdr17 records in gmapsupp as MapSource when map is created with --x-split-name-index. Please review my changes in the branch. I still see one small difference in Mdr 4: mkgmap writes this entry 0250 | 18 | 2a 00 00| Type 0x2a00. Unknown 0x0 and MapSource doesn't. Maybe the sub type 0 is not needed what other subtypes follow? Gerd Von: mkgmap-dev im Auftrag von Steve Ratcliffe Gesendet: Dienstag, 11. April 2017 10:53:03 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Address search on device with --x-split-name-index option Hi Gerd > BTW: Why do we fill mdr17 when index is created for the PC? > It seems not to be written but requires memory. That's true, it is not used and does not need to be calculated for the desktop index. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Address search on device with --x-split-name-index option
Hi Gerd BTW: Why do we fill mdr17 when index is created for the PC? It seems not to be written but requires memory. That's true, it is not used and does not need to be calculated for the desktop index. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Address search on device with --x-split-name-index option
Hi Steve, I think that means that mdr17 should only see those mdr7 records which have getNameOffset()==0 ? BTW: Why do we fill mdr17 when index is created for the PC? It seems not to be written but requires memory. Gerd Von: mkgmap-dev im Auftrag von Steve Ratcliffe Gesendet: Dienstag, 11. April 2017 10:03:53 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Address search on device with --x-split-name-index option On 11/04/17 07:54, Gerd Petermann wrote: > One point that might be interesting: I compare the listing produced by > MdrDisplay for the gmapsupp produced by r3449 and the one from MapSource. > I see a much longer list in Mdr17 for r3449. Oh yes you are right, from a quick look it appears that mkgmap is ignoring the name offset when creating mdr17 so there are a lot of extra and out of order entries. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Address search on device with --x-split-name-index option
Hi Gerd I just noticed that the gmapsupp produced by MapSource changes a lot when I enable/disable option --x-split-name-index, so it probably calculates the gmapsupp index based on the index calculated by mkgmap, not from scratch. If that is true it is probably not a good idea to use that as a reference. It is true that it uses the desktop index to generate the device index, but it is still useful information because the formats are different and so it has to calculate those, and some things have to be recalculated anyway. So as you noted it appears to be fixing up mdr17, and it also fixes the repeat flags. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Address search on device with --x-split-name-index option
On 11/04/17 07:54, Gerd Petermann wrote: One point that might be interesting: I compare the listing produced by MdrDisplay for the gmapsupp produced by r3449 and the one from MapSource. I see a much longer list in Mdr17 for r3449. Oh yes you are right, from a quick look it appears that mkgmap is ignoring the name offset when creating mdr17 so there are a lot of extra and out of order entries. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Address search on device with --x-split-name-index option
Hi Steve, I just noticed that the gmapsupp produced by MapSource changes a lot when I enable/disable option --x-split-name-index, so it probably calculates the gmapsupp index based on the index calculated by mkgmap, not from scratch. If that is true it is probably not a good idea to use that as a reference. Gerd Von: mkgmap-dev im Auftrag von Gerd Petermann Gesendet: Dienstag, 11. April 2017 08:54:19 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Address search on device with --x-split-name-index option Hi Steve, sorry, maybe I made a mistake while testing. The search for "Rheing" in Feuerthalen shows a list with "Rheingasse" and "Rheingutstrasse", when I select "Rheingasse" and leave the house number field empty it lists "Rheingasse 10", "Obere Rheingasse" , "Untere Rheingasse" and "Rheingasse". The search for "Rheing" in Switzerland (no City) also lists "Rheingasse" and "Rheingutstrasse" , when I select "Rheingasse" and leave house number empty it shows a map with Rheingasse 2 in Basel. I expected to see a list with all roads named "Rheingasse" (or maybe all roads containing "Rheingasse") in Switzerland, but the device only shows the one in Basel. I am sitting near Bremen, distance to Basel is 598km , distance to Feuerthalen is 580km, so maybe it just selects the first match. One point that might be interesting: I compare the listing produced by MdrDisplay for the gmapsupp produced by r3449 and the one from MapSource. I see a much longer list in Mdr17 for r3449. Gerd Von: mkgmap-dev im Auftrag von Gerd Petermann Gesendet: Dienstag, 11. April 2017 07:56:16 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Address search on device with --x-split-name-index option Hi Steve, good question. The street search works but searching for "Rheing" in Switzerland doesn't list "Obere Rheingasse". The city search is similar, I also don't see "Obere Rheingasse" when I search for "Rheing" in Feuerthalen. I do find "Rue de la Concorde" when I search for "Conc" in France and also when I search it in City Huningue in France. Unfortunately MdrDisplay fails to print the mdr 22 index for the gmapsupp produced by MapSource. It writes a few lines and then an error: - MDR 22 (streets by country) -- || | Record 1 000abf53 | 00 | 02 | 2 map number || | street 0 R 000abf54 | 01 | 8d | flag 141 || | Record 2 000abf55 | 02 | cb | 203 map number || | street 0 R 000abf56 | 03 | 80 | flag 128 ... 000abf6b | 18 | 01 | 1 map number || | street 0 R 000abf6c | 19 | 34 | flag 52 || | Record 14 000abf6d | 1a | 75 | 117 map number Failed in section 22: java.lang.AssertionError: not a map number 117 Similar problem with the gmapsupp produed by r3449: - MDR 22 (streets by country) -- || | Record 1 0012a419 | 00 | 03 | 3 map number || | street 0 R 0012a41a | 01 | 61 | flag 97 || | Record 2 0012a41b | 02 | 4b | 75 map number Failed in section 22: java.lang.AssertionError: not a map number 75 Gerd Von: mkgmap-dev im Auftrag von Steve Ratcliffe Gesendet: Montag, 10. April 2017 23:13:57 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Address search on device with --x-split-name-index option Hi Gerd, > same problem with r3449 and r3472. Oh that is a shame. Does it work if mapsource creates the gmapsupp? The mdr20 looks similar in either case, although the repeat flags are incorrect in the mkgmap generated one. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
