[gdal-dev] Passing open options along dataset name in a string ?

[Even Rouault]

Sean,

What GDN stands for: GDAL Dataset Name ?

> The URN or GDN version might look something like the thing below, using ?+
> and ?= [3] to identify vsi and driver option sections
> 
> gdn:curl:csv:
> example.com/foo.csv?a=1&b=2?+max_retry=5?=autodetect_type=yes&keep_geom_colu
> mns=no

The http or https protocol should be captured too.

> Bringing a little more order to how we name and address datasets was on my
> todo list at the start of the year, but then 2020 went into a spiral. I
> don't think rasterio's "zip+s3" etc approach is the best.

I see fsspec has a syntax for chaining filesystems in
https://filesystem-spec.readthedocs.io/en/latest/features.html#url-chaining

Another particularity we have in GDAL is that the dataset name might be almost 
anything. Most of the time, it is a regular file path, or some /vsi path. But 
sometimes, it can be JSON content (the GeoJSON driver accepts the content to 
be directly provided as the dataset name), or XML (VRT, WMS drivers).
We have also the subdataset syntax "HDF5:foo.hdf:my_variable"

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com