...
It is possible to setup the WaterMl2 import to read from a WaterMl2 webserver using the WaterMlServerParser or it is possible to read directly form an import directory using the WaterMLTimeSeriesParser.
Table of Contents |
---|
TimeSeries XML Request format
...
- externalLocation values are written as Feature Id
- externalParameter values are written as ObservedProperty
- 1st externalQualifier values are written as procedure (if not required fill in 'unknown')
- 2nd externalQualifier values are written as offering (if not required fill in 'unknown' or omit)
Parsing of response HRef items
Due to the nature of the WaterML standard, requested items such as featureOfInterest, observedProperties and procedure are returned in the form of xlink:href values. Such values give an URI representation of the original requested value. In order for the FEWS system to extract the original information from these URI's the response value is parsed. The following parsing scheme has been implemented for the given URI formats:
1.Fragments
example: http://sweet.jpl.nasa.gov/2.2/phenHydro.owl#StreamDischarge
parse: new URI("http://sweet.jpl.nasa.gov/2.2/phenHydro.owl#StreamDischarge").getFragment()
result: StreamDischarge
2.Queries
example: http://nwis.waterdata.usgs.gov/usa/nwis/pmcodes?00065
_parse:_new URI("http://nwis.waterdata.usgs.gov/usa/nwis/pmcodes?00065").getQuery()
result: 00065
3. Path
example: http://kiwis.kisters.de/parameters/Q
parse: new File( new URI("http://kiwis.kisters.de/parameters/Q").getPath()).getName()
...