<p>In this section you can find out how to obtain data for each of the resources listed above.</p>
<p>Each of the sources expected is a CSV file encoded with <b>UTF-8</b> format, except for geodata in GeoJSON format.</p>
<h4id="people-details">people_details</h4>
<p>
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”
</p><p>
So, at this stage, producing the table with the fields listed above requires to run the query called “<b>QryPeopleExport</b>”.
</p><p>
We expect the table to have this header:
<tableclass="head">
<tr>
<tdalign="left"><b>MrMrs</b></td>
<tdalign="left"><b>Title</b></td>
<tdalign="left"><b>First name</b></td>
<tdalign="left"><b>Last name</b></td>
<tdalign="left"><b>Position</b></td>
<tdalign="left"><b>e-mail 1</b></td>
<tdalign="left"><b>URL</b></td>
<tdalign="left"><b>Organisation English</b></td>
<tdalign="left"><b>Country</b></td>
<tdalign="left"><b>Biography</b></td>
<tdalign="left"><b>Field of expertise</b></td>
<tdalign="left"><b>Taxa</b></td>
<tdalign="left"><b>Methods</b></td>
<tdalign="left"><b>Geographic area of expertise</b></td>
<tdalign="left"><b>Scale</b></td>
<tdalign="left"><b>ProfileOnWeb</b></td>
<tdalign="left"><b>ID</b></td>
</tr>
</table>
</p>
<h4id="resources">resources</h4>
<p>This is a full export of the <b>Resources</b> table.</p>
<tableclass="head">
<tr>
<tdalign="left"><b>ID</b></td>
<tdalign="left"><b>Title</b></td>
<tdalign="left"><b>Citation</b></td>
<tdalign="left"><b>Type</b></td>
<tdalign="left"><b>Range</b></td>
<tdalign="left"><b>URL</b></td>
<tdalign="left"><b>Abstract</b></td>
<tdalign="left"><b>AuthorKeywords</b></td>
<tdalign="left"><b>Lat</b></td>
<tdalign="left"><b>Lon</b></td>
<tdalign="left"><b>Stars</b></td>
</tr>
</table>
<h4id="ranges">ranges</h4>
<p>This is a full export of the (Mountain) <b>Ranges</b> table.</p>
<tableclass="head">
<tr>
<tdalign="left"><b>Range_ID</b></td>
<tdalign="left"><b>RangeName</b></td>
<tdalign="left"><b>RangeNameLanguage</b></td>
<tdalign="left"><b>MotherRange</b></td>
<tdalign="left"><b>Level</b></td>
<tdalign="left"><b>Centroid_Latitude</b></td>
<tdalign="left"><b>Centroid_Longitude</b></td>
<tdalign="left"><b>Orogeny</b></td>
<tdalign="left"><b>Area</b></td>
<tdalign="left"><b>GMBA_ID</b></td>
<tdalign="left"><b>Countries</b></td>
<tdalign="left"><b>Peak_Elevation</b></td>
<tdalign="left"><b>Peak_Name</b></td>
<tdalign="left"><b>Peak_Latitude</b></td>
<tdalign="left"><b>Peak_Longitude</b></td>
<tdalign="left"><b>Comments</b></td>
<tdalign="left"><b>Checked</b></td>
<tdalign="left"><b>Source</b></td>
<tdalign="left"><b>Range_AlternateID</b></td>
</tr>
</table>
<h4id="people_resources">people_resources</h4>
<p>This is a full export of the <b>People to Resources</b> table.</p>
<tableclass="head">
<tr>
<tdalign="left"><b>ID</b></td>
<tdalign="left"><b>Resource</b></td>
<tdalign="left"><b>Person</b></td>
<tdalign="left"><b>Role</b></td>
</tr>
</table>
<h4id="people_ranges">people_ranges</h4>
<p>This is a full export of the <b>People to Ranges</b> table.</p>
<tableclass="head">
<tr>
<tdalign="left"><b>ID</b></td>
<tdalign="left"><b>Person</b></td>
<tdalign="left"><b>MountainRange</b></td>
</tr>
</table>
<h4id="gmba">gmba.geojson</h4>
<p>This file contains geodata about mountain ranges in
<ahref="http://geojson.org/">GeoJSON</a> 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
<ahref="https://www.qgis.org/">QGIS</a> or <ahref="https://mapshaper.org/">Mapshaper</a>.
Each polygon comes with a GMBA-ID that matches the <b>people_ranges</b> table.
</p>
<p>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