Nathan Mixter <[email protected]> writes: > For instance an open space parcel probably isn't that useful because > it is not represented in OSM. It could be broken up into meadow, wood, > scrub, forest, etc.
Jason and I are using 'open space' to mean land that is protected from development with some legal mechanism; this is orthogonal to landcover. > Other parcel data that don't translate well include things like flood > planes or highway zones. Even some forest parcels may not always > translate into landuse=forest. Agreed; per-case mapper judgement is needed. > Within cities, you have parcels that are subdivided into areas like > medium family residential, multi family residential, non retail That sounds like zoning rather than parcel. > commercial, mixed use, etc. Parcel data tends to be too vague or tends to > overlap other features. A better way to add it is to filter out each > individual feature first, verify them and then upload them individually. Here's a specific example of what I'm talking about:b http://osm.org/go/ZfIZMM6m The area labeled "Leggett" is a single parcel (lot), owned by my local land trust. The protected area is exactly what the trust owns, and the massgis lot data is the best available set of coordinates, absent hiring surveyors (in this case, in my judgement, having walked the land and knowing most of the board of the land trust).
pgpdTcHwZx1WX.pgp
Description: PGP signature
_______________________________________________ Talk-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-us
