I recently notice a similar problem here in Spokane on the CycleMap where the Spokane River has seemingly escaped its bounds and flooded a good portion of the Spokane Valley:
I may have once flooded the entire US (only in osmarender) by sticking an apparently bad tag onto the Siletz River.
A few days after adding "natural=water" onto the riverbank I randomly went to the tiles@home map and saw everyone was drowning. I knew that it hadn't always been that way, but assumed it was the result of somebody else's waterway edits. After we remained flooded for quite some time though, I removed the tag "just in case" and lo, the waters receded and the great flood was over.
Though T@H doesn't show any massive flooding in Oregon, it could still be a similar tagging issue.
OpenStreetMap
Discussion
Comment from axodys on 7 November 2009 at 15:50
I recently notice a similar problem here in Spokane on the CycleMap where the Spokane River has seemingly escaped its bounds and flooded a good portion of the Spokane Valley:
osm.org/?lat=45.253&lon=-122.795&zoom=9&layers=00B0FTF
Comment from axodys on 7 November 2009 at 15:52
Put the wrong link up. This should work better:
osm.org/?lat=47.6733&lon=-117.3389&zoom=12&layers=00B0FTF
Comment from JigPu on 8 November 2009 at 09:35
I may have once flooded the entire US (only in osmarender) by sticking an apparently bad tag onto the Siletz River.
A few days after adding "natural=water" onto the riverbank I randomly went to the tiles@home map and saw everyone was drowning. I knew that it hadn't always been that way, but assumed it was the result of somebody else's waterway edits. After we remained flooded for quite some time though, I removed the tag "just in case" and lo, the waters receded and the great flood was over.
Though T@H doesn't show any massive flooding in Oregon, it could still be a similar tagging issue.