Summary of a small design sprint with @vmora and me, on possible evolutions to the configuration part of QGeoloGIS.
Here are some propositions to resolve some needs:
Save the ordering of columns (resp. rows for timeseries)
Current situation
Columns are stored in different arrays:
stratigraphy_configlog_measuresimagery_data
So it is not very clear how to order logs vs. stratigraphy or vs. imagery
Proposed change
Have two objects of high-level logs and timeseries that store source definitions as JSON arrays.
It will merge stratigraphy, log_measures and imagery_data into the same common array logs
A new key type allows the distinction between stratigraphy, logs, imagery and so on.
Store the symbology
Add a configuration key symbology that stores the raw QGIS QML symbology of each column / row
Remove the concept of "sub-selection"
The current code is designed to work with some data sources that have multiple measures stored in the same table (e.g. chemical analysis).
It is based on a logic of filtering and grouping on data:
- the "sub selection" combobox of the data selection dialog scans the source layer for unique values on a given field and allows the user to select one value
- then the selected value is used to filter data from the source layer
It was initially thought to allow flexibility in the configuration of data sources when the list of distinct values cannot be defined a priori.
However it adds too much complexity to the code base and does not fit very well with the simple idea of "1 measure = 1 data source".
Proposed change
Remove the concept of "sub selection".
Each single measure should be configured as a separate data source, with the possibility to add a QGIS filter (with the configuration key filter)
Replace layer IDs by (uri, name, provider)
Current situation
The configuration uses layer IDs to reference data sources.
Problem: it makes the configuration tied to a specific QGIS project file.
Proposed change
Change layer IDs to a triple (name, URI, provider)
This will also allow a trivial import / export function to have a separate configuration file (that can be put on git easier)
Merged plots
In order to merge different plots on the same column (or row), the configuration will allow to specify for each column an array of data sources.
See the complete example.
Additional metadata on graphs
- minimum value,
- maximum value,
- font title
- font size
- column / row width in pixels
Configuration example
# The "main" layer of points, to be replaced by (name, uri, provider)
"collar_7e814841_4cc9_495a_8ef6_9229fcfffb5e" :
{
"id_column": "id",
"name_column": "id",
# new keys for fonts
"font": Helvetica,
"font_size": 14,
"logs":[
{
# width (in pixels) of the column
"width": 200,
"name": "Stratigraphy",
# each data has one or more "series"
series = [
{
"provider": "postgres",
"uri":"dbname=....",
"type": stratigraphy,
"feature_ref_column": "hole_id",
"depth_from_column": "from_",
"depth_to_column": "to_",
"formation_code_column": "comments",
"rock_code_column": "code",
"formation_description_column": "comments",
"rock_description_column": "code",
"style": "formation_style.xml",
# new key to specify whether a column is visible or not
"visible": true
}],
{
"name": "Radiometry",
"width": 200,
"visible": false,
"series": [
{
"source": "radiometry_9d3b823d_d1b6_47a8_a1c2_dd0895a7262e",
"uom": "Gamma",
"feature_ref_column": "hole_id",
# min and max values
"min": null,
"max": null,
# new filter key
"filter":"element='Au'",
"type": "instantaneous_log",
# serialized QGIS symbology
"symbology": "xml_string",
"event_column": "from_",
"value_column": "gamma",
"visible": false
# possible addition to blend different plots during the merge
"blending_mode": "multiply"
}
]
},
{
"name": "Image",
"source": "radiometry_9d3b823d_d1b6_47a8_a1c2_dd0895a7262e",
"feature_ref_column": "hole_id",
"type": "imagery_log",
"event_column": "from_",
"value_column": "gamma",
"visible": false
},
],
"timeseries": []
Tasks
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent