[mkgmap-dev] Commit r4434: remove :: from pre-formatted section in documentation

2020-01-30 Thread svn commit 
Version mkgmap-r4434 was committed by gerd on Fri, 31 Jan 2020

remove :: from pre-formatted section in documentation 

http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4434
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] Need help with build scripts

2020-01-30 Thread Gerd Petermann 
The attached patch changes the build process so that the 
mkgmap\resources\help\en\options is generated. It uses a slightly modified 
version of Mike Baggaleys program to compute this file with 
mkgmap\doc\options.txt as input.

My problem:
Up to now the generated file is in the svn repo and Eclipse uses this file when 
compiling mkgmap while 
ant dist 
first builds the file and then creates a copy of it and uses this copy to build 
mkgmap.jar.

My problems so far:
- if someone edits mkgmap\resources\help\en\options he will lose his edits when 
he runs ant 
- if someone uses Eclipse to debug or develop mkgmap the file is not build, 
probably the same problem in other IDEs

Any hints how to solve this? 

Gerd


options-generator.patch
Description: options-generator.patch
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Splitter Build Failure

2020-01-30 Thread News 
Ok I've got it now. I noticed in the following that I successfully 
downloaded ivy-2.5.0.jar but then seemed to be trying to use "Apache Ivy 
2.3.0-local-2017090712 - 2017090712" which was a local 
Apache-Ivy I had previously installed in order to try and fix this 
before asking the list. The updated build.xml and uninstalling the 
apache-ivy package did the trick


Thanks

Paul


download-ivy:
[mkdir] Created dir: 
/home/miscellaneous/Maps/tile-splitter/splitter/lib/build
[mkdir] Created dir: 
/home/miscellaneous/Maps/tile-splitter/splitter/lib/compile
[mkdir] Created dir: 
/home/miscellaneous/Maps/tile-splitter/splitter/lib/test
  [get] Getting: 
https://repo1.maven.org/maven2/org/apache/ivy/ivy/2.5.0/ivy-2.5.0.jar
  [get] To: 
/home/miscellaneous/Maps/tile-splitter/splitter/lib/build/ivy-2.5.0.jar


init-ivy:
Trying to override old definition of task antlib:org.apache.ivy.ant:buildobr
Trying to override old definition of task antlib:org.apache.ivy.ant:buildobr
[ivy:configure] impossible to define new type: class not found: 
org.apache.ivy.plugins.signer.bouncycastle.OpenPGPSignatureGenerator in 
[] nor Ivy classloader
[ivy:configure] :: Apache Ivy 2.3.0-local-2017090712 - 
2017090712 :: http://ant.apache.org/ivy/ ::
[ivy:configure] :: loading settings :: file = 
/home/miscellaneous/Maps/tile-splitter/splitter/ivysettings.xml


resolve-compile:
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve]  WARNINGS
[ivy:retrieve]  module not found: xpp3#xpp3;1.1.4c
[ivy:retrieve]   local: tried
[ivy:retrieve]/home/user/.ivy2/local/xpp3/xpp3/1.1.4c/ivys/ivy.xml
[ivy:retrieve]-- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve]/home/user/.ivy2/local/xpp3/xpp3/1.1.4c/jars/xpp3.jar
[ivy:retrieve]   shared: tried
[ivy:retrieve]/home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/ivys/ivy.xml
[ivy:retrieve]-- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve]/home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/jars/xpp3.jar
[ivy:retrieve]   public: tried
[ivy:retrieve] 
http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom

[ivy:retrieve]-- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve] 
http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar

[ivy:retrieve]   mkgmap: tried
[ivy:retrieve] 
http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/ivys/ivy.xml

[ivy:retrieve]-- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve] 
http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/jars/xpp3.jar

[ivy:retrieve]  ::
[ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
[ivy:retrieve]  ::
[ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
[ivy:retrieve]  ::
[ivy:retrieve]  ERRORS
[ivy:retrieve]  SERVER ERROR: HTTPS Required 
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
[ivy:retrieve]  SERVER ERROR: HTTPS Required 
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar

[ivy:retrieve]
[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

BUILD FAILED
/home/miscellaneous/Maps/tile-splitter/splitter/build.xml:113: 
impossible to resolve dependencies:

resolve failed - see output for details


On 30/01/2020 15:13, Steve Ratcliffe wrote:

Hi

I didn't fix any thing before you sent this message, but I found I needed to 
upgrade ivy for it to work. So I've committed that now.

mkgmap already used a later version.

Steve

On 30 January 2020 13:45:55 GMT, Gerd Petermann 
 wrote:

Hi all,

I just tried again after renaming .ivy cache directory with a clean checkout of 
spliter and mkgmap and both builds worked. A few minutes ago it didn't.
Maybe Steve has already fixed something. I've never cared much about the ivy 
stuff.

Gerd


Von: mkgmap-dev  im Auftrag von DD8KQ 

Gesendet: Donnerstag, 30. Januar 2020 14:44
An: Development list for mkgmap; News
Betreff: Re: [mkgmap-dev] Splitter Build Failure

I have a short look to your failures. For me, it looks like you have to
change the url-requests form http to https. But i don't know, where you
have to change it. 'repo1.maven.org' don't want to communicate with
unsecure http anymore.

Am 30.01.2020 um 14:04 schrieb News:

Hi Gerd

Sorry. This still fails. Full info below

[ivy:configure] impossible to define new type: class not found:
org.apache.ivy.plugins.signer.bouncycastle.OpenPGPSignatureGenerator
in [] nor Ivy classloader
[ivy:configure] :: Apache Ivy 2.3.0-local-2017090712 -
2017090712 :: http://ant.apache.org/ivy/ ::
[ivy:configure] :: loading settings :: file =
/home/miscellaneous/Maps/tile-splitter/splitter/ivysettings.xml

resolve-compile:
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve]  WARNINGS
[ivy:retrieve]  module not found: xpp3#xpp3;1.1.4c
[ivy:retrieve]   local

[mkgmap-dev] Commit r4433: improve documentation (Patch by Mike Baggaley)

2020-01-30 Thread svn commit 
Version mkgmap-r4433 was committed by gerd on Thu, 30 Jan 2020

improve documentation (Patch by Mike Baggaley)
TODO: add program to compile help/en/options from doc/options.txt during the 
build process

http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4433
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Splitter Build Failure

2020-01-30 Thread Steve Ratcliffe 
Hi

I didn't fix any thing before you sent this message, but I found I needed to 
upgrade ivy for it to work. So I've committed that now.

mkgmap already used a later version.

Steve

On 30 January 2020 13:45:55 GMT, Gerd Petermann 
 wrote:
>Hi all,
>
>I just tried again after renaming .ivy cache directory with a clean checkout 
>of spliter and mkgmap and both builds worked. A few minutes ago it didn't.
>Maybe Steve has already fixed something. I've never cared much about the ivy 
>stuff.
>
>Gerd
>
>
>Von: mkgmap-dev  im Auftrag von DD8KQ 
>
>Gesendet: Donnerstag, 30. Januar 2020 14:44
>An: Development list for mkgmap; News
>Betreff: Re: [mkgmap-dev] Splitter Build Failure
>
>I have a short look to your failures. For me, it looks like you have to
>change the url-requests form http to https. But i don't know, where you
>have to change it. 'repo1.maven.org' don't want to communicate with
>unsecure http anymore.
>
>Am 30.01.2020 um 14:04 schrieb News:
>> Hi Gerd
>>
>> Sorry. This still fails. Full info below
>>
>> [ivy:configure] impossible to define new type: class not found:
>> org.apache.ivy.plugins.signer.bouncycastle.OpenPGPSignatureGenerator
>> in [] nor Ivy classloader
>> [ivy:configure] :: Apache Ivy 2.3.0-local-2017090712 -
>> 2017090712 :: http://ant.apache.org/ivy/ ::
>> [ivy:configure] :: loading settings :: file =
>> /home/miscellaneous/Maps/tile-splitter/splitter/ivysettings.xml
>>
>> resolve-compile:
>> [ivy:retrieve]
>> [ivy:retrieve] :: problems summary ::
>> [ivy:retrieve]  WARNINGS
>> [ivy:retrieve]  module not found: xpp3#xpp3;1.1.4c
>> [ivy:retrieve]   local: tried
>> [ivy:retrieve] /home/user/.ivy2/local/xpp3/xpp3/1.1.4c/ivys/ivy.xml
>> [ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
>> [ivy:retrieve] /home/user/.ivy2/local/xpp3/xpp3/1.1.4c/jars/xpp3.jar
>> [ivy:retrieve]   shared: tried
>> [ivy:retrieve] /home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/ivys/ivy.xml
>> [ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
>> [ivy:retrieve] /home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/jars/xpp3.jar
>> [ivy:retrieve]   public: tried
>> [ivy:retrieve]
>> http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
>> [ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
>> [ivy:retrieve]
>> http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar
>> [ivy:retrieve]   mkgmap: tried
>> [ivy:retrieve]
>> http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/ivys/ivy.xml
>> [ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
>> [ivy:retrieve]
>> http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/jars/xpp3.jar
>> [ivy:retrieve] ::
>> [ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
>> [ivy:retrieve] ::
>> [ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
>> [ivy:retrieve] ::
>> [ivy:retrieve]  ERRORS
>> [ivy:retrieve]  SERVER ERROR: HTTPS Required
>> url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
>> [ivy:retrieve]  SERVER ERROR: HTTPS Required
>> url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar
>> [ivy:retrieve]
>> [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>>
>> BUILD FAILED
>> /home/miscellaneous/Maps/tile-splitter/splitter/build.xml:113:
>> impossible to resolve dependencies:
>> resolve failed - see output for details
>>
>> Thanks
>>
>> Paul
>>
>> On 30/01/2020 13:10, Gerd Petermann wrote:
>>> Hi Paul,
>>>
>>> please update, see
>>> http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&rev=596
>>>
>>> Gerd
>>>
>>> 
>>> Von: mkgmap-dev  im Auftrag
>>> von News 
>>> Gesendet: Donnerstag, 30. Januar 2020 13:05
>>> An: 'Development list for mkgmap'
>>> Betreff: [mkgmap-dev] Splitter Build Failure
>>>
>>> I recently clean reinstalled my PC (openSuSE Leap 15.1) and today was
>>> the first time I tried to build splitter and received the following
>>> errors
>>>
>>> BUILD FAILED
>>> /home/miscellaneous/Maps/tile-splitter/splitter/build.xml:95: Can't get
>>> http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.2.0/ivy-2.2.0.jar to
>>> /home/miscellaneous/Maps/tile-splitter/splitter/lib/build/ivy-2.2.0.jar
>>>
>>> I changed the line in build.xml to use https instead of http and I then
>>> got past this error and received the following error snippet
>>>
>>> [ivy:retrieve] ::
>>> [ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
>>> [ivy:retrieve] ::
>>> [ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
>>> [ivy:retrieve] ::
>>> [ivy:retrieve]  ERRORS
>>> [ivy:retrieve]  SERVER ERROR: HTTPS Required
>>> url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
>>> [ivy:retrieve]  S

Re: [mkgmap-dev] Splitter Build Failure

2020-01-30 Thread Gerd Petermann 
Hi all,

I just tried again after renaming .ivy cache directory with a clean checkout of 
spliter and mkgmap and both builds worked. A few minutes ago it didn't.
Maybe Steve has already fixed something. I've never cared much about the ivy 
stuff.

Gerd


Von: mkgmap-dev  im Auftrag von DD8KQ 

Gesendet: Donnerstag, 30. Januar 2020 14:44
An: Development list for mkgmap; News
Betreff: Re: [mkgmap-dev] Splitter Build Failure

I have a short look to your failures. For me, it looks like you have to
change the url-requests form http to https. But i don't know, where you
have to change it. 'repo1.maven.org' don't want to communicate with
unsecure http anymore.

Am 30.01.2020 um 14:04 schrieb News:
> Hi Gerd
>
> Sorry. This still fails. Full info below
>
> [ivy:configure] impossible to define new type: class not found:
> org.apache.ivy.plugins.signer.bouncycastle.OpenPGPSignatureGenerator
> in [] nor Ivy classloader
> [ivy:configure] :: Apache Ivy 2.3.0-local-2017090712 -
> 2017090712 :: http://ant.apache.org/ivy/ ::
> [ivy:configure] :: loading settings :: file =
> /home/miscellaneous/Maps/tile-splitter/splitter/ivysettings.xml
>
> resolve-compile:
> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve]  WARNINGS
> [ivy:retrieve]  module not found: xpp3#xpp3;1.1.4c
> [ivy:retrieve]   local: tried
> [ivy:retrieve] /home/user/.ivy2/local/xpp3/xpp3/1.1.4c/ivys/ivy.xml
> [ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
> [ivy:retrieve] /home/user/.ivy2/local/xpp3/xpp3/1.1.4c/jars/xpp3.jar
> [ivy:retrieve]   shared: tried
> [ivy:retrieve] /home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/ivys/ivy.xml
> [ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
> [ivy:retrieve] /home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/jars/xpp3.jar
> [ivy:retrieve]   public: tried
> [ivy:retrieve]
> http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
> [ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
> [ivy:retrieve]
> http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar
> [ivy:retrieve]   mkgmap: tried
> [ivy:retrieve]
> http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/ivys/ivy.xml
> [ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
> [ivy:retrieve]
> http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/jars/xpp3.jar
> [ivy:retrieve] ::
> [ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
> [ivy:retrieve] ::
> [ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
> [ivy:retrieve] ::
> [ivy:retrieve]  ERRORS
> [ivy:retrieve]  SERVER ERROR: HTTPS Required
> url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
> [ivy:retrieve]  SERVER ERROR: HTTPS Required
> url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar
> [ivy:retrieve]
> [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>
> BUILD FAILED
> /home/miscellaneous/Maps/tile-splitter/splitter/build.xml:113:
> impossible to resolve dependencies:
> resolve failed - see output for details
>
> Thanks
>
> Paul
>
> On 30/01/2020 13:10, Gerd Petermann wrote:
>> Hi Paul,
>>
>> please update, see
>> http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&rev=596
>>
>> Gerd
>>
>> 
>> Von: mkgmap-dev  im Auftrag
>> von News 
>> Gesendet: Donnerstag, 30. Januar 2020 13:05
>> An: 'Development list for mkgmap'
>> Betreff: [mkgmap-dev] Splitter Build Failure
>>
>> I recently clean reinstalled my PC (openSuSE Leap 15.1) and today was
>> the first time I tried to build splitter and received the following
>> errors
>>
>> BUILD FAILED
>> /home/miscellaneous/Maps/tile-splitter/splitter/build.xml:95: Can't get
>> http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.2.0/ivy-2.2.0.jar to
>> /home/miscellaneous/Maps/tile-splitter/splitter/lib/build/ivy-2.2.0.jar
>>
>> I changed the line in build.xml to use https instead of http and I then
>> got past this error and received the following error snippet
>>
>> [ivy:retrieve] ::
>> [ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
>> [ivy:retrieve] ::
>> [ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
>> [ivy:retrieve] ::
>> [ivy:retrieve]  ERRORS
>> [ivy:retrieve]  SERVER ERROR: HTTPS Required
>> url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
>> [ivy:retrieve]  SERVER ERROR: HTTPS Required
>> url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar
>>
>> So it seems that maven.org is only accepting https connections but I
>> can't find where to correct the above error
>>
>> Any suggestions?
>>
>> Thanks
>>
>> Paul
>> ___
>> mkgmap-dev mailing list
>> mkgmap-dev

Re: [mkgmap-dev] Splitter Build Failure

2020-01-30 Thread DD8KQ 

I have a short look to your failures. For me, it looks like you have to
change the url-requests form http to https. But i don't know, where you
have to change it. 'repo1.maven.org' don't want to communicate with
unsecure http anymore.

Am 30.01.2020 um 14:04 schrieb News:

Hi Gerd

Sorry. This still fails. Full info below

[ivy:configure] impossible to define new type: class not found:
org.apache.ivy.plugins.signer.bouncycastle.OpenPGPSignatureGenerator
in [] nor Ivy classloader
[ivy:configure] :: Apache Ivy 2.3.0-local-2017090712 -
2017090712 :: http://ant.apache.org/ivy/ ::
[ivy:configure] :: loading settings :: file =
/home/miscellaneous/Maps/tile-splitter/splitter/ivysettings.xml

resolve-compile:
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve]  WARNINGS
[ivy:retrieve]  module not found: xpp3#xpp3;1.1.4c
[ivy:retrieve]   local: tried
[ivy:retrieve] /home/user/.ivy2/local/xpp3/xpp3/1.1.4c/ivys/ivy.xml
[ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve] /home/user/.ivy2/local/xpp3/xpp3/1.1.4c/jars/xpp3.jar
[ivy:retrieve]   shared: tried
[ivy:retrieve] /home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/ivys/ivy.xml
[ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve] /home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/jars/xpp3.jar
[ivy:retrieve]   public: tried
[ivy:retrieve]
http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
[ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve]
http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar
[ivy:retrieve]   mkgmap: tried
[ivy:retrieve]
http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/ivys/ivy.xml
[ivy:retrieve]    -- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve]
http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/jars/xpp3.jar
[ivy:retrieve] ::
[ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
[ivy:retrieve] ::
[ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
[ivy:retrieve] ::
[ivy:retrieve]  ERRORS
[ivy:retrieve]  SERVER ERROR: HTTPS Required
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
[ivy:retrieve]  SERVER ERROR: HTTPS Required
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar
[ivy:retrieve]
[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

BUILD FAILED
/home/miscellaneous/Maps/tile-splitter/splitter/build.xml:113:
impossible to resolve dependencies:
    resolve failed - see output for details

Thanks

Paul

On 30/01/2020 13:10, Gerd Petermann wrote:

Hi Paul,

please update, see
http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&rev=596

Gerd


Von: mkgmap-dev  im Auftrag
von News 
Gesendet: Donnerstag, 30. Januar 2020 13:05
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] Splitter Build Failure

I recently clean reinstalled my PC (openSuSE Leap 15.1) and today was
the first time I tried to build splitter and received the following
errors

BUILD FAILED
/home/miscellaneous/Maps/tile-splitter/splitter/build.xml:95: Can't get
http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.2.0/ivy-2.2.0.jar to
/home/miscellaneous/Maps/tile-splitter/splitter/lib/build/ivy-2.2.0.jar

I changed the line in build.xml to use https instead of http and I then
got past this error and received the following error snippet

[ivy:retrieve] ::
[ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
[ivy:retrieve] ::
[ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
[ivy:retrieve] ::
[ivy:retrieve]  ERRORS
[ivy:retrieve]  SERVER ERROR: HTTPS Required
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
[ivy:retrieve]  SERVER ERROR: HTTPS Required
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar

So it seems that maven.org is only accepting https connections but I
can't find where to correct the above error

Any suggestions?

Thanks

Paul
___
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


--

#

 Viele Grüße und 73 de Manfred Haiduk, DD8KQ
 e-mail mhai...@t-online.de dd...@gmx.de

#

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://

Re: [mkgmap-dev] Splitter Build Failure

2020-01-30 Thread News 

Hi Gerd

Sorry. This still fails. Full info below

[ivy:configure] impossible to define new type: class not found: 
org.apache.ivy.plugins.signer.bouncycastle.OpenPGPSignatureGenerator in 
[] nor Ivy classloader
[ivy:configure] :: Apache Ivy 2.3.0-local-2017090712 - 
2017090712 :: http://ant.apache.org/ivy/ ::
[ivy:configure] :: loading settings :: file = 
/home/miscellaneous/Maps/tile-splitter/splitter/ivysettings.xml


resolve-compile:
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve]  WARNINGS
[ivy:retrieve]  module not found: xpp3#xpp3;1.1.4c
[ivy:retrieve]   local: tried
[ivy:retrieve]/home/user/.ivy2/local/xpp3/xpp3/1.1.4c/ivys/ivy.xml
[ivy:retrieve]-- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve]/home/user/.ivy2/local/xpp3/xpp3/1.1.4c/jars/xpp3.jar
[ivy:retrieve]   shared: tried
[ivy:retrieve]/home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/ivys/ivy.xml
[ivy:retrieve]-- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve]/home/user/.ivy2/shared/xpp3/xpp3/1.1.4c/jars/xpp3.jar
[ivy:retrieve]   public: tried
[ivy:retrieve] 
http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom

[ivy:retrieve]-- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve] 
http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar

[ivy:retrieve]   mkgmap: tried
[ivy:retrieve] http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/ivys/ivy.xml
[ivy:retrieve]-- artifact xpp3#xpp3;1.1.4c!xpp3.jar:
[ivy:retrieve] http://ivy.mkgmap.org.uk/repo/xpp3/xpp3/1.1.4c/jars/xpp3.jar
[ivy:retrieve]  ::
[ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
[ivy:retrieve]  ::
[ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
[ivy:retrieve]  ::
[ivy:retrieve]  ERRORS
[ivy:retrieve]  SERVER ERROR: HTTPS Required 
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
[ivy:retrieve]  SERVER ERROR: HTTPS Required 
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar

[ivy:retrieve]
[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

BUILD FAILED
/home/miscellaneous/Maps/tile-splitter/splitter/build.xml:113: 
impossible to resolve dependencies:

resolve failed - see output for details

Thanks

Paul

On 30/01/2020 13:10, Gerd Petermann wrote:

Hi Paul,

please update, see 
http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&rev=596

Gerd


Von: mkgmap-dev  im Auftrag von News 

Gesendet: Donnerstag, 30. Januar 2020 13:05
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] Splitter Build Failure

I recently clean reinstalled my PC (openSuSE Leap 15.1) and today was
the first time I tried to build splitter and received the following errors

BUILD FAILED
/home/miscellaneous/Maps/tile-splitter/splitter/build.xml:95: Can't get
http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.2.0/ivy-2.2.0.jar to
/home/miscellaneous/Maps/tile-splitter/splitter/lib/build/ivy-2.2.0.jar

I changed the line in build.xml to use https instead of http and I then
got past this error and received the following error snippet

[ivy:retrieve]  ::
[ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
[ivy:retrieve]  ::
[ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
[ivy:retrieve]  ::
[ivy:retrieve]  ERRORS
[ivy:retrieve]  SERVER ERROR: HTTPS Required
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
[ivy:retrieve]  SERVER ERROR: HTTPS Required
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar

So it seems that maven.org is only accepting https connections but I
can't find where to correct the above error

Any suggestions?

Thanks

Paul
___
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] documentation improvement patch

2020-01-30 Thread Gerd Petermann 
Hi Mike,

OK, I'll commit the changes to the doc files etc. soon. The java program needs 
a bit more work because it should be called in the build process.

I wish you a nice holiday!

Gerd


Von: Mike Baggaley 
Gesendet: Donnerstag, 30. Januar 2020 13:47
An: 'Gerd Petermann'; mkgmap-dev@lists.mkgmap.org.uk
Betreff: RE: [mkgmap-dev] documentation improvement patch

Hi Gerd, no issues with those changes. I think I also inadvertently lost a
blank line immediately before === Mkgmap options ===.

However, I think it is illogical to use stderr to display the version. I was
considering following up with a small patch to change the version output
from stderr and stop the program exiting after outputting the version. It
seems illogical to exit if --version is anywhere on the command line
regardless of the other options, and the documentation doesn't say it does
this (the splitter documentation does). I'm off on holiday shortly, so
probably won't be sending anything else for a while.

Cheers,
Mike

-Original Message-
From: Gerd Petermann [mailto:gpetermann_muenc...@hotmail.com]
Sent: 30 January 2020 09:30
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] documentation improvement patch

Hi Mike,

if I got that right you didn't compile help\options before you created
doc-v7.patch.
I also have some problems checking your patch because you changed the line
endings to windows style (0d0a) instead of unix(0a)
I've attached two patches:
doc-v7-unix.patch:
used your patch with line endings converted to unix and create a new patch.
This is much smaller.
doc-v8.patch:
- two small changes in options.txt
 + --version writs to stderr, this information is considered important, see
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=2642
 + addedd missing "when"
- freshly compiled help\options

If you agree with  these small changes I'll commit the v8.
doc-v7-unix.patch

doc-v8.patch 

Mike Baggaley wrote
> Hi Gerd,
>
> It appears that mkgmap can only display ASCII characters, so although
> non-ASCII characters are copied faithfully from options.txt to options,
> mkgmap cannot display them. I have added an ASCII test to the code which
> displays the line number and offending text, - it transpires there was a
> non
> ASCII letter in the example usage of --mdr7-excl=name plus three special
> hyphens.
>
> For the long lines, I hadn't handled the case where adding two lines
> together exceeded 160 characters and hence needed chopping twice. Now
> fixed.
>
> I did wonder about taking out the example file. I have removed this from
> options.txt and put it in a new file logging.txt and referenced it from
> index.txt. I've also put it in a logging file for display from the command
> line with help=logging. It may still look like a stack trace there, but
> should at least be more expected. I have added a bit more information and
> a
> reference to the Java documentation on logging at the end (primarily so
> you
> can see something after the 'stacktrace').
>
> How does that seem?
> Mike
> doc-v7.patch (200K)
> ;





--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html


___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] documentation improvement patch

2020-01-30 Thread Mike Baggaley 
Hi Gerd, no issues with those changes. I think I also inadvertently lost a
blank line immediately before === Mkgmap options ===.

However, I think it is illogical to use stderr to display the version. I was
considering following up with a small patch to change the version output
from stderr and stop the program exiting after outputting the version. It
seems illogical to exit if --version is anywhere on the command line
regardless of the other options, and the documentation doesn't say it does
this (the splitter documentation does). I'm off on holiday shortly, so
probably won't be sending anything else for a while.

Cheers,
Mike

-Original Message-
From: Gerd Petermann [mailto:gpetermann_muenc...@hotmail.com] 
Sent: 30 January 2020 09:30
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] documentation improvement patch

Hi Mike,

if I got that right you didn't compile help\options before you created
doc-v7.patch.
I also have some problems checking your patch because you changed the line
endings to windows style (0d0a) instead of unix(0a)
I've attached two patches:
doc-v7-unix.patch:
used your patch with line endings converted to unix and create a new patch.
This is much smaller. 
doc-v8.patch:
- two small changes in options.txt
 + --version writs to stderr, this information is considered important, see
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=2642
 + addedd missing "when" 
- freshly compiled help\options

If you agree with  these small changes I'll commit the v8.
doc-v7-unix.patch
  
doc-v8.patch   

Mike Baggaley wrote
> Hi Gerd,
> 
> It appears that mkgmap can only display ASCII characters, so although
> non-ASCII characters are copied faithfully from options.txt to options,
> mkgmap cannot display them. I have added an ASCII test to the code which
> displays the line number and offending text, - it transpires there was a
> non
> ASCII letter in the example usage of --mdr7-excl=name plus three special
> hyphens.
> 
> For the long lines, I hadn't handled the case where adding two lines
> together exceeded 160 characters and hence needed chopping twice. Now
> fixed.
> 
> I did wonder about taking out the example file. I have removed this from
> options.txt and put it in a new file logging.txt and referenced it from
> index.txt. I've also put it in a logging file for display from the command
> line with help=logging. It may still look like a stack trace there, but
> should at least be more expected. I have added a bit more information and
> a
> reference to the Java documentation on logging at the end (primarily so
> you
> can see something after the 'stacktrace').
> 
> How does that seem?
> Mike
> doc-v7.patch (200K)
> ;





--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html


___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Splitter Build Failure

2020-01-30 Thread Gerd Petermann 
Hi Paul,

please update, see 
http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&rev=596

Gerd


Von: mkgmap-dev  im Auftrag von News 

Gesendet: Donnerstag, 30. Januar 2020 13:05
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] Splitter Build Failure

I recently clean reinstalled my PC (openSuSE Leap 15.1) and today was
the first time I tried to build splitter and received the following errors

BUILD FAILED
/home/miscellaneous/Maps/tile-splitter/splitter/build.xml:95: Can't get
http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.2.0/ivy-2.2.0.jar to
/home/miscellaneous/Maps/tile-splitter/splitter/lib/build/ivy-2.2.0.jar

I changed the line in build.xml to use https instead of http and I then
got past this error and received the following error snippet

[ivy:retrieve]  ::
[ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
[ivy:retrieve]  ::
[ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
[ivy:retrieve]  ::
[ivy:retrieve]  ERRORS
[ivy:retrieve]  SERVER ERROR: HTTPS Required
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
[ivy:retrieve]  SERVER ERROR: HTTPS Required
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar

So it seems that maven.org is only accepting https connections but I
can't find where to correct the above error

Any suggestions?

Thanks

Paul
___
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] Splitter Build Failure

2020-01-30 Thread News 
I recently clean reinstalled my PC (openSuSE Leap 15.1) and today was 
the first time I tried to build splitter and received the following errors


BUILD FAILED
/home/miscellaneous/Maps/tile-splitter/splitter/build.xml:95: Can't get 
http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.2.0/ivy-2.2.0.jar to 
/home/miscellaneous/Maps/tile-splitter/splitter/lib/build/ivy-2.2.0.jar


I changed the line in build.xml to use https instead of http and I then 
got past this error and received the following error snippet


[ivy:retrieve]  ::
[ivy:retrieve]  ::  UNRESOLVED DEPENDENCIES ::
[ivy:retrieve]  ::
[ivy:retrieve]  :: xpp3#xpp3;1.1.4c: not found
[ivy:retrieve]  ::
[ivy:retrieve]  ERRORS
[ivy:retrieve]  SERVER ERROR: HTTPS Required 
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.pom
[ivy:retrieve]  SERVER ERROR: HTTPS Required 
url=http://repo1.maven.org/maven2/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar


So it seems that maven.org is only accepting https connections but I 
can't find where to correct the above error


Any suggestions?

Thanks

Paul
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] precompiled sea

2020-01-30 Thread Ticker Berkin 
Hi

Having just generated full britain-and-ireland with current trunk
(r4432), I'm also now seeing some tiles (5 out of 101) with sea/land
flipped when using option:
  --generate-sea="multipolygon,extend-sea-sectors,close-gaps=350"
but when I process some of the same tiles with r4295 they are OK.

It's not a problem for me at the moment, I've simply replaced above
with
  --precomp-sea=sea-latest.zip

However I prefer to use --generate-sea for various reasons:
- saves downloading sea.zip every now and again.
- island cut-outs match land features exactly, whereas there were
slight differences with sea.zip.
- not had these problems before.
- no noticeable performance problems.

Sometime I'll try and pin down when the change happened. I hadn't
noticed before because the tiles in the small map I use day-to-day
don't show the problem.

Ticker

On Wed, 2020-01-29 at 22:50 +, Mike Baggaley wrote:
> Hi Gerd, up to now I have built my UK map with the sea and land in a
> single
> pass using --generate-sea. However, some tiles are getting the sea
> and land
> inverted, typically where a very small amount of sea is in the tile.
> I was
> trying to see whether if I precompiled the sea, the problem would go
> away -
> I was assuming the tiles of precompiled sea would be bigger because
> they
> contained no other data, so the probability of inversion would be
> reduced. I
> was therefore first trying to generate precompiled sea, then use it
> to build
> my UK map. It may be that my assumption is incorrect and that it
> won't make
> any difference anyway.
> 
> Regards,
> Mike
> 
> -Original Message-
> From: Gerd Petermann [mailto:gpetermann_muenc...@hotmail.com] 
> Sent: 29 January 2020 19:22
> To: Development list for mkgmap 
> Subject: Re: [mkgmap-dev] precompiled sea
> 
> Hi Mike,
> 
> not sure what you are trying to do. What do you expect to get with
> the last
> command?
> 
> Gerd
> 
> 
> Von: mkgmap-dev  im Auftrag
> von Mike
> Baggaley 
> Gesendet: Mittwoch, 29. Januar 2020 19:20
> An: 'Development list for mkgmap'
> Betreff: [mkgmap-dev] precompiled sea
> 
> Hi, I have not used precomp sea before and am struggling to compile
> the sea
> tiles. Using the following process I get a map with no sea:
> 
> Used osmfilter to extract just the coastline data
> Used splitter on the coastline data
> Used mkgmap on the splitter data with a simple style that just
> processes
> coastline and with --generate-sea=multipolygon. I can see some img
> files
> created in my sea folder
> Used splitter again on the original data
> Used mkgmap again with --precomp-sea and --generate-sea=multipolygon
> 
> Am I doing something wrong?
> 
> Regards,
> Mike
> 
> ___
> 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] documentation improvement patch

2020-01-30 Thread Gerd Petermann 
Hi Mike,

if I got that right you didn't compile help\options before you created
doc-v7.patch.
I also have some problems checking your patch because you changed the line
endings to windows style (0d0a) instead of unix(0a)
I've attached two patches:
doc-v7-unix.patch:
used your patch with line endings converted to unix and create a new patch.
This is much smaller. 
doc-v8.patch:
- two small changes in options.txt
 + --version writs to stderr, this information is considered important, see
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=2642
 + addedd missing "when" 
- freshly compiled help\options

If you agree with  these small changes I'll commit the v8.
doc-v7-unix.patch
  
doc-v8.patch   

Mike Baggaley wrote
> Hi Gerd,
> 
> It appears that mkgmap can only display ASCII characters, so although
> non-ASCII characters are copied faithfully from options.txt to options,
> mkgmap cannot display them. I have added an ASCII test to the code which
> displays the line number and offending text, - it transpires there was a
> non
> ASCII letter in the example usage of --mdr7-excl=name plus three special
> hyphens.
> 
> For the long lines, I hadn't handled the case where adding two lines
> together exceeded 160 characters and hence needed chopping twice. Now
> fixed.
> 
> I did wonder about taking out the example file. I have removed this from
> options.txt and put it in a new file logging.txt and referenced it from
> index.txt. I've also put it in a logging file for display from the command
> line with help=logging. It may still look like a stack trace there, but
> should at least be more expected. I have added a bit more information and
> a
> reference to the Java documentation on logging at the end (primarily so
> you
> can see something after the 'stacktrace').
> 
> How does that seem?
> Mike
> doc-v7.patch (200K)
> ;





--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] precompiled sea

2020-01-30 Thread Gerd Petermann 
Hi Mike,

quite a lot of missunderstandings ;)
1) The data in land-polygons-split-4326.zip is calculated (compiled) from OSM 
coastline data. AFAIK the same data is used by the renderer of 
https://www.openstreetmap.org
Find more details  here https://osmdata.openstreetmap.de/data/land-polygons.html
The expected avantage is that the coastline data produced by them is complete 
and correct (no gaps, no reversed coastline)
2) The data in sea.zip uses the OSM pbf format. It containes the result of 
processing this (hopefully correct) data using the algorithm that is used with 
--generate-sea=multipolygon. That's also a reason why it is called pre-compiled.
3) You should load the data of a rather small sea*.pbf file into JOSM to sea 
what it contains. You'll sea the result of "cutting out holes(islands) of a 
multipolygon".
So, the file contains only simple ways, no multipolygons.

If you don't want or cannot use precompiled sea data you should try the sub 
options of --generate-sea.

Gerd
PS: See also my trick regarding testing sea: 
http://gis.19327.n8.nabble.com/precomp-sea-problem-tp5953261p5953281.html


Von: Mike Baggaley 
Gesendet: Donnerstag, 30. Januar 2020 00:24
An: 'Gerd Petermann'; 'Development list for mkgmap'
Betreff: RE: [mkgmap-dev] precompiled sea

Hi Gerd, having now read your link on generating sea yourself, I gather that
mkgmap cannot produce precompiled sea from OSM files, only from ESRI files.
I also wasn't aware that optional code had to be included to use the sea
generator. I could include the optional code in my mkgmap build, but it
looks like using precompiled sea is a non-starter for me if it can't read
OSM data. The original source of my land/sea border was ESRI, but this data
has gone through a filtering process and been converted to OSM format.

I had assumed that the precompiled sea tiles were in img format, but from
opening the precompiled sea zip file from the download page, I see the files
are pbf, suggesting that 'precompiled' is something of a misnomer if they
are just OSM files. I assume it refers to converting from ESRI to OSM, which
I don't need, as it looks like it is doing something pretty similar to what
I already have.

Ah well, back to the drawing board...

Cheers,
Mike

-Original Message-
From: Gerd Petermann [mailto:gpetermann_muenc...@hotmail.com]
Sent: 29 January 2020 20:12
To: Development list for mkgmap 
Subject: Re: [mkgmap-dev] precompiled sea

Hi Mike,

if you want to compile your own  sea.zip see
https://wiki.openstreetmap.org/wiki/Mkgmap/help/options#Using_precompiled_se
a

If you want to create a map similar to that created with
java -jar mkgmap.jar  --generate-sea=multipolygon
--style-file=styles\coastline -c template.args
you have to use something like
java -jar mkgmap.jar --precomp-sea=\osm\sea.zip
--style-file=styles\coastline -c template.args

Gerd


Von: mkgmap-dev  im Auftrag von Gerd
Petermann 
Gesendet: Mittwoch, 29. Januar 2020 20:22
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] precompiled sea

Hi Mike,

not sure what you are trying to do. What do you expect to get with the last
command?

Gerd


Von: mkgmap-dev  im Auftrag von Mike
Baggaley 
Gesendet: Mittwoch, 29. Januar 2020 19:20
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] precompiled sea

Hi, I have not used precomp sea before and am struggling to compile the sea
tiles. Using the following process I get a map with no sea:

Used osmfilter to extract just the coastline data
Used splitter on the coastline data
Used mkgmap on the splitter data with a simple style that just processes
coastline and with --generate-sea=multipolygon. I can see some img files
created in my sea folder
Used splitter again on the original data
Used mkgmap again with --precomp-sea and --generate-sea=multipolygon

Am I doing something wrong?

Regards,
Mike

___
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