[gdal-dev] Re: HDF-EOS vs. GDAL: order of dimensions

[Lucena, Ivan]

Hi Ivan

Sorry for my poor example, but the concept is that users indeed should 
be able to override the *order* of the dimension at the end of the 
sub-dataset string.

That could be done is several different ways like ":y=100,x=100,z=100", 
just the order like in ":z,y,x" or something like that. It am not sure 
how that should work better. My suggestion doesn't go that far. :)

Best regards,

Ivan


Ivan Shmakov wrote:
>>>>>> Lucena, Ivan <ivan.lucena at pmldnet.com> writes:
> 
>  >> I would like to have the last option implemented. This requires addition
>  >> of the open option concept to raster core of GDAL.
> 
>  > Can we add the user-defined dimension request to the end of the
>  > subdataset name string?
> 
>  > HDF4_SDS:subdataset_type:file_name:subdataset_index:user-defined-dimension
> 
>  > Ex:
> 
>  > gdalinfo HDF4_SDS:MODIS_L1B:my-hdf-file.hdf:2:134x2040
>  > ^^^^^^^^
> 
>  > That will not require any changes in the GDALOpen() API.
> 
> 	Please note that the point is not to override dimensions, but to
> 	override their order.  If the data is, say, 100x100x100, its
> 	spatial dimensions are 100x100, but it obviously does matter
> 	which 100 are for X, Y and the bands.
> 
> 	It may be that it's HDF4_SDS:...[:MAY-BE-OPTIONS...] thing that
> 	needs to be implemented, but GDALOpen () seems to be rather
> 	overloaded already.
> 
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
> 
>