- mkgmap-dev - The mkgmap lists

Commit: r853: When creating a multipolygon, we have to do a complete deep copy
by svn commit 26 Jan '09

26 Jan '09

Version 853 was commited by steve on 2009-01-26 22:55:13 +0000 (Mon, 26 Jan 2009) When creating a multipolygon, we have to do a complete deep copy of the original generic relation.

1 0

Relations and Multiple Tag Parsing Style Rules
by f.hartmann 26 Jan '09

26 Jan '09

1. Is there any possibility to give a different tag to relations? The problem is that many cycleroutes are tagged as relation id=12345.... which then lists the way sections that belong to the relation. So the ways itself are not tagged differently. Here is one example (I shortened the ways which belong to it) which I would like to highlight. Is there a possibilty to highlight all relations of route=bicycle or route=mtb etc....? <relation id='17206' timestamp='2008-11-03T14:41:59+00:00' user='Loschi' visible='true'> <member type='node' ref='15733829' role='' /> <member type='way' ref='3220516' role='' /> <member type='way' ref='4682210' role='' /> <member type='way' ref='4776002' role='' /> <tag k='created_by' v='Potlatch 0.10f' /> <tag k='ref' v='6' /> <tag k='rcn' v='yes' /> <tag k='route' v='bicycle' /> <tag k='name' v='Donauradweg (NÖ)' /> <tag k='type' v='route' /> <tag k='network' v='rcn' /> 2. Could Multiple Tag parsing be implemented into the style rules somehow? I know that I could use combinations like highway=path & mtb:scale=0 --> 0x01 and highwway=path & mtb:scale=1 --> 0x02 But that poses several problems: a) Running out of definitions --> Mapsource only displays 0x00 to 0x2a (excluding 0x17 and 0x20 to 0x25 that are reserved for contourlines). b) There are other mtb related tags such as mtb:scale:uphill= and interesting tags like smoothness and tracktype. Writing combinations for all of them to display seperately will become very complicated. Solution: If a way has two tags that are listed in the style file, both should be included seperately into the image. By using a .typ file one can then decide how to map them. Using transparency it's easy to see at the same time 4-5 different tags. I.e. you have the way in the middle. And on either side of the way you put dots or symbols to show further attributes. As a way can be drawn up to 32 pixels wide. One has 15 pixels open for putting in additional information to each side of a way that is 2 pixels wide (this assumes that the ways are identical copies of each other, just with a different 0x?? definition). For the moment I have to generate a seperate map for each tag that I assume to appear in combination with other tags (Well I can through togehter some tags with Regex rules) and then make all maps except one transparent before I upload them to the Garmin GPS. On the GPS it will display without problems, but I can't use Mapsource for planning a trip now, having 5-6 maps to show me all attributes that I consider important for mountainbiking. Felix Diese Nachricht erhalten Sie von einem Studierenden der IMC Fachhochschule Krems. Für Übermittlungsfehler oder sonstige Irrtümer bei Übermittlung besteht keine Haftung seitens der IMC Fachhochschule Krems. This message is being transmitted by an IMC student. The sender does not accept liability for any errors or omissions as a result of the transmission.

3 14

[mkgmap-dev] Commit: r852: These 2 byte versions of the place codes, (city, town etc) appear
by svn commit 26 Jan '09

26 Jan '09

Version 852 was commited by steve on 2009-01-26 21:24:01 +0000 (Mon, 26 Jan 2009) These 2 byte versions of the place codes, (city, town etc) appear to enable different and better behaviour on GPS units. - Mark Burton.

1 0

Commit: r849: All relations other that the first were not being processed
by svn commit 25 Jan '09

25 Jan '09

Version 849 was commited by steve on 2009-01-25 22:10:47 +0000 (Sun, 25 Jan 2009) All relations other that the first were not being processed through the style system.

1 0

Commit: r848: Add option to ignore any bound or bounds elements in the
by svn commit 24 Jan '09

24 Jan '09

Version 848 was commited by steve on 2009-01-24 18:34:29 +0000 (Sat, 24 Jan 2009) Add option to ignore any bound or bounds elements in the .osm files. - Mark Burton

1 0

Commit: r832: Use the cp1252 code page for reading .mp files.
by svn commit 24 Jan '09

24 Jan '09

Version 832 was commited by steve on 2009-01-11 14:54:38 +0000 (Sun, 11 Jan 2009) Use the cp1252 code page for reading .mp files. Recognise the CodePage option in a .mp file. This doesn't currently work as the file is already open with the default charset.

3 2

Commit: r847: Use the correct code page as declared in the .mp file
by svn commit 24 Jan '09

24 Jan '09

Version 847 was commited by steve on 2009-01-24 15:23:24 +0000 (Sat, 24 Jan 2009) Use the correct code page as declared in the .mp file to read the label values. For polish file format. Tested somewhat for czech with cp1250.

1 0

Commit: r846: The mkgmap packages are not meant to be used from within imgfmt
by svn commit 24 Jan '09

24 Jan '09

Version 846 was commited by steve on 2009-01-24 14:38:15 +0000 (Sat, 24 Jan 2009) The mkgmap packages are not meant to be used from within imgfmt so removed usage of RoadNetwork from there and passed the constituent data structures instead. Rename ConfiguredByProperties to Configurable.

1 0

Commit: r845: Removed lots of unused code etc.
by svn commit 22 Jan '09

22 Jan '09

Version 845 was commited by steve on 2009-01-22 22:11:57 +0000 (Thu, 22 Jan 2009) Removed lots of unused code etc.

1 0

Program exit codes
by Toby Speight 21 Jan '09

21 Jan '09

First, let me introduce myself to the list. I'm new to geosystems, but learning quickly after I acquired a GPS receiver two weeks ago. I've written a makefile to turn SRTM elevation data into vector contour maps (I'll write it up on OpenStreetMap.org once I'm happy with it). One of the problems[1] I've had is that mkgmap exits with return code 0 always, even on failure. This means that the makefile blindly continues to make its dependents, with a missing or invalid .img file - or in the worst case, an old, out-of-date one. If you were to add System.exit(1) in appropriate places (probably just the exception handler in main()?) - I'd be really grateful, and so probably would others. [1] The biggest problem I had was with re-referencing the EGM96 data to OSGM02 - until I realised that the difference is well within the 1-metre precision of the source data, never mind its accuracy! BTW, does mkgmap dislike negative ID values when reading OSM files? gpsbabel writes these when writing, and I was wondering whether that's what was causing empty tiles in my first attempt.

3 4