Field Data Overview
The Field Data category in Geodb.io captures critical on-the-ground information for mineral exploration, with each model designed to handle spatial data effectively. Here’s how it works:
Each model in Field Data can include geometry:
- LandHolding: Supports polygon or multipolygon geometry, perfect for defining property boundaries or claim areas.
- PointSamples, Archaeology, FieldObservations, and StructuralMeasurements: Use point geometry for precise location-based data, such as sample points or observation sites.
When this data is saved, Geodb.io converts it to latitude/longitude (Lat/Lon) coordinates in the database. This ensures it can be queried spatially and visualized seamlessly—such as in QGIS—while adhering to our no-data-loss principle. The original location information is preserved as follows:
- For LandHolding: The Manual Geometry column retains the raw input data.
- For point-based models (PointSamples, etc.): The original Lat/Northing, Lon/Easting, and Elevation values are stored, along with the EPSG datum provided, so you never lose context about how the data was collected.
The remaining fields in each model vary depending on their purpose and are designed to be intuitive:
- LandHolding: Includes details like ownership, staking info, and related documents or photos.
- PointSamples: Captures sample-specific data like type or description.
- Archaeology: Records archaeological findings or observations.
- FieldObservations: Stores general notes from the field.
- StructuralMeasurements: Tracks structural data like orientation or type.
This geospatial integration makes Field Data a powerful tool for mapping, analyzing, and sharing exploration insights in real time.