The SpatiumCube open source initiative "offers an integration framework of software technologies than can help users and programmers with the development of Spatial Data Infraestructures (SDIs) and their services." Their first released product is CatalogCube - a CSW 2.0.2 service implementation and CSW test client.
ESSI-Lab offers a new release of their graphical GI-go GeoBrowser client to their GI-cat CSW server. According to their web site, the GI-go client supports:
WCS 1.0, 1.1
WMS 1.3.0, 1.1.1
WFS 1.0.0
CSW 2.0.2 Core, AP ISO 1.0, ebRIM/CIM, ebRIM/EO
THREDDS 1.0.1, 1.0.2
Accessors for GeoNetwork (tested with versions 2.2.0 and 2.4.1) and deegree (tested with version 2.2) catalog services
OpenSearch accessor
GENESI RDF OpenSearch accessor
Download and visualization of XML metadata
CDI 1.04, 1.3
GI-cat 5.x, 6.x
GBIF
The GI-cat server is advertised to support the following profiles:
Profilers (CSW ebRIM CIM 2.0.2, CSW ebRIM EO 2.0.2)
Steps 2 and 3 are specific to Ubuntu 9.04 (Jaunty). Ubuntu 9.10 (Karmic) already includes PostgreSQL 8.4.1. You can check the PostgreSQL version(s) of your APT repositories with the following command:
Dominic Owen has been working with the Catalog Connector project to add some new capabilties and features to the CatalogConnector CSW client. The objective is to produce a light-weight client that can be used to search a wide variety of CSW services. Dominic has implemented functionality to allow the client to get capabilities from the catalogs it has been configured to search. This operation serves first to determine which services are currently 'live', and to obtain a list of the the available outputSchemas offered by the service. Currently, we have xslt transforamtions to produce html browse pages for results from the CSW default 'csw:record' schema , and from ISO19139 MD_Metadata schema. Other xslt's may be added to format xml results in other output formats. The User interface allows selection from the available output formats for each catalog, or viewing of the raw xml search result.
Catalog connector uses a Java Servlet as a middleware component to do most of the processing required. This keeps the html client on the users browser very light weight. Communication between the actual desktop web client and the CSW servlet actually uses JSON. The CSW servlet communicates with other CSW servers using the CSW protocols.
GeoNetwork on tomcat doesn't need a ridiculous amount of memory! :-) Your error message indicates you need to increase the size of the memory allocated to the permanent generation (seems like you've been increasing general heap space which won't fix this).
Use:
-XX:MaxPermSize=128m
option when you start the service in tomcat.
I think 2.4.1 comes with 128m set by default but that is set in the jetty startup script and you probably haven't got that in your tomcat service startup.
Doing some searches on "PermGen error" should bring descriptions of what the permanent generation is etc.
I haven't read it all yet, but at first glance it sounds to me like
the "smart clients" approach to data interoperability. Instead of
focusing work on generating data in standard formats, clearly identify
the interoperable functionality that you want, and build clients
capable of performing those functions on data thrown at it in any way,
shape, or form.
The SpatiumCube open source initiative "offers an integration framework of software technologies than can help users and programmers with the development of Spatial Data Infraestructures (SDIs) and their services." Their first released product is CatalogCube - a CSW 2.0.2 service implementation and CSW test client.
ESSI-Lab offers a new release of their graphical GI-go GeoBrowser client to their GI-cat CSW server. According to their web site, the GI-go client supports:
The GI-cat server is advertised to support the following profiles:
If you encounter a permission error in Tomcat, the following permission changes may fix it:
Add bold text to the end of the file:
Reboot Tomcat
Steps 2 and 3 are specific to Ubuntu 9.04 (Jaunty). Ubuntu 9.10 (Karmic) already includes PostgreSQL 8.4.1. You can check the PostgreSQL version(s) of your APT repositories with the following command:
Apparently, keyserver.ubuntu.com is frequently down (https://answers.launchpad.net/ubuntu/+question/81538) but it may be your firewall.
Make sure that the outbound port 11371 is open for your Linux machine.
Dominic Owen has been working with the Catalog Connector project to add some new capabilties and features to the CatalogConnector CSW client. The objective is to produce a light-weight client that can be used to search a wide variety of CSW services. Dominic has implemented functionality to allow the client to get capabilities from the catalogs it has been configured to search. This operation serves first to determine which services are currently 'live', and to obtain a list of the the available outputSchemas offered by the service. Currently, we have xslt transforamtions to produce html browse pages for results from the CSW default 'csw:record' schema , and from ISO19139 MD_Metadata schema. Other xslt's may be added to format xml results in other output formats. The User interface allows selection from the available output formats for each catalog, or viewing of the raw xml search result.
Catalog connector uses a Java Servlet as a middleware component to do most of the processing required. This keeps the html client on the users browser very light weight. Communication between the actual desktop web client and the CSW servlet actually uses JSON. The CSW servlet communicates with other CSW servers using the CSW protocols.
Stay tuned for ongoing development.
Here is my current favorite one-page Unix/Linux command reference cheat sheet. They also came out with an Ubuntu reference cheat sheet version. They probably only changed the color scheme to match Ubuntu's ;)
Check the GeoNetwork developer Wiki for examples in other languages http://trac.osgeo.org/geonetwork/wiki/HowToDoCSWTransactionOperations
Simon Pigot came to the rescue and posted the following solution:
Hi Wolfgang,
GeoNetwork on tomcat doesn't need a ridiculous amount of memory! :-) Your error message indicates you need to increase the size of the memory allocated to the permanent generation (seems like you've been increasing general heap space which won't fix this).
Use:
-XX:MaxPermSize=128m
option when you start the service in tomcat.
I think 2.4.1 comes with 128m set by default but that is set in the jetty startup script and you probably haven't got that in your tomcat service startup.
Doing some searches on "PermGen error" should bring descriptions of what the permanent generation is etc.
Cheers,
Simon
http://trac.osgeo.org/geonetwork/wiki/HowToRunUnderTomcat
http://trac.osgeo.org/geonetwork/wiki/CSW202Improvements
useful?
Linked from that blog post is an interesting paper:
http://www.eecs.berkeley.edu/~franklin/Papers/dataspaceSR.pdf
I haven't read it all yet, but at first glance it sounds to me like the "smart clients" approach to data interoperability. Instead of focusing work on generating data in standard formats, clearly identify the interoperable functionality that you want, and build clients capable of performing those functions on data thrown at it in any way, shape, or form.