You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user from Sweco (participant in the TKI training) experienced this unique issue when following the Tutorial.
From the GeoPackage tab he clicks "New" to open a new model. Unfortunately only the layer 'timml Domain:Domain" is created. The second layer, normally created by default, "timml Aquifer:Aquifer" is not created. There is no way to create it manually from the Elements tab. Reading an existing gpkg file (e.g. from the online tutorial) gives no issue.
he works with the latest version (qgis, deltaforge, plug-in)
saving the new model to another location or without spaces does not fix the issue.
his colleague doesn't encounter this issue, neither other participants during recent training events.
First conclusion: this is probably a machine (settings) related issue, but still worth checking.
Suggestions: check the python code for the statement where the Aquifer layer is created. Perhaps additions arguments or checks can prevent this error. Otherwise, get in touch with the user for a demo/debug session.
The text was updated successfully, but these errors were encountered:
A user from Sweco (participant in the TKI training) experienced this unique issue when following the Tutorial.
From the GeoPackage tab he clicks "New" to open a new model. Unfortunately only the layer 'timml Domain:Domain" is created. The second layer, normally created by default, "timml Aquifer:Aquifer" is not created. There is no way to create it manually from the Elements tab. Reading an existing gpkg file (e.g. from the online tutorial) gives no issue.
First conclusion: this is probably a machine (settings) related issue, but still worth checking.
Suggestions: check the python code for the statement where the Aquifer layer is created. Perhaps additions arguments or checks can prevent this error. Otherwise, get in touch with the user for a demo/debug session.
The text was updated successfully, but these errors were encountered: