User talk:Breki

From OpenStreetMap Wiki
Jump to navigation Jump to search

download tiles don't work

i test kosmos and put an comment on main wiki page about i can't succeed donload tiles using kosmos . Doe anybody helse have the same behaviour ? France-59-valenciennes France-59-valenciennes 06:30, 2 May 2009 (UTC)

PDF printer driver

Do you have any pointers to where one can find a printer driver? (Renderers feature list) Erik Johansson 09:23, 13 January 2009 (UTC)

I've added a link to the one which I used to the Renderers feature list --Breki 20:01, 13 January 2009 (UTC)

Excellent work!

Hi there, just wanted to say thank you for your efforts! I have been looking to generate some maps for my Garmin unit Etrex Legend HCx with a view to making available for download some locality/county maps that are updated on a regular basis for the UK with different focuses on roads/hiking. Some of the existing maps available are a few months old.

I was starting to try and piece together all the programs to make it work, but it was proving tricky. I have just found your excellent project and I believe it does everything I need. I'll be trying it out over the next week and hopefully will be able to publish some maps soon! GregRobson 23:20, 3 February 2009 (UTC)

Hi Greg, I'm glad you like it. Thanks for your support, if you have any suggestions on how GroundTruth could be improved, I'll be happy to listen --Breki 05:56, 4 February 2009 (UTC)

background color of map

What I did not find out is: why is the background of my generated map on my Garmin Etrex Vista Hcx black? --katpatuka 16:21, 5 February 2009 (UTC)

Hmmm the background color for "empty" space is not set by GroundTruth. Are you sure the unit hasn't switched to nightlight colors? You can force the unit to use different color scheme in the Setup menu. --Breki 16:45, 5 February 2009 (UTC)
Yes, you are right,thanks! ;-) Is there some more information on how to edit or create rule files somewhere? Or is that something which has to be written first!?... ;-) --katpatuka 17:34, 5 February 2009 (UTC)
I'm describing it in the manual, but the process very slow :) --Breki 19:01, 5 February 2009 (UTC)

Water under Residential?

On my map a river (water area) fanishes when entering a residential area (town) - how is layering getting managed ? --katpatuka 05:53, 7 February 2009 (UTC)

Currently layer tags are not taken into account. I'm not too sure I can persuade the unit to display certain individual elements over each other, I'll have to make an experiment with that. The only ordering is based on order of area rules - the first rule is displayed on top, the last on the bottom - that's a facility provided by TYP files. --Breki 15:27, 7 February 2009 (UTC)
Ok - I think I'll take a copy of GroundTruth_Hiking_Map and play around with it. Another thing: do you know if UTF is supported by Garmin* at all? Since I live in Turkey I'd like to be able to have turkish characters (as you would like to have Slovenian...). And: is it possible to have small characters instead of CAPITAL? --katpatuka 19:28, 7 February 2009 (UTC)
I've played around a lot with encodings and I could not make my Vista Cx show national characters. So I guess my unit does not support it, I don't know about others. As for small characters - it's possible to have labels for POI in small characters, but for lines (street names etc) my unit just (and some others, from the reports I received) prints gibberish for small case chars. That's why I made GroundTruth generate all line labels in uppercase. --Breki 21:16, 7 February 2009 (UTC)

Cycling maps?

Would a cycling map be feasible? Which features should be shown on it?

Of course, it's just that I'm not a cyclist, so I hadn't really taken the time to create a cycling map :). I've just prepared the template to help interested users get started: GroundTruth Cycling Map (there are some people that already expressed interest in creating the cycling map). --Breki 16:46, 17 February 2009 (UTC)

Extra columns for the rule pages

Can I add extra columns (for comments and such) to the tables in the rule pages, and to the table with the standard Garmin types?

If you're referring to GroundTruth rules, I guess you can, but I would recommend trying it out locally on your disk with GroundTruth before committing any changes to the Wiki pages - just to make sure GT can parse them. --Breki 14:37, 20 March 2009 (UTC)

are contour maps working ?

I tried to generate a contour map for my region in combination with normal map data but I don't see contours. I created the output.ibf once and then executed:

groundtruth makemap 

Am I thinking wrong? --katpatuka 09:06, 3 April 2009 (UTC)

  1. What is the size of the output.ibf file?
  2. You don't need -param=Transparent:Y, it's done automatically. In fact, I recommend removing this parameter since it could conflict with other stuff.
  3. Since you haven't specified any -osm files, you don't need -rules=""
  4. Have you checked if you see the contours in MapSource? Make sure you set the detail level at "Highest", just to be safe.

--Breki 15:58, 3 April 2009 (UTC)

  1. 3.27 Mb
  2. ok, no problem
  3. if I specify makemap only, are output.osm and output.ibf both being used automatically if found?
No, just output.osm. You need to specify output.ibf explicitly.
  1. no contours to be seen in mapsource too even if detail level is set to Highest;
    I use NxxE0xx.hgt where xx = [37-39] and yy = [34,35] (btw: is there a .hgt file viewer?)
.hgt is a plain text file, so you can view it with Notepad.
I use a garmin etrex vista hcx and latest mapsource ver.
are you sometimes on irc (#osm) ? --katpatuka 05:44, 7 April 2009 (UTC)
no, I haven't got the time for irc, unfortunately. Maybe I'll start using it --Breki 07:16, 8 April 2009 (UTC)

Anyway, I don't know why you don't see the contours. Here are some further steps for investigation:

  1. Look into generated .MP files. Do they contain contour data or not? (you can send me one of them if you like)
  2. What is the size of generated IMG files?
  3. Try generating contours for a different area, like western Europe.

--Breki 07:16, 8 April 2009 (UTC)

Generating Contours

I tryed to generate contours for my area and type after downloading osmdata : GroundTruth contours --bu "" and get folowing error-msg:

 ERROR: Brejc.DemLibrary.DemLoaderException: Error downloading SRTM data. ---> Sy
stem.Net.WebException: Der Remoteserver hat einen Fehler zurückgegeben: (404) Ni
cht gefunden.

kann sein, dass die uri für die srtm-daten falsch ist?

win xp .net 3.5 GroundTruth --ChrSchultz 13:29, 18 October 2009 (UTC)

Just released a new version, could you try with the new one? --Breki 15:21, 18 October 2009 (UTC)

blue water

I'm using GroundTruth and my sea isn't blue even when I set the rule "natural=sea => blue". Is it a bug or a missing feature or my mistake? --Sparcuser 11:24, 20 July 2009 (GMT+2)

Have you tried setting the SeaColor option in rules? (Kosmos_General_Purpose_Rules#Options) --Breki 07:42, 22 July 2009 (UTC)
Yes, now I've tried without success. I'm using these Rules and the osm-data from The baltic sea has the same color as the Land and moreover I'm missing the coastline in the southwest of Fehmarn. What am I doing wrong? --Sparcuser 06:22, 24 July 2009 (UTC)
Can you post some image sample? --Breki 20:06, 26 July 2009 (UTC)
Have a look at this picture ( It is a picture of my Garmin Oregon 300 showing the map of southwest Fehmarn. --Sparcuser 18:06, 4 August 2009 (UTC)
Sorry, I thought you were asking about Kosmos :). GroundTruth currently doesn't fill the sea polygons, it can only show the coastline. I don't know why the coastline is missing, though. If you open the original OSM file in JOSM, does it show the whole coastline? --Breki 06:46, 5 August 2009 (UTC)

GroundTruth Standard Garmin Types

Hello, I added the 0x on GroundTruth Standard Garmin Types so that we see it is an hexa value. Also, when the table is sorted all values are sorted correctly, if removed all hex number containing a letter are sorted before the numbers. Do you know a way to sort it correctly? Thanks. Nakor 09:25, 31 July 2009 (UTC)

Kosmos and optional name rendering

Hi, great job with Kosmos, it's really a useful program! Then, I'd like to ask you, since I haven't found any reference online if it's possible in the rendering rules to render a second tag as a name only if it does exist. Something like: TagToUse=name:fur, IF EXIST loc_name ADD (loc_name) This could possibly be useful also for places like Greece, in order to render a name both in Greek and Latin alphabet. In the rendering rules page I've seen optional expression only for element selectors, not for this purpose. Thanks for your help.--Klenje 15:44, 24 September 2009 (UTC)

Hi, well currently the expressions are quite simple, so you won't be able to achieve this. But I'm working hard on a new version and a more elaborate expression system is one the features I was planning to introduce. --Breki 07:46, 25 September 2009 (UTC)

Kosmos and roles rendering

Hi, i want to render Bus-relations with kosmos-tool and any nodes have a fwd/backwd role.. Is it possible to render it and how can I create the template in my Rules.. Thanks --ChrSchultz 07:52, 11 October 2009 (UTC)

Currently Kosmos' support for relations is a bit sketchy, so you won't be able to do this kind of rendering. I'm workin on improvements for the relation stuff and I hope to be able to release it soon. --Breki 04:47, 12 October 2009 (UTC)



First ,thanks for the GroundTruth tools ! I'm trying to generate a map as complete as possible, usable both for OSM scouting, but also usefull for hiking. Is the sometag=* syntax accepted and working ? I think I tried shop=* but some shops did not appear. Also, can I select unnamed objects with something like name=<none> (or maybe not name=*) ?

Thanks, Gnurf

shop=* in the rule selector should match all shops. As for "none", this is currently not possible, but it will be in Kosmos v3. --Breki 16:32, 31 October 2009 (UTC)
Thanks for your support. I was using shop=*, but now it's working with your syntax ! As for noname, setting: not name=* seems to match certain things (maybe too much).

Source code

Hi, on it says:

The source is licensed under the BSD license, which means you can do practically anything with the code

Could you clarify which specific BSD license? Thank you! logictheo 18:31, 22 November 2009 (UTC)

Hmmm are there any specific BSD licenses? :) The released source code comes with the license file, you can check it out --Breki 21:08, 23 November 2009 (UTC)

Maybe a bug on generating OSM contours

Hi, I downloaded and installed the last version (1.7.702.14), and run it under Debian Linux. I want to make contours of the Réunion ([1] Map of the Réunion). The line I wrote was

 ./ contours --int 10 --gridlat 2 --gridlon 2 --nocut -o ../../contours/reunion.ibf -b=-22,54,-20,57

It work very well, and downloaded the srtm without any problem, and made the IBF file (it take 1.8MB). To make the OSM contours to use with mkgmap, I wrote

 ./ ibf2osm --ibf ../../contours/reunion.ibf --od ../../contours/temp --of reunion0.osm --sid 2003000000 --tagce --cat=100,20

It made the job, and I have a file which is 28MB. But if I want to use this file, there are many problems. This is the beginning of the file:

 <?xml version="1.0" encoding="utf-8"?>
 <osm version="0.6" generator="GroundTruth">
       <node id="2004173768" visible="false" lat="57.663333333333334" lon="-19.999166666666667" />
       <node id="2004173769" visible="false" lat="57.663333333333334" lon="-19.999166666666667" />
       <node id="2004173770" visible="false" lat="57.664166666666667" lon="-19.999166666666667" />

It seems that it switched the lat with the lon

Another thing:

It claim that this is 0.6 API version. But, with this version, each node MUST have a version number, so, this is not 0.6 version, but 0.5 API version.

A correct version, with coordinates and 0.6 API version should be:

 <?xml version="1.0" encoding="utf-8"?>
 <osm version="0.6" generator="GroundTruth">
       <node id="2004173768" version="1" visible="false" lat="57.663333333333334" lon="-19.999166666666667" />
       <node id="2004173769" version="1" visible="false" lat="57.663333333333334" lon="-19.999166666666667" />
       <node id="2004173770" version="1" visible="false" lat="57.664166666666667" lon="-19.999166666666667" />

or change the <osm version="0.6" generator="GroundTruth"> to <osm version="0.5" generator="GroundTruth">

--Lolo 32 14:47, 15 January 2010 (UTC)

It most certainly is a bug (switching lat/lon), I'll try to fix it soon. As for the 0.6 version number: I want to avoid generating unnecessary text for these OSM files (since they are too hig anyway), and I think putting version="1" everywhere would be unnecessary. Do you have any problems with loading this file into other OSM software? --Breki 19:26, 18 January 2010 (UTC)
And here's the fix (hopefully ;) :
Yes, if you don't specify the version, osmosis can't use it with 0.6 version. I must load it with "--read-xml-0.5" command, and do a "--migrate" later.
If you specify the element version="1" with the node elements, do not forget to specify it with the way elements, because this is the same problem ;)
Last thing: why don't you compress the output file with gzip or bzip2 (standard tools from osm use it natively, and it take less space) --Lolo 32 16:09, 20 January 2010 (UTC)
Good point, I'll try to do that --Breki 20:11, 20 January 2010 (UTC)
Fixed: --Breki 21:33, 22 January 2010 (UTC)

Thank you very much

Thank you for your help with OSM in Dragash!

you great job 4 #OSM #Flossk in Dragash Kosovo. converted the #SRTM for the area into OSM format! -

Awesome work

Hi, I just want to let you know that its AWESOME what you did. I just learned how to make a Garmin MapSource installer from the maps, & looks great! I will be using your method for creating the routes across Canada. Thanks, Sam Vekemans Across Canada Trails--acrosscanadatrails 03:14, 1 March 2010 (UTC)

Thanks, I'm glad you like it :) --Breki 12:28, 1 March 2010 (UTC)

Charset problems

First of all: you did a great job!

I have been playing to make my own Garmin maps from OSM data. My primary intention was to make a ski map. I know publishes some prefab OpenPistemap img-files, but I wanted to make my own representation (adding some features interesting for me, but missing on the maps).

It took me a while to figure out why some POI's did not show a nice category icon in MapSource, even though I entered the Garmin type name in the type column of the rules.

After looking at the source code (hey, I have a development background, though not .NET), I understood how to fix it. I added some Garmin types to my rules file, and that worked. After I found out how it worked, I also finally understood the section about the Garmin types in the manual/command line help ;-)

Now, I still have a problem with accented characters. My OSM file (saved locally using data downloaded with JOSM) contains accented characters. It is correctly saved in UTF-8 (verified that with a hex editor). The sample character illustrating the issue is C389 ( This exact byte-sequence is present in my source osm-file (as a label for a line).

The generated temporary mp-file contains this exact same byte-sequence. No matter what I use as the codepage param for cGPSmapper, the result is always the same: the resulting img-file contains the same byte-sequence C389, but it still shows in MapSource as interpreted in win-1252 (LATIN CAPITAL LETTER A WITH TILDE followed by PER MILLE SIGN).

I tried the following settings for the codepage param:

  1. - (no codepage)
  2. 1252 (windows 1252)
  3. 65001 (utf-8)

The last option seems 'correct' to me: groundtruth generates mp-files with utf-8 encoding and instructs cgpsmapper to handle the mp-files as utf-8. However, MapSource does not agree :(

If I look at the mp-files generated by groundtruth with the codepage=65001 with the GpsMapEdit tool, the accented characters are shown correctly. The hex-editor also shows the exact C389-sequence.

Looking at the generated img-files with gmapedit, the codepage stored inside the generated img-files is 1252 for the last 2 options of the codepage parameter. So it seems that cgpsmapper is not able to work with codepage 65001 and falls back to a default value (1252 apparently). Apparently GroundTruth always saves mp-files in UTF-8 encoding (without BOM).

If my analysis so far is correct, I would like to suggest the following change:
Add an extra parameter to instruct GroundTruth to generate the intermediate mp-files in a specific charset/codepage. Or, alternatively, deduce this charset from a possible codepage-parameter (but that would be a backwards incompatible change).

Now, I realize this maybe a cGPSmapper problem. Maybe cGPSmapper is not able to handle utf-8 mp-files. Still, the suggested change would help as a work-around and also it would help for devices not able to handle multi-byte charsets.

By the way, I do realize that I could use the chartable command-line option to define replacement characters, but it would be nice to have working accented characters. --Remke 00:12, 6 February 2011 (UTC)

SRTM2OSM with Proxy

Ich habe den Code für mich leicht ergänzt um das Programm auch hinter einem Proxy mit Passwordabfrage verwenden zu können. Das könnte aber vielleicht auch in die "offizielle" Version aufgenommen werden.

In der Datei Srtm2Osm\Srtm2Osm\Srtm2OsmCommand.cs werden zunächst die Optionen ergänzt

   public enum Srtm2OsmCommandOption
       // ...

Dann wird in der Funktion ParseArgs() ergänzt

           options.AddOption(new ConsoleApplicationOption((int)Srtm2OsmCommandOption.ProxyUser, "proxyuser", 1));
           options.AddOption(new ConsoleApplicationOption((int)Srtm2OsmCommandOption.ProxyPassword, "proxypassword", 1));

und schließlich im darauffolgenden switch

               switch ((Srtm2OsmCommandOption)option.OptionId)
                   // ...
                   case Srtm2OsmCommandOption.ProxyUser:
                       Brejc.DemLibrary.InetHelper.User = option.Parameters [0];
                   case Srtm2OsmCommandOption.ProxyPassword:
                       Brejc.DemLibrary.InetHelper.Password = option.Parameters [0];

Die Klasse Brejc.DemLibrary.InetHelper habe als static-Klasse in die Datei Srtm2Osm\Brejc.DemLibrary\Srtm3Storage.cs eingefügt:

  public static class InetHelper {
     public static string User { get; set; }
     public static string Password { get; set; }
     public static void SetProxy(WebRequest request) {
        request.Proxy = System.Net.WebRequest.DefaultWebProxy;
        if (User != null && User.Length > 0) {
           IWebProxy pr = System.Net.WebRequest.GetSystemWebProxy();
           pr.Credentials = new NetworkCredential(User, Password);
           request.Proxy = pr;

Und damit das ganze auch zur Wirkung kommt wurde in Srtm2Osm\Brejc.DemLibrary\SrtmIndex.cs in der Funktion Generate() zwischen WebRequest und WebResponse eine Zeile eingefügt

               WebRequest request = WebRequest.Create(new System.Uri(url));
               InetHelper.SetProxy(request);                                  // <== new
               WebResponse response = (HttpWebResponse) request.GetResponse();

Problem with Version 0.5

A very simple hack to convert the SRT2OSM-output from Version 0.5 to 0.6 is a little Perl-Code:

while (<STDIN>) {
  s/<osm version=\"0\.5\"/<osm version=\"0\.6\"/;
  s/<node /<node version=\"1\" /;
  s/<way /<way version=\"1\" /;

That insert the version-attribute in nodes and ways. At a second step i use osmosis:

osmosis --read-xml enableDateParsing=no perloutput.osm --sort --wx v06.osm

Are Kosmos Rules still useful?

This wiki has a lot of links to Kosmos_rules. Kosmos is outdated now. But are its rules still useful for Maperitive or could those category links be removed? --Hb 12:58, 19 May 2015 (UTC)

Yes, Kosmos is obsolete, so the rules are obsolete, too. You can remove the category links --Breki (talk) 18:37, 19 May 2015 (UTC)

dead link

FYI, went dead Mateusz Konieczny (talk) 09:49, 24 June 2018 (UTC)

Update to version v0.7.55

Just to clarify, I tested the entire procedure with the updated version and It worked perfectly. Thanks again for your excellent guide.