Hello list, I tried the indexing stuff for the first time. It does work a little bit: it will find the location of streets if I select them from the list of all streets. However, I can't seem to search for streets or cities. Also, the country of all these is "country" and in the list of cities, there is an "ABC" behind the names - could that be a hard coded state name? (I suppose the above is just how it works now and nothing to worry about). Best regards, Valentijn
-----Original Message----- From: Valentijn Sessink [mailto:valentyn@blub.net] Sent: 05 November 2009 17:43 PM To: Development list for mkgmap Subject: [mkgmap-dev] indexing stuff Hello list, I tried the indexing stuff for the first time. It does work a little bit: it will find the location of streets if I select them from the list of all streets. However, I can't seem to search for streets or cities. Also, the country of all these is "country" and in the list of cities, there is an "ABC" behind the names - could that be a hard coded state name? (I suppose the above is just how it works now and nothing to worry about). Best regards, Valentijn ----------------------------- Hi Valentijn, No, I don't think this is just how it works now. I get the impression that some people has fully functional address search on their devices? Someone please confirm. For myself address search is still not available on the device. I have tried Felix' mtb maps of my area, and the problem remains. So I don't think my compiling methods (options used) is to blame. Possibilities are: 1) Not all devices can cope with --index. I use Nuvi200W, someone had exact same complain using Nuvi250 "Device asks for province/state and can't find any" Problem is that with the original Garmin map my device ask for country, and then city- never province 2) OSM input data insufficient. Maybe there is no address data in the file and that might be what is required? I see a lot of "fix my address" labels that I can't find in the OSM data, so might be generated by mkgmap? Or maybe I just can't find it. I deleted all is_in tags, but it had no effect, I added is_in tags- no effect. I deleted all is_in:state tags, but it had no effect, I added is_in:state tags- no effect. (same with is_in:province) 3) No-one else can get it to work on the device, and we're just assuming everyone else is happy, or maybe resigned? I believe "ABC" is mkgmap's default --country-abbr if you don't specify it. I am unsure whether "country" is mkgmap's default country-name? I am not complaining - All & all I am extremely happy with the work all these developers have done. So I can't search streets by address - so what - I am quite happy with -road-name-pois=0x2f15 for now. On the other hand I gladly share ny findings just to help development. BTW I found a style file work around to increase routing distance. Where my map's max was 1400km before I can now route up to 2200km, by simply upgrading the road-class of the major long distance connector roads. BennieD ##################################################################################### Scanned by MailMarshal - Marshal's comprehensive email content security solution. Download a free evaluation of MailMarshal at www.marshal.com #####################################################################################
On Fri, Nov 6, 2009 at 1:45 PM, Du Plessis, Bennie <Bennie.DuPlessis@sappi.com> wrote:
BTW I found a style file work around to increase routing distance.
Where my map’s max was 1400km before I can now route up to 2200km, by simply upgrading the road-class of the major long distance connector roads.
Would you be so kind as to share with us what you exactly did here? ;-) In terms of address search, I have used this successfully on my eTrex, but so far only in my local region. I think getting this to work depends on a lot of factors, such as your area, how you compile and install the map, and how you transfer it to your device. Most likely when this feature stabilizes, there will be better instructions on how to use it. Cheers.
-----Original Message----- From: Clinton Gladstone [mailto:clinton.gladstone@googlemail.com] Sent: 06 November 2009 14:56 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] indexing stuff On Fri, Nov 6, 2009 at 1:45 PM, Du Plessis, Bennie <Bennie.DuPlessis@sappi.com> wrote:
BTW I found a style file work around to increase routing distance.
Where my map's max was 1400km before I can now route up to 2200km, by simply
upgrading the road-class of the major long distance connector roads.
Would you be so kind as to share with us what you exactly did here? ;-) I added the following to the lines stylefile after the line highway=motorway {add oneway = yes; add bicycle = no; add foot = no } [0x01 road_class=4 road_speed=6 resolution 12] #handling specific long distance connector routes highway=trunk & (ref=N1|ref=N2|ref=N3|ref=N4) [0x02 road_class=4 road_speed=5 resolution 12] N routes in South Africa = national routes, but does not qualify to be motorways in OSM. Even so I want it to be visible at a high zoom level, specifically the N1 to N4, which is major long distance connector roads. I therefore started palying with the stylefile, and the intention was to increase the resolution, so that the line is visible earlier. I left the line type at 0x02 (trunk) to still have visual distinction betwn trunk & motorway. I also increased the road class, and speed by 1 each because it gives me slightly more realistic times (I think). Bad move to do all these changes at once, because one of them enabled my Nuvi to now route longer distances, I think it was the increase in road class. The improvement still only works if preference = faster route and not for Shorter route. In terms of address search, I have used this successfully on my eTrex, but so far only in my local region. I think getting this to work depends on a lot of factors, such as your area, how you compile and install the map, and how you transfer it to your device. Most likely when this feature stabilizes, there will be better instructions on how to use it. Hmm yeah, instructions... realy kind of vital for guys like me. I try to keep track of the forum, to have an idea, but with the zipped txt archives that doesn't work it becomes very cumbersome to catch tips that I've missed. How do I compile changes to help files to suggest for commitment? I see files, is it also called patches, with a lot of lines and symbols like @ @@ ++ -- + - at the start of each / some lines, sometimes number pairs that looks like coordinates? How does all this stuff work and what does each symbol mean? If I understand I can maybe help update the help files? Garmin Basemaps: Another interesting observation I've made: My Nuvi200 came with 2 maps: GmapSupp on SD card, and a basemap gmapbmap.img on the device itself, which I removed because my earlier OSM maps did not work with it. I've now put it back and found the following changed: My custom map is now selectable on the GPS, which failed before. The longer routing now also works for "shorter routes" preference. My OSM map is transparent and with draw priority 3, so I have an irritating basemap cluttering up my display. Next to do: Build a map with MyStyle for longer routing, and one with standard style, and test routing now on both maps with basemap installed Build my map with higher Draw Priority than basemap (I assume it will be 25, and will start at 26 and work gradualy down) and not transparent. See if I can build my own basemap. Groete BennieD ##################################################################################### Scanned by MailMarshal - Marshal's comprehensive email content security solution. Download a free evaluation of MailMarshal at www.marshal.com #####################################################################################
On Nov 9, 2009, at 8:27, Du Plessis, Bennie wrote:
BTW I found a style file work around to increase routing distance.
Where my map’s max was 1400km before I can now route up to 2200km, by simply upgrading the road-class of the major long distance connector roads.
I added the following to the lines stylefile after the line
highway=motorway {add oneway = yes; add bicycle = no; add foot = no } [0x01 road_class=4 road_speed=6 resolution 12]
#handling specific long distance connector routes highway=trunk & (ref=N1|ref=N2|ref=N3|ref=N4) [0x02 road_class=4 road_speed=5 resolution 12]
Thanks. I'll try this out. The cGPSMapper manual contains the following fairly obscure statement: ...it is important to prepare data with non broken road network keeping specific road class... This might be related to the reason for your longer routing distances. Cheers.
Clinton Gladstone wrote:
On Nov 9, 2009, at 8:27, Du Plessis, Bennie wrote:
BTW I found a style file work around to increase routing distance.
Where my map’s max was 1400km before I can now route up to 2200km, by simply upgrading the road-class of the major long distance connector roads.
I added the following to the lines stylefile after the line
highway=motorway {add oneway = yes; add bicycle = no; add foot = no } [0x01 road_class=4 road_speed=6 resolution 12]
*#handling specific long distance connector routes* *highway=trunk & (ref=N1|ref=N2|ref=N3|ref=N4) [0x02 road_class=4 road_speed=5 resolution 12]*
I would guess you would get even better routing using highway=motorway {add oneway = yes; add bicycle = no; add foot = no } [0x01 road_class=4 road_speed=7 resolution 12] *highway=trunk & (ref=N1|ref=N2|ref=N3|ref=N4) [0x02 road_class=4 road_speed=6 resolution 12] **highway=trunk [0x02 road_class=4 road_speed=5 resolution 12] I'ld actually go so far to put all road_class=4 and road_speed=7 - though then you're estimated arrival times will get a bit quick.. cGpsMapper manual should not be trusted regarding their proposals - best is trial and error but changing few variables at a time. *
Thanks. I'll try this out. The cGPSMapper manual contains the following fairly obscure statement:
...it is important to prepare data with non broken road network keeping specific road class...
This might be related to the reason for your longer routing distances.
Cheers. ------------------------------------------------------------------------
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Du Plessis, Bennie escribió:
-----Original Message----- From: Valentijn Sessink [mailto:valentyn@blub.net] Sent: 05 November 2009 17:43 PM To: Development list for mkgmap Subject: [mkgmap-dev] indexing stuff
Hello list,
I tried the indexing stuff for the first time. It does work a little
bit: it will find the location of streets if I select them from the list
of all streets. However, I can't seem to search for streets or cities.
Also, the country of all these is "country" and in the list of cities,
there is an "ABC" behind the names - could that be a hard coded state name?
(I suppose the above is just how it works now and nothing to worry about).
Best regards,
Valentijn
-----------------------------
Hi Valentijn,
No, I don't think this is just how it works now.
I get the impression that some people has fully functional address search on their devices? Someone please confirm.
For myself address search is still not available on the device.
I have tried Felix' mtb maps of my area, and the problem remains. So I don't think my compiling methods (options used) is to blame.
Possibilities are:
1) Not all devices can cope with -–index.
I use Nuvi200W, someone had exact same complain using Nuvi250 "Device asks for province/state and can't find any"
Similar in nuvi 300, but only asks for state
Problem is that with the original Garmin map my device ask for country, and then city- never province
2) OSM input data insufficient. Maybe there is no address data in the file and that might be what is required?
I see a lot of "fix my address" labels that I can't find in the OSM data, so might be generated by mkgmap?
Yes, that is added by mkgmap to all POI's lacking address information. It's just a message to the user to complete that information.
participants (5)
-
Carlos Dávila -
Clinton Gladstone -
Du Plessis, Bennie -
Felix Hartmann -
Valentijn Sessink