Problems about FeatureOfInterest while using SOS importer

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Problems about FeatureOfInterest while using SOS importer

Deen
Hi everyone,

currently I am running some tests with SOS and trying to import some data to the DB by using SOS importer. However I am a bit confused  when I configured the 'FeatureOfInterest' part.  In my dataset, the density of nitric oxide 'NO' were measured by a NO dectector, which was carried by a car along a street, following is a piece of the dataset. As depicted, the Lat and Lon represent the location where the observation took place.      

Time,                        Latitude,     Longitude,         NO 
2015-12-13 05:58:51, 49.053822, 8.390437,2595, 2.27,
2015-12-13 05:58:52, 49.053799, 8.390374,2595, 3.18,
2015-12-13 05:58:53, 49.053768, 8.390308,2595, 3.24,

As far as I understand O&M, FOI represents the geometry of obersvations so from my perspective, each observation should be associated with one FOI, which is represented by column 'Lat' and 'Lon' , Here is how I configured the FOI part in SOS importer 






After the configuration, I checked out the config file and found out there was only one single FOI to be generated, which looks like following code,
but what I expected was that the number of FOIs should be same as the number of observations. 
    
<FeatureOfInterest>
   <GeneratedSpatialResource>
      <ID>foi-181816075</ID>
      <Number>1</Number>
      <Number>2</Number>
      <URI useAsPrefix="false"/>
      <ConcatString/>
      <Position>
        <Group>A</Group>
      </Position>
   </GeneratedSpatialResource>
</FeatureOfInterest>


Here are my question, firstly, how can I define thousands of  FOIs automatically which are associated with observations?
Secondly, today I noticed a hint on SOS wizard, which says "A feature of interest is involved in making observations concerning a domain feature". This makes me more confused, in my dataset, the location where the value were measured, is not a domain feature, they are just sampling points. If the street, where the car drove along, is considered as FOI, how do I represent the geometry for the street, since the dataset doesn't direct contains any geometry infomation for the street?so what should be considered as FOI in this case?

This problem is bugging me for a while and any help I will appreciate, Thanks in advance 

Kind Regards 
Deen




  


Reply | Threaded
Open this post in threaded view
|

Re: Problems about FeatureOfInterest while using SOS importer

Eike Hinderk Jürrens
Hi Deen,
sorry for the delayed reply. I am quite busy at the moment.

Find my answers inline.

On 02.06.2016 17:40, Deen wrote:

> [...]
> Time,                        Latitude,     Longitude,         NO
> 2015-12-13 05:58:51, 49.053822, 8.390437,2595, 2.27,
> 2015-12-13 05:58:52, 49.053799, 8.390374,2595, 3.18,
> 2015-12-13 05:58:53, 49.053768, 8.390308,2595, 3.24,
> [...]
> <FeatureOfInterest>
>    <GeneratedSpatialResource>
>       <ID>foi-181816075</ID>
>       <Number>1</Number>
>       <Number>2</Number>
>       <URI useAsPrefix="false"/>
>       <ConcatString/>
>       <Position>
>         <Group>A</Group>
>       </Position>
>    </GeneratedSpatialResource>
> </FeatureOfInterest>
>
>
> Here are my question, firstly, how can I define thousands of  FOIs
> automatically which are associated with observations?

You already did. The tag under feature of interest (FOI) is
"GeneratedSpatialResource". The meaning behind this is, that the
importer is using the data from column 1 and 2 (see "Number" tags)  for
generating the FOIs. Hence, for each observation an own FOI is generated
and inserted into the SOS.


> Secondly, today I noticed a hint on SOS wizard, which says "A feature of
> interest is involved in making observations concerning a domain feature".
> This makes me more confused, in my dataset, the location where the value
> were measured, is not a domain feature, they are just sampling points. If
> the street, where the car drove along, is considered as FOI, how do I
> represent the geometry for the street, since the dataset doesn't direct
> contains any geometry infomation for the street?

If you want to create a more complex model, you could think of the
generated FOIs being part of the domain feature "street A" or "route
66". It depends on your use case, if this level of complexity is required.


I hope this helps!

Kind regards,
Eike


>  So what should be considered as FOI in this case?
>
> This problem is bugging me for a while and any help I will appreciate,
> Thanks in advance
>
> Kind Regards
> Deen
>
>
> foi.png (44K) <http://sensorweb.forum.52north.org/attachment/4028525/0/foi.png>
>
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/Problems-about-FeatureOfInterest-while-using-SOS-importer-tp4028525.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines


--
Eike Hinderk Jürrens
52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: [hidden email]
Fon: +49-(0)-251–396371-33
Fax: +49-(0)-251–396371-11
http://52north.org/
Twitter: @FiveTwoN
General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849

_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines