I recently had a problem where my disk filled up while running splitter, but
splitter did not exit, continuing to run for over an hour before I looked at
it and killed the process. I assume it was waiting for something which could
never happen.
The log file ended with the following:
Exception in
style manual layout sometime
Ticker
On 26/01/2022 01:10, Mike Baggaley wrote:
> I tried the following:
>
> highway=* & name=* & ${name|not-contained: :rn}!=* {echotags "Highway with
> name of route"; delete name}
>
> but I get "Error in style : error :
mething wrong?
Cheers,
Mike
-Original Message-
From: Mike Baggaley [mailto:m...@tvage.co.uk]
Sent: 25 January 2022 20:14
To: 'Development list for mkgmap'
Subject: RE: [mkgmap-dev] tag value within regular expression
Hi Ticker,
I had wondered about using not-contained (although
?
Ticker
On Tue, 2022-01-25 at 13:51 +, Mike Baggaley wrote:
> Hi,
>
> Section 4.2.3 of the style manual shows how to compare the values of
> two
> tags, but does not indicate whether it is possible to use tag values
> within
> a regular expression. Is this possible? If
Hi,
Section 4.2.3 of the style manual shows how to compare the values of two
tags, but does not indicate whether it is possible to use tag values within
a regular expression. Is this possible? If the name of a highway is
contained within the tag I use to contain the route name, I would like to
Hi Gerd,
My suggestion was simply that it was more logical to remove them from
anywhere, I don't actually use the option.
I would be in favour of changing the existing option unless anyone states
they specifically need to only remove the words from the end of the label.
I would not be in favour
bel that doesn't contain a blank
is an array with one element.
I have no idea how well this works with languages that are read from
right to left, but that's a different story.
Maybe you find better wording?
Gerd
____
Von: mkgmap-dev im Auftrag von Mike
B
Hi Gerd,
Please find attached a minor documentation patch.
Cheers,
Mike
options.patch
Description: Binary data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I create a separate line for national and regional walking and cycling
routes, thus the name of the route doesn't need to go in the road name. I do
have quite complex rules to handle this as I have national routes in one
colour, cycling in another and alternating where there are both, and these
Can't Felix just use substring in his style to limit the length?
Cheers,
Mike
-Original Message-
From: Gerd Petermann [mailto:gpetermann_muenc...@hotmail.com]
Sent: 06 December 2021 08:25
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] Building display.jar fails
Hi Felix,
I
2021 10:18
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] relation label patch
Hi Mike,
OK, that's something I didn't think about before. You probably don't use the
--housenumbers option?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
's the reason for this
trick?
Gerd
____
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Sonntag, 28. November 2021 17:59
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] relation label patch
Hi Gerd,
Please find attached a small patch that allows
Hi Gerd,
Please find attached a small patch that allows a node tagged with a role of
label or admin_centre to be still used if it has no name defined, rather
than only if it matches the name on the relation. Also an improvement in the
diagnostic message when a role label node is not being used.
Hi Gerd,
I think the original documentation for --reduce-point-density and
--reduce-point-density-polygon could do with some improvement. It also seems
bizarre to have a recommended value that is not the default. Is 2.6 the
default if --reduce-point-density is specified without a value, or is it
>Version mkgmap-r4735 was committed by gerd on Mon, 24 May 2021
>improve Logging/ debugging : todegrees.patch
>- change Coord.toString() to return the same as toDegreeString() instead of
a pair of Garmin units
>- add method toGarminString() to get a string with Garmin units
>- deprecate
with a description what's wrong and what
effect that has on routing?
If I got you right you use the messages to fix OSM data? Do you have a link
to a changeset?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Mittwoch, 26. Mai 2021 10:12
is simply not the right tool for OSM QA
checks.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 24. Mai 2021 09:14
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] logging improvement
Hi Gerd,
I know that the field
lace. What kind of problem should be detected
by those tests and what are those rules about?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Samstag, 22. Mai 2021 10:49
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] logging i
arcs?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Samstag, 22. Mai 2021 00:51
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] Similar Arcs
Hi Gerd,
Please find attached the patch for deleting similar arcs. It uses a new
that --check-roundabouts doesn't produce any messages in the console
when no logging.properties are used, just reverses wrong roundabouts.
That's what happened before the logging changes, right?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet
Hi Gerd,
Please find attached the patch for deleting similar arcs. It uses a new
mkgmap:nooverlap tag which can be set to a number between 0 and 127 (default
0) in the lines file. If set to a number greater than zero then the
overlapping part of the line will be deleted if it overlaps another
: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Freitag, 21. Mai 2021 14:12
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] logging improvement
HI Gerd,
Happy to set --fix-roundabout-direction on if --check-roundabouts is set -
see attached updated patch.
The reversing
is the same as before.
The message "... reversing it " is logged when --check-roundabouts is used
but the way is not reversed?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Donnerstag, 20. Mai 2021 13:13
An: 'Development list
(done in StyledConverter) without also getting all the check messages from
RoadNetwork.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Mittwoch, 19. Mai 2021 12:18
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] logging improvement
ways, and using my style file have reduced the number of
similar arcs warnings from about 21000 to about 600 which also results in a
reduction in size of the gmapsupp file. I will be posting this patch
shortly.
Cheers,
Mike
-Original Message-
From: Mike Baggaley [mailto:m...@tvage.co.uk
improvement
Hi Mike,
please help me: In what situation do we create roads from ways which were
created from relations?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Samstag, 15. Mai 2021 14:31
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev
Hi Gerd,
Please find attached a small patch that changes the logging of RoadDef when
the original element is a relation. Currently it just says "generated way";
with the patch it gives the URL of the relation in the same way as it does
for ways.
Cheers,
Mike
originalid.patch
Description:
__
Von: mkgmap-dev
mailto:mkgmap-dev-boun...@lists.mkgm
ap.org.uk><mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk<mailto:mkgmap-dev-b
oun...@lists.mkgmap.org.uk>>> im Auftrag von Mike Baggaley
mailto:m...@tvage.co.uk><mailto:m...@tvage.co.uk<mailto:mi
k...@tvage.c
Auftrag von Mike
Baggaley
Gesendet: Dienstag, 11. Mai 2021 13:15
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Commit r4703: improve RoadMerger (based on
merge-roads-reversed-v6.patch)
Hi Gerd,
I may be misunderstanding this, but the explanation of when it is enabled
seems illogical
Hi Gerd,
Please find attached a small patch that fixes a problem with the use of the
label role in multi-polygon relations. Currently, if a node has the role of
label but has no name or a different name from the polygon, a message is
output saying the node will not be used. However, it is used
Hi Gerd,
I may be misunderstanding this, but the explanation of when it is enabled seems
illogical.
It seems to me that reversing should be the default except on ways that have
mkgmap:has-direction=true unless a switch is given to disable it.
Or it could be off by default and a switch enables
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 10. Mai 2021 17:15
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] Duplicate roads added by default style
Hi Gerd,
I misunderstood the problem you were discussing - I was indeed referring to
overlapping ways from
Hi Gerd,
Would it not be better for the code to detect whether it is a combiner and
adjust the message accordingly?
Cheers,
Mike
-Original Message-
From: svn commit [mailto:s...@mkgmap.org.uk]
Sent: 11 May 2021 08:33
To: mkgmap-...@lists.mkgmap.org.uk; mkgmap-dev@lists.mkgmap.org.uk
is like v5 but contains the additional check in
StyledConverter.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 10. Mai 2021 16:56
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] Duplicate roads added by default style
HI Gerd
HI Gerd,
I would ideally like a new mkgmap tag that if found would remove the
duplicated way or part of a way. This could get tricky when the part to be
deleted is in the middle of the way, as it would need to produce two ways.
Something like:
railway=platform {set mkgmap:removeoverlap=true}
Hi Gerd,
Please find attached the previously discussed patch that splits checking and
fixing roundabouts and flares and provides enhanced flare analysis. I note
that some checks are performed when the style is being processed with others
being performed later. I have not attempted to combine
Hi Gerd,
I believe this activity is a precursor to reducing zig zags at low
resolutions (though I may be confusing two different activities). I think
the case shown here would be better handled by seeing whether at the low
resolution the two entry points to the A13 can be reduced to a single
Hi Gerd, I haven't posted it yet. I'm away on holiday at the moment, hence the
lack of input from me as it is difficult to reply to the digest from a phone. I
will post the patch when I return home.
Cheers, Mike___
mkgmap-dev mailing list
Hi Gerd,
Attached is a patch that provides additional information about logging.
Cheers,
Mike
logging.txt.patch
Description: Binary data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
a
console handler.
Writing this I wonder if it is now impossible to see only error messages on
stderr when the reporting options are enabled?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 12. April 2021 17:56
An: 'Development list
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 12. April 2021 17:02
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] logging
Hi Gerd,
In the attached patch there are a few improvements to messages as well as
some more use of logging:
In ImgFS, the message from
Hi Gerd,
Please find attached a patch with the remainder of the logging changes
(apart from CommandArgs).
There are changes to the main program so that the dates and times are only
output if mkgmap is processing one or more files.
The patch includes an update to the unit test. Note that this
Hi Gerd,
In the attached patch there are a few improvements to messages as well as
some more use of logging:
In ImgFS, the message from the FileNotWritableException was displaying the
filename twice, so I have fixed that.
In TdbBuilder, I have removed an unnecessary log.error
In StyledConverter,
atever reason mkgmap should just stop.
Rest looks good.
Gerd
Von: mkgmap-dev < <mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk>
mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Mike Baggaley <
<mailto:m...@tvage.co.uk> m...@tvage
Hi Gerd,
Here's the next patch. Hopefully should only need a couple more patches to
package up the remainder of the changes.
Cheers,
Mike
yetmorelogging.patch
Description: Binary data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
k MdxFile should use Logger.defaultLogger.error() and maybe
LblFileReader should use Logger.defaultLogger.warn()
(as in attached patch)..
Just my feeling, can't prove anything.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Sonntag, 11. April 2021 16:10
A
Hi Gerd,
Here is the next patch. This one moves a number of messages from writing to
stdout/err to using logging. There are several files changed, but most have
only very small changes.
I'd be interested to know what the message "Map has tide prediction, please
implement" in LBLFileReader
Hi Gerd,
Attached is the next small patch. This brings echo and echotags under
logging control.
Cheers,
Mike
-Original Message-
From: Mike Baggaley [mailto:m...@tvage.co.uk]
Sent: 11 April 2021 09:59
To: 'Development list for mkgmap'
Subject: RE: [mkgmap-dev] Re logging improvements
thout a ConsoleHandler")
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Freitag, 9. April 2021 09:30
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] Re logging improvements
Hi Gerd,
Please find attached the updated version of the patc
Hi Gerd,
I suggest a couple of minor tweaks to the commit message:
diagnostics.patch by Mike Baggaley
- diagnostic messages are now written to stderr when there is no logging
configuration specified.
- diagnostic messages have the level DIAGNOSTIC when they are logged. Before
some had WARNING
74016 direction is wrong - .." written to stderr now. Why not stdout?
If I use -Dlog.config=logging.properties the diagnostic messages are not
written to the console. Is that intended?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Mittwoch
of the codepage patch. I've added two words.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Mittwoch, 7. April 2021 11:00
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] diagnostic patch
Hi Gerd,
Please find attached two patches - one
Hi Gerd,
Please find attached the updated version of the patch. It adds
synchronisation of the static variables in StyledConverter and fixes the
unit test.
It includes the not yet committed changes in codepage.patch,
diagnostics.patch and Tests.patch.
Cheers,
Mike
logging4.patch
Description:
Hi Gerd,
Please find attached a patch that fixes the unit tests when using logging
instead of writing to stderr/out (a few of the tests will fail if used
against the current mkgmap release as I have changed some checkNoError()
calls to checkError("Number of ExitExceptions: 0") - this was written
Hi Gerd,
Please find attached two patches - one that contains the user interface and
logging changes to provide improved output from the diagnostic options,
along with the other logging interface changes in readiness for replacing
direct writes to stdout/err. The second documents the steps that
with a patch
that fixes the unit tests (if you have an idea) and the other errors that
you found so far. I prefer to have a few smaller commits with clear commit
messages.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Dienstag, 6. April 2021 02
do
anything that works somehow.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 29. März 2021 21:57
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] logging improvements
Hi Gerd,
If the changes to the logging are
Hi Gerd,
I have been having difficulties with the mkgmap test code which uses the
discontinued javax.xml.bind.DatatypeConverter for a single function
printHexBinary. Despite downloading a copy of the library and telling
Eclipse to use it, it doesn't seem to want to work. I found a replacement
attached file.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Sonntag, 28. März 2021 16:43
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] logging improvements
Hi Gerd,
To assist with examining the patch, most of the source files hav
mkgmap-dev] logging improvements
Hi Mike,
again: Please separate the changes regarding --check-routing-island-len from
those changes reg. logging.
It's a huge patch and I don't see a reason to mix the two things.
Gerd
Von: mkgmap-dev im Auftrag von Mik
the two things.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Donnerstag, 25. März 2021 11:15
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] logging improvements
Hi Gerd,
Please find attached an updated patch.
Regarding your
. By default this global logger allows
errors and warnings though, whereas the other loggers only allow errors.
This means that program warnings can be displayed without having to display
OSM data warnings as well.
Cheers,
Mike
-Original Message-
From: Mike Baggaley [mailto:m...@tvage.co.uk
th your patch.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Samstag, 20. März 2021 00:52
An: 'mkgmap development'
Betreff: [mkgmap-dev] logging improvements
Dear all,
Please find attached a first stab at improving the way error and other
messages are written, which at present
Dear all,
Please find attached a first stab at improving the way error and other
messages are written, which at present is an ad hoc mixture of writing to
stderr, stdout and using Java logging, with no apparent logical structure.
Writing to stderr or stdout is not thread safe and causes problems
I don't use precomp-sea, but I don't use floodblocker either, so the suggestion
is fine by me. It may however be worth displaying a warning if a tile appears
to be flooded.
Cheers,
Mike
-Original Message-
From: Ticker Berkin [mailto:rwb-mkg...@jagit.co.uk]
Sent: 17 March 2021 09:28
as default. I see +500
warning messages for a single tile in my home area. Most of them are about
problems in the data, many of those data "problems" have no effect on the
map or are caused by incomplete data.
Gerd
Von: mkgmap-dev im Auftrag von Mik
HI Gerd/Steve,
The current code with the handler set to SEVERE and logger set to WARNING
doesn't seem to make a lot of sense. Wouldn't it be better if the default
handler level was FINE, so that just logger filters the messages. I think
warnings should be allowed through by default as well, so
Hi all,
At low resolutions I would like to be able to remove parallel lines so that
(for example) only a single motorway carriageway or railway track is shown
instead of two or (in the case of the West Coast Main Line) four lines,
which due to different Douglas Peucker line simplifications end
Hi Gerd,
The attached patch fixes a crash if you inadvertently specify a .o5m file
after the -c command line argument.
Cheers,
Mike
CommandArgsReader.patch
Description: Binary data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
ach would be to change the
> resolution/level for the object, so I wonder why we need a special
> variable.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag
> von Mike Baggaley
> Gesendet: Sonntag, 7. März 2021 22:30
> An: 'Development list f
Hi Karl,
The first tile is likely to be generated with only a single thread running
whilst memory usage is checked, then the remainder may use both your
processors. If there is something about this tile that causes it to take a
long time, it may be worth moving it back in the list so that it
Mike,
do you have a use case for that? My approach would be to change the
resolution/level for the object, so I wonder why we need a special variable.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Sonntag, 7. März 2021 22:30
An: 'Development
Hi Gerd,
Please find attached a patch that causes objects that have
mkgmap:nooverview=yes to be omitted from the overview map.
Cheers,
Mike
OverviewContent.patch
Description: Binary data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
k I prefer to change the constructor for BufferedImgFileWriter to pass
the section name instead of extracting it from the stacktrace. Did you
consider this?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Sonntag, 28. Februar 2021 17:38
An: 'Develo
: Re: [mkgmap-dev] Error writing overviewmap - continue at failure
Don't you have sea in your map? If yes, what do you need coastline for?
El 28/2/21 a las 17:47, Mike Baggaley escribió:
> I have coastline in my overview of the UK down to the lowest level. At the
> lowest level, my ov
I have coastline in my overview of the UK down to the lowest level. At the
lowest level, my overview contains just coastline, country boundaries, major
cities and motorways. For an island, I would suggest the coastline is the most
important thing to have in the overview.
Cheers,
Mike
amending every
sub file handler, so have resorted to examining the stack trace. I've also
changed the keep going handling to what works for me and seems more logical.
Let me know if you think it is not quite right.
Cheers,
Mike
-Original Message-
From: Mike Baggaley [mailto:m...@tvage.co.uk
Hi Joris,
I will soon be passing an updated patch to Gerd to improve this, as I had
also been experiencing similar problems. The overview map is not built until
all the tiles have been created (assuming the error is not in an overview
tile), and I don't think it uses the style file at that
ize. So, maybe show that sub file name also?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Mittwoch, 24. Februar 2021 00:16
An: 'Development list for mkgmap'
Betreff: [mkgmap-dev] Overview Too Big
Hi Gerd,
The error message that mkgmap outp
Oops, attached the wrong patch. Here's the correct one...
-Original Message-
From: Mike Baggaley [mailto:m...@tvage.co.uk]
Sent: 24 February 2021 13:43
To: 'Gerd Petermann' ; 'Development list
for mkgmap'
Subject: RE: [mkgmap-dev] minor documentation improvement
Hi Gerd,
>I th
Hi Gerd,
>I think "Error checking options" is too strong. My understanding is that
the options enable additional plausibility checks which may help to explain
>unexpected results in routing. So, maybe "Diagnostic options" is better?
Sounds reasonable - please find an updated patch.
>reg. "POI
Hi Gerd,
Please find attached a patch to move some of the miscellaneous options into
new sections Error checking options and POI options. There is no change to
any of the actual wording.
Cheers,
Mike
docsections.patch
Description: Binary data
___
Hi Gerd,
The error message that mkgmap outputs when the overview map is too big is
not helpful. Please find attached a patch that improves this.
Cheers,
Mike
OverviewTooBig.patch
Description: Binary data
___
mkgmap-dev mailing list
Hi Gerd,
I've further edited the documentation in the light of your comments - see
below inline.
>- reg. --add-pois-to-lines (and also add-pois-to-areas)
>I think the texts (and of course the option names) are misleading. The
program doesn't generate "POI", it just generates additional nodes
error
Hi Mike,
I cannot reproduce your result with the command
java -jar mkgmap.jar -gmapi test.osm.
I assume you look at cached data. Did you press Ctrl+G 2 times?
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Donnerstag, 18. Februar 2021 01
Hi Gerd,
Please find attached a patch to improve the documentation of sea processing
plus minor changes to --add-pois-to-lines.
I note that extend-sea-sectors says "Adds a point so coastline reaches the
nearest tile boundary. This implies no-sea-sectors". But no-sea-sectors
disables the
HI Ticker,
If you name the typ in the typ file, there should be no need for a default name
in the style, and as the typ file already allows multiple languages this should
mostly negate the need for a 'translate' function. Of course, this assumes that
you don't use a generic typ code for
ot sure what is confusing you?
I've made some minor changes to the code to reduce complexity, but didn't
check the details of the new code.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 8. Februar 2021 15:58
An: 'Development lis
HI Joris,
I do not think we should be hard coding non-standard tags into mkgmap, even
if there are a number of them in some countries.
cycleway:left=opposite, cycleway:left=opposite_lane and
cycleway:left=opposite_track are all non-standard and to me don't make any
sense.
I suggest you add
HI Gerd, I don't have a build that includes the PrecompSeaGenerator, but I
would expect the impact to be the same as for in-line sea generation: an
increase in execution time if /check is specified with a reduction if it is
not specified.
I'm not quite clear what happens if you specify
Hi Gerd/Ticker,
Please find attached an updated patch that adds the --generate-sea=check option
and fixes the other typo.
Cheers,
Mike
-Original Message-
From: Mike Baggaley [mailto:m...@tvage.co.uk]
Sent: 31 January 2021 17:31
To: 'Development list for mkgmap'
Subject: RE: [mkgmap
is). I suggest having
an option to enable the extra checking.
I don't have any problem with more detailed logging.
Good to fix the spelling mistake (but should fix loadLandAndSee as
well)
Ticker
On Fri, 2021-01-29 at 11:18 +, Mike Baggaley wrote:
> Hi Gerd, attached is a slightly updated
Auftrag von Mike
Baggaley
Gesendet: Montag, 18. Januar 2021 10:06
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] Fix Sea Patch
Hi Gerd,
I had too little logging information in the version I sent previously. The
attached remedies that.
Cheers,
Mike
-Original Message-
From: Mike
: Re: [mkgmap-dev] Fix Sea Patch
Hi Mike,
it would be great to have some unit tests or at least a sample file
containing the problem cases which are treated by your patch.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 18. Januar
Hi Gerd,
I had too little logging information in the version I sent previously. The
attached remedies that.
Cheers,
Mike
-Original Message-
From: Mike Baggaley [mailto:m...@tvage.co.uk]
Sent: 18 January 2021 00:28
To: 'Development list for mkgmap'
Subject: RE: [mkgmap-dev] Fix Sea
fix problems which only occur in
data that is produced by a 3rd party software. My understanding is that the
"fixing" should happen in that 3rd party software, not in mkgmap.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 4. Jan
Hi Gerd,
I have made a couple of small changes in the attached version.
Cheers,
Mike
-Original Message-
From: Gerd Petermann [mailto:gpetermann_muenc...@hotmail.com]
Sent: 15 January 2021 08:26
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] improved diagnostics patch v2
Hi
p://www.openstreetmap.org/; + kind() + "/" + id;
}
Gerd
____
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Donnerstag, 14. Januar 2021 12:59
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] improved diagnostics patc
ngAngleFixer f:\osm\work.osm:
removing obsolete point on almost straight segment in way
http://www.openstreetmap.org/relation/1518688 at
http://www.openstreetmap.org/?mlat=53.892259=8.684634=17
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet:
HI Gerd,
I spotted a problem in Element.getBasicLogInformation if it is called on an
element that does not have an OSM Id. The attached patch fixes that. The
previous version only fixed it in Element.toBrowseURL.
Cheers,
Mike
-Original Message-
From: Mike Baggaley [mailto:m
1 - 100 of 327 matches
Mail list logo
