Von: mkgmap-dev im Auftrag von Felix
Herwegh
Gesendet: Mittwoch, 20. März 2024 20:39
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Splitter Java Heap
Hi Gerd,
Thanks!
>From the java --version output (in the first mail) I assumed already beeing on
>a 64-bit JRE and, fol
März 2024 15:03
An:mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] Splitter Java Heap
Hi,
switching to my Ultrabook (6 GB) while travelling I recently faced some kind of
borderline condition with splitter. On the first run it throws "OutOfMemoryError:
Java heap space", on closely s
switch of the --keep-complete option
(with the corresponding disadvantages)
Gerd
Von: mkgmap-dev im Auftrag von Felix
Herwegh
Gesendet: Mittwoch, 20. März 2024 15:03
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] Splitter Java Heap
Hi,
switching
Hi,
switching to my Ultrabook (6 GB) while travelling I recently faced some
kind of borderline condition with splitter. On the first run it throws
"OutOfMemoryError: Java heap space", on closely subsequent runs without
any modifications it does not. Repeating the task after some delay fails
a
right/left hand side driving.
ciao
Gerd
Von: mkgmap-dev im Auftrag von Carlos Dávila
Gesendet: Sonntag, 3. Dezember 2023 12:26
An: Development list for mkgmap
Betreff: [mkgmap-dev] Splitter feature request
Hi all
I usually let splitter decide tiles base
ciao
Gerd
Von: mkgmap-dev im Auftrag von Carlos
Dávila
Gesendet: Sonntag, 3. Dezember 2023 12:26
An: Development list for mkgmap
Betreff: [mkgmap-dev] Splitter feature request
Hi all
I usually let splitter decide tiles based on max-nodes value, but for
some maps
Hi all
I usually let splitter decide tiles based on max-nodes value, but for
some maps I need to supply splitter an areas.list file which I adjust
manually. Reasons for that include reducing the total number of tiles,
avoiding cutting of some islands and separating right/left hand side
drivin
trag von 7770
> <7...@foskan.eu> Gesendet: Mittwoch, 16. Februar 2022 17:52
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: [mkgmap-dev] splitter with --polygon-desc-file crashes
>
> Hi.
> I have asked long ago about this particular problem i have and it was long
> tim
o)
Gerd
Von: mkgmap-dev im Auftrag von 7770
<7...@foskan.eu>
Gesendet: Mittwoch, 16. Februar 2022 17:52
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] splitter with --polygon-desc-file crashes
Hi.
I have asked long ago about this particular problem i have a
Hi.
I have asked long ago about this particular problem i have and it was long
time ago i last tried, but now i did again. It relates to splitter and usage
of --polygon-desc-file=
This is how i have tried:
1. Download data for Estonia and Latvia.
https://download.geofabrik.de/europe/estonia-lat
erd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Donnerstag, 1. Juli 2021 09:58
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter r609 released
Well here are the results for 615:
If you would like the log files for any of those runs - tell me. Significantly
bet
cnt0 = 227"
"for greenland use polygon-file - cnt1 = 4 cnt0 = 2"
"for mexico use polygon-file - cnt1 = 44 cnt0 = 42"
"for reunion do not use polygon-file - cnt1 = 3 cnt0 = 5"
On Wed, 30 Jun 2021 at 12:30, Gerd Petermann <
gpetermann_muenc...@hotmail.com> wrote
tmann
Gesendet: Mittwoch, 30. Juni 2021 10:52
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter r609 released
well yeah by now my list is down to very few countries (different then with
older splitter.jar) that profit from --polygon-file.
I feel like I will only use polygon-fil
don't expect to always get fewer tiles when you use a polygon-file ;)
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Mittwoch, 30. Juni 2021 10:10
> An: Development list for mkgmap
> Betreff
nstein, no problem with that. Just
don't expect to always get fewer tiles when you use a polygon-file ;)
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Mittwoch, 30. Juni 2021 10:10
An: Development list for mkgmap
Betreff: Re: [mkgma
; I'll try to find a fix so that splitter doesn't try to fit the tiles into
> the polygon when this happens...
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Mittwoch, 30. Juni 2021 08:55
>
when this happens...
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Mittwoch, 30. Juni 2021 08:55
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter r609 released
okay yeah I think I misunderstood the polygon-file a bit.
have to download the full norway extract to find out...
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Mittwoch, 30. Juni 2021 08:55
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter r609 released
okay yeah I th
> Felix Hartmann
> Gesendet: Dienstag, 29. Juni 2021 23:04
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] splitter r609 released
>
> I found (server) time to run my test again - using splitter v614 - search
> limit 100
> Problem cases in bold. I also
polygon?
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Dienstag, 29. Juni 2021 23:04
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter r609 released
I found (server) time to run my test again - using splitter v614 - search limit
1
I found (server) time to run my test again - using splitter v614 - search
limit 100
Problem cases in bold. I also added the number of tiles that splitter v602
needed (well on one week older geofabrik extract - but that should not make
such a difference for Norway or South America). I feel 602 w
Hi all,
I think with r609 there should be no need to use a polygon file. See
https://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&rev=609
Please let me know when this version produces much worse results compared to
older releases (using the same options and input) and provide the files
Hi all
Outermost level should be as Gerd suggests
5 levels of overview seems excessive - what about:
overview-levels = 4:17, 5:15, 6:13
Ticker
On Tue, 2021-06-01 at 13:29 +, Gerd Petermann wrote:
> Hi all,
>
> I am not sure but I think it is a bad idea to have
> overview-levels = 4:17, 5
g.uk>
Onderwerp: [mkgmap-dev] splitter default resolution 13 and overview map from
default style
Hi all,
I am not sure but I think it is a bad idea to have overview-levels = 4:17,
5:16, 6:15, 7:14, 8:12 in the default style.
The lowest resolution is 12 while splitter uses the
Hi all,
I am not sure but I think it is a bad idea to have
overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12
in the default style.
The lowest resolution is 12 while splitter uses the default 13 for its
resolution. This also means that tiles from splitter are aligned to a
resolution of 13. The lowe
__
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Freitag, 28. Mai 2021 19:29
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Splitter only writes points, not ways on huge
> file?
>
> Attached the full splitter.log
litter can copy with that but maybe
phyghtmap cannot? Try with two separate *.poly files
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Freitag, 28. Mai 2021 19:29
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Splitter only w
the pbf file really contains only nodes.
>> Can you attach the splitter log file and the asia.poly, please?
>>
>> Gerd
>>
>>
>> Von: mkgmap-dev im Auftrag von
>> Felix Hartmann
>> Gesendet: Freitag, 28. Mai
; Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Freitag, 28. Mai 2021 11:18
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Splitter only writes points, not ways on huge
> file?
>
> Hi Gerd,
> sorry - fixed. I attached the file. I could also put t
: [mkgmap-dev] Splitter only writes points, not ways on huge file?
Hi Gerd,
sorry - fixed. I attached the file. I could also put the whole 60GB file for
analysis. But do not know if you could download such a huge file or analyse it
better.
https://openmtbmap.org/75400407.osm.pbf
Felix
On Fri, 28
enc...@hotmail.com> wrote:
> Hi Felix,
>
> the link to the pbf file seems to be wrong? I get an 404
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Freitag, 28. Mai 2021 07:56
> An: Development list for
Hi Felix,
the link to the pbf file seems to be wrong? I get an 404
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Freitag, 28. Mai 2021 07:56
An: Development list for mkgmap
Betreff: [mkgmap-dev] Splitter only writes points, not ways on
I used phyghtmap to create a huge file (60GB) of 10m equidistance osm.pbf
contourlines data.
phyghtmap --jobs=2 --polygon=/home/contourlines/bounds/asia.poly --step=10
--no-zero-contour --void-range-max=-420 --output-prefix="Asia10m"
--line-cat=500,100--start-node-id=1000 --start-way-id=1
You can update it with the attached (minor) patch
El 1/2/21 a las 22:24, Steve Ratcliffe escribió:
Hi
Download for splitter r597 (and all older versions) is broken.
Please check.
Thanks for reporting, I have rebuild the latest release.
It was removed because it is over a year old!
Best wis
Hi
Download for splitter r597 (and all older versions) is broken.
Please check.
Thanks for reporting, I have rebuild the latest release.
It was removed because it is over a year old!
Best wishes
Steve
___
mkgmap-dev mailing list
mkgmap-dev@lists.mk
Hi all
Download for splitter r597 (and all older versions) is broken.
Please check.
Best regards
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Bez
Gesendet: Dienstag, 22. Dezember 2020 20:41
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter performance with "osm.pbf" compared to "o5m"
Hi Gerd,
thanks for your tests.
On your machine it's still more than double, on my machine almost
tripple the
von
> Franco Bez
> Gesendet: Samstag, 19. Dezember 2020 13:37
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] splitter performance with "osm.pbf" compared to
> "o5m"
>
> |Hi Gerd,|
>
> |here are the two log files.
> |
>
> |http://files.mkg
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter performance with "osm.pbf" compared to "o5m"
|Hi Gerd,|
|here are the two log files.
|
|http://files.mkgmap.org.uk/download/491/logs.tgz|
|Ciao,|
|Franco
|
Am 19.12.20 um 12:09 schrieb Gerd Petermann:
> Hi Franco,
>
1:45
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] splitter performance with "osm.pbf" compared to
> "o5m"
>
> Hi Gerd,
>
> thanks for the fast reply.
>
> I tried "java -ea -Xmx16G -Xms16G" but this doen&#
von Franco
Bez
Gesendet: Samstag, 19. Dezember 2020 11:45
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter performance with "osm.pbf" compared to
"o5m"
Hi Gerd,
thanks for the fast reply.
I tried "java -ea -Xmx16G -Xms16G" but this doen&
Hi Gerd,
thanks for the fast reply.
I tried "java -ea -Xmx16G -Xms16G" but this doen't make any difference
on my machine, AMD Ryzen 7 3700X 32GB Ram 2 SSDs 1TB each
see the log extracts below.
Ciao,
Franco
O5M-
-dev im Auftrag von Franco
Bez
Gesendet: Samstag, 19. Dezember 2020 09:40
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] splitter performance with "osm.pbf" compared to "o5m"
Hi all,
I noticed that splitter has a major performance lag on osm.pbf files
compared to o5
Hi all,
I noticed that splitter has a major performance lag on osm.pbf files
compared to o5m.
splitting off my DACH region in pbf format takes 15min 45sec, while
splitting the same region in o5m format is finished after 5min 17sec.
So it takes almost 3 times as long splitting pbf data.
mkgmap
> Von: mkgmap-dev im Auftrag
> von 7770 <7...@foskan.eu>
> Gesendet: Donnerstag, 22. Oktober 2020 11:36
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] splitter questions
>
> Hi Gerd.
>
> I managed to run the spli
_
Von: mkgmap-dev im Auftrag von 7770
<7...@foskan.eu>
Gesendet: Donnerstag, 22. Oktober 2020 11:36
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter questions
Hi Gerd.
I managed to run the splitter and it completed well with
java -Xmx1800m and setting the --max-nodes=160.
gt; index in mkgmap.
>
> Gerd
>
>
>
> Von: mkgmap-dev im Auftrag von 7770
> <7...@foskan.eu> Gesendet: Donnerstag, 22. Oktober 2020 10:59
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] splitter questions
>
> Hi Gerd.
> Yes, it is 64-bit, but i do
mkgmap
Betreff: Re: [mkgmap-dev] splitter questions
Hi Gerd.
Yes, it is 64-bit, but i don't have a lot of memory.
--keep-complete=false, can it impact routing possibilities (routing may not
work well) or is it mainly affecting how the map will look?
Regards
Karl
On torsdag 22 oktober 2020 k
_
> Von: mkgmap-dev im Auftrag von 7770
> <7...@foskan.eu> Gesendet: Donnerstag, 22. Oktober 2020 10:45
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: [mkgmap-dev] splitter questions
>
> Hi.
>
> I am trying to split data for some 15 countries. First ste
im Auftrag von 7770
<7...@foskan.eu>
Gesendet: Donnerstag, 22. Oktober 2020 10:45
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] splitter questions
Hi.
I am trying to split data for some 15 countries. First step is to combine the
country data (with osmconvert) to one large o5m
Hi.
I am trying to split data for some 15 countries. First step is to combine the
country data (with osmconvert) to one large o5m file and then try to split the
combined file.
The o5m file is about 14 GB in size.
When running splitter i give java -Xmx1600m
options to splitter are: --max-nodes=1
Hi Gerd,
Thanks will try that next time. My initial problem has been solved.
Dave
-Original Message-
From: mkgmap-dev On Behalf Of Gerd
Petermann
Sent: 02 September 2020 12:20
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] Splitter 597 xml format output problem
Hi Dave
t for mkgmap'
Betreff: [mkgmap-dev] Splitter 597 xml format output problem
Hi,
While trying to troubleshoot a map creation problem I had I decided to
output the data from Splitter using --output=xml rather than pbf so I could
open the resultant file in JOSM version 16812 (I wasn't sure if
Hi,
While trying to troubleshoot a map creation problem I had I decided to
output the data from Splitter using --output=xml rather than pbf so I could
open the resultant file in JOSM version 16812 (I wasn't sure if the
unexpected results were caused by Splitter or Mkgmap), JOSM gave the
following
> empty string so that splitter would always generate a unique tile
> description.
>
> Gerd
>
>
>
> Von: Randolph J. Herber
> Gesendet: Freitag, 10. April 2020 02:17
> An: Development list for mkgmap; Gerd Petermann; Mike Baggal
s improves something.
Gerd
Von: mkgmap-dev im Auftrag von Gerd
Petermann
Gesendet: Mittwoch, 8. April 2020 16:40
An: Development list for mkgmap; Ticker Berkin
Betreff: Re: [mkgmap-dev] splitter and options --description/
--geonames-file
Hi Ran
Betreff: Re: [mkgmap-dev] splitter and options --description / --geonames-file
Hi, all,
The Definition of Google Plus Codes, a.k.a. Opern Location Codes, can be
found at https://en.wikipedia.org/wiki/Open_Location_Code
The complete code also specifies, by its length, the size of the area
being
Hi, all,
The Definition of Google Plus Codes, a.k.a. Opern Location Codes, can be
found at https://en.wikipedia.org/wiki/Open_Location_Code
The complete code also specifies, by its length, the size of the area
being described. When using them in splitter, I have never seen a tile
whose code
Hi, all!
It would be best if each title has its own, separate identity.
Randolph J. Herber
On 4/8/2020 3:38 AM, Gerd Petermann wrote:
Hi all,
this is a follow up of
http://gis.19327.n8.nabble.com/documentation-improvement-tp5962609p5962747.html
Since I don't use these options for my maps I
Hi Gerd
I'd say that if the splitter is going to generate descriptions per tile
(geonames) it should generate one for each tile and, if there isn't a
centre of a city within the tile and no default description, it should
use a modified form of the nearest city to make it unique from a
possible adj
Hi all,
this is a follow up of
http://gis.19327.n8.nabble.com/documentation-improvement-tp5962609p5962747.html
Since I don't use these options for my maps I am unsure what is best.
The --geonames-file option tries to find a city within the calculated tile. If
none is found it either writes the
ed 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, i
gt;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
__
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. B
e:
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]
5
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
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
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.
Von: mkgmap-dev im Auftrag von dave
pitney
Gesendet: Samstag, 23. Februar 2019 18:37
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] splitter option? (or new request)
Hello -
Is there is an option to not compress pbf output files when using splitter?
I
Hello -
Is there is an option to not compress pbf output files when using splitter?
I use the split files as input to mkgmap.
Osmium has an option "pbf_compression=none" which is placed in the
json file as an option. This increases file size (appx double) but allows
faster file reading/writing.
Hi Gerd,
we can use any formula to assign mapid. If this formula would be widely
accepted, there wouldn't be much conflicts between maps created by
different developers.
If we use the original Garmin's formula, then we would avoid conflicts
with many existing Garmin's maps too. The only requ
Hi Andrzej,
looked at this again now. What I don't understand is why you want to use
exactly the same formular
as Garmin. I think my approach would be to make sure that we DON'T use their
numbers to avoid conflicts.
Gerd
popej wrote
> Hi Gerd,
>
> yes, I got the formula after examining numerou
p-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter, mapid
Hi Gerd,
yes, I got the formula after examining numerous Garmin's maps. I know,
that City Navigator is different, my guess is that next CN map gets next
free mapid. I'm not sure about marine maps and other new maps from Garmin.
Hi Gerd,
yes, I got the formula after examining numerous Garmin's maps. I know,
that City Navigator is different, my guess is that next CN map gets next
free mapid. I'm not sure about marine maps and other new maps from Garmin.
It looks like the formula is easy to support up to FID 45744. For
owski
Gesendet: Montag, 17. Dezember 2018 15:17
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter, mapid
Hi,
basically map ID should be unique for all tiles, regardless of FID. If
you load 2 tiles with the same map ID to a GPS, it will silently ignore
one of these tiles. Most probabl
65535, 0x
On 12/17/18 4:41 PM, brad wrote:
What is the max famid? the docs say , but I know there are
mapid's larger. maybe 9?
On 12/17/18 7:17 AM, Andrzej Popowski wrote:
Hi,
basically map ID should be unique for all tiles, regardless of FID.
If you load 2 tiles with the sa
What is the max famid? the docs say , but I know there are mapid's
larger. maybe 9?
On 12/17/18 7:17 AM, Andrzej Popowski wrote:
Hi,
basically map ID should be unique for all tiles, regardless of FID. If
you load 2 tiles with the same map ID to a GPS, it will silently
ignore one o
. Dezember 2018 17:59
An: Gerd Petermann; Development list for mkgmap
Betreff: Re: AW: [mkgmap-dev] splitter, mapid
I'd be happy to take a stab at updating some docs.It looks like the
docs are the same on mkgmap.org and wiki.openstreetmap.org. Do the
changes on mkgmap.org flow to OSM, or the
kgmap.org.uk
Betreff: [mkgmap-dev] splitter, mapid
One thing I think I missed, is that each tile on a garmin device needs a
unique mapid. A different family-id and mapname for each gmap is not
sufficient. Does this sound correct?
I'd been downloading US states from Geofabrik, creating m
Hi,
basically map ID should be unique for all tiles, regardless of FID. If
you load 2 tiles with the same map ID to a GPS, it will silently ignore
one of these tiles. Most probably GPS assume, that these are the same
tiles and there is no reason to process both.
Search index contains map ID.
on: mkgmap-dev im Auftrag von brad
>
> Gesendet: Montag, 17. Dezember 2018 01:47
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: [mkgmap-dev] splitter, mapid
>
> One thing I think I missed, is that each tile on a garmin device needs a
> unique mapid. A different fami
atch or maybe a new version of one or
more files).
Gerd
Von: mkgmap-dev im Auftrag von brad
Gesendet: Montag, 17. Dezember 2018 01:47
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] splitter, mapid
One thing I think I missed, is that each t
nd it's an ongoing process ;-)
Feel free to improve the docu (post a patch or maybe a new version of one or
more files).
Gerd
Von: mkgmap-dev im Auftrag von brad
Gesendet: Montag, 17. Dezember 2018 01:47
An: mkgmap-dev@lists.mkgmap.org.uk
Betre
One thing I think I missed, is that each tile on a garmin device needs a
unique mapid. A different family-id and mapname for each gmap is not
sufficient. Does this sound correct?
I'd been downloading US states from Geofabrik, creating maps with unique
family-id, mapname, every name & id th
8 14:54
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
Thanks all,
meanwhile I could generate a map which looks fine in QLandkarte and on
my Oregon.
I'd like to summarize the findings for those who try to create contour
lines with srtm2osm and f
Thanks all,
meanwhile I could generate a map which looks fine in QLandkarte and on
my Oregon.
I'd like to summarize the findings for those who try to create contour
lines with srtm2osm and feed them into a Garmin map. I updated the wiki
page https://wiki.openstreetmap.org/wiki/Srtm2Osm
First
, versuch es mal mit der Option -maxwaynodes=5000
oder noch kleiner.
Gerd
Von: mkgmap-dev im Auftrag von Gerd
Petermann
Gesendet: Sonntag, 4. November 2018 11:26
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area
: [mkgmap-dev] splitter: option for maximum tile area?
Hi Gerd,
I've uploaded some files:
splitter log:
https://drive.google.com/open?id=12wsnncNkfwKruEw-4UIgmvddK3E_TxtE
kml: https://drive.google.com/open?id=1UOv_FTtl_pK_Nj126WDFnirhaswnvyfZ
smallest tile:
https://drive.google.com/op
ard,
just a guess: If you use option --add-pois-to-lines and you have a rule in the
points file which processes ele to add a POI
you may see something like that.
Gerd
Von: mkgmap-dev im Auftrag von Gerd
Petermann
Gesendet: Freitag, 2. November 2018 19:24
Von: mkgmap-dev im Auftrag von
Bernhard Hiller
Gesendet: Samstag, 3. November 2018 11:25
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
Hi Gerd,
contour lines were created with srtm2osm -step 25 -cat 500 100 25
-large
guess: If you use option --add-pois-to-lines and you have a rule in the
points file which processes ele to add a POI
you may see something like that.
Gerd
Von: mkgmap-dev im Auftrag von Gerd
Petermann
Gesendet: Freitag, 2. November 2018 19:24
An:
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
On 11/02/2018 07:31 PM, Gerd Petermann wrote:
> just a guess: If you use option --add-pois-to-lines and you have a rule in
> the points file which processes ele to add a POI
> you may see something like that.
I may have u
On 11/02/2018 07:31 PM, Gerd Petermann wrote:
> just a guess: If you use option --add-pois-to-lines and you have a rule in
> the points file which processes ele to add a POI
> you may see something like that.
I may have understood this wrong, but wasn't the file size comparison
after the splitte
. November 2018 19:24
An: Bernhard Hiller; Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
Hi Bernhard,
what are your rules for the contour lines?
Gerd
Von: mkgmap-dev im Auftrag von
Bernhard Hiller
Gesendet
Hi Bernhard,
what are your rules for the contour lines?
Gerd
Von: mkgmap-dev im Auftrag von
Bernhard Hiller
Gesendet: Freitag, 2. November 2018 19:18
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area
Petermann
Gesendet: Mittwoch, 31. Oktober 2018 22:49
An: Gerd Petermann; Development list for mkgmap
Betreff: AW: [mkgmap-dev] splitter: option for maximum tile area?
Hi Bernhard,
looked again at the splitter command in your last post. You also use a rather
high max-nodes value.
Such a high valu
Von: mkgmap-dev im Auftrag von Gerd
Petermann
Gesendet: Donnerstag, 1. November 2018 15:15
An: Thorsten Kukuk; Development list for mkgmap
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
Hi Thorsten,
thanks for the info. What is it that
:38
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
On Thu, Nov 01, Gerd Petermann wrote:
> Hi Bernhard,
>
> my understanding is that you should never see broken precompiled sea data,
> because the data source is not directly OS
On Thu, Nov 01, Gerd Petermann wrote:
> Hi Bernhard,
>
> my understanding is that you should never see broken precompiled sea data,
> because the data source is not directly OSM
> but http://openstreetmapdata.com/data/land-polygons where Jochen Topf invests
> time to check that the data is OK b
date but should always be OK.
Gerd
Von: mkgmap-dev im Auftrag von
Bernhard Hiller
Gesendet: Donnerstag, 1. November 2018 11:23
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
Hi Gerd,
thanks a lot for
1 - 100 of 1152 matches
Mail list logo
