> -----Original Message----- > From: UMN MapServer Users List > [mailto:[EMAIL PROTECTED] On Behalf Of Charlton Purvis > Sent: 05 July, 2007 5:23 PM > To: [email protected] > Subject: Re: [UMN_MAPSERVER-USERS] SOS disconnect > > Thanks, Assefa: > > > > Is there some controlling mechanism that says, hey, here > is my data > > > in MapServer land, and here is how it needs to spit out > in SOS land? > > > This > > same > > > data is being serviced by another SOS flavor (not > MapServer), and it > > returns > > > a field like this: > > > > > > <om:result> > > > 2007-07-03T20:04:00Z,42.5,-70.5999984741211,0.0,289.950012207031 > > > </om:result> > > > > > > And that's what I want! I can see it in my WFS, but I > want to SOS- > > ercise > > > it. > > > > > You should be able to add output the attributes values > (components > > in > > SOS) by adding a metadata on the layer for each attribute > you want to > > display. Something like sos_nameofattribute_componenturl "some href" > > > > eg : "sos_COLOUR_componenturl" > "http://www.ec.gc.ca/envirodat#COLOUR"; > > > > The component url would be published when doing the > GetCapabilities > > and the attribute value would be pulished for GetObservation > > That did the trick. > > "sos_m_value_alias" "wind_speed" > "sos_m_value_componenturl" > "http://marinemetadata.org/cf#wind_speed"; > "sos_m_lon_alias" "lon" > "sos_m_lon_componenturl" "urn:ogc:phenomenon:longitude:wgs84" > "sos_m_lat_alias" "lat" > "sos_m_lat_componenturl" "urn:ogc:phenomenon:latitude:wgs84" > "sos_m_z_alias" "z" > "sos_m_z_componenturl" "urn:ogc:phenomenon:depth" > "sos_timeitem" "m_date" > "sos_offering_timeextent" "20070530T1800Z" > > And now I have lovely observations. > > I have two issues, if I haven't worn out my welcome . . . > > * I am pulling 10 different types of observations from this > particular buoy. > I have listed them all as the same offering and each LAYER > has an identical GROUP -- so they all show up nicely under > ndbc_44029. The problem is, when I have more than 4 or so > SOS LAYERS, whether or not they are part of the same group, I > all of a sudden get an empty .xml. And Apache logs show > nothing. I know for a fact that there is not a problem w/ > the LAYER definition because it's just a matter of cutting > and pasting to change from something like a wind_speed column > to wind_speed_of_gust. Is there some kind of SOS limit in a > *.h somewhere? > > * Secondly, is there a trick to the TIME element? Here is a working > request: > > http://sos-web.tamu.edu/sos-cgi/madis?service=sos&request=GetO bservation&ver > sion=0.0.31&offering=ndbc_44029&format=application/com-xml&obs ervedProperty= > http://marinemetadata.org/cf%23sea_surface_temperature >
N.B. are you intentionally setting observedproperty to a URL in the mapfile? Note that it can also be a plain old string, etc. :) > And it does say it recognizes a timePeriod, but when I tack > on a time parameter, it bombs w/ 'msSOSGetObservation(): SOS > server error. Invalid time value given for the eventTime > parameter'. I dug around in the code, and it still doesn't > shed any light on where the problem is occurring. > When I try: http://sos-web.tamu.edu/sos-cgi/madis?service=sos&request=GetObservation &version=0.0.31&offering=ndbc_44029&format=application/com-xml&observedP roperty=http://marinemetadata.org/cf%23sea_surface_temperature&eventTime =<gml:TimePeriod><gml:beginPosition>2007-06</gml:beginPosition><gml:endP osition>2007-07</gml:endPosition></gml:TimePeriod> It seems to work; mind you there looks to be only one record. How are you passing the time query? > The getcaps behind all of this is here: > http://sos-web.tamu.edu/sos-cgi/madis?service=sos&request=getc apabilities&ve > rsion=0.0.31. > > I do plan on writing up how I have gotten this far, so it may > help someone in the long run, too. > > Many, many thanks. > > Charlton >
