Hello,
i am running version 2.12.2, and am trying to add a RPFTOC Store from a
local drive on my VM, whenever I do I get "Could not list layers for this
store, an error occurred retrieving them: Unsupported input type"
The only way I am able to import map data is to move the data to the
GeoServer Data_Dir which I have on the same drive as the map data.
Here are a few lines from the error
2018-02-26 11:55:36,590 WARN [geoserver.catalog] - Unable to convert
coverage URL to a URI, attempting to use it as a path
2018-02-26 11:55:36,590 INFO [geoserver.web] - Getting list of coverages for
saved store file://M:\AZ\_RPF\CB01\CIB01_31n\RPF\A.TOC
Caused by: java.lang.IllegalArgumentException: Unsupported input type
While adding the store please try Jukka's advice: "User must change the backslashes to forward slashes manually."
Kind regards,
Ben.
On 27/02/18 09:00, Jbake wrote:
Hello,
i am running version 2.12.2, and am trying to add a RPFTOC Store from a
local drive on my VM, whenever I do I get "Could not list layers for this
store, an error occurred retrieving them: Unsupported input type"
The only way I am able to import map data is to move the data to the
GeoServer Data_Dir which I have on the same drive as the map data.
Here are a few lines from the error
2018-02-26 11:55:36,590 WARN [geoserver.catalog] - Unable to convert
coverage URL to a URI, attempting to use it as a path
2018-02-26 11:55:36,590 INFO [geoserver.web] - Getting list of coverages for
saved store file://M:\AZ\_RPF\CB01\CIB01_31n\RPF\A.TOC
Caused by: java.lang.IllegalArgumentException: Unsupported input type
------------------------------------------------------------------------------
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
Thank you, that was a good bandaid to the issue. And I appreciate the link
to the bug report. I may have to go back to 2.10 since this hasnt been
resolved for a year. My users wont want to do this manually, I know they
will complain otherwise.
Thank you, that was a good bandaid to the issue. And I appreciate the link
to the bug report. I may have to go back to 2.10 since this hasnt been
resolved for a year. My users wont want to do this manually, I know they
will complain otherwise.
Will do Ian, I’m going to see if the developers on my team can find a quick
fix. I hope they can spare an hour to take a look and fix it since we want
to use geoserver for our WMS needs..
If we do get a fix I’ll update and figure out how I can submit the change.