Hi Bart,
To me It seems like this all could go into the core of OL: SOS is an OGC
standard and it will be just another format that OL supports
(hopefully). Of course OL is growing bigger with every release, which
will push more people to make customised versions for themselves when
they feel it's getting too big. But that is another issue.
Regards, Roald
Bart van den Eijnden (OSGIS) wrote:
> Hi Eric,
>
> it contains:
>
> 1) a protocol (Protocol.SOS)
> 2) several formats (SOSCapabilities, SOSDescribeSensor,
> SOSGetFeatureOfInterest, SOSGetObservation)
> 3) a wrapper class to integrate them easily for the end-user (currently
> part of the example html)
>
> Best regards.
> Bart
>
> Eric Lemoine wrote:
>
>> On Tue, Nov 3, 2009 at 11:39 AM, Bart van den Eijnden (OSGIS)
>> <
[hidden email]> wrote:
>>
>>
>>> Hi list,
>>>
>>> I've been working on an SOS (Sensor Observation Service) client in
>>> OpenLayers in a sandbox [1], and I think this would be a good candidate
>>> for an addin. But before I put more work into it (shaping it up to be an
>>> addin), I want to know if this is a good candidate.
>>>
>>> Best regards,
>>> Bart
>>>
>>> [1]
>>>
http://dev.openlayers.org/sandbox/bartvde/sosclient/openlayers/examples/sos.html>>>
>>>
>> The three addins that we currently have are controls. What would your
>> SOS addin be composed of? I'm just curious... If your code includes
>> formats, I'm wondering if it'd make sense to have them in trunk
>> instead of in the addin?
>>
>> Thanks,
>>
>>
>
>
>
_______________________________________________
Dev mailing list
[hidden email]
http://openlayers.org/mailman/listinfo/dev
