-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Matthew Dangerfield
committed
Oct 16, 2017
1 parent
3d4a1e6
commit c5f7777
Showing
8 changed files
with
91 additions
and
47 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
// See readme for details | ||
exports.config = { | ||
mapsAPIKey: 'YOUR_KEY_HERE', | ||
auth: 'YOUR_FAMILY_SEARCH_AUTHORIZATION_HERE', | ||
cookie: `YOUR_FAMILY_SEARCH_COOKIE_HERE`, | ||
rootPersonId: 'YOUR_FAMILY_SEARCH_PERSON_ID_HERE', | ||
} |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Family Search Grave Mapper | ||
|
||
![Example of the result](./images/example-screenshot.PNG) | ||
|
||
This web app creates a visualization of where your ancestors are buried. You can use this to find ancestors buried near you so you can visit their grave sites. Have fun! | ||
|
||
## Setting up config.js | ||
Create a file, called config.js, with these properties exported on a variable called config: | ||
|
||
### mapsAPIKey | ||
API key for the Google Maps Javscript API. You can get one [here](https://developers.google.com/maps/documentation/javascript/) | ||
|
||
### rootPersonId | ||
The family search person id of the person who's ancestors you want to get burial data for. This will probably be yourself, so you can see ancestors with burial sites near you. | ||
|
||
### auth | ||
Go to www.familysearch.org/tree/, and open the chrome developer tools. Go to the **network** tab, and click on **XHR** to only show XHR requests. Click on a random person on your tree to make their info card pop up. In the network tab, you should see a request to the `card` endpoint. Click on that request to show its details, and copy everything listed in the `authorization` property under **Request Headers**. | ||
|
||
### cookie | ||
Follow the steps above, and copy the `cookie` property under **Request Headers**. | ||
|
||
## Run it | ||
First, run `npm install`, and then `npm run fetchData` to download all the ancestor's data from family search. Then, run `npm start` to start the web app, and go to a browser. It should automatically open the app in a new tab. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters