New features in WFS 2.0
The version 2.0 has been extended compared to the previous version 1.1 in their functions. The innovations include the introduction of a revised version of the Filter Encoding standards and Stored Queries and Joins (see. [GeoServer]).
FES 2.0 The new Filter Encoding Standard permits temporal filtering options.
Stored queries Stored queries are a way to store the server side (complex) queries. The corresponding stored query can be accessed via its ID.
Example: Deliver all the lakes in the district of Munich
In addition, placeholders can be defined that are occupied when calling with a value in the Stored Queries.
Example: Deliver all farms larger than $ AREA | $ AREA = 1000
To this end, the operations CreateStoredQuery, Drops Goals Query, ListStoredQueries, DescribeStoredQueries be provided.
Joins (Optional) About WFS queries can be realized joins, as known from spatial databases.
Example: Deliver all parks where there are lakes.
New features in WFS 2.0The version 2.0 has been extended compared to the previous version 1.1 in their functions. The innovations include the introduction of a revised version of the Filter Encoding standards and Stored Queries and Joins (see. [GeoServer]).FES 2.0 The new Filter Encoding Standard permits temporal filtering options.Stored queries Stored queries are a way to store the server side (complex) queries. The corresponding stored query can be accessed via its ID.Example: Deliver all the lakes in the district of MunichIn addition, placeholders can be defined that are occupied when calling with a value in the Stored Queries.Example: Deliver all farms larger than $ AREA | $ AREA = 1000To this end, the operations CreateStoredQuery, Drops Goals Query, ListStoredQueries, DescribeStoredQueries be provided.Joins (Optional) About WFS queries can be realized joins, as known from spatial databases.Example: Deliver all parks where there are lakes.
การแปล กรุณารอสักครู่..