-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 28.04.2013 15:00, schrieb GerdP:
> What problem do you have with the diff? If you use e.g. java -jar
> splitter.jar --help > splitter.options you should get a normal text
> file. If you do that again with an older version of splitter and
> another o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 28.04.2013 13:39, schrieb GerdP:
> I'm happy with the way how it works, but feel free to post a
> patch. Look into ParamParser.displayUsage()
Sorry, i wrote ambiguous.
Everything works fine, except there is a cosmetic problem with CR/LF.
Every opt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 28.04.2013 13:38, schrieb Henning Scholland:
Hi Henning
> I'm sending stdout to a file lika splitter.log. Terminal stays
> clean and in case of an error I (or a dev) can take a look in the
> log.
Something like that?
java -jar splitter.jar 2>&1 >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
is it possible to reduce output of splitter on stdout?
Most infos are IMHO useless for DAUs like me and shut be on stderr or
in a logfile like mkgmap's
tia
Bernd
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
'java -jar splitter.jar --help=options > splitter_options' print out
very long lines, up to 267 characters.
I found SplitterParams.java, but i don't now how to fix this
I'm using openSUSE Linux as OS
Bernd
-BEGIN PGP SIGNATURE-
Version:
Am 15.04.2013 15:54, schrieb Josef Latt:
> this style is missing cycleway=track ...
>
> Could someone contact Bernd.
I'm here ;-)
Thanks for this hint
And you should have my mail-address
Bernd
signature.asc
Description: OpenPGP digital signature
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 13.04.2013 17:58, schrieb Franco Bez:
> As the use of routable types for road2 in overlays might break the
> routing (route goes to tile border and then jumps on a straight
> line to the target, a non existant way is used for routing), you
> should
Am 13.04.2013 12:51, schrieb Gerd Petermann:
Hi
> I don't think that the problem with Robert-Bosch-Str. 14 is caused by that.
I'm testing at this moment some changes of the style oon my Oregon, to
use invisible lines for 0x08, 0x09 and 0x0c.
Over this lines, i have put some nonroutable types li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.04.2013 13:28, schrieb Franco Bez:
> I will do a few more tests soon, and post the results here. I
> currently have the impression that at least the roundabout -
> overlay - problem might still be there.
Ok, all roundabouts with this overlay(s)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 10.04.2013 18:27, schrieb GerdP:
> with "it works" I mean that you don't see the described routing
> problems. Do you mean the same or do you talk about how it looks
> like?
I didn't see this routing problems on other streets, only on this
specia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 10.04.2013 14:35, schrieb GerdP:
> My result with an Oregon 450t , software version 5.50: version
> 2447: routing to POI "Schönwetter Automobile" works, but address
> "Robert-Bosch-Straße 14" doesn't work.
As i write in the other mail, the last pa
Am 10.04.2013 17:55, schrieb Gerd Petermann:
Hello Gerd
> does that mean that you think that it only works when the 2nd type is also
> routable?
IMHO yes, but maybe types like 0x14, 0x15,to 0x2f also work, i didn't
test them.
all other types 0x10001ff didn't work for me.
0x0c with overlay 0x0
Am 10.04.2013 09:10, schrieb GerdP:
> My understanding of the program code is that it simply adds lines with the
> given types.
> Maybe it was meant to be
> "Make sure that only the first way in the overlays file is routeable. "
+1
I made some tests with nonroutable Types for the overlays like 0x
Am 20.03.2013 08:38, schrieb Gerd Petermann:
> Hi all,
>>> Solved, if i use 'name-tag-list=name:de,name,int_name' in '-c map.conf'
>>>
>>> 'name_tag = name:de, name' in ³STYLE/options' didn't work.
>>>
>>> Don't know why ;-)
>>
>> I didn't try, but the source code evaluates name-tag-list, not na
hen
On 21/03/13 23:00, Bernd Weigelt wrote:
> Done
>
> bayern_basemap_gmapsupp.img.zip
Thanks, I will investigate. No guarantees that I will be able to find
anything quickly though.
..Steve
___
mkgmap-dev mailing list
mkgmap-dev@lists
Am 21.03.2013 23:44, schrieb Steve Ratcliffe:
> Could you upload a single .img tile that contains an example of the
> problem. You could use http://files.mkgmap.org.uk
Done
bayern_basemap_gmapsupp.img.zip
Build with 'x-housenumbers'
I can build you a map of England. too
Bernd
signature.as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 21.03.2013 11:27, schrieb Bernd Weigelt:
> Yes, that worksforme.
>
> I'm able to build some maps with 'x-housenumber' IMHO the source
> of this problem, and without it.
Without 'x-housenumbers' all streets ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 21.03.2013 11:19, schrieb GerdP:
> sounds reasonable if their is no routable way to that adress. Does
> that mean that one has to be careful how he selects the target or
> are some roads never displayed without a number?
Yes, that worksforme.
I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 20.03.2013 11:47, schrieb franco_bez:
>> Gerd
>
> This sounds very bad indeed. I can only partly agree that the bug
> has to be fixed in the garmin software, not the img file. As the
> bug not only affects one single garmin device (Remember the sa
Am 17.03.2013 10:26, schrieb Bernd Weigelt:
> Maybe it is a problem with _my_ own systemconfig openSUSE 12.2 and 12.3.
Solved, if i use 'name-tag-list=name:de,name,int_name' in '-c map.conf'
'name_tag = name:de, name' in ³STYLE/options' didn't work.
Am 19.03.2013 14:40, schrieb GerdP:
> thanks for the hints, I tried it and found no problem. Seems that I exactly
> the same input file(s) and style to reproduce the problem.
> Please post them if possible (not all o5m files, only the one (or maybe
> more) which contain the data for this area.
Hi
> I cannot reproduce the error in Basecamp :-(I didn't test my maps with BC, it happened on my Oregon, too> I remember that I saw similar error messages on my Oregon when I installed a> new map and tried to use previously created waypoints. May this be the case> here as well?I didn't use waypoints
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 16.03.2013 21:01, schrieb Carlos Dávila:
> I downloaded bounds_20130308.zip when WanMil announced it in the
> list but yesterday I noticed mkgmap wasn't able to use it. I
> re-downloaded it and now it works fine. Maybe you have the same
> problem.
oblem with bounds_*.zip
El 16/03/13 18:51, Bernd Weigelt escribió:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello
>
> I've got a mail from an user in Sri Lanka, who use a map on a Nüvi
>
>
> | The last OSM Sri Lanka only map that you sent me has a Reg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
I've got a mail from an user in Sri Lanka, who use a map on a Nüvi
| The last OSM Sri Lanka only map that you sent me has a Region
| Error.Garmin nuvi device shows the country
| name of the map as *Sh??rii Lnkaa.* It spells Sri Lanka deadly wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
and it happens with polygons, too
18:34:57 WARNING (MultiPolygonRelation):
/home/bernd/map_build/tiles/63240003.o5m: Polygon
4611686018427393360(36P)(145416916[3P],142957969[9P],25495183[2P],142957968[6P],25885914[2P],142957952[3P],142957958[4P],32
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 15.03.2013 18:03, schrieb Bernd Weigelt:
BTW
I see this with ways without using 'process-destination', i'm using
'process-exits'
Bernd
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 15.03.2013 17:20, schrieb GerdP:
> please check: Do they disappear when you remove option
> process-destination? I think thats the only function which creates
> ways before the connection check is done, but I was not able to
> reproduce the problem
201 - 228 of 228 matches
Mail list logo