Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#2051 closed enhancement (fixed)

possibility to use run time subsitution on sos_describesensor_url

Reported by: assefa Owned by: assefa
Priority: high Milestone:
Component: SOS Server Version: 5.0
Severity: minor Keywords:
Cc:

Description

possibility to use run time subsitution on sos_describesensor_url.

The user could possibly have someting like %SensorID% as part of the value of
the metadata and that will be substitued with the value of SensorID passed as
part of the DescribeSensor request

Change History (5)

comment:1 by assefa, 17 years ago

Cc: tom.kralidis@… added
add Tom in cc.

Tom what do you think of just using the same metadata sos_describesensor_url and
give it the possiblity is use the vaiables substitutions coming from the
request. I think It gives us more flexibility to do the patterning. 

comment:2 by tomkralidis, 17 years ago

Sounds good to me. I think this will work.

So, for the code, if a sensorid (case-insensitive) parameter is found the 
DescribeSensor request, MapServer will process that putting that into the URL

So, example:

Request:

http://foo/foo?service=SOS&version=0.1.2b&request=DescribeSensor&sensorid=1234

MapServer:

If MapServer does NOT have LAYER/METADATA/sos_describesensor_url defined, then 
a ExceptionReport is thrown as the response.

If MapServer does have LAYER/METADATA/sos_describesensor_url defined, then it 
passes the sensorid parameter from the request to the HTTP Location directive.

"sos_describesensor_url" "http://foo/foo?mysensor=%sensorid%"

Does this make sense?

comment:3 by assefa, 17 years ago

commited as described in comment #2. Will close att the bugs after tests.

comment:4 by tomkralidis, 17 years ago

Resolution: fixed
Status: newclosed
Tested.  Works.  

comment:5 by tomkralidis, 17 years ago

P.S. this change should be documented.
Note: See TracTickets for help on using tickets.