+1 to Elliot Plack's proposal to use Simplify to remove the redundant
nodes from the poor quality imported buildings.
In fact, I did this myself for another massive import: User "jumbanho"
imported buildings for the large city of Raleigh, NC back in January
2010.
There were lots of degenerate
+1 to what AlaskaDave said.
As far as I can tell in this case, the jaggies are a result of running
ScanAerial on imagery of a low resolution (i.e. zoomed out). At that
level (LandSat resolution), a smooth lake edge looks like a jagged set
of individual pixels, where each pixel is 28 meters
I've probably done the most NHD cleanup so far (at least some degree
of fixing on the entire state of NC, most of IL, northern MI, parts of
OK/TX/UT/CO, and a lot of CA), many hundreds of hours of manual work.
Just to chime in with agreement on what everyone has said, yes to:
1. NHD has lots of
If you look across a large area of the Maryland, for example around here:
https://www.openstreetmap.org/#map=19/39.11882/-76.62031
You may notice a few very odd things.
1. Back in 2015, user 'gdoyle' created a large number of buildings,
using small, incorrect geometry.
2. This week, user
Just to chime in..
As someone who has worked on protected areas in OSM globally, it has
always been obvious that the landuse tags and the boundary tags
serve clear and different purposes.
US National Forests are boundaries around land which contain many
uses(*), and landuse=forest is only one of
5 matches
Mail list logo
