Hi Daniele and Geoserver-Users,
I have built now a workaround to my problem. NetCDF with custum dimensions
can be now implemented to Geoserver, even that it is not implented directly,
as described in the Geosolution slides or examples shown (Polyphemus,
windfields e.g.).
https://geoserver.geo-solutions.it/edu/en/multidim/mosaic_config/netcdf_mosaic.html
http://osgeo-org.1560.x6.nabble.com/Netcdf-import-error-Netcdf-supported-formats-td5370365.html
I could not reproduce these solutions. If anybody has still some hints on
this, I would still appreciate feedback.
So instead of having the custum dimensions, like wavelength, versionnumber,
etc within the netCDF-file, I was separating the Files into several small
files, each consisting basically only of one layer with regular dimensions
lat/lon.
Custom dimension are included then in the filenaming only.
e.g. file_YYYYMMDD_WAVELENGTH_VERSIONNO.nc
Now custom dimensions could be defined properly with Collectors in the
indexer.xml.
It can be, that the original file was too big (1.2GB per file).
Now the layers are separated in several small layer-netCDF-files of size
~145KB.
Question to the developers: Is there a size limit for netCDF-files existing?
Or implementation of custom dimensions within one single netCDF was not
working properly.
----------------------------------------------------------------
*Summary of my solution:*
Custom dimension are included in the filenaming externally.
e.g. file_YYYYMMDD_WAVELENGTH_VERSIONNO.nc
for each custom dimension the domain is defined, referring to a collector
(indexer.xml)
<domain name="wavelength">
<attributes><attribute
ref="wavelengthCollector">wavelength</attribute></attributes>
</domain>
…
the custom dimension is named in the scheme (indexer.xml)
<schema name="default" >
<attributes>the_geom:Polygon,location:String,imageindex:Integer,time:java.util.Date,wavelength:java.lang.Integer,version:java.lang.String</attributes>
</schema>
…
the layer variable refers to the custom dimension domain (indexer.xml)
<coverage>
<name>variable</name>
<schema ref="default"></schema>
<domains>
<domain ref="time" />
<domain ref="wavelength" />
…
the collector defines the dimension extraction from filename (indexer.xml)
<collector name="wavelengthCollector">
<value>[0-9]{3}(?=\.)</value>
<spi>FloatFileNameExtractorSPI</spi>
<mapped>wavelength</mapped>
</collector>
…
an auxiliary .xml has the same scheme stored
<parameter name="AuxiliaryFile" value="_auxfile.xml" />
Request of custom dimensions is then with
&dim_wavelength=XX
----------------------------------------------------------------
Kind regards
MiriamK
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
