"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"

About

Added to help with the fine details correcting what's being returned, as tested by the stylesheets.

The stylesheets were written to the _inline samples in Examples/geochem and checked against the schema.

As of 30 Nov 2004, most testing has been against Analyte values being returned, due to lack of a map context to test the SVG stylesheet.

Due to TerryHannant advising me their setup was cloned, all corrections are being published as being of potential use to others.

AndyDent testing of stylesheets is primarily with XML Spy 2005.

schemaLocation

Re this issue:

in the xsi:schemaLocation="http://www.opengis.net/wfs

http://mapservertst.mpr.wa.gov.au:80/geoserver/data/capabilitieswfs/1.0.0/WFS-basic.xsd

should be

http://mapservertst.mpr.wa.gov.au:80/geoserver/data/capabilities/wfs/1.0.0/WFS-basic.xsd

This is a bug in the geoserver code base fixed since we branched. Should not be a problem for the demo as we really wont expect clients to validate at run time in production environments anyway, except during mission critical data exchanges - certainly not when trying to respond interactively.

Also, there is an argument the WFS really should point to the authoritative schema not what it is prepared to offer. Symptomatic of this problem is that geoserver doesnt return the definitive schema which may include all sorts of remote components, but actually dumps the "flat" view of the schema. This loses important semantic information IMHO.

Finally, the "query schema" vs "response schema" issue needs to be resolved anyway, and WFS semantics clarified.

In a nutshell, we can ignore this issue for now but it will get resolved in a future version.

-- RobAtkinson - 30 Nov 2004

PIRSA WFS Response

demo from http://geodev.metadev.com.au:4662/geoserver/demos.html

working as of 01 Dec 2004 in that the AnalytePortrayal1.xslt table output stylesheet formats it correctly. It doesn't validate due possibly to the error described below.

Query Includes Zeros

As pointed out in a public demo yesterday, despite the query being values above 5ppm, the xmml:resultMeasureExact frequently contains zero values.

I confirmed this with the direct WFS demo, using the typeName=xmml:GeochemMeasurementsByAnalyteAndValue request.

-- AndyDent - 10 Dec 2004

PIRSA-specific response

This may not apply to others

In http://geodev.metadev.com.au:4662/geoserver/wfs/DescribeFeatureType?typeName=pirsa:GeochemSpecimenByAnalyteAndValue

type='pirsa:PIRSA Geochemical Analyses' Should possibly be type='pirsa:PIRSAGeochemicalAnalyses'

I'm not sure if that is related but after changing the above, the file now gives a validation error of being unable to load schema, from:

GA Sample

Due to the spatial query problems, testing was performed against a sample document.

xmml namespace URN

In the xmlns:xmml="http://www.seegrid.csiro.au/xmml" should be xmlns:xmml="http://www.opengis.net/xmml" whch is the RDDL standard location

localhost response

There's also what I suspect is an inappropriate localhost xsi:schemaLocation="http://www.seegrid.csiro.au/xmml http://localhost:8080/geoserver/wfs/DescribeFeatureType?typeName=xmml:GeochemSpecimenByAnalyteAndValue http://www.opengis.net/wfs http://localhost:8080/geoserver/data/capabilitieswfs/1.0.0/WFS-basic.xsd

StuartGirvan has already responded:

The address in the response header wil be:

http://www.ga.gov.au/ogcservices/wfs/DescribeFeatureType?typeName=xmml:GeochemSpecimenByID http://www.opengis.net/wfs http://www.ga.gov.au/ogcservices/data/capabilitieswfs/1.0.0/WFS-basic.xsd"

when we get the Oracle spatial problem sorted out and republish the feature types externally.

WA WFS Response

Testing http://mapservertst.mpr.wa.gov.au/geoserver/wfs/TestWfsPost with WA_AnalyteValueQuery-2004-11-30.xml (attached).

results are fine as of -- AndyDent - 06 Dec 2004

query Still not interoperable - feature type names do not match target names:

xmml:GeochemSpecimenByAnalyteAndValue

note Case as well!

see MCAProjectUI for how to test in UI

-- RobAtkinson - 07 Dec 2004

apparent incorrect namespace specifications - WA

The following has been left as a warning. It appears the server is working fine and what was reported below was a bizarre side-effect of the way FireFox saved a query. If you check the FireFox downloads window it will show the query as being re-transmitted (which takes a while longer on a slower link). If you open the document before FireFox says it has finished saving, you get a well-formed document lacking namespaces!

Apologies for:

As of 10.45 6/Dec, the namespaces returned from the WA Analyte Value query were incorrect - all were of the format xmml="blah" gml="blah". Changes required:
  1. xmml= becomes xmlns= because that's the default namespace
  2. all others need the namespace name prefixing with xmlns:

schemaLocation-WA

see discussion above by RobAtkinson

in the xsi:schemaLocation="http://www.opengis.net/wfs

http://mapservertst.mpr.wa.gov.au:80/geoserver/data/capabilitieswfs/1.0.0/WFS-basic.xsd

should be

http://mapservertst.mpr.wa.gov.au:80/geoserver/data/capabilities/wfs/1.0.0/WFS-basic.xsd
Topic attachments
I Attachment Action Size Date Who Comment
WA_AnalyteValueQuery-2004-11-30.xmlxml WA_AnalyteValueQuery-2004-11-30.xml manage 0.8 K 30 Nov 2004 - 10:42 AndyDent Sample query
WA_SpecimenIDQuery-2004-11-30.xmlxml WA_SpecimenIDQuery-2004-11-30.xml manage 0.6 K 30 Nov 2004 - 10:42 AndyDent Sample query
Topic revision: r13 - 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).