[PATCH] some natural points
Some natural=* POI values were missing from the translation. On the Edge 705, natural=wood will be displayed with an icon. That would be useful for marking the names of forest areas in cities. The other two (natural=rock, natural=water) will be displayed as hollow white circles by the Edge 705. The attribute natural=rock is not listed at http://wiki.openstreetmap.org/wiki/Key:natural, but I thought that it would be OK to mark large rocks (diameter over 1 m) as natural=rock. Please apply the attached patch. On a related note, when I tested this, I originally downloaded a small area and tried to create a map. The map was blank when zoomed at anything closer than 80 m. No tooltips were presented for any roads or POIs, and the Edge 705 complained something about no POI information being available. The bounding box of the download was as follows: minlat='60.3461917134347' minlon='25.0977978880827' maxlat='60.3564969730713' maxlon='25.1192281119173' Surprisingly, routing worked, even though the map was blank at closer zoom levels (tested 20 to 50 m). Ultimately, I edited a 180MB *.osm map tile in a text editor and changed some attributes there. When compiled, that map tile was displayed OK. Regards, Marko
On Sat, Jun 20, 2009 at 11:23:16PM +0300, Marko Mäkelä wrote:
Some natural=* POI values were missing from the translation. On the Edge 705, natural=wood will be displayed with an icon. That would be useful for marking the names of forest areas in cities.
The other two (natural=rock, natural=water) will be displayed as hollow white circles by the Edge 705. The attribute natural=rock is not listed at http://wiki.openstreetmap.org/wiki/Key:natural, but I thought that it would be OK to mark large rocks (diameter over 1 m) as natural=rock.
It turns out that unnamed natural=rock are called “kari” in the Finnish pop-up label, which means a rock that is submerged in water (dangerous for boats). I don't think that it is a grave mistake, though. I played with test-map:all-elements today. I set the environment variables BASE_LAT and BASE_LONG to my location, because the one close to London was too far for the “Find Places” menu to list any items. The result of my findings is in the attached patch. I also modified or added some translations in the points file. I'm not sure if this rule is syntactically correct, and I didn't test it: amenity=fuel & fuel:HGV_diesel=yes [ 0x2f16 resolution 19 ] This would be the third type of a fuel station, displayed with a truck icon. The patch also moves shop=bicycle to Other/Repair Services category, to differentiate it from shop=organic, which remains in Shops/Speciality Retail. Also hairdressers and beauty salons will be in the Other/Personal Service menu. Both are rendered as hollow white rectangles by the Edge 705. There are many “other“ shops, restaurants and lodgings. I believe that these codes are useful in connection with custom TYP files, which can override the label “Other“. The “other-all” entries seem less useful: the Edge 705 only displays them in the “All Categories” listing together with the combined contents of all submenus. The code 0x2f14 (social-service) would seem useful for things like amenity=prison, amenity=shelter or amenity=vending_machine, but unfortunately the Finnish translation is calling it “social welfare office”. Again, this could be addressed with a custom TYP file. Please apply the patch, at least to garmin_feature_list.csv. I wonder if mkgmap could include a TYP file in the style definition. Conceptually, the TYP file goes hand-in-hand with point and line translations. It could be a nicer (multi-lingual) solution to things like default_name. One more thing: while playing with test-map:all-elements, I noticed that there are numerous symbols that are probably meant for motorway exits. When I hovered or clicked on them, the pop-up window would show a different set of icons, such as a bed, fuel station, ellipsis (…). I did not try to find any pattern, as I am not that interested in amenities for motorists. Best regards, Marko
On Wed, Jun 24, 2009 at 01:07:40AM +0300, Marko Mäkelä wrote:
I'm not sure if this rule is syntactically correct, and I didn't test it:
amenity=fuel & fuel:HGV_diesel=yes [ 0x2f16 resolution 19 ]
This would be the third type of a fuel station, displayed with a truck icon.
Tested. I'd move this rule before amenity=fuel & shop=convenience, though, like this: amenity=fuel & fuel:HGV_diesel=yes [ 0x2f16 resolution 19 ] amenity=fuel & shop=* [ 0x2e06 resolution 19 ] amenity=fuel { name '${operator}: ${name}' | '${name}' | '${operator}' } [0x2f01 resolution 19 ] I'd also replace the shop=convenience with shop=*, as above. The Edge 705 displays 0x2f01 as a fuel pump, 0x2e06 as a fuel pump with a + inside, and 0x2f16 as a truck symbol. I think that we could use the + to indicate a manned fuel station. Marko
Hi Marko, I've started to compile a list of the behaviour of different GPS units with regard to POIs. As the different units handle the POIs differently it is important to have such a list, because what displays on your GPS unit just fine might be invisible on a different unit. For now I added the information about the Oregon 300 and partly about the nüvi 255W. It would be great if you could add your findings about the Edge. You'll find the list at http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/POI_Types Regards Thilo
Hi Thilo,
I've started to compile a list of the behaviour of different GPS units with regard to POIs. As the different units handle the POIs differently it is important to have such a list, because what displays on your GPS unit just fine might be invisible on a different unit. For now I added the information about the Oregon 300 and partly about the nüvi 255W. It would be great if you could add your findings about the Edge. You'll find the list at
http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/POI_Types
Thanks, I added an empty column for the Edge 605/705, firmware 2.80. It should be the same as 2.60, which I previously used (2.70 routinely corrupted saved tracks). I will fill in the data some time after Wednesday. Marko
Hi, Here's an updated version of this patch in case anybody is using it. Cheers, Ben On 06/20/2009 04:23 PM, Marko Mäkelä wrote:
Some natural=* POI values were missing from the translation. On the Edge 705, natural=wood will be displayed with an icon. That would be useful for marking the names of forest areas in cities.
The other two (natural=rock, natural=water) will be displayed as hollow white circles by the Edge 705. The attribute natural=rock is not listed at http://wiki.openstreetmap.org/wiki/Key:natural, but I thought that it would be OK to mark large rocks (diameter over 1 m) as natural=rock.
Please apply the attached patch.
On a related note, when I tested this, I originally downloaded a small area and tried to create a map. The map was blank when zoomed at anything closer than 80 m. No tooltips were presented for any roads or POIs, and the Edge 705 complained something about no POI information being available. The bounding box of the download was as follows:
minlat='60.3461917134347' minlon='25.0977978880827' maxlat='60.3564969730713' maxlon='25.1192281119173'
Surprisingly, routing worked, even though the map was blank at closer zoom levels (tested 20 to 50 m).
Ultimately, I edited a 180MB *.osm map tile in a text editor and changed some attributes there. When compiled, that map tile was displayed OK.
Regards,
Marko
------------------------------------------------------------------------
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Marko, I meant to reply to your message entitled '[PATCH] Find Places items from test-map:all-elements' for this patch update. Sorry for the confusion everybody. Cheers, Ben On Sat, Jul 11, 2009 at 12:48 AM, Ben Konrath<ben@bagu.org> wrote:
Hi,
Here's an updated version of this patch in case anybody is using it.
Cheers, Ben
On 06/20/2009 04:23 PM, Marko Mäkelä wrote:
Some natural=* POI values were missing from the translation. On the Edge 705, natural=wood will be displayed with an icon. That would be useful for marking the names of forest areas in cities.
The other two (natural=rock, natural=water) will be displayed as hollow white circles by the Edge 705. The attribute natural=rock is not listed at http://wiki.openstreetmap.org/wiki/Key:natural, but I thought that it would be OK to mark large rocks (diameter over 1 m) as natural=rock.
Please apply the attached patch.
On a related note, when I tested this, I originally downloaded a small area and tried to create a map. The map was blank when zoomed at anything closer than 80 m. No tooltips were presented for any roads or POIs, and the Edge 705 complained something about no POI information being available. The bounding box of the download was as follows:
minlat='60.3461917134347' minlon='25.0977978880827' maxlat='60.3564969730713' maxlon='25.1192281119173'
Surprisingly, routing worked, even though the map was blank at closer zoom levels (tested 20 to 50 m).
Ultimately, I edited a 180MB *.osm map tile in a text editor and changed some attributes there. When compiled, that map tile was displayed OK.
Regards,
Marko
------------------------------------------------------------------------
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Sat, Jul 11, 2009 at 12:52:10AM -0400, Ben Konrath wrote:
I meant to reply to your message entitled '[PATCH] Find Places items from test-map:all-elements' for this patch update. Sorry for the confusion everybody.
Thanks, Ben. I have used the patch for compiling the map of Finland <http://www.polkupyoraily.net/osm/> a couple of times. But I haven't tested (or heard from anyone testing) the patch on anything else than the Edge 705. I promise to look at your patch and revise http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/POI_Types some time next week. (Vacation is busy time when you have small children. Yesterday I was at least able to combine fun and "work" by making a 30km mapping trip with my kids on the family bicycle.) Marko
Hi Ben, I compared your patch to mine. I only noticed two differences: First, in my patch, truck stops have precedence over manned fuel stations (to make the map more useful to truck drivers): +amenity=fuel & fuel:HGV_diesel=yes [ 0x2f16 resolution 19 ] amenity=fuel & shop=convenience [ 0x2e06 resolution 19 ] I may have posted an initial version of the patch where this was not the case. Second, in my patch, natural=rock is added before natural=spring, not after it. It is a cosmetic thing (maintaining alphabetical order). Did you perhaps post the wrong patch? Marko
Hi Marko, I have applied your patch from Ben's updated patch and made your changes. Hope that is all correct, could you check please. Thanks, ..Steve
I compared your patch to mine. I only noticed two differences:
First, in my patch, truck stops have precedence over manned fuel stations (to make the map more useful to truck drivers):
+amenity=fuel & fuel:HGV_diesel=yes [ 0x2f16 resolution 19 ] amenity=fuel & shop=convenience [ 0x2e06 resolution 19 ]
I may have posted an initial version of the patch where this was not the case.
Second, in my patch, natural=rock is added before natural=spring, not after it. It is a cosmetic thing (maintaining alphabetical order).
Hi Steve,
I have applied your patch from Ben's updated patch and made your changes. Hope that is all correct, could you check please.
It merged with zero conflicts, no diff. Only this diff remains, in resources/styles/default/lines (I sent it a couple of days ago): +railway=platform {add access = no; add foot = yes} [0x16 road_class=0 road_speed=0 resolution 23] Maybe it would be better to write action rules to explicitly map railway=platform to highway=footway. Sorry, I was too lazy to learn how. Best regards, Marko
Hi Marko, On Sat, Jul 11, 2009 at 1:41 AM, Marko Mäkelä<marko.makela@iki.fi> wrote:
Hi Ben,
I compared your patch to mine. I only noticed two differences:
First, in my patch, truck stops have precedence over manned fuel stations (to make the map more useful to truck drivers):
+amenity=fuel & fuel:HGV_diesel=yes [ 0x2f16 resolution 19 ] amenity=fuel & shop=convenience [ 0x2e06 resolution 19 ]
I may have posted an initial version of the patch where this was not the case.
Second, in my patch, natural=rock is added before natural=spring, not after it. It is a cosmetic thing (maintaining alphabetical order).
Did you perhaps post the wrong patch?
I may have made a mistake here. Thanks for looking at the patch and catching the error. Cheers, Ben
participants (4)
-
Ben Konrath -
Marko Mäkelä -
Steve Ratcliffe -
Thilo Hannemann