1. GeoSciML testbed 3 implementation
Eric Boisvert, Alex Smirnoff
Laboratoire de cartographie numérique et de photogrammétrie
Commission géologique du Canada
Québec,Qc

2. Tier implementation
Implementation is done in the context of a similar system for Groundwater
Our requirements are a bit different has we have to connect to a series of non-GeoSciML (non-GWML) services and mediate them
Modular implementation, open to various mapping strategy (Boyan keeps asking for Ontology based)

3. Configuration files

4. WMS served by MapServer
Use the TEMPLATE structure to bounce back to WFS when a GetFeatureInfo is issued (so the WMS implementation is completely independent of WFS)
MapServer catches a arbitrary field value and passes it to another url (here, we redirect to WFS)
Data read from the same database (postgis)
SLD is pointing to framework, so it is resolved and transformed (SLD=myserver/SLD/urn:cgi:document:SLD:…)

5. WFS ‘rebound’ GetFeatureInfo redirected to WFS
GetFeature (BBOX) redirected through link provided in Capabilities ? Or the Registries know ??
Remaining issue – try to convince WMS client to invoke text/html by default (Gaia uses text/plain)

6. MapServer configuration

7. Components based
Built in a XML framework, where you can align various components (Cocoon)

8. Architecture
Mediator
WFS
Handled through a mapping file

9. Mapping file
<gsml:GeologicUnit xmlns:gsml="urn:cgi:xmlns:CGI:GeoSciML:2.0" xmlns:gml=" xmlns:proc="urn:x-lcnp:proc" mappedType="gsc:GeologicUnit">
<proc:namespace name="gsc">
<gml:name codeSpace=”urn:ietf:rfc:2141”>gsc:uname</gml:name>
<gsml:preferredAge>
<gsml:GeologicEvent>
<gsml:eventAge>
<gsml:CGI_Term>
<gsml:value>gsc:preferredAge/gsc:Age/gsc:ga_name</gsml:value>
</gsml:CGI_Term>
<gsml:CGI_Numeric>
<gsml:principalValue>gsc:preferredAge/gsc:Age/gsc:ga_age</gsml:value>
</gsml:CGI_Numeric>
</gsml:eventAge>
</gsml:GeologicEvent>
</gsml:preferredAge>
</gsml:GeologicUnit>

10. WFS-DB mapping file

11. 2 levels of mappings first for WFS to WFS Second for WFS to DB
But if you can map all in the DB-WFS, the WFS-WFS becomes quite trivial (almost a ‘pass-through’), so the mapping file does not provide any mapping.
The framework does have a internal component based on Deegree (but we could create a GeoServer too)
Connects to Oracle,PostGIS,ArcSDE,ShapeFiles

12. Result handling Handled through XSLT / STX
Mediator
WFS
Handled through XSLT / STX
Different profile = Different StyleSheet

13. Support
Profiles
Resolver
Not based on published API, but will be
Primitive SLD translator (term mapping and structure mapping configuration)
Multiple datasource merged into a single result (done by the Mediator)

14. Some queries

15. Issues XPath for property name
= ‘..’]/>
<And> <PropertyName>gml:name</PropertyName> </And>
Means different things for my application.