search

valentinedwv / ioostech

Automatically exported from code.google.com/p/ioostech
0 stars 0 forks source link

GetObs gml:boundedBy moved to om:featureOfInterest/gml:FeatureCollection block #27

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
In the past, gml:boundedBy has been placed by itself in the GetObs response at 
the same hierarchy level as om:procedure, om:samplingTime, etc.

Now that we're fully exploiting om:featureOfInterest, it makes a ton of sense 
to treat om:featureOfInterest as the single container for all geospatial and 
feature-type response metadata (ie, information that's outside the om:result 
block). The bounding box envelope is one such element; see the GetObs template:
http://code.google.com/p/ioostech/source/browse/trunk/templates/Milestone1.0/GO-
Station-SingleFT-timeSeries-MultiSensor.xml

What's shown in that template validates (with Oxygen), so it's just as valid as 
having gml:boundedBy outside om:featureOfInterest as was previously done. 

For multi-station responses (eg, from a network:all offering), the Envelope 
coordinates will define an actual rectangle, while for single-station responses 
(as in the template above) they collapse to the station location.

Any objections to this change, or to any aspect of the gml:boundedBy 
implementation depicted on the template?

Original issue reported on code.google.com by emilioma...@gmail.com on 26 Jun 2012 at 5:16

GoogleCodeExporter commented 8 years ago 
No one has objected or commented on this. As far as I know this change doesn't 
have any real side effects, other than having to recode your SOS server and 
client.

I'm closing the issue and going with the proposal as described and already 
implemented on the template.

Original comment by emilioma...@gmail.com on 30 Jun 2012 at 2:42