![]() |
![]() |
|||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||
| Accessing Geospatial Data > Querying Geospatial Data | Page 13 of 17 | |||||||||||||||||||||||||||||
|
|
Filter Encoding Geography Markup Language allows you to encode geographic data, and a web feature service enables you to manipulate that data; but how do users find your “manipulated”, GML-encoded geographic information? To find geographic content online, users generally issue an Internet-wide search. There must be a common means for those searches to be specified so that servers will understand them. OGC is developing specifications that define services that must be supported by geographic search servers. OGC’s Filter Encoding specification is a means of defining what those properties are; it is used to filter the objects out of geospatial servers. It is an XML encoding of OGC’s Common Query Language; in other words, it is an XML schema for creating a query about spatial objects to pass to a web service. Filter encoding provides:
Search servers may describe geographic objects using a set of attributes. The filter constrains those attributes using the following query properties:
One or more of the attributes from the catalogue may be used in expressions or functions defined by the filter. The filter may then apply comparison or matching operators to the outcome of those expressions or functions. Sample filter queries
|
|||||||||||||||||||||||||||||
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
||||||||||||||||||||||||||||||
| Page 13 of 17 | ||||||||||||||||||||||||||||||