Description of Error - 636: Bogus death location
Location is probably not correct.
Content of info column: Empty
Possible Causes
This location is inserted as location by autocomplete operations of some softwares or websites.
Action Steps
Verify the location. If location is correct, mark it as False error.
|
Error Status
For each Error you can set status. You can set it as Corrected, Not corrected, False Error, Proposed merge or just add a Comment.
If there are related errors for the profile, you will also see them on status page.
Full description is available on Status Help Page.
Questions and Discussions on this Error
You can read what other people have asked here db_error_636.
You can also share your best practices, experiences, problems about the Error by posting a question in G2G. If you create a new G2G discussion for this Error, add tag data_doctors and db_error_636.
Technical Stuff
Checks if location is included in Space:Database_Errors_Definition. There is also the reason why the location is bogus.
Suggestion reports
You can see the weekly prepared list of the latest suggestions prepared on March 9th 2025. You can also get the online report on WikiTree+.
|
- This page is part of the Data Doctors Project.
- Latest report: March 9th 2025.
- Data Doctors Challenge: Orphaned_Profiles_LII and
.
- Custom reports by: Suggestion lists, Unsourced lists, Unconnected lists.
- See
for custom reports and statistics and our Video Collection.
- Latest ProjectBox Report: Project Report
- Latest Categories Report: Categories Suggestions Report
