if drill data layer source is a database, chose file location for output, or use project directory

[damstep]

we store drillhole data in an mssql database, which means there is no location of the file on the hdd, so when the plugin tries to save the output to the collar file location it cant do it and the resulting table shows an unavailable layer.

Would it be possible to check the datasource and if it is a database default to either the project home or request a file location?

I understand the workaround of saving all database tables to a geopackage and then using that to desurvey etc, but it defeats the purpose of having live database links.

i know that this plugin is deprecated in favour of openlog (which still cannot do sections), but it makes no sense to create a second drill database as required by openlog to use it, as this would again fail to retain a live link to the paretn database and leave open the likelihood of having mutliple versions of the truth.

[rolandhill]

I'm not sure where you got the information that this plugin is deprecated in favour of OpenLog, but it is not and is in use by tens of thousands of people. I'm very busy writing a 3D visualisation application at the moment and don't have time to modify Geoscience to handle data from MSSQL. It's easy to set up a system where you simply update your local files (this can even be scripted and done daily) then just rerun the drillhole processing steps in Geoscience, which you would have to do anyway. Roland Hill Director Four Winds Technology Pty Ltd Spatial Integration <https://www.spatialintegration.com/>

…

On Thu, 28 Aug 2025 at 14:48, damstep ***@***.***> wrote: *damstep* created an issue (rolandhill/geoscience#24) <#24> we store drillhole data in an mssql database, which means there is no location of the file on the hdd, so when the plugin tries to save the output to the collar file location it cant do it and the resulting table shows an unavailable layer. Would it be possible to check the datasource and if it is a database default to either the project home or request a file location? I understand the workaround of saving all database tables to a geopackage and then using that to desurvey etc, but it defeats the purpose of having live database links. i know that this plugin is deprecated in favour of openlog (which still cannot do sections), but it makes no sense to create a second drill database as required by openlog to use it, as this would again fail to retain a live link to the paretn database and leave open the likelihood of having mutliple versions of the truth. — Reply to this email directly, view it on GitHub <#24>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPOEQ26K4CJARXK2FPGJ2D3P2CZJAVCNFSM6AAAAACFAFLGRKVHI2DSMVQWIX3LMV43ASLTON2WKOZTGM3DCNZXHE2DKMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>