Sorry, I am a newbie to posting so this question might not turn out right. My question concerns the proper rendering of a river. On the OSM web page this river renders correctly at all zoom levels. By that I mean that it is represented as the full river width. But in Garmin BaseCamp (and my Oregon GPSr) when the image is zoomed out the river is just what I would call a schematic rendering just to show the river route. When the image is zoomed in the river is shown at its full width. My question is: "Is this a problem which needs to be corrected in the conversion of the OSM data to GARMIN format or is this a problem that needs to be corrected in the OSM data". In the OSM data there are ways for the riverbanks and they are tagged as Waterway=riverbank but not all of them are closed polygons. I understand from reading other questions that this can cause problems. I Don't have the skills or knowledge (yet) to fix this problem or even to know if it really is a problem. Where would I start? I am using JOSM as an editor.

RiverZoomedOUT RiverZoomedIN

asked 07 Jul '12, 08:47

sejofgville's gravatar image

accept rate: 0%

edited 07 Jul '12, 08:49

Based on my experience with Garmin Nuvis and MapSource (... I don't have BaseCamp) it seems to me quite clearly that Garmi renders different stuff even more "liberally" than the tile renderings we see in web maps.

Waterway=riverbanks would all need to be closed polygons and that may (or may not) be part of the problem (perhaps not, because you say that the river delta/ bay area is rendering ok in higher zoom levels.

The thin river is probably just the waterway=river that is supposed to run through the *=riverbank area.

I wouldn't worry about this so long as things show up in either higher zoom levels or/and the Garmin search -- but I would fix the *=riverbank polygons.

permanent link

answered 08 Jul '12, 03:41

jaakkoh's gravatar image

accept rate: 0%

I like your clear and illustrated question. My Vista HCX and Nuvi 1310t both show the riverbank polygons at all levels.The maps I get for my garmin are of GB from Talkytoaster as I have not managed to render my own yet. Polygons must be joined up,this is what happens when they are broken. I have drawn a lot of the river Great Ouse between Bedford and Ely,I usually create polygons of short sections otherwise edits would take hours and one break will make it all disappear. The old river way line is also required for routing so that must be left in and separate . The rendering you have on your garmin can only show what was downloaded and rendered at that time of course.When drawing a polygon I avoid using the riverbank twice or more times for example riverbank and riverside park polygon as fixing faults are hard, but I find after drawing the riverbank I can then turn off bing and then at high magnifications I can then draw a very close separate line for the park polygon. Hope this is of help.

permanent link

answered 08 Jul '12, 10:15

andy%20mackey's gravatar image

andy mackey
accept rate: 4%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 07 Jul '12, 08:47

question was seen: 3,392 times

last updated: 08 Jul '12, 10:15

powered by OSQA