![]() The link in the leftmost column of the place-check window is useful here: it will take you to that place in the place hierarchy (so NOT the GoogleMaps part). In such cases, you will have to change the error in the GEDCOM data. a missing level ("Faxfjord, Troms, Norway") or a missing comma (Faxfjord, Dyrøy Troms, Norway). In the "place check" window, you may come across places that are incorrectly placed, e.g. If not, you can instead find the place on the map manually.ĥ. Try "search globally" - if you're lucky, Google will find your place name, and you can click "Save" and move on to the next item. This will be placed in the Gulf of Guinea (lat/long 0,0). This will open a GoogleMap window with a place marker. Now, all you have to do - which may be quite a lot - is to go through all the names in red and add coordinates. This will list all the place names in the GoogleMaps list which lack coordinates. Your google-maps place data table will now be populated with all the places from your GEDCOM's place hierarchy.Ĥ. Click on "Import" next to "Import all places from a family tree". When you have an orderly place hierarchy, go back to admin > GoogleMaps (or use the "Geographic data" link beneath the map in the place hierarchy window). But don't despair: it will all be wonderful in a couple more steps.ģ. Until #2 is finished, anything GoogleMaps related will be virtually useless, which can be discouraging if you have a lot of geodata to organize. Which scheme you choose is largely up to you, but be consistent - you'll regret it sorely if you aren't. ![]() It is best to do this from the place hierarchy and not from the Google maps area. Decide on a naming and ordering convention, and arrange all your existing data in accordance with the scheme you have chosen. Leave the admin area and go to Lists > Place hierarchy. Go to Admin > GoogleMaps, Place Hierarchy tab: make sure "Use Google Maps™ for the place hierarchy" is set to "yes".Ģ. NN: born in Faxfjord, Dyrøy, Troms, Norway) are not automatically synchronized with the GoogleMaps table, so there is a lot of manual work, and some of it may seem like double work (which it may or may not be, and which may or may not be a bad thing).Īnyway, what the wiki lacks is a six-step walkthrough:ġ. Part of the problem with geodata in webtrees is that place names in your GEDCOM data (e.g. The wiki article is very detailed, and it gives all the technical details about how the place-mapping mechanism works. Please Log in or Create an account to join the conversation. You may need to inspect any data you acquire to verify that they fit one of the following conventions: Provides drill down coordinate searches by name Which includes cemetery information (as does Histopolis, above) Which provides excellent information and search on many levels , which is a method of obtaining co-ordinates from normal Google maps Some well-known sources include:īy-hand discovery and recording using Google Earth Location data may be obtained in various ways. So, while both Google Analytics code snippets will populate your GA account some people may prefer to stick with Universal Analytics.What's this? need to download and install? By default, Google now includes the new gtag.js script in the Tracking Code section (under Admin > Property Settings) but the GA4 layout is different (see screenshot). I would suggest updating the webtrees Google Analytics module to include a checkbox to the effect 'Do you wish to use the new Google Analytics gtag.js code?' This would give webtrees users the option to continue to use Universal Analytics or the new gtag.js code. (Setting up a new GA Property means data only starts flowing in to the associated Views from the date the new Property is created). Most people are going to use the same Account ID in order to ensure their GA data continues uninterrupted. You can use the same GA Account ID, although you can user a new code if you prefer which would generate a new GA Property. The new code snippet is a straight slot-in replacement for the old Universal Analytics code snippet. I'll raise an issue on Github, although it's not a bug more an update to the latest Google Analytics script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |