Difference between revisions of "Feature Processor for Points"
Line 21: | Line 21: | ||
[http://128.252.202.19:8080/CIRA?service=WFS&version=1.0.0&request=GetFeature&typename=VIEWS&outputFormat=text/csv CIRA/VIEWS location table] | [http://128.252.202.19:8080/CIRA?service=WFS&version=1.0.0&request=GetFeature&typename=VIEWS&outputFormat=text/csv CIRA/VIEWS location table] | ||
− | [[Category:StationPoint]] | + | [[Category:StationPoint]][[Category:Server]] |
Revision as of 12:58, September 3, 2010
< Back to Glossary | Edit with Form
Feature_Processor_for_Points Description: Reads the Point Data Location Configuration information, creates an SQL query to extract the location table, executes the query and writes the result into a CSV file. Used in WFS GetFeature Query.
Glossary Domain: {{{Glossary Domain}}}"{{{Glossary Domain}}}" is not in the list (WCS, HTAP, AQInfrastructure) of allowed values for the "Glossary Domain" property.
Related Links
Links to this page
[[Links::Location Configuration for Points WFS GetFeature Query]]
Contributors
No Contributors
History
No History Available
Term Details
Web Feature Service, WFS, is good in publishing geographic information that does not change by time.
With datafed WCS it is used to publish the location table for point data, because WCS DescribeCoverage Document does not support such rich dimensions well and location tables are static geographic information.
The component that performs three different activities:
- WFS Query Parser. The syntax is checked and output is binary object of all the query elements.
- Subsetter.
- Each field may have different location table. If a the data is sparse, some fields have data only in a few locations, it makes sense to return only those locations.
- Locations may also be filtered by geographic bounding box.
- Other WFS filters are not implemented.
- Formatter. The data is returned in desired format. Currently the only supported is CSV, Comma Separated Values