-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DODS/OPeNDAP Driver Removal... Please don't #5173
Comments
Which driver do you use: the raster one or the vector one ? One issue we have is that our unit tests (https://github.com/OSGeo/gdal/blob/master/autotest/ogr/ogr_dods.py and https://github.com/OSGeo/gdal/blob/master/autotest/gdrivers/dods.py) don't work anymore due to test servers used initially not being available, and we (at least I) have no idea of how to test that driver and if it still works (the base assumption is that untested code is broken code). Are there public DODS servers somewhere ? |
Call for action to the mailing list audience: https://lists.osgeo.org/pipermail/gdal-dev/2022-January/thread.html#55348 |
Could the code be moved to the CRAN driver? If it is the only known user, seems possible. |
@vtdrfuka Please provide feedback regarding the questions posted in this ticket |
Let me review the test that is failing, as possibly it is just an outdated link. If this is the cause of the removal, it might be within my capability to get it to pass again! I will review a few options and test, with a response within a week; possibly linking the test to the OPeNDAP active development server which has been alive for quite some time. Also, Thank You for tagging me, for some reason the replies were hidden in my inbox! |
@vtdrfuka - please share your example sources, perhaps it's better done with NetCDF itself (I haven't used DODS via GDAL for a long time, but NetCDF generally works with URLs in GDAL - and often I disable the DODS driver, or use /vsicurl or NetCDF: to avoid conflation - perhaps we can find alternatives along those lines for you) |
@vtdrfuka can you provide some feedback ? Otherwise the driver will be removed as planned |
I'm unclear why the recipe tests this particular driver... Anyway I'm about to either remove that driver upstream (cf OSGeo/gdal#5173), or perhaps less radical option, just require to have a DODS_RASTER: prefix at the beginning of the connection string. In any case, if not changing this recipee, this would break the GDAL upstream CI task that uses this recipee to build Conda package from master.
I'm unclear why the recipe tests this particular driver... Anyway I'm about to either remove that driver upstream (cf OSGeo/gdal#5173), or perhaps less radical option, just require to have a DODS_RASTER: prefix at the beginning of the connection string. In any case, if not changing this recipee, this would break the GDAL upstream CI task that uses this recipee to build Conda package from master.
Pull request removing the DODS drivers: #5666 |
thanks @rouault ! |
Why reopening ? |
Hmm, I can't recall doing this -- must have been an errant click! |
Just opening the ticket to request that the DODS driver remains in the mix. We have dependencies on this driver in several CRAN packages and python libraries.
DODS/OPeNDAP
Driver short name: DODS
Driver is considered for removal in GDAL 3.5. You are invited to convert any dataset in that format to another more common one. If you need this driver in future GDAL versions, create a ticket at https://github.com/OSGeo/gdal (look first for an existing one first) to explain how critical it is for you (but the GDAL project may still remove it). T
The text was updated successfully, but these errors were encountered: