[EMAIL PROTECTED] ha scritto: > Hi, > > I noticed that most (all?) of the coverage data sets in Geoserver 1.5.0 beta2 > aren't working. If I use them to create a new coverage I get an exception > (see > below). For example, try creating a coverage that uses gtopo30. > > Looks like a problem with relative paths in the CoverageDataSets.
Yeah, that's something happening when you use the development version. And it's not something related to the operating system, but to the way the data dir is handled. In the release, the data dir is explicitly set. In the development version, the data dir is assumed to be the geoserver root, which is, in your case: /opt/apache-tomcat-5.5.20/webapps/geoserver and not /opt/apache-tomcat-5.5.20/webapps/geoserver/data People, we need to take a decision on this. If the data dir is the current, then coverages should be put in: /opt/apache-tomcat-5.5.20/webapps/geoserver/coverages and not in: /opt/apache-tomcat-5.5.20/webapps/geoserver/data/coverages Alternatively, we have to change the coverages location from file:/coverages/xxx.tiff to file:/data/coverages/xxx.tiff just like shapefiles are doing now. Final alternative, have the default data dir be: /opt/apache-tomcat-5.5.20/webapps/geoserver/data instead of: /opt/apache-tomcat-5.5.20/webapps/geoserver Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
