- mkgmap-dev - The mkgmap lists

Commit: r1493: Only produce oversize sea polygons when
by svn commit 18 Jan '10

18 Jan '10

Version 1493 was commited by steve on 2010-01-18 18:24:58 +0000 (Mon, 18 Jan 2010) BRANCH: mp Only produce oversize sea polygons when generateSeaUsingMP is true. - WanMil

1 0

[PATCH v1] Preserve horizontal and vertical lines
by Mark Burton 18 Jan '10

18 Jan '10

This is just a rework of my earlier patch with the filter class renamed so that there can be no doubt as to what it does. As before, the rational behind this is to stop the DP filter from deleting the end points of lines that have been introduced by either the clipper or the polygon splitter (such lines are always horizontal or vertical). Yes, it will also preserve horizontal and vertical lines that occur in the OSM data. Whether that is good or bad, I do not know. Mark

1 0

Commit: r1492: Read of highways is one or two bytes depending on
by svn commit 18 Jan '10

18 Jan '10

Version 1492 was commited by steve on 2010-01-18 17:53:22 +0000 (Mon, 18 Jan 2010) Read of highways is one or two bytes depending on how many there are. Plus some code tidying.

1 0

overlays file for POIs
by Felix Hartmann 18 Jan '10

18 Jan '10

Hi, would it be possible to integrate an overlays file for POIs? The current overlays file (inside the style-file) only works for polylines. I would like to do the same for POIs. (I don't think it is needed for polygons, but maybe someone has creative ideas in his head and would like to have it for polygons too). I don't manage to program this, but I hope that it proves easy as we already have that functionality for lines. Would be great if it could be integrated. I tried to do it by using "continue" but this does not work. (continue will only work if the key or value is different). This does not work currently either (and the overlays function would be much better for this example anyhow): rcn_ref=10 [0x1800 resolution 22 continue] rcn_ref=10 [0x1701 resolution 22] *For what could we use it?* *1.* By creating invisible POIs and a visible point one could have different icons for different POIs however they would still be found under the same category. e.g. we know that 0x2f08 is found under transport --> ground transportation. We would like to have different symbols for a tube entrance, a bus_station a bus_halt,.... but would like all of them to show up under the search for ground transportation. so I would like to have in my "points" file the following entries: railway=subway_entrance { name 'tube ${name} ${ref}' | 'tube ${ref}' | 'tube ${name}' | 'tube' } [0x2f0801 resolution 22] railway=tram_stop { name 'tram_stop ${name} ${tram_lines} ${ref}' | 'tram_stop ${name}'} [0x2f0802 resolution 23] amenity=bus_stop { name 'bus_stop ${name} ${ref} ${bus_lines} ${operator}' | 'bus_stop ${name}' | 'bus_stop'} [0x2f0803 resolution 24] ..... now we know there are no 6 digit points code, therefore in our new pointsoverlay file we put 0x2f0801: 0x2f08, 0x1700 0x2f0802: 0x2f08, 0x1701 0x2f0803: 0x2f08, 0x1702 in our typfile we make 0x2f08 invisble, and create 3 nice icons to have a different layout for the different POI. *2.* In the netherlands and some other countries there are nodes with a number from 0-99 that are part of a cycle node network. I would like to display these points with an icon showing the number(and that is the real problem I face). We could add nice icons showing a number for rcn_ref=* * being a number from 0-99 (if it is 0-999 it would make even more sense). Currently I would have to create 100 different icons in my .TYPfile to be able to put a numbers from 0-99 on my map. If we had an overlays file I can reduce this to 20 icons in my Typfile and it would use only 20 ids instead of 100. (by having one icon for the "decimal number", and one icon for the right number). They should be displayed side by side by making half of the icon transparent, once to the left, once to the right. The same could be done for housenumbers (imagine designing 1000 entries in the typfile for numbers from 0-999, and only 30 if we would have an pointsoverlay file). *3.* we have the same for polylines and it has proven very useful. The overlays file currently only works for lines.

3 11

NullPointerException in Tdb while generating a map
by Marko Mäkelä 18 Jan '10

18 Jan '10

I think I reported something similar a while back, and it was fixed by reverting some revision. This one is somewhat different, because the crash occurs with Geofabrik's finland.osm.bz2 from Jan 18 (today), but Jan 13 is fine. I am using mkgmap r1490 and splitter r103. Exception in thread "main" java.lang.NullPointerException at uk.me.parabola.tdbfmt.OverviewMapBlock.setArea(OverviewMapBlock.java:100) at uk.me.parabola.mkgmap.combiners.TdbBuilder.addToTdb(TdbBuilder.java:114) at uk.me.parabola.mkgmap.combiners.TdbBuilder.onMapEnd(TdbBuilder.java:103) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:369) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:124) at uk.me.parabola.mkgmap.main.Main.main(Main.java:122) Any ideas or anything that I should try? My scripts are available at http://www.polkupyoraily.net/osm/. Marko

1 0

Commit: r1490: Give a more appropriate example
by svn commit 18 Jan '10

18 Jan '10

Version 1490 was commited by marko on 2010-01-18 10:10:53 +0000 (Mon, 18 Jan 2010) Give a more appropriate example in the comment of RuleFileReader.optimiseAndSaveAndOr().

1 0

Commit: r1489: In the default style, correctly set mkgmap:unpaved
by svn commit 18 Jan '10

18 Jan '10

Version 1489 was commited by marko on 2010-01-18 09:23:08 +0000 (Mon, 18 Jan 2010) In the default style, correctly set mkgmap:unpaved based on smoothness and sac_scale. In the regexps, the meta-characters |()*? are not to be escaped.

1 0

natural=wetland
by Carlos Dávila 18 Jan '10

18 Jan '10

According to osm wiki [1] natural=marsh is deprecated and intended to be substituted by natural=wetland + wetland=*. I think we should adapt default polygons style accordingly (see attached patch). Regards, Carlos [1] http://wiki.openstreetmap.org/wiki/Map_Features#Natural Index: resources/styles/default/polygons =================================================================== --- resources/styles/default/polygons (revisión: 1480) +++ resources/styles/default/polygons (copia de trabajo) @@ -61,6 +61,7 @@ military=range [0x04 resolution 18] natural=glacier [0x4d resolution 16] +natural=wetland [0x51 resolution 20] natural=marsh [0x51 resolution 20] natural=mud [0x51 resolution 20] natural=scrub [0x4f resolution 20]

3 7

Bug in LineSizeFilter/PolishMapDataSource splitting Polylines in polish format input
by Gert Münzel 18 Jan '10

18 Jan '10

Hi, Using polish-format as input, polylines exceeding MAX_POINTS_IN_LINE in LineSplitterFilter.java, will be splitted in a part which gets the original routeparam values and a splitted part where the routeparam seems to be unset.(e.g Line Typ 0x07 speedclass=2(40km/h) roadclass=0 will be splitted in first part speedclass=2(40km/h) roadclass=0 + second part speedclass=0(5km/h) roadclass=0. OSM-data input instead will be splitted as expected in two parts with the same routeparams. cheers Gert

1 0

Commit: r1487: The sea background
by svn commit 17 Jan '10

17 Jan '10

Version 1487 was commited by steve on 2010-01-17 23:33:42 +0000 (Sun, 17 Jan 2010) BRANCH: mp The sea background area (which is the outer area in the mp) is increased by 1 so that it does not share any lines and points with any of the inner areas. Fixes flodded areas problem arising from the mp code: mp does not recognize that polygon pi is in polygon po if they share a line or a point. - WanMil (patch v2/v3, merge series)

1 0