User Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
geoscene3d:building_a_layered_model:spatialite_database_structure [2025/09/02 09:12] – [Introduction] devgeoscene3d:building_a_layered_model:spatialite_database_structure [2025/09/02 10:23] (current) – [Using the Database in QGIS] dev
Line 55: Line 55:
 ''xypoint'': POINT — geometry field storing the coordinates as Easting and Northing ''xypoint'': POINT — geometry field storing the coordinates as Easting and Northing
  
-----+
 {{:geoscene3d:building_a_layered_model:fieldsspl.png|}} {{:geoscene3d:building_a_layered_model:fieldsspl.png|}}
  
Line 68: Line 68:
 **Important:**  Geocene3D itself does **not use projections**  internally. The EPSG code only matters when the database is opened in external software such as QGIS, where the coordinates need to be placed correctly on a projected map. The EPSG value is defined by the user during the modeling setup process ([[modelsetup-stepbystep|]]) to ensure consistency when exchanging data with mapping tools.  **Important:**  Geocene3D itself does **not use projections**  internally. The EPSG code only matters when the database is opened in external software such as QGIS, where the coordinates need to be placed correctly on a projected map. The EPSG value is defined by the user during the modeling setup process ([[modelsetup-stepbystep|]]) to ensure consistency when exchanging data with mapping tools. 
  
----- 
  
-==== Required Field: GUID in Specific Format ====+==== Required Field: uid ====
  
-The database require a **GUID (Globally Unique Identifier)** to uniquely identify each entry. A GUID is a 128-bit value written as a string in a fixed format, using five groups of hexadecimal digits separated by hyphens, in the 8-4-4-4-12 pattern.+The database requires a **GUID (Globally Unique Identifier)** to uniquely identify each entry. A GUID is a 128-bit value written as a string in a fixed format, using five groups of hexadecimal digits separated by hyphens, in the 8-4-4-4-12 pattern.
  
-This is the exact format used in Geocene3D:+This is the exact format used:
  
 {D362ABBF-E812-4276-B216-AE55CB04B187} {D362ABBF-E812-4276-B216-AE55CB04B187}
  
-Format rules:+**Format rules:**
  
-The value must begin and end with curly braces ''{}''+   * The value must begin and end with curly braces ''{}'' 
 +  * All letters must be uppercase 
 +  * Hyphens must follow the 8-4-4-4-12 grouping 
 +  * The total length must be 38 characters, including the braces
  
-All letters must be uppercase+**Important:**  The GUID must be generated using code that produces valid and unique identifiers. \\ **Copying GUIDs is not allowed — not even between different tables or layers.**  Every point must have its own unique GUID, even if it belongs to a separate interpretation layer. Manually typed, duplicated, or reused values will not be accepted and may break uniqueness or cause conflicts in further processing.
  
-Hyphens must follow the 8-4-4-4-12 grouping+{{:geoscene3d:building_a_layered_model:recordspl.png}}
  
-The total length must be 38 characters, including the braces+---- 
 + 
 + 
 +==== Using the Database in GeoCloud LARCOS ==== 
 + 
 +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, ensuring that your changes are reflected and made available to other users or cloud-based workflows.
  
-**Important:** The GUID must be generated using code that produces valid and unique identifiers.\\ +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 above — GUIDs must never be reused, even between different interpretation layers. 
-**Copying GUIDs is not allowed — not even between different tables or layers.** Every point must have its own unique GUID, even if it belongs to a separate interpretation layer. Manually typed, duplicated, or reused values will not be accepted and may break uniqueness or cause conflicts in further processing.+====   ====
  
 ---- ----
-{{:geoscene3d:building_a_layered_model:recordspl.png|}}+
  
 ==== Using the Database in QGIS ==== ==== Using the Database in QGIS ====
Line 98: 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 ''Layer > Add Layer > Add SpatiaLite Layer'' +      * Start QGIS and open a project (new or existing). 
-  - Click "New" to connect to your ''.sqlite''  database file +  - **Drag the database into QGIS** 
-  - Select the database file and click "Open" +      * In your file system, locate the ''.sqlite''  database file. 
-  - QGIS will now list all spatial tables that contain geometry +      * Drag it directly onto the **QGIS map canvas**. 
-  - Select the table containing the interpretation points and click "Add" to load it into the map +  - **Confirm the layer is added** 
 +      * The point layer from the database loads automatically into the **Layers panel**  and is displayed on the map. 
 +  - **Inspect or style the layer** 
 +      * **​​​​​​​**Use the **Identify Features**, **Symbology**, or **Attribute Table**  tools to explore and work with the layer as needed.
 When loaded, QGIS will use the **EPSG code stored in the geometry metadata**  to display each point at the correct Easting and Northing coordinates on the map. When loaded, QGIS will use the **EPSG code stored in the geometry metadata**  to display each point at the correct Easting and Northing coordinates on the map.
  
  

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also, you acknowledge that you have read and understand our Privacy Policy. If you do not agree, please leave the website.

More information