-
Configuration
-
- Settings and data used in the application can be uploaded and refreshed here.
-
-
-
1. Obtain data exports
-
-
Each of the following data exports from the GMBA Access database are needed to completely refresh the database.
- Details on how to export them is documented below. The filenames need to exactly match the ones in this list:
-
-
-
-
-
2. Send data to the server
-
Use this form to select a file on your machine for uploading to the server.
- Repeat the process until each source above has a green checkmark.
-
-
-
-
3. Refresh application data
-
Once the files have all been uploaded (green), you can press the orange button here to
- validate and refresh the information in the app. Any errors will stop the processing,
- and you will see a notification at the top of the screen. This step takes a few minutes.
-
-
-
-
4. Prepare the search engine
-
The last step is to reindex the application's search engine by clicking the button below.
- At this point users will see information in the search results.
-
-
-
-
-
Data sources
-
-
In this section you can find out how to obtain data for each of the resources listed above.
-
Each of the sources expected is a CSV file encoded with UTF-8 format, except for geodata in GeoJSON format.
-
-
people_details
-
- The fields being updated are all part of one query on three tables: “People”, “Organisations” and “LU_Countries”. Selected fields come from the different tables and the selection of people is based on the Yes/No value “ProfileOnWeb” (lower right field in the screenshot).
-
-
-
- The fields: “Taxa”, “Methods” and “Geographic area of expertise” and “Scale“ concatenate information from various YesNo columns, as you see at the bottom of the screenshot for “Scale”
-
- So, at this stage, producing the table with the fields listed above requires to run the query called “QryPeopleExport”.
-
- We expect the table to have this header:
-
-
- MrMrs |
- Title |
- First name |
- Last name |
- Position |
- e-mail 1 |
- URL |
- Organisation English |
- Country |
- Biography |
- Field of expertise |
- Taxa |
- Methods |
- Geographic area of expertise |
- Scale |
- ProfileOnWeb |
- ID |
-
-
-
-
-
resources
-
This is a full export of the Resources table.
-
-
-
- ID |
- Title |
- Citation |
- Type |
- Range |
- URL |
- Abstract |
- AuthorKeywords |
- Lat |
- Lon |
- Stars |
-
-
-
-
ranges
-
This is a full export of the (Mountain) Ranges table.
-
-
-
- Range_ID |
- RangeName |
- RangeNameLanguage |
- MotherRange |
- Level |
- Centroid_Latitude |
- Centroid_Longitude |
- Orogeny |
- Area |
- GMBA_ID |
- Countries |
- Peak_Elevation |
- Peak_Name |
- Peak_Latitude |
- Peak_Longitude |
- Comments |
- Checked |
- Source |
- Range_AlternateID |
-
-
-
-
people_resources
-
This is a full export of the People to Resources table.
-
-
-
- ID |
- Resource |
- Person |
- Role |
-
-
-
-
people_ranges
-
This is a full export of the People to Ranges table.
-
-
-
- ID |
- Person |
- MountainRange |
-
-
-
-
gmba.geojson
-
-
This file contains geodata about mountain ranges in
- GeoJSON format.
- The source of the data is a GIS layer maintained by GMBA with mountain polygons.
- The export folder contains one small scale layer and one large scale one.
- We use the small scale version, additionally simplified and compressed using
- QGIS or Mapshaper.
- Each polygon comes with a GMBA-ID that matches the people_ranges table.
-
-
-
The data can be uploaded in the backend, but will be reset on deployments.
- To ensure that it is preserved, it should also be updated in the
- source code
- - geodata folder.
-
-