Cemeteries have various issues.

1) maintenance - on the one hand, old data rarely goes out of date. on the
other hand, for active cemeteries there is frequently new data.

2) bad old data - some cemeteries have misidentified graves.
   a) there is the recent scandal at Arlington
   b) there is the issue in the Southeastern US where confederate heritage
       organizations have been getting headstones from the federal
       government and scattering them somewhat randomly in
       cemeteries where they believe the confederate soldier is buried.

i'm not saying these are reasons not to do it, but they are reasons to be
careful about how you represent the data if you do enter it. yes, there is a
stone there with specific text on it, but that's actually all you have unless
there is more supporting documentation.

On 7/29/13 10:54 AM, Kathleen Danielson wrote:
There is the Congressional Cemetery in DC:
http://openstreetmap.org/?lat=38.88099&lon=-76.97739&zoom=17&layers=M The
MappingDC folks had a mapping party there a year or two ago.

And there's also Arlington National Cemetery, although it doesn't have the
level of granularity you're talking about:
http://openstreetmap.org/?lat=38.88013&lon=-77.06823&zoom=16&layers=M


On Mon, Jul 29, 2013 at 10:49 AM, Thomas Colson <thomas_col...@nps.gov>wrote:

Are there any examples of detailed cemetery mapping in OSM? E.g.
individual head-stones are mapped with interred information. *Is this
even an appropriate use of OSM?* I have a cemetery mapping  project with
LOTS of good data, pondering the best way to publish it....****

** **

** **

** **

_______________________________________________
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us




_______________________________________________
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

_______________________________________________
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us

Reply via email to