The NHD viewer (http://nhdgeo.usgs.gov/viewer.htm) shows areas for rivers that are "big enough" (I see areas for the Mississippi, for example).
I haven't tried converting an area that has such a river yet, but I'll bet the script handles it. On Fri, May 2, 2008 at 1:17 PM, Adam Schreiber <[EMAIL PROTECTED]> wrote: > Is there a reason the NHD treats rivers as linear features instead of > areas? Is area data present for the river banks that isn't being > converted yet? > > Cheers, > > Adam > > On Fri, May 2, 2008 at 9:46 AM, Ian Dees <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] is starting to show the data I uploaded yesterday: > > > > http://tah.openstreetmap.org/Browse/?x=1971&y=2935&z=13&layer=tile > > > > It looks like the water bodies aren't given "name" tags. > > > > > > > > On Thu, May 1, 2008 at 2:17 PM, Ian Dees <[EMAIL PROTECTED]> wrote: > > > > > I'm 80 minutes away from finishing an import in this area: > > > > > > http://tah.openstreetmap.org/Browse/?x=245&y=367&z=10&layer=tile > > > > > > I'll probably have to "fill in the holes" for islands and maybe slice > up > > the extra-long ways (both are TODOs on Matthew's python script I think). > > > > > > > > > > > > _______________________________________________ > > Talk-us mailing list > > [email protected] > > http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us > > > > >
_______________________________________________ Talk-us mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
