Thanks for the information.
My netCDF files are CF-compliant and are readable and geo-locatable in all
of the netCDF tools I am using. When you mention world files, what do you
mean? Do you mean that the netCDF data be CF-compliant and be geo-located
or something else entirely? If it is a separate file, can you refer me to
an example? I have seen GeoServer sometimes create hidden (i.e.,
".20170331T1615Z_3376911e8b9a4c789001ddeb28f4a90e75a14444") directories but
not sure if this is the same thing. Are these the automatically created
files Adam is referring to? If they are separate files, is there a way to
easily generate them from netCDF files?
If I am understanding your responses it sounds like the tiling behavior
should work with world files (possibly generated by GeoServer) and by
having correct information in
user_projections/netcdf.projections.properties, indexer.xml, ancillary.xml,
and datastore.properties in the directory as usual. GeoServer will then
automatically detect that these netCDF files are geographic tiles and
create a store/layer appropriately.
Thanks for the reference to the REST API, but I am starting out small with
a handful of files (eight files) before I expand to the full set. However,
each time I try pointing GeoServer to my directory when adding a store
(through the web UI) it has repeatedly failed on a variety of issues
depending on small changes in my input files and/or configuration. The
world files might be the problem for me, but otherwise it seems likely that
there are other errors that may be happening before the geographic tiling
is performed.
Aaron
On Thu, Apr 6, 2017 at 8:32 PM, Adam Steer <[email protected]> wrote:
> Hi Aaron - with netCDF files I’ve used a postGIS store to index the data
> and then create an imagemosaic store.
>
> I’ve been meaning to test a very large mosaic - which needs some care to
> build [1]. My process is described after Daniele’s comments - it works fine
> for a few hundred tiles but not for many thousands with interesting
> reference systems :)
>
> But in short, yes, and with netCDF, and with a world file for each
> (although Geoserver will create it’s own indexing parts - so the data
> directory needs to be writable by tomcat. We link files from our RO
> filesystem into someplace on the geoserver host to enable this)
>
> Cheers
>
> Adam
>
> [1] https://sourceforge.net/p/geoserver/mailman/message/35736574/
>
>
> --
> Dr. Adam Steer
> Earth systems data service specialist
> National Computational Infrastructure
> Leonard Huxley Building, Mills Road
> The Australian National University
> Acton ACT 2600 Australia
>
> [email protected]
> +61 2 6125 1413
> http://nci.org.au
>
>
>
> > On 7 Apr 2017, at 12:44 am, Jason Newmoyer <[email protected]>
> wrote:
> >
> > As long as the tiles have geographic metadata (world file, geotiff, etc)
> then ImageMosaic will automatically index them with a shapefile. You just
> point the new store to the directory containing all of the tiles when
> creating it.
> >
> >
> > Jason Newmoyer
> > Newmoyer Geospatial Solutions
> > 843.606.0424
> > [email protected]
> >
> >
> >
> > On Wed, Apr 5, 2017 at 5:40 PM, Aaron Braeckel <[email protected]>
> wrote:
> > Hello,
> >
> > I am trying to determine if ImageMosaic can be used to gather and
> re-assemble tiles into a virtual mosaic. I am using ImageMosaic (as
> opposed to ImagePyramid) since we need to aggregate our weather data across
> time and elevation and other custom dimensions. The files I am receiving
> have tile indices indicating their physical location relative to one
> another, but I have yet to find any ImageMosaic indexer option to aggregate
> them into a geographic mosaic.
> >
> > For example I have several files with information similar to the
> following, where "T01" refers to the tile index from 1 to 4 (T01 is upper
> left, T02 is upper right, etc.):
> >
> > 20170331T1645Z_SITE_FIELD_T01.nc
> >
> > 20170331T1645Z_SITE_FIELD_T02.nc
> >
> > 20170331T1645Z_SITE_FIELD_T03.nc
> >
> > 20170331T1645Z_SITE_FIELD_T04.nc
> >
> > ...
> >
> >
> >
> > In several areas of the GeoServer documentation it seems to be saying
> that this can be done but I have not found any configuration mechanism to
> do so. Is there any way to configure the indexer.xml file to reassemble
> these files into a single, virtual dataset? While I can re-assemble these
> tiles into the mosaic myself and use those in GeoServer it is not the most
> desirable option due to the data volumes.
> >
> > Thanks!
> > Aaron
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Geoserver-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
> _________________________________________
> > Geoserver-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
