Re: [mkgmap-dev] [mkgmap-svn] Commit: r1671: output dir

Hi I still have the same problem with r1671 or later. The problem is caused by the --index option. Maps generated without --index work fine on MapSource. Nobody else has this problem? OK Thanks for the information. I assume you are not using --output-dir? I'll try building an index before

Re: [mkgmap-dev] [mkgmap-svn] Commit: r1671: output dir

Steve Ratcliffe (st...@parabola.me.uk) wrote: Hi I still have the same problem with r1671 or later. The problem is caused by the --index option. Maps generated without --index work fine on MapSource. Nobody else has this problem? OK Thanks for the information. I assume you are not using

Re: [mkgmap-dev] [mkgmap-svn] Commit: r1671: output dir

OK Thanks for the information. I assume you are not using --output-dir? I'll try building an index before and after r1671 there should be no difference. Perhaps the file is being created in the wrong place/wrong name. Thanks again. I have now found the probable problem and will get a

[mkgmap-dev] Index problem fixed

Hi I've just committed a fix for a problem building valid index files that was introduced in version r1671. Everyone having problems with the index should upgrade to r1691 (or downgrade to r1670 or lower!) ..Steve ___ mkgmap-dev mailing list

Re: [mkgmap-dev] Proposal: Multipolygon handling andline based multipolygons

Hi WanMil, Thanks so much for the fix. I have tried it so far on 2 style files and it works great. I can now also run the splitter overlap very high to allow for long distances between nodes and it still works. I even tried 5 and it works. It even fixed the mutltiple border names. Normally

Re: [mkgmap-dev] Proposal: Multipolygon handlingandline based multipolygons

I forgot to mention, I finally worked out how to apply a patch, it is now very easy. I use TortoiseSVN to download the SVN then use TortoiseSVN with its inbuilt apply patch. Then I use ANT to compile the build.xml. Markus_g -Original Message- From:

Re: [mkgmap-dev] Index problem fixed

using 1671, I get these errors: ava.lang.IllegalArgumentException: InputStream cannot be null at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:117) at uk.me.parabola.mkgmap.build.LocatorConfig.loadConfig(LocatorConfig.java:70) at

Re: [mkgmap-dev] Index problem fixed

But no mapsource crash. On Wed, Sep 15, 2010 at 7:05 PM, maning sambale emmanuel.samb...@gmail.com wrote: Using r1691 ava.lang.IllegalArgumentException: InputStream cannot be null        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:117)        at

[mkgmap-dev] Commit: r1692: Fix bug in constructing jar file introduced in 1688.

Version 1692 was commited by steve on 2010-09-15 12:25:41 +0100 (Wed, 15 Sep 2010) Fix bug in constructing jar file introduced in 1688. Causes problem like: java.lang.IllegalArgumentException: InputStream cannot be null at

Re: [mkgmap-dev] Index problem fixed

On 15/09/10 12:05, maning sambale wrote: using 1671, I get these errors: ava.lang.IllegalArgumentException: InputStream cannot be null at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:117) Sorry that is a bug that I introduced yesterday in the construction of the jar

Re: [mkgmap-dev] Index problem fixed

No more MapSource crashes neither exceptions with 1692 El 15/09/10 13:26, Steve Ratcliffe escribió: On 15/09/10 12:05, maning sambale wrote: using 1671, I get these errors: ava.lang.IllegalArgumentException: InputStream cannot be null at

[mkgmap-dev] Commit: r1694: This patch enables mkgmap to make use of real multipolygons and of multipolygons where only the members should be tagged (e.g. country boundaries) without any change on the

Version 1694 was commited by steve on 2010-09-15 14:11:45 +0100 (Wed, 15 Sep 2010) This patch enables mkgmap to make use of real multipolygons and of multipolygons where only the members should be tagged (e.g. country boundaries) without any change on the style rules. It adds a copy of each