[mkgmap-dev] Missing cities in mapsource search entry field

Thu Jan 28 14:57:24 GMT 2010

Hi Steve,

> > For example, if I type 'm' it shows a list of names and the first entry
> > is 'Mod Abbey Wood' and the next entry is 'Mabe' which can't be right
> > if they are meant to be in alphabetic order. If you then type 'o' it
> > shows a list of names with the 'mo' prefix but, interestingly 'mod
> > abbey wood' isn't among them. So that's weird. If you type 'a'
> > after the 'm', it goes bong and you don't get any names. It's as if the
> > 'mod abbey wood' is in the wrong position in the list?
> 
> I don't get any of this wierdness and I just tried again after the 
> recent check-in-fest.
> 
> Thats the sort of thing that happens however if your index files are not 
> generated from the exact same .img files in the map, like your
> first Baltic map you posted.

Yes, at some point in the Baltic map work, I turned off index
generation and so it was using a previous index. Fair enough, but with
the UK map I am sure the index is being generated from the right files.

This is the command line:

java -Xmx2000m -Dlog.config=/home/markb/OSM/logging.properties -ea -jar /home/markb/OSM/mkgmap.jar --adjust-turn-headings --country-abbr=GBR --country-name=GBR --code-page=1250 --check-roundabouts --check-roundabout-flares --description=A fine map --draw-priority=28 --family-id=909 --family-name=Burto Maps --gmapsupp --generate-sea=polygons,no-sea-sectors,close-gaps=2000 --ignore-maxspeeds --index --latin1 --link-pois-to-ways --make-all-cycleways --max-jobs=1 --nsis --product-id=6324 --region-abbr=UK --remove-bogus-nodes --report-dead-ends=2 --region-name=UK --route --remove-short-arcs --series-name=OSM map --style-file=/home/markb/OSM/mkgmap-burto-style --tdbfile -c template.args /home/markb/OSM/M000038d.TYP

and template.args is:

mapname: 63240001
description: IE-Cork
input-file: 63240001.osm.gz

mapname: 63240002
description: GB-Plymouth
input-file: 63240002.osm.gz

mapname: 63240003
description: GB-Cardiff
input-file: 63240003.osm.gz

mapname: 63240004
description: GB-Southampton
input-file: 63240004.osm.gz

mapname: 63240005
description: GB-Bristol
input-file: 63240005.osm.gz

mapname: 63240006
description: GB-Wolverhampton
input-file: 63240006.osm.gz

mapname: 63240007
description: GB-Birmingham
input-file: 63240007.osm.gz

mapname: 63240008
description: GB-Portsmouth
input-file: 63240008.osm.gz

mapname: 63240009
description: GB-Reading
input-file: 63240009.osm.gz

mapname: 63240010
description: GB-Slough
input-file: 63240010.osm.gz

mapname: 63240011
description: GB-London
input-file: 63240011.osm.gz

mapname: 63240012
description: GB-Southend-on-Sea
input-file: 63240012.osm.gz

mapname: 63240013
description: GB-Luton
input-file: 63240013.osm.gz

mapname: 63240014
description: GB-Leicester
input-file: 63240014.osm.gz

mapname: 63240015
description: GB-Cambridge
input-file: 63240015.osm.gz

mapname: 63240016
description: GB-Norwich
input-file: 63240016.osm.gz

mapname: 63240017
description: IE-Dublin
input-file: 63240017.osm.gz

mapname: 63240018
description: GB-Stoke-on-Trent
input-file: 63240018.osm.gz

mapname: 63240019
description: GB-Liverpool
input-file: 63240019.osm.gz

mapname: 63240020
description: GB-Preston
input-file: 63240020.osm.gz

mapname: 63240021
description: GB-Sheffield
input-file: 63240021.osm.gz

mapname: 63240022
description: GB-Leeds
input-file: 63240022.osm.gz

mapname: 63240023
description: GB-Nottingham
input-file: 63240023.osm.gz

mapname: 63240024
description: GB-Kingston upon Hull
input-file: 63240024.osm.gz

mapname: 63240025
description: GB-Glasgow
input-file: 63240025.osm.gz

mapname: 63240026
description: GB-Newcastle upon Tyne
input-file: 63240026.osm.gz

mapname: 63240027
description: GB-Fort William
input-file: 63240027.osm.gz

mapname: 63240028
description: GB-Aberdeen
input-file: 63240028.osm.gz

----------

Its generating the .img files and the index all in one run - is that OK?

Cheers,

Mark