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:upgrading-access-interpretation-database [2025/09/15 11:31] – [Introduction] dev | geoscene3d:building_a_layered_model:upgrading-access-interpretation-database [2025/09/15 12:05] (current) – [Stand-Alone Conversion] dev | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Access-based interpretation databases are no longer supported in Geocene3D and have been replaced by the SpatiaLite format. To continue working with existing data, a one-time conversion to SpatiaLite is required. | Access-based interpretation databases are no longer supported in Geocene3D and have been replaced by the SpatiaLite format. To continue working with existing data, a one-time conversion to SpatiaLite is required. | ||
| - | During the conversion, a new SpatiaLite .sqlite file is created, and all valid interpretation data is copied into it. Once the conversion is complete, the new database is ready for use — you can start editing | + | During the conversion, a new SpatiaLite .sqlite file is created, and all valid interpretation data is copied into it. Once the conversion is complete, the new database is ready for use — you can start edit sessions and add new interpretation points as needed. |
| Line 13: | Line 13: | ||
| 2. Find the Access database | 2. Find the Access database | ||
| - | * In the source list, locate the row with Type: Access | + | * In the source list, locate the Access |
| 3. Right-click and convert | 3. Right-click and convert | ||
| Line 20: | Line 20: | ||
| 4. Configure conversion settings | 4. Configure conversion settings | ||
| - | * In the SpatiaLite Conversion dialog: | ||
| * Click Points EPSG... and choose the appropriate EPSG code | * Click Points EPSG... and choose the appropriate EPSG code | ||
| * Set the Destination File Name for the new .sqlite file | * Set the Destination File Name for the new .sqlite file | ||
| Line 28: | Line 27: | ||
| 5. Check result in Source Manager | 5. Check result in Source Manager | ||
| * A new SpatiaLite source is added to the list | * A new SpatiaLite source is added to the list | ||
| - | * The original Access source remains but is no longer used | ||
| * Any linked point layers (e.g., L1, L2) are now automatically connected to the new SpatiaLite file | * Any linked point layers (e.g., L1, L2) are now automatically connected to the new SpatiaLite file | ||
| {{: | {{: | ||
| + | * The original Access source remains but is no longer used. It can be removed manually | ||
| + | * Optional: Select "Used by" to see which interpretations point are now using the new Spatialite file | ||
| {{: | {{: | ||
| 6. Start editing | 6. Start editing | ||
| * The project is now ready to continue with the converted database | * The project is now ready to continue with the converted database | ||
| - | * You can start a new edit session | + | * You can start a new edit session to add points to the new database |
| {{: | {{: | ||
| Line 43: | Line 43: | ||
| * Only tables with UID, X, Y, and Z columns are included in the conversion | * Only tables with UID, X, Y, and Z columns are included in the conversion | ||
| * These columns are required for a table to be recognized as an interpretation table | * These columns are required for a table to be recognized as an interpretation table | ||
| - | * For each valid table, all fields are preserved in the SpatiaLite output | + | * For each valid table, all standard |
| - | * Tables are included even if they were not imported as point layers in the Layer Manager | + | * Tables are included even if they were not point layers in layer manager |
| * This ensures a complete and independent conversion of all valid interpretation tables | * This ensures a complete and independent conversion of all valid interpretation tables | ||
| ===== Coordinate Handling ===== | ===== Coordinate Handling ===== | ||
| - | * During conversion, the X and Y columns from Access are merged into a single geometry field named XYPoint | + | * During conversion, the X and Y columns from Access are merged into a single geometry field named XYPoint |
| * This field is stored as a 2D POINT with the selected EPSG code, used for correct placement in external GIS tools (e.g., QGIS) | * This field is stored as a 2D POINT with the selected EPSG code, used for correct placement in external GIS tools (e.g., QGIS) | ||
| * The Z value is kept as a separate column representing elevation | * The Z value is kept as a separate column representing elevation | ||
| Line 54: | Line 54: | ||
| ===== Stand-Alone Conversion ===== | ===== Stand-Alone Conversion ===== | ||
| - | * Access sources can be converted immediately after being added, even if no tables are imported | + | * Access sources can be converted immediately after being added to the Source Manager, even if no tables are imported as interpretation points |
| - | * In this case, the source appears | + | * This enables a fast, stand-alone upgrade to SpatiaLite without any modelling |
| - | * This enables a fast, stand-alone upgrade to SpatiaLite without any project | + | * After conversion, the new .sqlite file can be used in [[modelsetup-stepbystep|Setup Data for Modeling]] to add interpretation points. Select "Use existing database" |
| - | * After conversion, the new .sqlite file can be used in Setup Data for Modeling to add interpretation points | + | |