February 2011 - mkgmap-dev - The mkgmap lists

delete and replace is_in:country tags
by maning sambale 16 Feb '11

16 Feb '11

How do I do this within the style file? For the points, I tried this one: *=* {delete is_in:country=disputed territory} place=* {add is_in:country=Philippines} But I keep getting "disputed territory" for all my search results (POI and streets) I also get "Indonesia" in some streets Is this related to the location-autofill=1 switch? -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 4

Another failure with downloading filrs
by Steve Ratcliffe 15 Feb '11

15 Feb '11

Hi I've just got to let you all know that I've had another failure to download two adjacent tiles. So all is not fixed yet. I was looking into the umlaut problem - to confirm : the problems are only on a device and not seen in map source? ..Steve

2 1

which city hexcode are searcheable with city search and as POI
by maning sambale 15 Feb '11

15 Feb '11

I would like to know which of the city codes are: 1. Used in the city indexing 2. Used in the POI searching The cgpmapper manual has the following lists: N 0x0100-0x0500 256-1280 1-5 City name (Point, fat, big) N 0x0600-0x0A00 1536-2560 6-10 City name (Point, big) N 0x0B00 2816 11 City name (Point, small) N 0x0C00 3072 12 City name (Point, small) N 0x0D00 3328 13 City name (Point, small) N 0x0E00-0x1100 3584-4352 14-17 City name (Point, big) Why? The city search for very minor places like hamlets and village clutter the list. Although city search is now enabled, I can't use the the "Spell City" feature, instead, I have to browse through the very long list. I'm thinking of assigning hamlets and village as POI instead of the city searching index. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

1 0

mkgmap_svn_index mdr compile error on Finland
by Felix Hartmann 15 Feb '11

15 Feb '11

When I try to compile Finland (I think this has been already happening since around rev 1835) I get the following error - If I noticed right this happens on the mdr creation - maps compile fine beforehand: I don't think it was reported yet - that's why I send it out here. (similar error happens on some German Bundeslaender - however Germany as a whole compiles fine). This is compiling the Finland osm.pbf extract from Geofabrik. Can you get the same error or do I need to provide some more info? Exception in thread "main" java.lang.AssertionError at uk.me.parabola.mkgmap.combiners.MdrBuilder.addStreets(MdrBuilder.java:310) at uk.me.parabola.mkgmap.combiners.MdrBuilder.onMapEnd(MdrBuilder.java:171) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:411) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:126) at uk.me.parabola.mkgmap.main.Main.main(Main.java:129)

3 5

Need a coordinate or way ID in coastline warnings
by Marko Mäkelä 14 Feb '11

14 Feb '11

Hi WanMil, I got a mystery coastline error that I am unable to fix, because I fail to see any inverted sea and land on the map. It would be very helpful if these messages mentioned the original way IDs or just a map coordinate of the whereabouts of the error. Best regards, Marko 2011/02/13 11:16:31 WARNING (MultiPolygonRelation): 63240006.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427479706 contains errods. 2011/02/13 11:16:31 WARNING (MultiPolygonRelation): 63240006.osm.gz: Polygon 4611686018427486359(8P)(4611686018427482944[8P]) carries role inner but lies inside an inner polygon. Potentially its role should be outer. 2011/02/13 11:16:31 WARNING (MultiPolygonRelation): 63240006.osm.gz: Polygon 4611686018427486368(13P)(4611686018427482953[13P]) carries role inner but lies inside an inner polygon. Potentially its role should be outer.

2 3

mkgmap_svn_index: sending one tile always works, several tiles sometimes
by Felix Hartmann 14 Feb '11

14 Feb '11

Basically the subject title says everything. For some tiles I can up to 4-5 tiles and sending to gps with Basecamp/Mapsource works. Other tiles however only transfer if one sends them as single tile. Anyone found out a reason? It seems to be independant of the maxnodes value (usually I use 1200000 but also 550000 failed). The same regions as before seem to cause the problems. So I think it must be dependant on some (missing?) data that causes the problem.

3 6

place/city search question(Re: Index branch - success!)
by maning sambale 14 Feb '11

14 Feb '11

In our country, places and cities are usually under this hierarchy: village, city, province, region, country I have the following in my point style: # add is_in tags if there is one place=city {name '${name}, ${is_in:state}' | '${name}'} [0x0400 resolution 16] place=hamlet [0x0d00 resolution 23] place=locality [0x0d00 resolution 23] place=subdivision [0x0d00 resolution 23] place=suburb [0x0d00 resolution 23] place=town {name '${name}, ${is_in:state}' | '${name}'} [0x0800 resolution 18] place=village {name '${name}, ${is_in:town}, ${is_in:state}' | '${name}, ${is_in:town}' | '${name}, ${is_in:state}' | '${name}'} [0x0c00 resolution 21] place=purok [0x0d00 resolution 23] When using the new street search (basecamp and nuvi), I get different result when doing: street near village street near city The street is located on the village within the city. I also get this "Disputed Territory" when you click the details of the search results. Is this a data problem? Great work on the index btw! On Mon, Feb 14, 2011 at 10:00 AM, maning sambale <emmanuel.sambale(a)gmail.com> wrote: > My report using mkgmap-index-r1850.jar. > > Args file: > > code-page=1252 > tdbfile > latin1 > country-abbr=PHL > country-name=PHILIPPINES > remove-short-arcs=5 > route > add-pois-to-areas > family-id=639 > family-name=OSM_PHIL > overview-mapname=40000001 > series-name=OSM_PHIL > description=OSM_PHIL > generate-sea=polygons,extend-sea-sectors,close-gaps=1000 > index > make-poi-index > adjust-turn-headings > drive-on-right > report-dead-ends > ignore-maxspeeds > link-pois-to-ways > > > - Loading the map to basecamp and roadtrip - no crash > - loading the map to nuvi 1310 using map install - no crash > - using the Where to - Address - working! > - I see two countries in the "Select Country" (Disputed Territory and > Ph) - what do we mean by disputed territory? > I can search for streets under the "Disputed Category" but not in "Ph" > > I'm using the default style for now. Will report back using my own > style. Great work! > > On Sun, Feb 13, 2011 at 4:45 AM, Chris66 <chris66nrw(a)gmx.de> wrote: >> Am 12.02.2011 15:08, schrieb Henning Scholland: >> >>>> Now when I find for addresses on my Legend HCX, I can choose >>>> between region "Deutschland" and region "Germany". >>>> [...] >>>> I used location-autofill=1 and >>>> --country-name=germany >>>> --country-abbr=DE >>>> --area-name=DE >> >> when I change this to >> --country-name=Deutschland >> --country-abbr=DEU >> --area-name=DEU >> then only region "Deutschland" is available and this is choosen >> automatically in the address-find page. >> >>>> For region Deutschland I have to enter "LÜ" to find >>>> cities starting with "Lü" but for Region Germany I >>>> have to enter "LU" to find cities starting with "Lü". >> >>> did you use --code-page//=1252? This should fix the problem with >>> umlauts. >> >> I used -latin1 but when I change to codepage/charset 1252 there is no >> difference. >> >> So, searching cities with "LÜ" now gives: >> >> Lünen, Kreis Unna >> Lünen-Süd, DEU >> >> and looking for "LU" gives: >> >> Lüdinghausen, Kreis Coesfeld >> Lünen, Kreis Unna >> Lünen-Süd, DEU >> >> Very funny. >> >> Another question: >> >> Searching for housenumbers is not yet possible? >> >> Chris >> >> _______________________________________________ >> mkgmap-dev mailing list >> mkgmap-dev(a)lists.mkgmap.org.uk >> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >> > > > > -- > cheers, > maning > ------------------------------------------------------ > "Freedom is still the most radical idea of all" -N.Branden > wiki: http://esambale.wikispaces.com/ > blog: http://epsg4253.wordpress.com/ > ------------------------------------------------------ > -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

1 0

splitter and long way-segments
by Henning Scholland 12 Feb '11

12 Feb '11

Hi everyone I've a problem with ways with long segments (e.g. boarders or ferry-lines) and splitter. These ways gets broken, because the nodes are to far away from splitoffset. I've made a screenshot [1] for explanation. Increasing the splitter-offset wont be a good idea, because tiles will become to big. Also I wont add additional nodes in osm-data, because this only will solve the problem only for one map. Are there any other opportunities for fixing this problem and keep routing on ferry-lines alife? Henning [1] http://www.aighes.de/data/example.png

4 4

coastlinefile option
by Tomas Straupis 12 Feb '11

12 Feb '11

Hello I'm trying to use a separate file with natural=coastline information. I then provide it to mkgmap using option: --coastlinefile=lithuania_coast.osm But I get this when executing: SEVERE (CoastlineFileLoader): lithuania_.osm: java.lang.UnsupportedOperationException java.lang.UnsupportedOperationException at java.util.AbstractCollection.add(AbstractCollection.java:238) at java.util.AbstractCollection.addAll(AbstractCollection.java:322) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.createConverter(OsmMapDataSource.java:251) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.setupHandler(OsmMapDataSource.java:131) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5MapDataSource.load(Osm5MapDataSource.java:69) at uk.me.parabola.mkgmap.reader.osm.CoastlineFileLoader.loadFromFile(CoastlineFileLoader.java:90) at uk.me.parabola.mkgmap.reader.osm.CoastlineFileLoader.loadFile(CoastlineFileLoader.java:119) at uk.me.parabola.mkgmap.reader.osm.CoastlineFileLoader.loadCoastlinesImpl(CoastlineFileLoader.java:133) at uk.me.parabola.mkgmap.reader.osm.CoastlineFileLoader.loadCoastlines(CoastlineFileLoader.java:79) at uk.me.parabola.mkgmap.reader.osm.SeaGenerator.init(SeaGenerator.java:135) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.pluginChain(OsmMapDataSource.java:158) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.setupHandler(OsmMapDataSource.java:126) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5MapDataSource.load(Osm5MapDataSource.java:69) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:145) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:220) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:217) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) I tried creating coastline file using JOSM. Then I tried modifying this file (removing elements with action="delete" etc.). The last thing I've tried was to provide the full data osm file (the one used to generate a map) as natural coastline just to check that file format is OK, but I was still getting the same error... Full command line when creating a map: java -jar mkgmap.jar \ --style-file=/home/tomas/garmin/tomas_style \ --gmapsupp \ --tdbfile \ --family-name=OpenStreetMap \ --description=Lietuva`date +%Y%m%d` \ --country-name=Lithuania \ --country-abbr=LTU \ --preserve-element-order \ --lower-case \ --charset=windows-1257 \ --route \ --add-pois-to-areas \ --generate-sea=multipolygon \ --coastlinefile=lithuania_.osm \ lithuania_.osm What am I doing wrong? What should the format of this coastline file be? Thank you P.S. This is using rev1838. -- Tomas Straupis

2 1

Commit: r1846: Fixing UnsupportedOperationException when using the coastlinefile option
by svn commit 12 Feb '11

12 Feb '11

Version 1846 was commited by wanmil on 2011-02-12 10:00:36 +0000 (Sat, 12 Feb 2011) Fixing UnsupportedOperationException when using the coastlinefile option

1 0