After spending a few days experimenting and skilling up on SOS, I found the
approach I have taken is totally off track. I kept treating SOS 2.0 as wfs
because they look similar. I kept trying to kick/push/punch sos into wfs trying
to reuse all the wfs library such as featuresource, GetFeature etc etc.
I tried modifying sos request into a wfs request, wrapping a wfs response out
into a sos response. Totally the wrong approach.
I am starting to feel that the work required to do this is alot bigger then I
has initially imagined. For a start, perhaps the right way to approach this is
to have its own SOSFeatureSource, its own iterator, basically its own GT
module. It own set of configuration (how ? at the moment I am clueless due as
our use case require WaterML schema which is complex).
It should also have its own GetSOSFeature to handle getObservation request. My
knowledge in the spatial domain are still limited and therefore would like to
put my thoughts out there.
Please enlighten!!!
Thanks
Victor Tey
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
GeoTools-GT2-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
