<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Gerd,<br>
<br>
yes, it's a complicated world with these non-rectancular countries,
can't we change that ? ;-)<br>
<br>
I did some tests yesterday playing around with --no-trim and
--polygon-files with Luxembourge (small enough to do quick tests),
the result is not that much different if I'm skipping --no-trim or
use the polygon file, the result ist still 'quite' rectancular, just
a few bits are really left aside.... but I will have to do more
tests with other countries (more complicated ones and bigger ones
than LUX) to see if in my case I could/should skip --no-trim for
building other maps too.<br>
<br>
Regarding your implementation option:<br>
<ul>
<li>I would rather prefer not having option 2) implemented for the
same reason as you mention: it changes the default behaviour for
everyone. And as we have to say that for (rough guess) 99% of
the cases the actual behaviour is working that's too much.</li>
<li>I like option 3). But enabling that by default would possibly
increase the time used to split as it first has to run through
the file to see which bounds (bounds tag or calculated one) have
to be used... but I'm sure you could answer that much better
than me... ;-)</li>
<li>Option 1) is possibly the cheapest to implement ? <br>
</li>
</ul>
Thanks Patrik<br>
<br>
<div class="moz-cite-prefix">On 25.03.2016 07:33, Gerd Petermann
wrote:<br>
</div>
<blockquote
cite="mid:HE1PR08MB0764842390AE336544F771DF9E830@HE1PR08MB0764.eurprd08.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi Patrik,</p>
<p><br>
</p>
<p>good question. I also wondered if splitter can be changed to
ignore wrong bounds</p>
<p>tags. My thoughts:<br>
</p>
<p>In your case the bbox is far too large, means it claims to
contain data that is not there.</p>
<p>The normal case is vice versa: The file contains some nodes
outside of the bbox,
<br>
</p>
<p>maybe from ferry lines or other long ways, and my
understanding is that we don't</p>
<p>want to calculate the tiles based on those few nodes, since
we might get a map with</p>
<p>larger empty areas at the "border". No idea if that would
cause more trouble. <br>
</p>
<p>With typical data from geofabrik and the --no-trim option
there will always be large
<br>
</p>
<p>empty areas as most countries are not rectangular ;-)</p>
<p><br>
</p>
<p>Possible changes in the code:</p>
<p>1) add a --ignore-osm-bounds option and set the default to
false (means one gets </p>
<p>the same result like now when he uses the default)<br>
</p>
<p>2) add a --use-osm-bounds option and set the default to
false</p>
<p>(means one might get a different result when using the
default)<br>
</p>
<p>3) add code to check how the collected data matches the given
bounds, <br>
</p>
<p>use whatever is smaller. This might also be triggered by an
option if needed.<br>
</p>
<p><br>
</p>
<p>I'd like to get some feedback from others first.<br>
</p>
<p><br>
</p>
<p>Gerd<br>
</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
color="#000000" face="Calibri, sans-serif"><b>Von:</b>
mkgmap-dev <a class="moz-txt-link-rfc2396E" href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk"><mkgmap-dev-bounces@lists.mkgmap.org.uk></a>
im Auftrag von KeenOnKites <a class="moz-txt-link-rfc2396E" href="mailto:keenonkites@gmx.net"><keenonkites@gmx.net></a><br>
<b>Gesendet:</b> Freitag, 25. März 2016 00:13<br>
<b>An:</b> <a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<b>Betreff:</b> Re: [mkgmap-dev] Problem with splitter:
Failed to find a correct split</font>
<div> </div>
</div>
<div>Gerd,<br>
<br>
I couldn't go to sleep without getting to the ground of
this... <br>
<br>
I performed the following tests on linux, always with my
standard --no-trim present:<br>
<ul>
<li>original osm.pbf file downloaded from geofabrik (with
the problematic bounds tag in it)<br>
-> FAILURE </li>
<li>converted with the help of osmconvert to normal osm
format<br>
-> FAILURE (which was to be expected, same file, just
different format) </li>
<li>deleted the osm tag with a simple command like 'cat
file.osm | grep -v bounds > file-nobounds.osm' and
ran splitter against it, always with the same options<br>
-> SUCCESS </li>
</ul>
<p>This leads me to the question why the bounds tag is
read/used if it also works without and even gives less
problem ?<br>
</p>
<p><br>
.... sorry for bombarding you (and the list), but I think
it's nevertheless and interesting question.<br>
</p>
<p><br>
Cheers<br>
Patrik<br>
</p>
<br>
<div class="moz-cite-prefix">On 24.03.2016 23:51,
KeenOnKites wrote:<br>
</div>
<blockquote type="cite">Gerd,<br>
<br>
I did dig a bit deeper... also as it rang a bell:<br>
we had quite a similar problem with the wrong bounding box
in Alaska already October 2014. It was an illegal value of
maxlon="180.0005" causing splitter to bail out<br>
<br>
When I convert the osm.pbf file with the help of
osmconvert to osm and look at the first few lines I see a
'bounds' tag announcing the problematic bounding box (not
illegal as in 2014, but still 'suboptimal'):<br>
<blockquote><tt><?xml version='1.0'
encoding='UTF-8'?></tt><tt><br>
</tt><tt><osm version="0.6" generator="osmconvert
0.8.2" timestamp="2016-03-23T20:13:02Z"></tt><tt><br>
</tt><tt> <bounds minlat="49.8089"
minlon="-179.9532" maxlat="73.79794"
maxlon="179.9999"/></tt><tt><br>
</tt><tt> <node id="27207079" lat="64.7487541"
lon="-147.3242821" version="2"
</tt><tt><br>
...</tt><br>
</blockquote>
<br>
Getting the statistics via osmconvert with
--out-statistics seems to read through the file and checks
the 'real' bounding box:<br>
<blockquote>...<br>
<tt>lon min: -180.0000000</tt><br>
<tt>lon max: -122.5122525</tt><br>
<tt>lat min: 48.6234931</tt><br>
<tt>lat max: 71.6061501</tt><br>
...<br>
</blockquote>
<br>
I'm now wondering if splitter get's confused by the
existing but obviously strange bounds tag.
<br>
<br>
According to the findings in 2014 splitter can handle
files without the bounds tag and just gets the real
boundings from all the elements in the file.<br>
I did not test to run it through splitter without the
bounds tag as I'm having troubles converting the file
properly on my windows... but I'll try that probably
tomorrow again on linux (sort of late already today).<br>
The process would be<br>
<blockquote>osm.pbf -> osm -> get rid of the bounds
tag -> back to osm.pbf again (to have same source
file format)<br>
.... and then run the splitter and see what happens.<br>
</blockquote>
But if I have a proper osm file with the 'problematic'
bounds tag in it, I can also try to reproduce the problem
with the osm file. If it is reproducible I just drop the
tag and try it again.<br>
<br>
BTW: I've contacted geofabrik already via email<br>
<br>
Patrik<br>
<br>
<br>
<div class="moz-cite-prefix">On 24.03.2016 22:27,
KeenOnKites wrote:<br>
</div>
<blockquote type="cite">Gerd,<br>
<br>
I'll play a bit more with this option and check what
suits me best.<br>
<br>
Again thanks for the incredibly quick answer to my
problem/question.<br>
<br>
Cheers<br>
Patrik<br>
<br>
<div class="moz-cite-prefix">On 24.03.2016 22:20, Gerd
Petermann wrote:<br>
</div>
<blockquote type="cite">
<div id="divtagdefaultwrapper" style="font-size:12pt;
color:#000000; background-color:#FFFFFF;
font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Patrik,</p>
<p><br>
</p>
<p>I think the wanted effect of the no-trim option
is a rectangular map,</p>
<p>which some people prefer, esp. on the PC. <br>
</p>
<p><br>
</p>
<p>Gerd<br>
</p>
<br>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1" style="display:inline-block;
width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" color="#000000"
face="Calibri, sans-serif"><b>Von:</b>
mkgmap-dev
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk">
</a><a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk"><mkgmap-dev-bounces@lists.mkgmap.org.uk></a>
im Auftrag von KeenOnKites
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:keenonkites@gmx.net"><keenonkites@gmx.net></a><br>
<b>Gesendet:</b> Donnerstag, 24. März 2016
22:16<br>
<b>An:</b> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:mkgmap-dev@lists.mkgmap.org.uk">
mkgmap-dev@lists.mkgmap.org.uk</a><br>
<b>Betreff:</b> Re: [mkgmap-dev] Problem with
splitter: Failed to find a correct split</font>
<div> </div>
</div>
<div>Gerd,<br>
<br>
Sorry, your explanations came in during I was
writing up the test results ...<br>
<br>
Think it's all clear so far.<br>
<br>
As we're creating lot of different maps I'm just
wondering if I can/should drop the option
--no-trim for all map building or if I would
suddenly run into other/new problems...<br>
<br>
I'll contact geofabrik with the details.<br>
<br>
Many thanks and happy Easter.<br>
Patrik<br>
<br>
<div class="moz-cite-prefix">On 24.03.2016
22:07, Gerd Petermann wrote:<br>
</div>
<blockquote type="cite">
<div id="divtagdefaultwrapper"
style="font-size:12pt; color:#000000;
background-color:#FFFFFF;
font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Patrik,</p>
<p><br>
</p>
<p>I don't need the files, I downloaded the
alaska file and tried some variants.</p>
<p>See also my last post, send a few minutes
ago.</p>
<p><br>
</p>
<p>Gerd<br>
</p>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1"
style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" color="#000000"
face="Calibri, sans-serif"><b>Von:</b>
mkgmap-dev
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk">
<mkgmap-dev-bounces@lists.mkgmap.org.uk></a> im Auftrag von Patrik
Brunner <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:patrik.brunner@gmx.net">
</a><a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:patrik.brunner@gmx.net"><patrik.brunner@gmx.net></a><br>
<b>Gesendet:</b> Donnerstag, 24. März
2016 22:03<br>
<b>An:</b> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:mkgmap-dev@lists.mkgmap.org.uk">
mkgmap-dev@lists.mkgmap.org.uk</a><br>
<b>Betreff:</b> Re: [mkgmap-dev]
Problem with splitter: Failed to find
a correct split</font>
<div> </div>
</div>
<div>Gerd,<br>
<br>
Yes, alaska.osm.pbf is small.<br>
<br>
It works without --no-trim. And it also
works with the polygon file that belongs
to alaska.osm.pbf (also downloaded from
Geofabrik) which, according to
documentation, anyway would disable
--no-trim option.<br>
<br>
Do you still need the resulting
densities-out of the failure ? It's
about 700 kb... if yes, how should I
provide it ? Just attach it here ?<br>
<br>
You have to excuse my question, I'm not
the crack: is this now a problem of the
pbf file, or the splitter ? ... or just
the way I try to use it ?<br>
<br>
Thanks already now for your help.<br>
Patrik<br>
<br>
<div class="moz-cite-prefix">On
24.03.2016 21:14, Gerd Petermann
wrote:<br>
</div>
<blockquote type="cite">
<div id="divtagdefaultwrapper"
style="font-size:12pt;
color:#000000;
background-color:#FFFFFF;
font-family:Calibri,Arial,Helvetica,sans-serif">
<p><br>
</p>
<p>Ahh, sorry, I just noticed that
the file alaska.osm.pbf is small.</p>
<p>The problem is here is that the
bounding box spans from -180 to
180, <br>
</p>
<p>but this box is most empty. I
have to run splitter now to find
the details.</p>
<p>It works without --no-trim,
probably also with an appropriate
polygon file.</p>
<p>Does that help?</p>
<p><br>
</p>
<p>Gerd<br>
</p>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1"
style="display:inline-block;
width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt"
color="#000000" face="Calibri,
sans-serif"><b>Von:</b>
mkgmap-dev
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk">
<mkgmap-dev-bounces@lists.mkgmap.org.uk></a> im Auftrag von Gerd
Petermann <a
moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:GPetermann_muenchen@hotmail.com">
</a><a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:GPetermann_muenchen@hotmail.com"><GPetermann_muenchen@hotmail.com></a><br>
<b>Gesendet:</b> Donnerstag,
24. März 2016 21:01<br>
<b>An:</b> Development list
for mkgmap<br>
<b>Betreff:</b> Re:
[mkgmap-dev] Problem with
splitter: Failed to find a
correct split</font>
<div> </div>
</div>
<div>
<div id="divtagdefaultwrapper"
style="font-size:12pt;
color:#000000;
background-color:#FFFFFF;
font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Patrik,</p>
<p><br>
</p>
<div style="color:rgb(0,0,0)">please
provide the complete log
from splitter and the
densities-out.txt<br>
<br>
Gerd<br>
<br>
<hr tabindex="-1"
style="display:inline-block;
width:98%">
<div id="divRplyFwdMsg"
dir="ltr"><font
style="font-size:11pt"
color="#000000"
face="Calibri,
sans-serif"><b>Von:</b>
mkgmap-dev
<a
moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk">
</a><a
moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk"><a class="moz-txt-link-rfc2396E" href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk"><mkgmap-dev-bounces@lists.mkgmap.org.uk></a></a>
im Auftrag von
KeenOnKites
<a
moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:keenonkites@gmx.net"><a class="moz-txt-link-rfc2396E" href="mailto:keenonkites@gmx.net"><keenonkites@gmx.net></a></a><br>
<b>Gesendet:</b>
Donnerstag, 24. März
2016 20:25<br>
<b>An:</b> Development
list for mkgmap<br>
<b>Betreff:</b>
[mkgmap-dev] Problem
with splitter: Failed to
find a correct split</font>
<div> </div>
</div>
<div>Hello together,<br>
<br>
I'm running into a problem
with the splitter (r435
aswell as r427) when
splitting the US_ALASKA
file downloadable from
Geofabrik.<br>
<br>
The exception is:<br>
<blockquote><tt>Warning:
No solution found for
partition
(49.7900390625,-179.9560546875)
to (73.828125,180.0)
with 6'702'717 nodes</tt><br>
<tt>uk.me.parabola.splitter.SplitFailedException:
Failed to find a
correct split</tt><br>
<tt> at
uk.me.parabola.splitter.SplittableDensityArea.split(SplittableDensityArea.java:152)</tt><br>
<tt> at
uk.me.parabola.splitter.SplittableDensityArea.split(SplittableDensityArea.java:196)</tt><br>
<tt> at
uk.me.parabola.splitter.Main.calculateAreas(Main.java:645)</tt><br>
<tt> at
uk.me.parabola.splitter.Main.split(Main.java:258)</tt><br>
<tt> at
uk.me.parabola.splitter.Main.start(Main.java:187)</tt><br>
<tt> at
uk.me.parabola.splitter.Main.main(Main.java:157)</tt><br>
</blockquote>
<br>
The complete command line
with the splitter call is:<br>
<blockquote><tt>java
-Xmx1536M -jar
D:/fzk/develop/fzk-mde-garmin/Freizeitkarte-Entwicklung/tools/splitter/splitter.jar
--max-threads=2
--geonames-file=D:/fzk/develop/fzk-mde-garmin/Freizeitkarte-Entwicklung/cities/c</tt><tt><br>
</tt><tt>ities15000.zip
--no-trim
--precomp-sea=D:/fzk/develop/fzk-mde-garmin/Freizeitkarte-Entwicklung/sea
--keep-complete=true
--mapid=98200001
--max-nodes=800000
--output=xml
--output-dir=D:/fzk/develop/fzk</tt><tt><br>
</tt><tt>-mde-garmin/Freizeitkarte-Entwicklung/work/Freizeitkarte_US_ALASKA
D:/fzk/develop/fzk-mde-garmin/Freizeitkarte-Entwicklung/work/Freizeitkarte_US_ALASKA/Freizeitkarte_US_ALASKA.osm.pbf</tt><br>
</blockquote>
<br>
The pbf source file comes
from:<br>
<blockquote><a
moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://download.geofabrik.de/north-america/us/alaska-latest.osm.pbf"><a class="moz-txt-link-freetext" href="http://download.geofabrik.de/north-america/us/alaska-latest.osm.pbf">http://download.geofabrik.de/north-america/us/alaska-latest.osm.pbf</a></a><br>
</blockquote>
<br>
The osmconvert statistics
about that file is:<br>
<blockquote><tt>PS
Freizeitkarte-Entwicklung>
.\tools\osmconvert\windows\osmconvert.exe
.\work\Freizeitkarte_US_ALASKA\Freizeitkarte_US_ALASKA.osm.pbf
--out-statistics</tt><tt><br>
</tt><tt>timestamp min:
2007-06-05T03:23:59Z</tt><tt><br>
</tt><tt>timestamp max:
2016-03-23T05:41:43Z</tt><tt><br>
</tt><tt>lon min:
-180.0000000</tt><tt><br>
</tt><tt>lon max:
-122.5122525</tt><tt><br>
</tt><tt>lat min:
48.6234931</tt><tt><br>
</tt><tt>lat max:
71.6061501</tt><tt><br>
</tt><tt>nodes: 4360214</tt><tt><br>
</tt><tt>ways: 185550</tt><tt><br>
</tt><tt>relations: 2245</tt><tt><br>
</tt><tt>node id min:
27207079</tt><tt><br>
</tt><tt>node id max:
4072166815</tt><tt><br>
</tt><tt>way id min:
4708608</tt><tt><br>
</tt><tt>way id max:
404980503</tt><tt><br>
</tt><tt>relation id
min: 13971</tt><tt><br>
</tt><tt>relation id
max: 6033189</tt><tt><br>
</tt><tt>keyval pairs
max: 310</tt><tt><br>
</tt><tt>keyval pairs
max object: relation
60189</tt><tt><br>
</tt><tt>noderefs max:
2000</tt><tt><br>
</tt><tt>noderefs max
object: way 42394334</tt><tt><br>
</tt><tt>relrefs max:
681</tt><tt><br>
</tt><tt>relrefs max
object: relation
3337277</tt><tt><br>
</tt><tt>PS
Freizeitkarte-Entwicklung></tt><br>
</blockquote>
Interesting to mention:<br>
- splitter exception
mentiones a complete
different coverage area
than osmconvert
statistics.<br>
- the area is near -180 /
+180... always
complicated.<br>
<br>
Do I miss something ? All
other pbf's I've tried are
splitting properly without
any problems. Do I need to
change something in the
arguments ? Or is it a
simple problem of the
actual pbf file ?<br>
<br>
Any ideas are very
welcome....<br>
<br>
Cheers<br>
Patrik<br>
<br>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
mkgmap-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
mkgmap-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
mkgmap-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
mkgmap-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
mkgmap-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mkgmap-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
</blockquote>
<br>
</body>
</html>