I posted a message several days ago about a "Translator Error" and never
really reached a resolution. I have moved backwards though and found that on
a completely virgin 1.5.4 installation I get the following message during
startup. This seems to be the crux of my problems. Does anyone know how this
works?
Thanks.
10486 [WARNING] DefaultFactory - Unavailable authority factory: European
Petroleum Survey Group
org.opengis.referencing.FactoryException: Failed to connect to the EPSG
database.
--
View this message in context: http://www.nabble.com/Failed-to-connect-to-the-EPSG-database.-tf4731227.html#a13528435
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
Kevin@anonymised.com ha scritto:
I posted a message several days ago about a "Translator Error" and never
really reached a resolution. I have moved backwards though and found that on
a completely virgin 1.5.4 installation I get the following message during
startup. This seems to be the crux of my problems. Does anyone know how this
works?
Thanks.
10486 [WARNING] DefaultFactory - Unavailable authority factory: European
Petroleum Survey Group org.opengis.referencing.FactoryException: Failed to connect to the EPSG
database.
I answered you yesterday but apprently the answer did not get to the mailing list (I was having internet connection problems in fact).
Here it is again:
--------------------------------------------------------------------
GeoServer uses the official EPSG database for managing srs codes.
Now, the database is an hsql one, that gets created on the fly
in the temp directory under $yourJavaTempDirectory/GeoTools/Databases/Hsql.
When running GeoServer out of Jetty the temp directory is usually
the current user temp, whilst if you're running GeoServer in tomcat
it's usually $tomcatdir/temp.
Try to find the directory and wipe out the GeoTools folder, then
start GeoServer, it should recreate the database from scratch and
then you should be ok.
Let me know if this works.
Cheers
Andrea
I am interested in constructing a WFS GetFeature call that will return all features that are contained within another feature. I know that I can use the <ogc:Within> filter and specify the geometry of the containing feature, but I was wondering if it was possible to replace the geometry with a reference to the feature and its geometry. The reason is that, the geometry for the containing feature is quite large and I did not want to first request it with a GetFeature and then submit a second GetFeature with its geometry contained in the second request. Does this make any sense? Any ideas if this is possible and how to do this?
Thanks, David
--
David R Robison
Open Roads Consulting, Inc.
708 S. Battlefield Blvd., Chesapeake, VA 23322
phone: (757) 546-3401
e-mail: drrobison@anonymised.com
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com
book: http://www.xulonpress.com/book_detail.php?id=2579
Hi David,
Your request makes a lot of sense. But unfortunately I do not believe
there is an easy way to do this. In general we lack the ability to do
linking among features. And I could be wrong but I dont think the filter
spec really supports that.
The only thing that *might* work... and this a big stretch here is a
filter function. You could possibly write a custom function that could
take the fid of the feature whose geometry you would like to you use as
a constraint, as the server for it, and then suck out the geometry. But
that would be quite a bit of work.
Perhaps someone else might have a better idea for it. Again this sort of
thing falls into the realm of "WPS", i am not saying the OGC spec itself
but more the ability to invoke "operations" such as these on the server
side.
-Justin
David R Robison wrote:
I am interested in constructing a WFS GetFeature call that will return
all features that are contained within another feature. I know that I
can use the <ogc:Within> filter and specify the geometry of the
containing feature, but I was wondering if it was possible to replace
the geometry with a reference to the feature and its geometry. The
reason is that, the geometry for the containing feature is quite large
and I did not want to first request it with a GetFeature and then submit
a second GetFeature with its geometry contained in the second request.
Does this make any sense? Any ideas if this is possible and how to do this?
Thanks, David
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira wrote:
Hi David,
Your request makes a lot of sense. But unfortunately I do not believe
there is an easy way to do this. In general we lack the ability to do
linking among features. And I could be wrong but I dont think the filter
spec really supports that.
The only thing that *might* work... and this a big stretch here is a
filter function. You could possibly write a custom function that could
take the fid of the feature whose geometry you would like to you use as
a constraint, as the server for it, and then suck out the geometry. But
that would be quite a bit of work.
Hi,
at a recent meeting of the international GeoSciML testbed we ran into a similar set of issues, in this case we wanted to traverse feature relationships where the link is logical, not spatial. We can do this with the community-schema modules to an extent, but to generalise (and in particular allow for recursive traversal of unknown depths) we decided we'd need to use functions.
I cant find any docs or discussions on how to implement a function plugin, through I did find this useful doc on how to invoke them..
http://docs.codehaus.org/display/GEOSDOC/Filter+Function+tutorial+(unfinished)
is there anything out there that describes how to link a database function to a geoserver function?
Rob Atkinson
Perhaps someone else might have a better idea for it. Again this sort of
thing falls into the realm of "WPS", i am not saying the OGC spec itself
but more the ability to invoke "operations" such as these on the server
side.
-Justin
David R Robison wrote:
I am interested in constructing a WFS GetFeature call that will return all features that are contained within another feature. I know that I can use the <ogc:Within> filter and specify the geometry of the containing feature, but I was wondering if it was possible to replace the geometry with a reference to the feature and its geometry. The reason is that, the geometry for the containing feature is quite large and I did not want to first request it with a GetFeature and then submit a second GetFeature with its geometry contained in the second request. Does this make any sense? Any ideas if this is possible and how to do this?
Thanks, David
I ended up stracing startup.sh and found that the directory below was almost
correct. On my linux box this was in /tmp. Thanks for your help.
Kevin
drwxr-xr-x 3 geoserver geoserver 4096 Nov 2 08:35 Geotools
drwxr-xr-x 2 geoserver geoserver 4096 Nov 2 16:50 hsperfdata_geoserver
drwxr-xr-x 2 geoserver geoserver 4096 Nov 2 08:35 hsperfdata_root
drwxr-xr-x 3 geoserver geoserver 4096 Nov 2 16:50
Jetty_0_0_0_0_8080__geoserver_
[geoserver@anonymised.com tmp]$ ls Geotools/Databases/HSQL/
EPSG.data EPSG.properties EPSG.script
aaime wrote:
Kevin@anonymised.com ha scritto:
I posted a message several days ago about a "Translator Error" and never
really reached a resolution. I have moved backwards though and found that
on
a completely virgin 1.5.4 installation I get the following message during
startup. This seems to be the crux of my problems. Does anyone know how
this
works?
Thanks.
10486 [WARNING] DefaultFactory - Unavailable authority factory: European
Petroleum Survey Group
org.opengis.referencing.FactoryException: Failed to connect to the EPSG
database.
I answered you yesterday but apprently the answer did not get to the
mailing list (I was having internet connection problems in fact).
Here it is again:
--------------------------------------------------------------------
GeoServer uses the official EPSG database for managing srs codes.
Now, the database is an hsql one, that gets created on the fly
in the temp directory under
$yourJavaTempDirectory/GeoTools/Databases/Hsql.
When running GeoServer out of Jetty the temp directory is usually
the current user temp, whilst if you're running GeoServer in tomcat
it's usually $tomcatdir/temp.
Try to find the directory and wipe out the GeoTools folder, then
start GeoServer, it should recreate the database from scratch and
then you should be ok.
Let me know if this works.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
View this message in context: http://www.nabble.com/Failed-to-connect-to-the-EPSG-database.-tf4731227.html#a13557153
Sent from the GeoServer - Dev mailing list archive at Nabble.com.