[Auscope-geosciml] GeoSciML 3.0 (GML 3.1 version) in Geoserver? [SEC=UNCLASSIFIED]

Oliver.Raymond at ga.gov.au Oliver.Raymond at ga.gov.au
Mon Aug 2 18:40:20 EDT 2010

Hi Ryan, Ben,

Firstly, are you using the GML3.1 or GML3.2 schemas?

And could you expand on "looks like a schema resolution problem".  Is it a problem with Geoserver, or a problem with the schemas themselves?


Ollie Raymond

National Advice, Maps and Data Standards Project
Geoscience Australia

GeoSciML Design Group
IUGS Commission for the Management and Application of Geoscience Information


Address: GPO Box 378, Canberra, ACT, 2601, Australia | ABN: 80 091 799 039
Ph: +61 2 62499575 | Fax: +61 2 62499992 | Email: Oliver.Raymond at ga.gov.au<mailto:Oliver.Raymond at ga.gov.au> | Google Map<http://maps.google.com/maps?f=q&hl=en&geocode=&q=canberra+australia&ie=UTF8&ll=-35.344028,149.158362&spn=0.007684,0.016404&t=h&z=17&iwloc=addr&om=1>
National geological maps  http://www.ga.gov.au/minerals/research/national/nat_maps/nat_geol_maps.jsp
Geoscience Australia web services  http://www.ga.gov.au/resources/applications/ogc-wms.jsp

 --- This message was created with 100% recycled electrons ---

From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Ryan Clark
Sent: Tuesday, 3 August 2010 6:06 AM
To: auscope-geosciml at lists.arcs.org.au
Subject: [Auscope-geosciml] GeoSciML 3.0 (GML 3.1 version) in Geoserver?

Hello -

I'm curious if anyone else has tried experimenting with providing a GeoSciML 3.0 WFS through Geoserver? I started looking at it last week, and it failed. According to Ben Cardoc-Davies on the Geoserver list, it "looks like a schema resolution problem". I'm not at all sure what's going wrong, and I'm starting to dig in to debugging the application in order to try and find out. In the meantime, I'm just curious if anyone else has considered or tried to do this?

Also, as I recall from my previous experiences implementing a WFS with GeoSciML, one of the problems hiding under the covers was that the MappedFeature featuretype encompasses multiple geometries (points/lines/polygons). This is sensible conceptually, but when implementing a WFS it is assumed that any one FeatureType will have only one geometry type. In the Geoserver world this meant that I actually needed to create three different services, each with a different URL which provide gsml:MappedFeatures - one for points, one for lines, one for polygons. I wonder if anyone has thought about this or has a great idea about how to handle it?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20100803/bc4c3a82/attachment.htm>

More information about the GeoSciML mailing list