Hi Jukka,
On Tue, Nov 17, 2020 at 2:57 AM jratike80 <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> Hi,
>
> I have done some helpdesk work within the GDAL community and I know well
> that the open options and config options are confusing. I also know that
> they exists for a reason but
> The variation of subdataset syntax among drivers is a bug, let's try to fix
> this.
>
> It seems to me that the internet way to address subdatasets would be to use
> a # URL fragment. But since most of our formats and the servers that serve
> files of these formats are not aware, we may have to
Hi,
I have done some helpdesk work within the GDAL community and I know well
that the open options and config options are confusing. I also know that
they exists for a reason but simplified and uniform way to use them would be
nice.
Some comments on comments:
>> gdalinfo my.tif -oo
Hi Even,
On Wed, Nov 4, 2020 at 9:01 AM Even Rouault
wrote:
> > > 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
Even,
On Wed, Nov 4, 2020 at 3:40 AM Even Rouault
wrote:
> Sean,
>
> What GDN stands for: GDAL Dataset Name ?
>
Yes. I just made that up on the spot. Think of it as a GDAL or FOSS4G
specific namespace. Until now, GDAL has been using symbols like WFS: and
HDF5: in the global namespace, which
> > 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
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=2?+max_retry=5?=autodetect_type=yes_geom_colu
> mns=no
The http or
Even,
On Mon, Nov 2, 2020 at 1:16 PM Even Rouault
wrote:
> Sean,
>
> > We already have a way of passing "open" options for vsicurl:
> >
> https://gdal.org/user/virtual_file_systems.html#vsicurl-http-https-ftp-files
> > -random-access. What about reusing that conceptual framework and syntax?
> >
Hi Even,
On Mon, Nov 2, 2020 at 3:10 AM Even Rouault
wrote:
> Hi,
>
> I've heard interest in having the capability of passing a GDAL dataset
> name
> and its open options in a single string, since this is easier for storing.
>
> The syntax could be a JSON serialized string prefixed by
Sean,
> We already have a way of passing "open" options for vsicurl:
> https://gdal.org/user/virtual_file_systems.html#vsicurl-http-https-ftp-files
> -random-access. What about reusing that conceptual framework and syntax?
>
> For example:
>
> "foo.csv?AUTODETECT_TYPE=YES_GEOM_COLUMNS=NO"
I
Hi,
I've heard interest in having the capability of passing a GDAL dataset name
and its open options in a single string, since this is easier for storing.
The syntax could be a JSON serialized string prefixed by GDAL_JSON: to avoid
any ambiguity with drivers that would accept JSON as a
11 matches
Mail list logo
