Version mkgmap-r4105 was committed by gerd on Sun, 04 Feb 2018
improve description of options
documentation-v4.patch by Mike Baggaley:
-- Clarification that if you specify --route you do not also need to specify
--net.
-- Clarification that --net is for producing a map with full address search
Hi Andrzej,
your patch reverts that change that I made r4048 to solve your problems with
empty areas. Maybe it is no longer needed since 4101?
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q1/027704.html
Gerd
Von: mkgmap-dev
Hi Gerd,
I have compiled baddem6 and I confirm your observations. I have no idea,
what to do with it.
I have found a minor error, see attached patch. Mkgmap calculates
min/max heights for header using values form tiles, which have bitstream
data. This is wrong for flat surfaces, which have
Just after posting the last patch, I realised there were some more obsolete
options (that were listed as ignored). I've moved these to the end in the
attached V4 patch.
Regards,
Mike
documentation-v4.patch
Description: Binary data
___
mkgmap-dev
Version mkgmap-r4104 was committed by steve on Sat, 03 Feb 2018
Prevent crash when a typ text file contains an empty CodePage=
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4104
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Gerd, thanks for the information. Please find attached v3 patch with the
following changes:
Clarification that if you specify --route you do not also need to specify
--net.
Clarification that --net is for producing a map with full address search but
no routing.
Clarification that 25 is the
Hi Mike,
thanks, looks good to me.
One problem:
--net is no longer obsolete. I've once changed the code so that you can create
a map that allows full address search but no routing.
It seems I forgot to update the docs.
Please review my changes reg. --net and --route in attached v2 which is for
Hi Gerd,
I have attached a further patch for documentation improvements. This
clarifies the syntax for several of the options and moves all the deprecated
and obsolete options to the end. Please review and commit if happy.
In further reading the documentation, I have the following questions that
Hi Gerd,
I think that it is better to get a rational set of option names than worry
about causing confusion due to minor changes. I would think there are only a
handful of people using the DEM options at the moment, and I don't believe
anyone who is not on the development list will be using them
Hi Gerd
I did not understand the exact meaning of the error message
Error in style: Error: (inc/compat_lines:124): Unrecognised command 'no'
I guess there is some room for a better message there.
The problem is that setaccess takes one argument, so that setaccess=no
is really:
Version mkgmap-r4103 was committed by gerd on Sat, 03 Feb 2018
improve description of DEM options
dem-options2.patch by Carlos Dávila, changes in options.txt
should be similar
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4103
___
Hi all,
not sure what that means but I am also able to reproduce the problem when I
create the DEM
data with Franks program BuildDEMFile using my modified hgt file containing
some voids.
The voids are far from the route that causes the crash, somewhere around
N52.24588 E10.50330.
I've
Second version, adding your comments
El 03/02/18 a las 07:33, Gerd Petermann escribió:
Hi Carlos,
thanks again. Seems I need new glasses when I look at all those typos :O
I like the introducing chapter about DEM, but I don't fully agree reg.
dem-dists:
"Reasonable values for the highest
Hi Steve,
I did not understand the exact meaning of the error message
Error in style: Error: (inc/compat_lines:124): Unrecognised command 'no'
but the patch fixes the original problem and shows that there is an error in
this line,
so I think you should commit it.
Gerd
Hi Mike,
- I also wondered if mkgmap should produce more DEM levels when --dem-dists is
missing, the problem is that I was unsure about the values to use.
- I like your suggested option names but I'd prefer not to change the options
this late to avoid confusion.
- There is only one
Hi Gerd
Funny , you are right I can't reproduce it any more but thanks for the
pdf case sensitivity issue
Nick
On 03/02/2018 08:26, Gerd Petermann wrote:
Hi Nick,
I understand that this doesn't work:
input-file:F:\mp5\backup\FEB120~1\405269~2.PBF
The program checks if the extension is
Having read the explanation of --dem-dists I think that the default for when
the option is not provided needs to be changed. The explanation says "mkgmap
tries to determine a reasonable value based on the resolution found in the
*.hgt files", but it also says "for gps devices you need one for
Hi Nick,
I understand that this doesn't work:
input-file:F:\mp5\backup\FEB120~1\405269~2.PBF
The program checks if the extension is ".pbf", and this test is case sensitive.
Not sure if this shoud be changed.
Please double check:
I can reproduce that it also doesn't work with the name in quotes,
Hi Minko,
I tried more routes now and found that I also see crashes with the patched
version.
@Andrzej: With my sample set [1] I see the crash with the attached route.
So, I think the problem is related to the DEM boundaries but not exactly to the
alignment.
I guess that is good.
Gerd
[1]
19 matches
Mail list logo
