On Mon, Dec 7, 2009 at 4:01 PM, Apollinaris Schoell <[email protected]>wrote:
> Scott Atwood wrote: > > Finally, the source field references http://www.nationalatlas.gov/, but > all the import mapped data fields are prefixed with "massgis:", which seems > quite odd, since this data should have nothing to do with MassGIS. > > this data isn't good enough for an import. resolution is very crude and > contains many errors > So the National Atlas data has been previously evaluated and found to be of poor quality? > It looks like these boundaries were imported by user "John Serafin" in > April 2009. I tried contacting this user via the OSM messaging system, but > I got no response. I looked at the Import Catalogue on the OSM wiki, and I > couldn't find anything obvious that corresponds to these imports. > > Does anyone have any idea what the best way to get these boundaries fixed > up? Should they be deleted and reimported? > > If you have any better data, delete and import the better one > I did a quick web search and found that the US National Park Service maintains a website with a large collection of GIS data, including park boundaries and campgrounds: http://www.nps.gov/gis/data_info/park_gisdata/hi.htm How do people go about evaluating the quality of data that is being considered for import? I'm not sure there is a better source for US National Park boundaries than the NPS itself. It's not like it's possible to survey the boundaries by observations on the ground. The only way I was able to even determine that the previous import was problematic is that places I knew to be just inside the park boundaries appeared just outside the imported park boundaries. -Scott -Scott -- Scott Atwood The hill isn't in the way, it is the way.
_______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
