Completely missed that.
I do not understand that you still use those rectangle polygons (of cloudmate?).
Why not use real boundary polygons? Like here for Brazil:
Simple answer: because I haven’t found better ones 
Tell me, where are they from?
Anyway, it doesn’t matter anymore (perhaps the might help the processing speed, but not to the final result).
Is there any way Thai can be transliterated? Borders, etc. around there look hideous right now.
Thanks,
Peter.
As far as I know there are no simple rules and many exceptions. Even the “official” tool Chulalongkorn University: Thai Romanization Program is far from being perfect. The method of romanization is changing and even the authorities don’t follow them. Thus you can get different versions from the tool and the sign at the street. In another country there are other rules. Thus the map generation program ought to follow the exact border. I guess currently not doable.
I think the best way is to tag “name” and “name:en”. Where this is done a convenient bilingual map can be created, e.g. in Khon Kaen and the map is still useable if there’s only the local Thai name for some places given, e.g. at Chatuchak. A navigation program can offer switching the map between English and local Thai language, e.g. as Mapfactor Navigator Free does.
I startet using the “Worldwide routable Garmin map” of Thailand not long ago and I like it more and more. As I see it is using name:en, name. This is fine where name:en is given. But where there’s only name in Thai letters I see strange words in roman letters. I don’t know why. Get they converted during the map generation or are non Thai Garmin devices and programs not able to display Thai letters?
Many thanks to Lambertus and the other contributors
Willi
This service has a nice trick up it’s sleeve which -afaik- other OSM Garmin map providers don’t have, namely the addition of a custom transliteration application created by user Greencaps. This transliteration apparently works quite well for e.g. Slavic languages but frankly I don’t know how well it performs for other countries, so I’ll leave the more detailed answers to Greencaps…
And, yes, the way preference is given to OSM English and international names over transliterated and finally a fallback to the OSM name does help a little too.
Well you saw only one… I wrote a program which given the relation id of a country’s border downloads recursivly all containing relations and ways and finally the nodes. Then the individual ways often have to be sorted and some reversed to make it a nice closed loop boundary which I save as a .gpx file. Much later I discovered http://ra.osmsurround.org/analyze.jsp?relationId= which can analyse relations when given a relation id. At the end it offers a download possibility of the ‘border’ as gpx file.
Having these possibilities the bunch of work is to determine -by hand- the relation id’s of the borders.
Yes. Translit could do that too I think. But as I don’t know anything of Thai I did not even start. When there are many ways Thai can be transliterated (as Willi2006 said) then we could still choose one. If you are willing to help me to make a translitertation table then I will make a webpage wilth a Thai alfabet where you can fill in the transliteration (in the english way).
That is very well doable. As you can read in http://forum.openstreetmap.org/viewtopic.php?id=5554 translit was first designed to use country borders for the different languages. But then ‘I found out’ that country borders were not needed as every language occupied its own set of utf-8 characters. I think I can put in some thai-states-borders again. (I said I think. Did not see the code for quite some time now.)
I wish I could help you there, but I don’t read or understand Thai. I had a quick look at the transliteration table on the uni website (following Will’s link), but it looks very complicated.
Interestingly, the maps I compile myself strip out all Thai names in the name field, except for borders. Your maps show labels with long strings of gibberish. I guess we can conclude from that that Garmin MS and devices don’t display Thai characters, except for localised units, of course.
I guess the best thing to do would be for mappers (like myself) to run all Thai-only names through something like Google translate and then create then name:en field. Or should that be name:int?
Can anything be done about the borders?
SW of Yala the border is a complicated looking web of relations and multi-polygons. It’s interesting to note that the name for Malaysia can’t even be displayed in JOSM (it shows as a bunch of squares, this is the result of a copy and paste: မလေးရှားနိုင်ငံ), although Malaysia uses the roman script. I think this is an error.
The name field for the border line itself is Border Thailand - Malaysia, so I don’t know where mkgmap takes all the gibberish from.
Regards,
Peter.
I request for a routable Garmin map from garmin.na1400.info for Hokkaido Island and downloaded from:
<http://planetosm.oxilion.nl/~lambertus/garmin/routable/12-02-2011/27ae955bac04d1fcb5153f0e39f68230>
I found that the eastern part of the Island is not included.
Before this, I downloaded the whole of Japan and the Eastern part of Hokkaido Island was also missing. Any reason?
Will be visiting Hokkaido soon.
This looks more like a font that does not support Malaisian characters. It’s not a ‘i do not understand unicode’ issue. If you could force JOSM to use a different font? Or download the malaisian graphics for the used font?
Could you give an osm link to the island exactly on the line from where on there is no data?
Are you sure the tile from the eastern part was included in ‘your order’?
With all due respect, I think Greencaps is ‘on the problem’ here. I just ordered the same region (albeit a newer map version, but that should have no effect) using my admin super powers to get a quick turnaround time and it works just fine. See the Hokkaido island here or all of Japan here.
Downloaded both Hokkaido and Japan maps, both works fine. Thanks.
You seem to have missed an important part of my post:
There are no Malaysian characters, fonts or scripts. They use the same writing as you and I. This looks like a data error to me, so I just went ahead and corrected it.
I still don’t understand why mkgmap takes the name of the border from relations, rather than the name of the border line itself, but as I don’t understand what these relations do anyway there is no point in me asking on their mailing list. When I upload corrections to this border JOSM always throws a bunch of errors about unknown relation types and empty relations.
Regards,
Peter.
Hi,
These maps are a fantasitc service but I’m having some problems.
I’ve tried searing through the forums to see if others are having this same problem, but damn, this post is 35 pages long.
So, I’m trying to download France & Spain for an upcoming vacation but the maps seem to have missing tiles.
I’ve tried it a few different times, first by selecting the country from the drop-down lists, and then by selecting the tiles manually, but each times there are missing tiles - but not neccesarily the same ones.
Also, for a given download, both the gmapsupp.img file & the mapsource installer have the same areas missing.
Am I doing something wrong? Its getting kinda frustrating as the queue is about a week long.
When was the last time you downloaded a map? I’ve changed the way tiles are matched against country definitions so there should be no missing tiles anymore. Also, I’ve not seen any clear example where the site showed a selected tile while the result did not contain it. So I’ve requested France and Spain. I a few hours we’ll know…
The first bit can be explained by the different updates on the site. The second one scares me a bit 
That is what I would expect, otherwise things would have become spooky.
Edit: I’ve checked France & Spain and both are fine as far as I can see.
Sorry. I ment Thai characters.
And indeed I missed the point where you switched from Thai to Malaisian and did not pay attention to ‘using the same characters’. My brain just drops info… Sorry for the confusion.
There is no border line itself (well if there is please name it). There are border lines. Those are ways. Every way describes only a part of the border.
The relation with id 49865 describes the border of Thailand by summarising all the 's that constitute the border.
http://api.openstreetmap.org/api/0.6/relation/49865
http://www.openstreetmap.org/browse/relation/49865
http://www.openstreetmap.org/?relation=49865 (you have to wait long before the border is drawn)
Exciting new development: someone offered me to host the project on his beefy server. Hopefully this means there soon will be and end to long waiting queues (and perhaps some new features as well) 
Beefy server = big/fast server
It’s a quad-core with 8GB ram and 100MBit internet connection. It’s in the stage of getting it ready (i.e. install the necessary software). I don’t know how much disk space is available for the Garmin maps but it’s certainly much more then what’s available now. I might even use both machines to process and store the Garmin maps.
Any suggestions on how to find the culprit for routing errors? I had one happen today when I tried to route to a new geocache from work (I have successfully routed from work to other geocaches). Any advice on how to find the culprit is appreciated.
What king of errors exactly?
Which device or program did you use?
From where did you route?
To where did you route?
How to reproduce the error(s)?
Any link to your starting/finish position (OSM id’s perhaps) would help.
What version of the map are you using (i.e. when did you download the map)?
Did you try any of the webbased OSM routing applications like http://www.yournavigation.org?