In order to ensure the relevance of the results displayed, ArkeoGIS relies on a strict importation protocol. Every field specified as mandatory below really is! The absence of a compulsory field, a mistake or an approximation in the formulation of the field’s title could lead ArkeoGIS to refuse a site during its upload. Furthermore, a site can only be uploaded if it has at least one characterisation (real-estate, furniture, production, landscape or media).
A dedicated interface for the importations allows researchers to submit their database online.
- When submitting the database, an error report is generated by the server. It is then displayed on the browser to allow the researcher to correct the mistakes and quickly submit the new file.
- When the corrected database is submitted in its entirety, the new information replaces the one that have been saved during the first upload.
The file proposed for the import must be written in one of the four languages ArkeoGIS use (German, English, Spanish or French). It must be a .CSV format; the character set is « Unicode (UTF8); the field divider is « ; » and the text divider is « “ ». The first line of the imported database must use the English headers. The value, type and presence of every field into the importation file are described below. Further information about these fields can be found in the FAQ page of this handbook.
The updated standard file and its documentation are available at this address:
- AKG4.7 Addition of WEB_IMAGES column: Bernard, Loup et al. (2022) «Fichier d’importation standard et fichier descriptif des champs à partir de ArkeoGIS 4.7» [Dataset] NAKALA. https://doi.org/10.34847/nkl.ede43qsi
Title | Value | Type | Presence |
---|---|---|---|
An unknown value must be indicated as NULL Please don't use « 0 » which is a value | |||
SITE_SOURCE_ID | Unique identifier of the site into the source database. | Alphanumeric | MANDATORY |
SITE_NAME | Site's name or its mailing address. | Alphanumeric | |
MAIN_CITY_NAME | Name of the municipality on which the main part of the site is. | Alphanumeric | |
GEONAME_ID | MANDATORY If there are no Longitude and Latitude coordinates for the site. You can find them on the website : http://www.geonames.org/. Use the municipality’s name to request a Geoname, and use the GeoNameId “city villages” into ArkeoGIS. You will find this ID under the little “P” icon, or the “P.PPL” icon which means a populated place. Each line starting with the same SITE_SOURCE_ID must have the same GEONAME_ID. | Numerical | |
PROJECTION_SYSTEM | EPSG's code of the coordinate system For instance : WGS84 = 4326, RGF93 = 4171, Lambert93 = 2154, ETRS89 = 4258 Other correspondences can be found in Wikipedia. | Alphanumeric | MANDATORY |
LONGITUDE | MANDATORY if the site isn't classified as a city centroid. Each line starting with the same SITE_SOURCE_ID must have the same longitude. The decimal separator must be a dot, not a comma. | Numerical | |
LATITUDE | MANDATORY if the site isn't classified as a city centroid. Each line starting with the same SITE_SOURCE_ID must have the same latitude. The decimal separator must be a dot, not a comma. | Numerical | |
ALTITUDE | For the terrestrial sites, the highest altitude is chosen. For the submarine sites, the lowest altitude is chosen. The unit reference is the meter. Each line starting with the same SITE_SOURCE_ID must have the same altitude. The decimal separator must be a dot, not a comma. | Numerical | |
CITY_CENTROID | If the geographical coordinates are unknown (latitude X and longitude Y's fields are left empty) You need to choose « YES ». Then, ArkeoGIS will use the city centroid. | Yes-No | MANDATORY One the proposals. |
OCCUPATION | Each line starting with the same SITE_SOURCE_ID must have the same « occupation » amongst the following : Not documented – Single – Continuous – Multiple | Alphabetical | MANDATORY |
STATE_OF_KNOWLEDGE | Each line starting with the same SITE_SOURCE_ID can have a different state of knowledge, so that every element of characterisation can be better described. Please, choose between the following : Not documented – Literature – Airborne Survey – Foot survey – Probed – Excavated. | Alphabetical | MANDATORY |
STARTING_PERIOD | The values can be : - Either numerical : preceded by « + » or « - » The default value is « + » - Either textual : Undefined Each line starting with the same SITE_SOURCE_ID can have a different starting date relating to each element of characterisation. Some examples in Chronology page in this manual. | Alphanumeric | MANDATORY |
ENDING_PERIOD | The values can be : - Either numerical : preceded by « + » or « - » The default value is « + » - Either textual : Undefined Each line starting with the same SITE_SOURCE_ID can have a different ending date relating to each element of characterisation. Some examples in Chronology page in this manual. | Alphanumeric | MANDATORY |
CARAC_NAME | Please, choose one of the following suggestions : Realestate – Furniture – Production – Landscape or Medias. | Alphabetical | MANDATORY |
CARAC_LVL1 | Must use the exact same wording for the characterisation's level that has been defined in the CARAC_NAME's column | Alphabetical | MANDATORY |
CARAC_LVL2 | Must use the exact same wording for the characterisation's level that has been defined in the CARAC_NAME's column. The previous level must be filled in order to fill this one. | Alphabetical | |
CARAC_LVL3 | Must use the exact same wording for the characterisation's level that has been defined in the CARAC_NAME's column. The previous level must be filled in order to fill this one. | Alphabetical | |
CARAC_LVL4 | Must use the exact same wording for the characterisation's level that has been defined in the CARAC_NAME's column. The previous level must be filled in order to fill this one. | Alphabetical | |
CARAC_EXP | One of the proposals must be chosen | Yes-No | MANDATORY |
BIBLIOGRAPHY | A site with the same SITE_SOURCE_ID, but multiple lines, can have a distinct bibliography for each element of characterisation. | Alphanumeric | |
COMMENTS | A site with the same SITE_SOURCE_ID, but multiple lines, can have a distinct comment for each element of characterisation. | Alphanumeric | |
WEB_IMAGES | A site with the same "SITE_SOURCE_ID", on different lines, can thus have separate illustrations for each of the characterisation elements described. The author can put links to images stored on Nakala, which will be captioned if the deposit is made on Nakala, ArkeoGIS retrieving all the metadata from the DOI indicated, to generate a file in IIIF manifest.json format. It is also possible to specify manifest.json file URLs in IIIF format. These links should be entered separated by a ',' exe: https://doi.org/10.34847/nkl.b6e00u70, https://doi.org/10.34847/nkl.cb442502 , https://gallica.bnf.fr/iiif/ark:/12148/btv1b7742257s/manifest.json , https://media.getty.edu/iiif/manifest/8959676f-d7e7-4f73-99ed-3a7f6e46b1d1 They will be presented in a Mirador IIIF viewer on the ArkeOpen interface. | URI(s) |