Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| geoscene3d:building_a_layered_model:spatialite_database_structure [2025/09/02 10:07] – [Using the Database in GeoCloud LARCOS] dev | geoscene3d:building_a_layered_model:spatialite_database_structure [2025/09/02 10:23] (current) – [Using the Database in QGIS] dev | ||
|---|---|---|---|
| Line 95: | Line 95: | ||
| When using GeoCloud LARCOS, this specialized interpretation database is the file that is uploaded when you perform a check-in of your model edits. The edits are made in Geocene3D and then uploaded to the GeoCloud LARCOS website during the check-in process. Any interpretation points you have added or modified are stored in the SpatiaLite database and transferred to the cloud. These points are then used to update the current model in the cloud environment, | When using GeoCloud LARCOS, this specialized interpretation database is the file that is uploaded when you perform a check-in of your model edits. The edits are made in Geocene3D and then uploaded to the GeoCloud LARCOS website during the check-in process. Any interpretation points you have added or modified are stored in the SpatiaLite database and transferred to the cloud. These points are then used to update the current model in the cloud environment, | ||
| - | In GeoCloud LARCOS, all interpretation points from different layers are merged into a single table, where all existing points also reside. Because of this, it is essential that every GUID is globally unique across all tables in the SpatiaLite interpretation database. This prevents identifier conflicts and ensures that each point can be correctly recognized and updated | + | In GeoCloud LARCOS, all interpretation points from different layers are merged into a single table, where all existing points also reside. Because of this, it is essential that every GUID is globally unique across all tables in the SpatiaLite interpretation database. This prevents identifier conflicts and ensures that each point can be correctly recognized and updated. This design reinforces the rule described in the **Required Field: uid format** section |
| ==== ==== | ==== ==== | ||
| Line 105: | Line 105: | ||
| You can view and work with the Geocene3D SpatiaLite database in QGIS: | You can view and work with the Geocene3D SpatiaLite database in QGIS: | ||
| - | - Open QGIS | + | - **Open QGIS** |
| - | - Go to '' | + | * Start QGIS and open a project (new or existing). |
| - | - Click " | + | - **Drag the database into QGIS** |
| - | - Select | + | * In your file system, locate the '' |
| - | - QGIS will now list all spatial tables that contain geometry | + | * Drag it directly onto the **QGIS map canvas**. |
| - | | + | - **Confirm the layer is added** |
| + | * The point layer from the database | ||
| + | - **Inspect or style the layer** | ||
| + | * ****Use the **Identify Features**, **Symbology**, | ||
| When loaded, QGIS will use the **EPSG code stored in the geometry metadata** | When loaded, QGIS will use the **EPSG code stored in the geometry metadata** | ||
