November 2013 - mkgmap-dev - The mkgmap lists

[PATCH v1] finalizer style file
by WanMil 03 Nov '13

03 Nov '13

Hi, I had a look how much effort it is to add a finalizer style file that is used each time a rule with an element type definition matches. This might make it more easy to implement "general rules" (like the mkgmap:access tag which seems to be useful for complex styles). The finalize file must contain actions only. Otherwise mkgmap stops with an error message. Attached patch for the mergeroads branch realizes this. Maybe have a look on it and reply if you find it useful or superfluous. The patch also contains an additional style function type() returns node, way or relation depending on the elements type. @Steve: do you think it would be possible to add a finalize section to the bottom of each style file (especially points, lines and polygons)? I have the feeling that this is more understandable and maybe better to have different finalize styles for each element type. WanMil

3 5

mergeroad-branch r2795
by Bernd Weigelt 02 Nov '13

02 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all with the mergeroad-branch, i have got this errors svn is r2795, no problems with mergeroad-branch r2774 Bernd Time started: Sat Nov 02 12:14:28 CET 2013 Found one style in /home/bernd/map_build/mystyles/bikemap_style finished check-styles java.lang.NoSuchMethodError: uk.me.parabola.mkgmap.osmstyle.StyledConverter.<init>(Luk/me/parabola/mkgmap/reader/osm/Style;Luk/me/parabola/mkgmap/general/MapCollector;Ljava/util/Properties;)V at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.createConverter(OsmMapDataSource.java:259) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.setupHandler(OsmMapDataSource.java:158) at uk.me.parabola.mkgmap.reader.osm.o5m.O5mBinMapDataSource.load(O5mBinMapDataSource.java:43) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:127) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:167) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:63) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:220) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:216) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJ1ASEACgkQwCMdlf933K/IKACgnbcOExs2ckU/LMHaFRqcz7PL RbwAn1/4MbPwi/S6QPINNq64YOum4uel =bbwn -----END PGP SIGNATURE-----

2 2

[Patch v1] avoid wrong bearing results
by GerdP 01 Nov '13

01 Nov '13

Hi, a few weeks ago I suggested that we might need higher precision in the Coord class. Attached patch is a quick hack to implement this. If I got it right, this may allow to remove a lot of code that tries to correct what the rounding had done wrong. For the beginning, I've used the precise values only for bearing calculations, as I think that this is most important. high_precision_coord_v1.patch <http://gis.19327.n5.nabble.com/file/n5783533/high_precision_coord_v1.patch> Please let me know what you think about it. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Patch-v1-avoid-wrong-bearing-results-tp57835… Sent from the Mkgmap Development mailing list archive at Nabble.com.

4 7