hi Even, thanks for the quick reply - seems to make sense and chimes with
what we've found - certainly in the short term I think we can use
gml:PointProperty to get us where we want to go The Marine S-100 model
adds an association to an information type into the geometry primitive by
extension
Thanks, Even for the quick answer!
I tried it but I get "ERROR 6":
[nene:gdal/gdal/apps] hyoklee% ./gdalmdimtranslate -array
name='/HDFEOS/SWATHS/MOP02/Data
Fields/RetrievedSurfaceTemperature',view=\[:,0\]
~/NASAHDF/MOP02J-20131129-L2V17.8.3.he5 test.tif
ERROR 6: Unsupported number of dimen
On jeudi 25 juillet 2019 19:12:02 CEST Joe Lee wrote:
> I'm glad that this motion has passed!
>
> I got one question after reviewing Even's latest code and RFC.
>
> Does it consider a case that subsets 1d dataset from 2d dataset [1]?
> The organization of MOP02J (1-D SWATH) and its shape is like
I'm glad that this motion has passed!
I got one question after reviewing Even's latest code and RFC.
Does it consider a case that subsets 1d dataset from 2d dataset [1]?
The organization of MOP02J (1-D SWATH) and its shape is like below:
dset[2][n_points]
lat[n_points]
lon[n_points]
I wish I co
Jonathan,
Identification of geometries could probably be improved in the driver (was
mostly tested / developed for Inspire data models, and in my memories of the
ones that were tested, plain GML geometries were used). That said, if your
s100:PointPropertyType is just a plain gml:PointPropertyTy
Hi everyone,
I'm using the GMLAS driver in connection with the OGCs pilot project on
maritime limits and boundaries. The first part of the project is the
creation of an application schema and we're using the IHO S-100 profile of
GML. What I've noticed is that the GMLAS driver won't recognise geome
