December 2012 - mkgmap-dev - The mkgmap lists

Timestamp in PBF files will affect splitter and mkgmap?
by maning sambale 18 Dec '12

18 Dec '12

This has been announced recently: http://lists.openstreetmap.org/pipermail/dev/2012-December/026278.html New timestamp headers are added in Geofabrik's PBF downloads. Just checking the devs if this will affect splitter and mkgmap. Thanks! -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 2

--no-poi-address option handling broken
by Thorsten Kukuk 18 Dec '12

18 Dec '12

Hi, the --no-poi-address mkgmap option doesn't work anymore: Invalid option: 'poi-address' I assume this is the outcome of the changes in r2386. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

4 10

Commit: r2414: Add dependencies that should have been included, see original patch at
by svn commit 18 Dec '12

18 Dec '12

Version 2414 was committed by steve on 2012-12-18 10:47:08 +0000 (Tue, 18 Dec 2012) Add dependencies that should have been included, see original patch at http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20120626/7005c2… Make the build.xml use these.

1 0

problem in mkgmap build
by GerdP 18 Dec '12

18 Dec '12

Hi Steve, it seems that the optional libs have changed. ant resolve-optional leads to this error message resolve-optional: [ivy:retrieve] conflict on D:\mkgmap\lib\optional\license-1.1.3.txt in [optional]: 1.1.3 won and some missing gt-* jars Gerd -- View this message in context: http://gis.19327.n5.nabble.com/problem-in-mkgmap-build-tp5740805.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 1

Commit: r2413: - correction: o5m reader did not remove unwanted tags from ways
by svn commit 18 Dec '12

18 Dec '12

Version 2413 was committed by gerd on 2012-12-18 10:43:26 +0000 (Tue, 18 Dec 2012) - correction: o5m reader did not remove unwanted tags from ways - cleanup code

1 0

News and announcements
by Steve Ratcliffe 17 Dec '12

17 Dec '12

Hi The new website is ready to start publishing news again - just in time for Gerd's splitter release. It is important that we have a place where people can go to see a summary of all the new feature and progress that has been made, so I plan to write a story from now on for every significant new improvement. But I am aware that there is a lot to catch up on - many great new things have been added that have not had a write up outside of the mailling list. So I want to start a series of retrospective articles about some of the main features that have been added. I also see statements on the web about mkgmap that are incorrect or problems have been fixed for ages, and we could also do articles to make everyone aware of how to do those things. Anyway if there is anything you think should be published then let me know I will try to build up a series of articles that can be published at regular intervals. ..Steve

1 0

Missing city in road-name-pois
by Carlos Dávila 17 Dec '12

17 Dec '12

A member of the list reported me that with latest versions of mkgmap, road-name-pois get their name correctly, but city information is missing, making this feature much less useful. I confirm I have the same problem, using --bounds=bounds and --location-autofill=is_in. I've been doing some test with old versions of mkgmap and the problem was introduced with r2335. Previous versions produce name/city POI's as expected.

1 0

House numbers
by Steve Ratcliffe 17 Dec '12

17 Dec '12

Hi I've been looking into house numbers a little. They work by giving a range of numbers between two nodes on a road. A node here is a routing node - where two roads meet - and not the meaning of node in OSM. You can say if the numbers are odd, even or both and if there are no numbers down one side of a road you can say that too. You specify numbers as being on the left or on the right when looking in the direction the road is drawn in. So you might have on the left hand side of the road numbers are odd and go from 25 to 37 and on the right hand side they are even and go from 26 to 32. If house numbers decrease along the direction of the road, you just have a start number that is larger than the end number. This is also clear from the polish notation for house numbers, which for the above example is: Numbers1=0,O,25,37,E,26,32 I hope to have at least a 'hello world' example of numbering working in the next week. ..Steve

5 7

splitter r257
by GerdP 17 Dec '12

17 Dec '12

Hi all, I've committed r257. Changes since r254: - fixed memory leaks (appeared when more than max-areas tiles were processed). Now it shoud really require less memory if you lower the max-areas value so that multiple read passes are done (of course run time increases) - write areas.poly only if no split-file was given - don't write unneeded coordinates to areas.poly (filter points lying on a straight line) - correct handling of holes in polygon (experimental) - report number of "areas per pass" in problem-list-generator - increased allowed max-areas (now 4096) - increased default max-areas (now 512) If I don't get problem reports, this version will be merged to trunk next monday. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r257-tp5740402.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

6 8

splitter r261: performance improvements
by GerdP 16 Dec '12

16 Dec '12

Hi, I've committed r261: Changes -improve throughput: + use BufferedInputStream with 4MB buffer for pbf and o5m input + reduced (oversized) o5m writer hashtable (saves around 635KB for each open output file), + improved hash function to avoid collisions + avoid GC because of obsolete new String() On my machine, the effect is great: When splitting germany.o5m with r260, the hard disk is rattling and rattling, and it takes between 75 and 110 secs to split the file (yes, very random results) With r261, the disk sound is normal again and it takes more less constantly 60 secs to split the same file with the same parms. I did some other tests regarding performance and found out that splitter works best when input file is on a different disk (even a slow USB 2.0 drive) and heap (-Xmx) is big enough to avoid massive GC. It has no positive effect if you specify -Xmx7000m when -Xmx1600m is already good enough. Ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r261-performance-improvements-tp574… Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 5