Re: [mkgmap-dev] error in address index
On 05/03/15 12:50, GerdP wrote: I tried a lot of names in the last days, the problem only occured with names containing brackets. Not sure if all those names produce problems. I've found the problem -- it is the change in r3487. We really need the multi sort key. I'll think about another way, else I shall revert to the previous patch for it. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] MapSource error: MDR_TRIM_ADDR.CXX-347-6.16.3.0
On 05/03/15 16:50, Alexandre Loss wrote: The problem was in the ordering of the input-file in the args file. *They need to be sorted in descending order of their size.* OK that is helpful - but the order is actually by map number not by size. Happens to be the same thing by coincidence in this case :) It is the mapnumber that is recorded inside the file, not the name of the file itself that matter, although that is the usually the same thing for mkgmap produced maps. I did add code so that it didn't matter what order they were given but recently I found a case where it didn't seem to work and I guess that this now confirms it. The last fix was in r3211. I'm not sure if it is possible to fix it properly or if we are just going to have to give an error if it is wrong. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] --make-opposite-cycleways option
Hi Gerd, I added the following to the lines file in my style and it works
fine there if I remove the --make-opposite-cycleways option, allowing just
cycling and walking against the flow. However, it doesn't seem to work
correctly if I add it to the default style (it allows cars to go the wrong
way along the one-way street).
highway=* (oneway=yes | oneway=-1 | oneway=true | oneway=1 |
oneway=reverse) (oneway:bicycle=no | cycleway=opposite |
cycleway=opposite_lane | cycleway=opposite_track) {delete oneway; delete
cycleway; set access=no; delete foot; delete vehicle; delete motor_vehicle;
delete motorcar; delete goods; delete hgv; delete psv; delete emergency;
delete taxi; delete bus; add bicycle=yes; set highway=cycleway} [0x10
road_class=0 road_speed=1 resolution 24 continue]
I can't see why this might be happening. Has anyone any ideas (the attached
patch is what I changed)?
Regards,
Mike
From: Gerd Petermann [mailto:gpetermann_muenc...@hotmail.com]
Sent: 04 March 2015 16:22
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] --make-opposite-cycleways option
Hi Mike,
the style cannot create a way, but it can add multiple routable ways for one
OSM way.
Use continue or continue with actions for that.
The comment is a bit misleading and I think the code for old-style is now
obsolete as well.
Gerd
_
From: m...@tvage.co.uk mailto:m...@tvage.co.uk
To: mkgmap-dev@lists.mkgmap.org.uk mailto:mkgmap-dev@lists.mkgmap.org.uk
Date: Wed, 4 Mar 2015 16:01:56 +
Subject: Re: [mkgmap-dev] --make-opposite-cycleways option
Hi Gerd, I was not clear what you meant by change the style to produce the
same result, so I provided a change to the style that with the code changes
produces the same result as now. Unless a style can create an extra way, I
can't see how a style can be set up to allow cycling in both directions, but
other traffic only in one direction without using the extra way created by
the --make-opposite-cycleways code. Can a style create a way? I got the list
of tags to delete from the following code which suggested that the following
lines were all access tags (plus a few tags mentioned elsewhere that I also
included):
public boolean init(ElementSaver saver, EnhancedProperties
props) {
if (props.getProperty(old-style, false)) {
// the access tags need to
be loaded if the old style handling
// is active and access
restrictions are handled by the java
// source code and not by
the style
usedTags.add(access);
usedTags.add(bicycle);
usedTags.add(carpool);
usedTags.add(delivery);
usedTags.add(emergency);
usedTags.add(foot);
usedTags.add(goods);
usedTags.add(hgv);
usedTags.add(motorcar);
usedTags.add(motorcycle);
usedTags.add(psv);
usedTags.add(route);
usedTags.add(taxi);
}
I gather that route is not an access tag, so I agree that it should not be
included.
Regards,
Mike
From: Gerd Petermann [mailto:gpetermann_muenc...@hotmail.com]
Sent: 04 March 2015 05:31
To: mkgmap-dev@lists.mkgmap.org.uk mailto:mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] --make-opposite-cycleways option
Hi Mike,
as I said, I'd be more happy to have a patch that remove's the option
and shows how to change the default style instead to get the same result
as with your patch.
Your patch tries to remove all kinds of tags which might lead to wrong
routing:
+cycleWay.deleteTag(vehicle);
+cycleWay.deleteTag(motor_vehicle);
+cycleWay.deleteTag(carpool);
+cycleWay.deleteTag(delivery);
+cycleWay.deleteTag(emergency);
+cycleWay.deleteTag(foot);
+cycleWay.deleteTag(goods);
+cycleWay.deleteTag(hgv);
+cycleWay.deleteTag(motorcar);
+cycleWay.deleteTag(motorcycle);
+cycleWay.deleteTag(psv);
+cycleWay.deleteTag(route);
+cycleWay.deleteTag(taxi);
+cycleWay.deleteTag(bus);
+cycleWay.deleteTag(truck);
Please explain why you remove route=* .
I think that one should be kept.
Gerd
_
From: m...@tvage.co.uk mailto:m...@tvage.co.uk
To: mkgmap-dev@lists.mkgmap.org.uk mailto:mkgmap-dev@lists.mkgmap.org.uk
Date:
Re: [mkgmap-dev] MapSource error: MDR_TRIM_ADDR.CXX-347-6.16.3.0
Hi Steve, Give an error if it is wrong should be a good solution, better than allow install and get a error in MapSource. Anyway, your information was very useful. But the must interesting thing is that the order can be ascending or descending. Do you confirm that the order doesn't matter since it is ordered? Thanks 2015-03-05 19:59 GMT-03:00 Steve Ratcliffe st...@parabola.me.uk: On 05/03/15 16:50, Alexandre Loss wrote: The problem was in the ordering of the input-file in the args file. *They need to be sorted in descending order of their size.* OK that is helpful - but the order is actually by map number not by size. Happens to be the same thing by coincidence in this case :) It is the mapnumber that is recorded inside the file, not the name of the file itself that matter, although that is the usually the same thing for mkgmap produced maps. I did add code so that it didn't matter what order they were given but recently I found a case where it didn't seem to work and I guess that this now confirms it. The last fix was in r3211. I'm not sure if it is possible to fix it properly or if we are just going to have to give an error if it is wrong. ..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] --make-opposite-cycleways option
Hi Mike,
Hi Gerd, I added the following to the lines file in my style and it works fine
there if I remove the --make-opposite-cycleways option, allowing just cycling
and walking against the flow. However, it doesn’t seem to work correctly if I
add it to the default style (it allows cars to go the wrong way along the
one-way street). highway=* (oneway=yes | oneway=-1 | oneway=true | oneway=1 |
oneway=reverse) (oneway:bicycle=no | cycleway=opposite |
cycleway=opposite_lane | cycleway=opposite_track) {delete oneway; delete
cycleway; set access=no; delete foot; delete vehicle; delete motor_vehicle;
delete motorcar; delete goods; delete hgv; delete psv; delete emergency; delete
taxi; delete bus; add bicycle=yes; set highway=cycleway} [0x10 road_class=0
road_speed=1 resolution 24 continue] I can’t see why this might be happening.
Has anyone any ideas (the attached patch is what I changed)?
I think that is the problem I was discussing with Minko. The order in which
routable ways are added
by the style matters, although we don't know exactly why.
With the --make-opposite-cycleways the cycle way is added after the normal
way,
with your change below it is added before.
Garmin algos seem to use only one way in some cases, esp. at the beginning of a
route.
Further thoughts:
1) Your new patch also removes the special handling for mkgmap:synthesised in
inc/access
-#limit artificial cycleways to to resolution 24
-mkgmap:synthesised=yes mkgmap:bicycle=yes { set
mkgmap:highest-resolution-only = true }
This is okay for your case, but I should mention that the tag
mkgmap:synthesised is also evaluated within mkgmap to avoid some
meaningless warnings in e.g. the roundabout checks.
In other words: A style that adds multiple routable ways for one OSM way
should try to setmkgmap:synthesised=true
when options like --check-roundabouts or --check-roundabout-flares are used.
I think we might as well set that a corresponding flag in mkgmap when it
detects
that more than one routable way was added (with res 24) for one OSM way.
2) Maybe we can replace the --make-opposite-cycleways option by
a new special tag like mkgmap:add_cycleway=[before|after] ?
Gerd
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] MapSource error: MDR_TRIM_ADDR.CXX-347-6.16.3.0
Hi guys, I think I found the problem! It seems incredible, but the problem had nothing to do with meaningless names or something like that. The problem was in the ordering of the input-file in the args file. *They need to be sorted in descending order of their size.* I came to this conclusion by experimentation. At least it worked for me. I don't know if it has any theoretical foundation, but I think it is important to share this with you. Thank you. Alexandre 2015-03-05 9:32 GMT-03:00 Alexandre Loss alexandre.l...@gmail.com: Hi Gerd and Steve, I removed all meaningless names from the index, removing all mkgmap tag regarding address from these ways. They left to be shown in the MapSource address searching tool. But error persists. Alexandre 2015-03-05 3:28 GMT-03:00 Gerd Petermann gpetermann_muenc...@hotmail.com : Hi Alexandre, I think the message means that mkgmap has created an index that is not valid, probably because a limit was reached that mkgmap doesn't know. I noticed that your data contains a lot of highways with rather meaningless names like TERRA, RUA,ESTRADA MUNICIPAL etc. Maybe this is the reason. These names are also causing a long run time in the housenumber processing. Gerd -- Date: Wed, 4 Mar 2015 23:32:58 -0300 From: alexandre.l...@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] MapSource error: MDR_TRIM_ADDR.CXX-347-6.16.3.0 Hi Gerd, Some of the tiles that I compiled with mkgmap are throw a MapSource error MDR_TRIM_ADDR.CXX-347-6.16.3.0 when I'm trying to send the map to GPS. I found an old discussion about this error (i.e: https://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg13038.html) but it couldn't help me. Please, can you give me a help to deal with this problem? I uploaded the files at http://files.mkgmap.org.uk/download/258/trc.zip and this is my styles: http://files.mkgmap.org.uk/download/259/mkgmap-style-tracksource.rar And this is the command used to run mkgmap: java -Xmx4096m -XX:+UseConcMarkSweepGC -jar ..\Ferramentas\mkgmap.jar ^ --style-file=..\Ferramentas\mkgmap-style-tracksource ^ -c TRC-SC.args More specifically, I'm getting this error in the tile 94422861.osm.gz Any help will be great. Thank you. Alexandre ___ 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
Re: [mkgmap-dev] MapSource error: MDR_TRIM_ADDR.CXX-347-6.16.3.0
Hi Gerd, Any order produces a installable map for MapSource. However, depending of the order, this map should be or not installed into a GPS. Moreover, I tested the ascending order and it works too. Very strange. Alexandre 2015-03-05 14:27 GMT-03:00 GerdP gpetermann_muenc...@hotmail.com: Hi Alexandre, I think the information is important, but your args file contains the max-jobs option, that means the order is also dependend on the number of processors. Don't know if Steve needs the info, baybe you can say the order that doesn't work and one that works (both without the max-jobs option) Gerd Alexandre Loss wrote Hi guys, I think I found the problem! It seems incredible, but the problem had nothing to do with meaningless names or something like that. The problem was in the ordering of the input-file in the args file. *They need to be sorted in descending order of their size.* I came to this conclusion by experimentation. At least it worked for me. I don't know if it has any theoretical foundation, but I think it is important to share this with you. Thank you. Alexandre 2015-03-05 9:32 GMT-03:00 Alexandre Loss alexandre.loss@ : Hi Gerd and Steve, I removed all meaningless names from the index, removing all mkgmap tag regarding address from these ways. They left to be shown in the MapSource address searching tool. But error persists. Alexandre 2015-03-05 3:28 GMT-03:00 Gerd Petermann gpetermann_muenchen@ : Hi Alexandre, I think the message means that mkgmap has created an index that is not valid, probably because a limit was reached that mkgmap doesn't know. I noticed that your data contains a lot of highways with rather meaningless names like TERRA, RUA,ESTRADA MUNICIPAL etc. Maybe this is the reason. These names are also causing a long run time in the housenumber processing. Gerd -- Date: Wed, 4 Mar 2015 23:32:58 -0300 From: alexandre.loss@ To: mkgmap-dev@.org Subject: [mkgmap-dev] MapSource error: MDR_TRIM_ADDR.CXX-347-6.16.3.0 Hi Gerd, Some of the tiles that I compiled with mkgmap are throw a MapSource error MDR_TRIM_ADDR.CXX-347-6.16.3.0 when I'm trying to send the map to GPS. I found an old discussion about this error (i.e: https://www.mail-archive.com/ mkgmap-dev@.org /msg13038.html) but it couldn't help me. Please, can you give me a help to deal with this problem? I uploaded the files at http://files.mkgmap.org.uk/download/258/trc.zip and this is my styles: http://files.mkgmap.org.uk/download/259/mkgmap-style-tracksource.rar And this is the command used to run mkgmap: java -Xmx4096m -XX:+UseConcMarkSweepGC -jar ..\Ferramentas\mkgmap.jar ^ --style-file=..\Ferramentas\mkgmap-style-tracksource ^ -c TRC-SC.args More specifically, I'm getting this error in the tile 94422861.osm.gz Any help will be great. Thank you. Alexandre ___ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- View this message in context: http://gis.19327.n5.nabble.com/MapSource-error-MDR-TRIM-ADDR-CXX-347-6-16-3-0-tp5835857p5835973.html Sent from the Mkgmap Development mailing list archive at Nabble.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] Problem to understand splitter.jar --description
Hi Maybe it is a problem with my Oregon650, because the map description is different from my older Oregon 450, see the attached screenshot since the last weeekend i'm using template.args instead of tiles/*.o5m, but i can't get a usable description from splitter. before the change i got a description like 'bonn_20150305_1800' this is a workaround for me to limits of the O650 Other devices has a family name followed by the description as example: Basemap bonn_20150305_1800 I know, that template.args overwrite mkgmap's description and template.args should be overwritten by splitter's description. But the description the device is now the same as the description of the last tile. Can someone help me with the correct options? Bernd java -ea -Xmx6G -jar /home/bernd/map_build/splitter-r421/splitter.jar splitter.log --geonames-file=/home/bernd/map_build/cities15000.zip --description=bonn_20150305_1800 --mapid=6501 --output=o5m --precomp-sea=/home/bernd/map_build/sea_20150302.zip --write-kml=bonn.kml --keep-complete --overlap=0 --split-file=/home/bernd/map_build/areas/bonn_areas.list /home/bernd/map_build/o5m/bonn.o5m java -ea -Xmx6G -jar /home/bernd/map_build/mkgmap-housenumbers2-r3490/mkgmap.jar --bounds=/home/bernd/map_build/bounds_20150302.zip --precomp-sea=/home/bernd/map_build/sea_20150302.zip --generate-sea --style-file=/home/bernd/map_build/styles/basemap_style --name-tag-list=name:de,name,name:en,int_name --mapname=65001001 --family-id=4 --product-id=44 --family-name=Basemap --draw-priority=10 -c /home/bernd/map_build/styles/options -c /home/bernd/map_build/tiles/template.args /home/bernd/map_build/styles/styles_typ.txt # Following is a list of map tiles. Add a suitable description # for each one. mapname: 65010001 description: DE-Wiesbaden input-file: 65010001.o5m ... mapname: 65010026 description: DE-Oberhausen input-file: 65010026.o5m ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Problem to understand splitter.jar --description
El 05/03/15 a las 18:43, Bernd Weigelt escribió: Hi Maybe it is a problem with my Oregon650, because the map description is different from my older Oregon 450, see the attached screenshot since the last weeekend i'm using template.args instead of tiles/*.o5m, but i can't get a usable description from splitter. before the change i got a description like 'bonn_20150305_1800' this is a workaround for me to limits of the O650 Other devices has a family name followed by the description as example: Basemap bonn_20150305_1800 I know, that template.args overwrite mkgmap's description and template.args should be overwritten by splitter's description. But the description the device is now the same as the description of the last tile. Can someone help me with the correct options? Bernd java -ea -Xmx6G -jar /home/bernd/map_build/splitter-r421/splitter.jar splitter.log --geonames-file=/home/bernd/map_build/cities15000.zip --description=bonn_20150305_1800 --mapid=6501 --output=o5m --precomp-sea=/home/bernd/map_build/sea_20150302.zip --write-kml=bonn.kml --keep-complete --overlap=0 --split-file=/home/bernd/map_build/areas/bonn_areas.list /home/bernd/map_build/o5m/bonn.o5m java -ea -Xmx6G -jar /home/bernd/map_build/mkgmap-housenumbers2-r3490/mkgmap.jar --bounds=/home/bernd/map_build/bounds_20150302.zip --precomp-sea=/home/bernd/map_build/sea_20150302.zip --generate-sea --style-file=/home/bernd/map_build/styles/basemap_style --name-tag-list=name:de,name,name:en,int_name --mapname=65001001 --family-id=4 --product-id=44 --family-name=Basemap --draw-priority=10 -c /home/bernd/map_build/styles/options -c /home/bernd/map_build/tiles/template.args /home/bernd/map_build/styles/styles_typ.txt # Following is a list of map tiles. Add a suitable description # for each one. mapname: 65010001 description: DE-Wiesbaden input-file: 65010001.o5m ... mapname: 65010026 description: DE-Oberhausen input-file: 65010026.o5m Passing both --description and --geonames-file to splitter doesn't make sense as both parameters are used to add a description to each tile in template.args. If you use both only geonames-file is used and description is ignored. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] MapSource error: MDR_TRIM_ADDR.CXX-347-6.16.3.0
Hi Gerd and Steve, I removed all meaningless names from the index, removing all mkgmap tag regarding address from these ways. They left to be shown in the MapSource address searching tool. But error persists. Alexandre 2015-03-05 3:28 GMT-03:00 Gerd Petermann gpetermann_muenc...@hotmail.com: Hi Alexandre, I think the message means that mkgmap has created an index that is not valid, probably because a limit was reached that mkgmap doesn't know. I noticed that your data contains a lot of highways with rather meaningless names like TERRA, RUA,ESTRADA MUNICIPAL etc. Maybe this is the reason. These names are also causing a long run time in the housenumber processing. Gerd -- Date: Wed, 4 Mar 2015 23:32:58 -0300 From: alexandre.l...@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] MapSource error: MDR_TRIM_ADDR.CXX-347-6.16.3.0 Hi Gerd, Some of the tiles that I compiled with mkgmap are throw a MapSource error MDR_TRIM_ADDR.CXX-347-6.16.3.0 when I'm trying to send the map to GPS. I found an old discussion about this error (i.e: https://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg13038.html) but it couldn't help me. Please, can you give me a help to deal with this problem? I uploaded the files at http://files.mkgmap.org.uk/download/258/trc.zip and this is my styles: http://files.mkgmap.org.uk/download/259/mkgmap-style-tracksource.rar And this is the command used to run mkgmap: java -Xmx4096m -XX:+UseConcMarkSweepGC -jar ..\Ferramentas\mkgmap.jar ^ --style-file=..\Ferramentas\mkgmap-style-tracksource ^ -c TRC-SC.args More specifically, I'm getting this error in the tile 94422861.osm.gz Any help will be great. Thank you. Alexandre ___ 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
Re: [mkgmap-dev] error in address index
Hi Steve, I tried a lot of names in the last days, the problem only occured with names containing brackets. Not sure if all those names produce problems. Gerd Steve Ratcliffe wrote On 04/03/15 11:01, Gerd Petermann wrote: For some searches I get The selected street is not valid in this map product. Please select a different street. I see the problem only when both --x-split-name-index and --housenumbers are given (I thought --housenumbers was the default!). It happens with or without the city field. This is with Mapsource 6.10.2. It seems to me that the problem only occurs when there is a bracketed ref after the name. Do you see any examples where that is not the case? ..Steve ___ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- View this message in context: http://gis.19327.n5.nabble.com/error-in-address-index-tp5835767p5835938.html Sent from the Mkgmap Development mailing list archive at Nabble.com. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] error in address index
Hi Gerd please check the file http://files.mkgmap.org.uk/download/257/63240008.o5m For some searches I get The selected street is not valid in this map product. Please select a different street. I've downloaded it and looking at it now. I will also look at the MDR_ADDR_TRIM problem. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] error in address index
Great Steve! Thanks for the analysis of the MDR_ADDR_TRIM too! Alexandre 2015-03-05 7:27 GMT-03:00 Steve Ratcliffe st...@parabola.me.uk: Hi Gerd please check the file http://files.mkgmap.org.uk/download/257/63240008.o5m For some searches I get The selected street is not valid in this map product. Please select a different street. I've downloaded it and looking at it now. I will also look at the MDR_ADDR_TRIM problem. ..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] error in address index
On 04/03/15 11:01, Gerd Petermann wrote: For some searches I get The selected street is not valid in this map product. Please select a different street. I see the problem only when both --x-split-name-index and --housenumbers are given (I thought --housenumbers was the default!). It happens with or without the city field. This is with Mapsource 6.10.2. It seems to me that the problem only occurs when there is a bracketed ref after the name. Do you see any examples where that is not the case? ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] access rules
Hi all, the thread http://gis.19327.n5.nabble.com/make-opposite-cycleways-option-tp5835586.html made me think about the tag bicycle=designated In Germany this means bicycle and only bicycles are allowed http://wiki.openstreetmap.org/wiki/File:120px-Zeichen_237.svg.png I think we ignore this in inc/access. On the other hand, I am missing a simple method to say something like : ignore all access tags but one I think setaccess no was meant to be used for that, but it changes only the mkgmap:xxx values like mkgmap:car , and we learned that the use outside inc/access causes problems. Any thoughts? Gerd ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Problem to understand splitter.jar --description
Hi, I think Bernd should either not use the template.args file or add --description=xyz before --gmapsupp ? I never looked at it: What tool shows the description of an individual tile and where? Gerd Date: Thu, 5 Mar 2015 20:10:45 +0100 From: cdavi...@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem to understand splitter.jar --description El 05/03/15 a las 18:43, Bernd Weigelt escribió: Hi Maybe it is a problem with my Oregon650, because the map description is different from my older Oregon 450, see the attached screenshot since the last weeekend i'm using template.args instead of tiles/*.o5m, but i can't get a usable description from splitter. before the change i got a description like 'bonn_20150305_1800' this is a workaround for me to limits of the O650 Other devices has a family name followed by the description as example: Basemap bonn_20150305_1800 I know, that template.args overwrite mkgmap's description and template.args should be overwritten by splitter's description. But the description the device is now the same as the description of the last tile. Can someone help me with the correct options? Bernd java -ea -Xmx6G -jar /home/bernd/map_build/splitter-r421/splitter.jar splitter.log --geonames-file=/home/bernd/map_build/cities15000.zip --description=bonn_20150305_1800 --mapid=6501 --output=o5m --precomp-sea=/home/bernd/map_build/sea_20150302.zip --write-kml=bonn.kml --keep-complete --overlap=0 --split-file=/home/bernd/map_build/areas/bonn_areas.list /home/bernd/map_build/o5m/bonn.o5m java -ea -Xmx6G -jar /home/bernd/map_build/mkgmap-housenumbers2-r3490/mkgmap.jar --bounds=/home/bernd/map_build/bounds_20150302.zip --precomp-sea=/home/bernd/map_build/sea_20150302.zip --generate-sea --style-file=/home/bernd/map_build/styles/basemap_style --name-tag-list=name:de,name,name:en,int_name --mapname=65001001 --family-id=4 --product-id=44 --family-name=Basemap --draw-priority=10 -c /home/bernd/map_build/styles/options -c /home/bernd/map_build/tiles/template.args /home/bernd/map_build/styles/styles_typ.txt # Following is a list of map tiles. Add a suitable description # for each one. mapname: 65010001 description: DE-Wiesbaden input-file: 65010001.o5m ... mapname: 65010026 description: DE-Oberhausen input-file: 65010026.o5m Passing both --description and --geonames-file to splitter doesn't make sense as both parameters are used to add a description to each tile in template.args. If you use both only geonames-file is used and description is ignored. ___ 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
