Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

Multi-Phenomenon InsertObservation #79

Open
glegal opened this issue Jun 23, 2017 · 3 comments
Open

Multi-Phenomenon InsertObservation #79

glegal opened this issue Jun 23, 2017 · 3 comments
Assignees
Milestone

Comments

@glegal
Copy link

glegal commented Jun 23, 2017

I used the importer with the example data and observed that the importer send separated insertObservation for each phenomenon.

I'd like to add a new insertion mode where the N phenomenon are send in a single InsertObservation array.

Instead of :

<ns25:DataRecord>
          <ns25:field name="phenomenonTime">
              <ns25:Time definition="http://www.opengis.net/def/property/OGC/0/PhenomenonTime">
                   <ns25:uom xlink:href="http://www.opengis.net/def/uom/ISO-8601/0/Gregorian"/>
               </ns25:Time>
            </ns25:field>
             <ns25:field name="Water">
                  <ns25:Quantity definition="urn:phenomenon:Water">
                        <ns25:uom code="kg"/>
                    </ns25:Quantity>
            </ns25:field>
  </ns25:DataRecord>

and

<ns25:DataRecord>
          <ns25:field name="phenomenonTime">
              <ns25:Time definition="http://www.opengis.net/def/property/OGC/0/PhenomenonTime">
                   <ns25:uom xlink:href="http://www.opengis.net/def/uom/ISO-8601/0/Gregorian"/>
               </ns25:Time>
            </ns25:field>
             <ns25:field name="Krypton">
                  <ns25:Quantity definition="urn:phenomenon:Krypton">
                         <ns25:uom code="kg"/>
                   </ns25:Quantity>
               </ns25:field>
  </ns25:DataRecord>

The dataRecord will embed each phenomenon in a field :

<ns25:DataRecord>
          <ns25:field name="phenomenonTime">
              <ns25:Time definition="http://www.opengis.net/def/property/OGC/0/PhenomenonTime">
                   <ns25:uom xlink:href="http://www.opengis.net/def/uom/ISO-8601/0/Gregorian"/>
               </ns25:Time>
            </ns25:field>
             <ns25:field name="Water">
                  <ns25:Quantity definition="urn:phenomenon:Water">
                        <ns25:uom code="kg"/>
                    </ns25:Quantity>
            </ns25:field>
             <ns25:field name="Krypton">
                  <ns25:Quantity definition="urn:phenomenon:Krypton">
                         <ns25:uom code="kg"/>
                   </ns25:Quantity>
               </ns25:field>
  </ns25:DataRecord>

This mode can be activated by adding a new IMPORT_STRATEGY.

I join some example files of the insertObservation requests.
config-files.zip

@EHJ-52n
Copy link
Member

EHJ-52n commented Jun 23, 2017

Are you thinking about a extension of the SweArrayObservationWithSplitExtension strategy?

Please consider, that it might take a while for the SOS processing such large observation collections. Hence, you might test which values of HUNK_SIZE and insertSweArrayObservationTimeoutBuffer are useful within your set-up. In addition, please add your experience in the documentation of the schema.

@glegal
Copy link
Author

glegal commented Jun 23, 2017

Yes its kind of an extension of the SweArrayObservationWithSplitExtension strategy.
I will use HUMK_SIZE and insertSweArrayObservationTimeoutBuffer configuration.
The observation collections should not be extremly larger.

For my sos server wich is multi-phenomnon oriented, it will be much more faster and easier to process the observation in that way.

@EHJ-52n
Copy link
Member

EHJ-52n commented Jun 27, 2017

Okay, looking forward to your contribution.

@EHJ-52n EHJ-52n added this to the 0.5.0 milestone Jun 27, 2017
@EHJ-52n EHJ-52n modified the milestones: 0.5.0, 0.5.1 Jul 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants