TABLE 1. The main functionalities of a modular GIS constructed for spatial analysis (Albert, 2017).
| Functionalities | Description |
| Processing | The data processing tool is responsible for the digital recording of text (notes, reports), alphanumeric and logical (true/false) information, images (photos, scanned documents) and vector-geometry (line-plot maps, sections). |
| Storing | Data storage tools provide secure data store and make it possible to reach data in digital form, which is located on mass storage devices in its appropriate format. The storing is maintained and accessed via database and file management tools. |
| Representation | The tool that represents the data as a 2D map or a 3D model is a complex application, which not only visualizes the data, but most often serves as the GIS environment. It makes possible to access not only the visual representation of the data, but all the collected information from the database providing a user interface for spatial analysis. |
TABLE 2. Possible abbreviations/codes and their explanations used in a paleontological excavation site for quickly recording the information in the surveying device. The concatenation of codes in one single entry can be the following: B002_AN_B_2_121.
| Identification code types | Codes | Explanation |
| Category and serial numbers | B001, T001, C001, E001; r01 | One digit code of the category combined with the serial number of the finding of the certain category (e.g., B=bone, T=teeth, C=coprolite, E=else; r=stratigraphic element) |
| Groups | AN; P; E; PT; etc. | One or two digit codes of different taxonomical groups that were already described/expected to be find on the site (e.g., A=Anura; P=Pisces; E=Eusuchia; PT=Pterosauria) |
| Types | B; F; L; O; BF; OF; etc. | Maximum three-digit-long unique code of the anatomical type of the finding (e.g., B=bone; F=femur; L=limb bone; O=osteoderm; BF=bone fragment; OF=osteoderm fragment). |
| Size | 1 - 5; 1 - n | Size of the findings in absolute or - alternatively - in relative terms. |
| Documenter | Unique id. (e.g., 121) | The unique identifier of the paleontologist/working staff member who excavated the fossil (or alternatively the identifier of the place, where the fossil was found). |
TABLE 3. Data types and explanations of the columns (fields) of the exported query-result data table.
| Column name | Data type | Explanation |
| finds | Numeric (integer) | Within the given buffer distance (a 3D sphere), how many fossils were found around the concerning base point which belongs to one of the listed taxonomical groups, and has the appropriate anatomical type (if it was defined). |
| findType | Text | Category of the search result from the aspect of the listed taxonomical groups: E (empty); P (partial); T (total) |
| Code_list | Text | Group codes of the taxa that were find around the base point (one code may represent more matches from the same type). |
| Xm | Numeric | Easting of the meter-based geodesic coordinate system. (If the result is exported as a cm-based file for using it in JS this column is named as Xcm) |
| Ym | Numeric | Northing of the meter-based geodesic coordinate system. (If the result is exported as a cm-based file for using it in JS this column is named as Ycm) |
| Zelev | Numeric | Elevation of the meter-based geodesic coordinate system. (If the result is exported as a cm-based file for using it in JS this column is named as Zdepth) |
| Code(base) | Text | ID code of the base record (used as the center for the buffer search). |
| Code(finds) | Text | ID code(s) of the record(s) that was/were find around the base point. |
