"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

GeoServer GeoSciML Testbed 3 Downloads

This page is obsolete

See GeoserverDevelopment for information on GeoServer Application Schema Support (app-schema), which replaces community-schemas.

Download GeoServer GeoSciML Testbed 3 configuration

GeoServer GeoSciML Testbed 3 configuration (also known as a "data directory"):
  • https://twiki.auscope.org/projects/gsmltb3/geoserver-gsmltb3-config.2008-07-10.r2488.zip
    • Identifier rN is the subversion revision.
Requires GeoServer built with community-schemas support:

The latest (untested) GeoServer GeoSciML Testbed 3 configuration may be obtained directly from the Subversion repository:


  • Install GeoServer built with community-schemas support. See GeoserverCommunitySchemasDownloads.
  • Unpack the configuration in a data directory outside the servlet context. For example:
    • /usr/local/gsmltb3/data
  • Configure any feature types requiring it (see below).
  • Edit GeoServer WEB-INF/web.xml to uncomment GEOSERVER_DATA_DIR and point it at the data directory.
  • Change the admin password.
    • GeoServer ships with the admin password set to geoserver. This is insecure.
    • Change the admin password by editing security/users.properties (or later via the web interface).
  • Set permissions required for service to have read/write access to data directory. For example:
    • chown -R tomcat55:nogroup /usr/local/gsmltb3/data
  • Restart the servlet container. For example:
    • /etc/init.d/tomcat55 restart

Testing (optional)

  • Obtain and install XmlServiceTester.
  • Edit servicetester/test-suite.xml (in the data directory) to set your service URL and disable tests for any features that are not enabled.
  • Run the test-suite. For example, for XmlServiceTester unzipped in /usr/local/XmlServiceTester and configuration in /usr/local/gsmltb3/data:
    • /usr/local/XmlServiceTester/bin/XmlServiceTester.sh /usr/local/gsmltb3/data/servicetester/test-suite.xml
  • Testing comprises schema-validation and rudimentary content testing (counting features).

Feature types


  • gsml:MappedFeatureGaOracle backed by an Oracle Spatial database containing the Geoscience Australia reference data set. This feature type is sourced in its entirety from the GSML_EASTOZ_GEOLOGY table. To enable this feature type:
    • Create an Oracle Spatial database, populate it with the GeoscimlTestbed3Data, and make a gsmltb3 account to access it.
    • Copy an Oracle JDBC driver to WEB-INF/lib. Either ojdbc14.jar or ojdbc5.jar should work. The driver can be obtained from either of:
    • Copy MappedFeatureGaOracle.template.xml to MappedFeatureGaOracle.xml and edit to set the Oracle database server name, instance name, and account password.
    • 128 MB Java heap size is insufficient to process this dataset with Tomcat 5.5 / Java 5 i386 on Debian. Edit /etc/init.d/tomcat55 to increase the maximum heap size to 256 MB (change -Xmx128m to -Xmx256m).
    • Issues:
      • No srsName attribute for shape.
      • All rows of GSML_EASTOZ_GEOLOGY have blank INT_METHOD, thus all observationMethod elements are empty.


  • gsml:MappedFeatureType backed by a PostGIS database. To enable the feature type:
    • Create a PostGIS spatial database called gsmltb3 owned by role gsmltb3.
    • As gsmltb3 run MappedFeaturePostgis.sql to populate the database.
    • Copy MappedFeaturePostgis.template.xml to MappedFeaturePostgis.xml and edit to set your PostGIS server name and user password.


  • gsml:MappedFeatureType backed by a property file.
    • This feature type should always work and required no further configuration.


  • gsml:MappedFeatureType backed by a shapefile.
    • This feature type should always work and required no further configuration.


  • gsml:MappedFeature for each of TestBed3UseCase2 A and B backed by GSV data set.
    • Set up a PostGIS database gsmltb3 with user gsmltb3, as described for gsml:MappedFeaturePostgis (that is, use the same database).
    • Load the GSV data set, as described in GeoscimlTestbed3Data.
    • Configure each feature type by copying the MappedFeatureUseCase2{A,B}.template.xml to MappedFeatureUseCase2{A,B}.xml respectively and setting your PostGIS server name and user password.
    • Issues:
      • positionalAccuracy is always unknown because GeoServer cannot encode polymorphic types (type must be known at mapping time).
      • Attributes set on multi-valued properties all have the value of the first (that is, they are wrong). See GeoserverGeoscimlTestbed3Issues.



  • Added gsml:MappedFeatureUseCase2A and gsml:MappedFeatureUseCase2B backed by GSV PostGIS data set.
  • Included Subversion revision in file name.


  • Fixing the GeoServer attribute corruption bug [GEOT-1543] revealed that gsml:MappedFeatureUseCase2A was schema-valid only because that bug provided required (and incorrect) codeSpace attributes. Added mappings to provide intended codeSpace attributes.


  • Added preliminary gsml:MappedFeatureUseCase2A
  • Added XmlServiceTester test suite.


  • All feature types updated to be be schema-valid, as verified by XmlServiceTester.


  • Added gsml:MappedFeatureShapefile.


  • Added gsml:observationMethod and gsml:positionalAccuracy to gsml:MappedFeatureGaOracle.
  • Added schema cache, and enables it for all feature types.


  • Added preliminary gsml:MappedFeatureGaOracle with gsml:specification and gsml:shape.
Topic revision: r20 - 15 Oct 2010, UnknownUser

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).