- mkgmap-dev - The mkgmap lists

Commit r4680: Use https for all ivy downloads
by svn commit 26 Apr '21

26 Apr '21

Version mkgmap-r4680 was committed by steve on Mon, 26 Apr 2021 Use https for all ivy downloads http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4680

1 0

Check Roundabouts
by Mike Baggaley 26 Apr '21

26 Apr '21

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

2 1

check roundabouts
by Mike Baggaley 26 Apr '21

26 Apr '21

Hi Gerd, I have a largely completed change that extends the --check-roundabouts option to become --check-roundabouts=[all|loop|direction[:fix]|junctions|flares] and had made fixing reversed roundabouts an optional part of the direction option loop - check that roundabouts are formed from a single loop with no forks or gaps direction[:fix] - check and optionally fix the direction of travel around the roundabout junctions - check that no more than one connecting highway joins at each node flares - check that roundabout flare roads are one-way, are in the right direction, and don't extend beyond the flare However, separating the options completely allows for correction without displaying any message if desired, so I will look at that and I will change the reporting option name to --report-roundabout-issues as suggested, which brings it into line with the other diagnostic options. Also included in the change is code to more accurately try to identify roundabout flares, as the existing code produces more false results than wanted ones. It replaces --max-flare-length-ratio=NUM with --roundabout-flare-rules-config=filename where the config file can contain a set of rules for identifying flares. Cheers, Mike -----Original Message----- From: Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com] Sent: 12 April 2021 16:10 To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] logging Hi Mike, please have a look at the check-roundabouts and --check-roundabout-flares code. I think we missed the fact that --check-roundabouts may change the direction of roundabouts (in StyledConverter). So, I think we need a new option like report-roundabout-issues=[NUM] and another one for the reversing? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Mike Baggaley <mike(a)tvage.co.uk> 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 the FileNotWritableException was displaying the filename twice, so I have fixed that. In TdbBuilder, I have removed an unnecessary log.error In StyledConverter, I have added the synchronisation code for the removal of duplicate messages In O5mBinHandler, I have changed a thrown exception from IOException to FormatException so that it gets handled by its callers Cheers, Mike

2 1

Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution 23 raster problems
by John Thorn 26 Apr '21

26 Apr '21

I don't think this can be improved. As I understand it, internally Garmin devices hold coordinates in the number of bits specified in the level. So 24 bits has a resolution of 2.4 metres, 23 bits has a resolution of 4.8 meters and so on. If you look carefully, all the vertices of the lines lie on a square grid. Having said that, that must be a very steep slope - unless something else is creating the granularity. On Fri, 23 Apr 2021 at 12:06, <mkgmap-dev-request(a)lists.mkgmap.org.uk> wrote: > Send mkgmap-dev mailing list submissions to > mkgmap-dev(a)lists.mkgmap.org.uk > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > or, via email, send a message with subject or body 'help' to > mkgmap-dev-request(a)lists.mkgmap.org.uk > > You can reach the person managing the list at > mkgmap-dev-owner(a)lists.mkgmap.org.uk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mkgmap-dev digest..." > Today's Topics: > > 1. Resolution 23 raster problems (Felix Hartmann) > > > > ---------- Forwarded message ---------- > From: Felix Hartmann <extremecarver(a)gmail.com> > To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Bcc: > Date: Fri, 23 Apr 2021 18:01:15 +0800 > Subject: [mkgmap-dev] Resolution 23 raster problems > Any ideas why this is happening? > Some of the contourlines intersect each other at resolution 23 - I > especially used reduce-point-density=1.0 to try to stop it. > > java -jar -Xmx47000M /home/contourlines/mkgmap.jar --keep-going > --dem-poly=/home/contourlines/bounds/bayern.poly > --series-name=openmtbmap-cntrs-DBY-23-Apr-2021 > --dem=/home/contourlines/hgt/VIEW1/,/home/contourlines/hgt/SRTM1v3.0,/home/contourlines/hgt/VIEW3/,/home/contourlines/hgt/SRTM3v3.0/ > --dem-dists=5520 --max-jobs=7 --reduce-point-density=1 --transparent > --style-file=srtm24 --latin1 95260000.osm.pbf > > Is there any way to improve this? > > Look at the screenshots - the small one is resolution 23, the big one 24. > If using 10m interval contourlines this is pretty obviously not ideal. > Resolution 24 could be nicer - but I guess this is more a problem of > phyghtmap (while groundtruth can produce higher quality), but resolution 23 > really becomes confusing vs 24...: > [image: Simplification_23.PNG] > [image: Oiginal_24.PNG] > > If pictures don't show > https://openmtbmap.org/23.PNG > https://openmtbmap.org/24.PNG > -- > Felix Hartman - Openmtbmap.org & VeloMap.org > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

4 8

Resolution 23 raster problems
by Felix Hartmann 23 Apr '21

23 Apr '21

Any ideas why this is happening? Some of the contourlines intersect each other at resolution 23 - I especially used reduce-point-density=1.0 to try to stop it. java -jar -Xmx47000M /home/contourlines/mkgmap.jar --keep-going --dem-poly=/home/contourlines/bounds/bayern.poly --series-name=openmtbmap-cntrs-DBY-23-Apr-2021 --dem=/home/contourlines/hgt/VIEW1/,/home/contourlines/hgt/SRTM1v3.0,/home/contourlines/hgt/VIEW3/,/home/contourlines/hgt/SRTM3v3.0/ --dem-dists=5520 --max-jobs=7 --reduce-point-density=1 --transparent --style-file=srtm24 --latin1 95260000.osm.pbf Is there any way to improve this? Look at the screenshots - the small one is resolution 23, the big one 24. If using 10m interval contourlines this is pretty obviously not ideal. Resolution 24 could be nicer - but I guess this is more a problem of phyghtmap (while groundtruth can produce higher quality), but resolution 23 really becomes confusing vs 24...: [image: Simplification_23.PNG] [image: Oiginal_24.PNG] If pictures don't show https://openmtbmap.org/23.PNG https://openmtbmap.org/24.PNG -- Felix Hartman - Openmtbmap.org & VeloMap.org

2 1

Commit r4670: fix two more issues with method connectUnclosedWays() which might show up with incomplete multipolygons
by svn commit 23 Apr '21

23 Apr '21

Version mkgmap-r4670 was committed by gerd on Fri, 23 Apr 2021 fix two more issues with method connectUnclosedWays() which might show up with incomplete multipolygons 1) the algo supports a close of single unclosed way but did this only when at least two open ways were found. 2) if a single way was closed the code returned false instead of true. It seems that this error was previously fixed in the duplicated code BoundaryRelation but not here. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4670

1 0

Commit r4669: fix error found in faster-mp branch, see r4665
by svn commit 22 Apr '21

22 Apr '21

Version mkgmap-r4669 was committed by gerd on Thu, 22 Apr 2021 fix error found in faster-mp branch, see r4665 http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4669

1 0

WG: Yet More Logging
by Gerd Petermann 16 Apr '21

16 Apr '21

________________________________________ Von: Gerd Petermann <gpetermann_muenchen(a)hotmail.com> Gesendet: Freitag, 16. April 2021 15:51 An: Development list for mkgmap Betreff: AW: [mkgmap-dev] Yet More Logging Hi Mike, thanks, committed with r4663. And sorry, forgot to mention you in the log message Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)www.mkgmap.org.uk> im Auftrag von Mike Baggaley <mike(a)tvage.co.uk> Gesendet: Freitag, 16. April 2021 13:23 An: 'Development list for mkgmap' Betreff: Re: [mkgmap-dev] Yet More Logging Hi Gerd, Attached is a patch for CommandArgs that functions as you suggest. Cheers, Mike -----Original Message----- From: Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com] Sent: 11 April 2021 16:58 To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] Yet More Logging Hi Mike, not sure about the changes in CommandArgs. I'd prefer an info message for the new directory and exit with error if output-dir is not OK. For me it's normal to remove the directory and let mkgmap create it. If that fails for whatever reason mkgmap should just stop. Rest looks good. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgm ap.org.uk>> im Auftrag von Mike Baggaley <mike(a)tvage.co.uk<mailto:mike@tvage.co.uk>> Gesendet: Sonntag, 11. April 2021 17:44 An: 'Development list for mkgmap' Betreff: [mkgmap-dev] Yet More Logging 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

1 0

Re: [mkgmap-dev] Yet More Logging
by Mike Baggaley 16 Apr '21

16 Apr '21

Hi Gerd, Attached is a patch for CommandArgs that functions as you suggest. Cheers, Mike -----Original Message----- From: Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com] Sent: 11 April 2021 16:58 To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] Yet More Logging Hi Mike, not sure about the changes in CommandArgs. I'd prefer an info message for the new directory and exit with error if output-dir is not OK. For me it's normal to remove the directory and let mkgmap create it. If that fails for whatever reason mkgmap should just stop. Rest looks good. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgm ap.org.uk>> im Auftrag von Mike Baggaley <mike(a)tvage.co.uk<mailto:mike@tvage.co.uk>> Gesendet: Sonntag, 11. April 2021 17:44 An: 'Development list for mkgmap' Betreff: [mkgmap-dev] Yet More Logging 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

2 1

Please note when replying to messages
by Steve Ratcliffe 16 Apr '21

16 Apr '21

Hi everyone, For a day or so, messages have had a reply to address of mkgmap-dev(a)*www*.mkgmap.org.uk instead of the correct mkgmap-dev(a)*lists*.mkgmap.org.uk. This should be fixed now, but please check that you are sending messages to the correct address when replying. Steve

1 0