As I have gone through and sourced my pages, I have tried to add burial/cemetery information, with links to Find A Grave, as they are known. In some cases, birth/death information is only known because of dates on a tombstone, so I view this as sometimes vital.
One thing that has been a hassle in this regard is that for nearly every cemetery, even some large ones, I have had to make a place for all of them, even though this information is already out there on Find A Grave. Since it appears place names for countries/states/cities/counties was already scraped for WR from other sites, I wonder if it would be possible to scrape cemeteries from Find A Grave ?
I agree with the first poster that creating all these cemetery pages before one can finish an upload is a hassle we could do without if possible! This is one feature that currently turns off new users. If info could be taken from Find-a-Grave for the initial creation of place pages, then users could add or edit the pages as they see fit. I don't see the need to have a permanent link to cover corrections or edits; just give us a head start with the initial creation of these cemetery place pages. --janiejac 11:52, 28 November 2012 (EST)
Also would prefer to have Cemeteries in a different category (or subcategory). It's getting to be a real nuisance to have to fight through cemetery listings when trying to enter place names. As for Find A Grave, I use it because it's there, but it's not the most reliable source, whether we're talking about cemetery names, who's buried where (I've found several people buried in two different cemeteries), or other information. Probably not a good foundation for WeRelate. --GayelKnott 14:50, 30 November 2012 (EST)
I'm hitting "Watch" on this page, not necessarily because I support the suggestion of scraping Find A Grave for cemetery names, but because I want to keep abreast of any commentary this subject and possible changes to the use of cemetery placenames. I always thought that the use of cemeteries as actual placenames was awkward, akin to adding the name of a church as an actual separate placename for baptisms and marriages, or the name of the hospital as a placename for birth and death events, so I'm not sure I support importing all cemeteries to WR as separate places. My thought is they might be better identified in the "Description" field of the actual geographical place (village, township, city, county, etc.) on the person page. So my suggestion would be to maintain the status quo for now, keeping existing cemeteries with placename pages intact and keep the functionality for users to add cemeteries manually as placenames, but not to import all cemetery names and locations to WR and create a monumental amount of blank pages nobody uses or cares about. Also I don't look as this suggestion as a "value added" improvement worthy of costly programming time compared to other improvement suggestions on the list. --BobC 14:11, 31 March 2015 (UTC)
Given the conversation above, and the fact that the Terms of Service for Find A Grave prohibit downloading content for anything beyond a unique family history, I am going to move this to the rejected list. Users will have to continue to create cemetery pages if they want to use them (or put the cemetery name in the description instead).--DataAnalyst 02:07, 9 April 2017 (UTC)