We were using GeoServer 2.3.3 and loading everything via the REST API and decided to upgrade. However, loading any GDAL coverage fails when trying to publish the coverage. I can add the CoverageStore but when I try and add the Coverage it fails with an
…
IllegalArgumentException: The specified coverageName xxxxxx is not supported.
at org.geotools.coverage.grid.io.AbstractGridCoverage2DReader.getCoordinateReferenceSystem(AbstractGridCoverage2DReader.java:156)
It seems to only be doing this for GDAL coverages. Worked fine in 2.3.3 but fails in 2.4.4 and 2.5-RC2. This only happens when loading GDAL formats using the REST service, it loads GDAL fine when using the web interface.
Thanks
Ben
Hi Ben,
could you please open a JIRA for this by also attaching the REST request you are using and a sample to replicate it? (In case you can publicly share it).
Final question: which format is your dataset?
Please, let us know,
Daniele
···
Ing. Daniele Romagnoli
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Thu, Mar 6, 2014 at 9:21 PM, Ben Johnson <weagle08@anonymised.com> wrote:
We were using GeoServer 2.3.3 and loading everything via the REST API and decided to upgrade. However, loading any GDAL coverage fails when trying to publish the coverage. I can add the CoverageStore but when I try and add the Coverage it fails with an
…
IllegalArgumentException: The specified coverageName xxxxxx is not supported.
at org.geotools.coverage.grid.io.AbstractGridCoverage2DReader.getCoordinateReferenceSystem(AbstractGridCoverage2DReader.java:156)
It seems to only be doing this for GDAL coverages. Worked fine in 2.3.3 but fails in 2.4.4 and 2.5-RC2. This only happens when loading GDAL formats using the REST service, it loads GDAL fine when using the web interface.
Thanks
Ben
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
not sure how to do this… i don’t have a login for your JIRA that I’m aware.
The main data format I’ve been using is MrSID but it also fails on NITF formats also.
I don’t have an example request but unless the xml payload required for the rest service has changed between versions I’m sure it is correct.
···
On Fri, Mar 7, 2014 at 6:02 AM, Daniele Romagnoli <daniele.romagnoli@anonymised.com> wrote:
Hi Ben,
could you please open a JIRA for this by also attaching the REST request you are using and a sample to replicate it? (In case you can publicly share it).
Final question: which format is your dataset?
Please, let us know,
Daniele
Ing. Daniele Romagnoli
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Thu, Mar 6, 2014 at 9:21 PM, Ben Johnson <weagle08@anonymised.com> wrote:
We were using GeoServer 2.3.3 and loading everything via the REST API and decided to upgrade. However, loading any GDAL coverage fails when trying to publish the coverage. I can add the CoverageStore but when I try and add the Coverage it fails with an
…
IllegalArgumentException: The specified coverageName xxxxxx is not supported.
at org.geotools.coverage.grid.io.AbstractGridCoverage2DReader.getCoordinateReferenceSystem(AbstractGridCoverage2DReader.java:156)
It seems to only be doing this for GDAL coverages. Worked fine in 2.3.3 but fails in 2.4.4 and 2.5-RC2. This only happens when loading GDAL formats using the REST service, it loads GDAL fine when using the web interface.
Thanks
Ben
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi Ben,
Details on how to create a JIRA account are here: http://docs.geoserver.org/stable/en/user/introduction/gettinginvolved.html#bug-tracking
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
···
Cheers,
Jonathan
On 10 March 2014 21:09, Ben Johnson <weagle08@anonymised.com> wrote:
not sure how to do this… i don’t have a login for your JIRA that I’m aware.
The main data format I’ve been using is MrSID but it also fails on NITF formats also.
I don’t have an example request but unless the xml payload required for the rest service has changed between versions I’m sure it is correct.
Learn Graph Databases - Download FREE O’Reilly Book
“Graph Databases” is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
On Fri, Mar 7, 2014 at 6:02 AM, Daniele Romagnoli <daniele.romagnoli@anonymised.com> wrote:
Hi Ben,
could you please open a JIRA for this by also attaching the REST request you are using and a sample to replicate it? (In case you can publicly share it).
Final question: which format is your dataset?
Please, let us know,
Daniele
Ing. Daniele Romagnoli
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Thu, Mar 6, 2014 at 9:21 PM, Ben Johnson <weagle08@anonymised.com> wrote:
We were using GeoServer 2.3.3 and loading everything via the REST API and decided to upgrade. However, loading any GDAL coverage fails when trying to publish the coverage. I can add the CoverageStore but when I try and add the Coverage it fails with an
…
IllegalArgumentException: The specified coverageName xxxxxx is not supported.
at org.geotools.coverage.grid.io.AbstractGridCoverage2DReader.getCoordinateReferenceSystem(AbstractGridCoverage2DReader.java:156)
It seems to only be doing this for GDAL coverages. Worked fine in 2.3.3 but fails in 2.4.4 and 2.5-RC2. This only happens when loading GDAL formats using the REST service, it loads GDAL fine when using the web interface.
Thanks
Ben
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users