Deletes an existing feature.
The wildcard sign(*) could be used to delete all features in the layer.
Retrieves API Specification version information.
Retrieves the feature with the provided identifier.
Returns all of the features found for the provided list of ids. The response is always a FeatureCollection, even if there are no features with the provided ids.
Return the features which are inside a bounding box stipulated by bbox parameter.
Additional feature filters which compares the feature's property's value with the one specified in the query, resulting in a subset of features. The usage of multiple property names represents an AND operation. The usage of a comma (,) separating the properties values, represents an OR operation. Properties initiated with 'f.' are used to access values which are added by default in the stored feature. The possible values are: 'f.id', 'f.createdAt' and 'f.updatedAt'. Properties initiated with 'p.' are used to access values in the stored feature which are under the 'properties' property. Use it as a shorthand accessor for 'properties' values. The format should follow the specification below
?p.property_name_1=property_value_1&f.special_property_name_1=special_property_value_1
For example, the above query, the Features will be filtered by 'property' AND 'special property' equals to their respective values.
While in the following example ?p.property_name_1=value_1,value_2
The resulting Features list will contain all elements having value_1 OR value_2.
Additionally to the operators used in the examples above, the query can be written, with the same semantic,
by using the long operators: "=gte=", "=lte=", "=gt=", "=lt=" and "=cs=".
The below queries yield the same result:
?p.property_name_1>=10
?p.property_name_1=gte=10
The available operators are: "=" - equals "!=" - not equals ">=" or "=gte=" - greater than or equals "<=" or "=lte=" - less than or equals ">" or "=gt=" - greater than "<" or "=lt=" - less than "@>" or "=cs=" - contains
List the features which are inside the specified radius. The origin radius point is calculated based either on latitude & longitude or by specifying a feature's geometry.
Additional feature filters which compares the feature's property's value with the one specified in the query, resulting in a subset of features. The usage of multiple property names represents an AND operation. The usage of a comma (,) separating the properties values, represents an OR operation. Properties initiated with 'f.' are used to access values which are added by default in the stored feature. The possible values are: 'f.id', 'f.createdAt' and 'f.updatedAt'. Properties initiated with 'p.' are used to access values in the stored feature which are under the 'properties' property. Use it as a shorthand accessor for 'properties' values. The format should follow the specification below
?p.property_name_1=property_value_1&f.special_property_name_1=special_property_value_1
For example, the above query, the Features will be filtered by 'property' AND 'special property' equals to their respective values.
While in the following example ?p.property_name_1=value_1,value_2
The resulting Features list will contain all elements having value_1 OR value_2.
Additionally to the operators used in the examples above, the query can be written, with the same semantic,
by using the long operators: "=gte=", "=lte=", "=gt=", "=lt=" and "=cs=".
The below queries yield the same result:
?p.property_name_1>=10
?p.property_name_1=gte=10
The available operators are: "=" - equals "!=" - not equals ">=" or "=gte=" - greater than or equals "<=" or "=lte=" - less than or equals ">" or "=gt=" - greater than "<" or "=lt=" - less than "@>" or "=cs=" - contains
List the features which are inside the specified radius. The origin point is calculated based on the geometry provided as payload.
Additional feature filters which compares the feature's property's value with the one specified in the query, resulting in a subset of features. The usage of multiple property names represents an AND operation. The usage of a comma (,) separating the properties values, represents an OR operation. Properties initiated with 'f.' are used to access values which are added by default in the stored feature. The possible values are: 'f.id', 'f.createdAt' and 'f.updatedAt'. Properties initiated with 'p.' are used to access values in the stored feature which are under the 'properties' property. Use it as a shorthand accessor for 'properties' values. The format should follow the specification below
?p.property_name_1=property_value_1&f.special_property_name_1=special_property_value_1
For example, the above query, the Features will be filtered by 'property' AND 'special property' equals to their respective values.
While in the following example ?p.property_name_1=value_1,value_2
The resulting Features list will contain all elements having value_1 OR value_2.
Additionally to the operators used in the examples above, the query can be written, with the same semantic,
by using the long operators: "=gte=", "=lte=", "=gt=", "=lt=" and "=cs=".
The below queries yield the same result:
?p.property_name_1>=10
?p.property_name_1=gte=10
The available operators are: "=" - equals "!=" - not equals ">=" or "=gte=" - greater than or equals "<=" or "=lte=" - less than or equals ">" or "=gt=" - greater than "<" or "=lt=" - less than "@>" or "=cs=" - contains
Get features in tile
Additional feature filters which compares the feature's property's value with the one specified in the query, resulting in a subset of features. The usage of multiple property names represents an AND operation. The usage of a comma (,) separating the properties values, represents an OR operation. Properties initiated with 'f.' are used to access values which are added by default in the stored feature. The possible values are: 'f.id', 'f.createdAt' and 'f.updatedAt'. Properties initiated with 'p.' are used to access values in the stored feature which are under the 'properties' property. Use it as a shorthand accessor for 'properties' values. The format should follow the specification below
?p.property_name_1=property_value_1&f.special_property_name_1=special_property_value_1
For example, the above query, the Features will be filtered by 'property' AND 'special property' equals to their respective values.
While in the following example ?p.property_name_1=value_1,value_2
The resulting Features list will contain all elements having value_1 OR value_2.
Additionally to the operators used in the examples above, the query can be written, with the same semantic,
by using the long operators: "=gte=", "=lte=", "=gt=", "=lt=" and "=cs=".
The below queries yield the same result:
?p.property_name_1>=10
?p.property_name_1=gte=10
The available operators are: "=" - equals "!=" - not equals ">=" or "=gte=" - greater than or equals "<=" or "=lte=" - less than or equals ">" or "=gt=" - greater than "<" or "=lt=" - less than "@>" or "=cs=" - contains
Tests basic health of the service.
Returns statistical information about this layer.
Iterates all of the features in the layer. The features in the response are ordered so that no feature is returned twice. If there are more features, which could be loaded, the response FeatureCollection will contain the root attribute nextPageToken. The value of this attribute can be passed as a query parameter for the following request in order to continue the iteration from the marked position.
Patches an existing feature.
Create or patch features.
Creates or replaces a feature in the layer.
Create or replace the provided features.
Searches for features in the layer. The results are unordered and the request does not allow to continue the search, which is the main difference when compared to the iterate request.
Additional feature filters which compares the feature's property's value with the one specified in the query, resulting in a subset of features. The usage of multiple property names represents an AND operation. The usage of a comma (,) separating the properties values, represents an OR operation. Properties initiated with 'f.' are used to access values which are added by default in the stored feature. The possible values are: 'f.id', 'f.createdAt' and 'f.updatedAt'. Properties initiated with 'p.' are used to access values in the stored feature which are under the 'properties' property. Use it as a shorthand accessor for 'properties' values. The format should follow the specification below
?p.property_name_1=property_value_1&f.special_property_name_1=special_property_value_1
For example, the above query, the Features will be filtered by 'property' AND 'special property' equals to their respective values.
While in the following example ?p.property_name_1=value_1,value_2
The resulting Features list will contain all elements having value_1 OR value_2.
Additionally to the operators used in the examples above, the query can be written, with the same semantic,
by using the long operators: "=gte=", "=lte=", "=gt=", "=lt=" and "=cs=".
The below queries yield the same result:
?p.property_name_1>=10
?p.property_name_1=gte=10
The available operators are: "=" - equals "!=" - not equals ">=" or "=gte=" - greater than or equals "<=" or "=lte=" - less than or equals ">" or "=gt=" - greater than "<" or "=lt=" - less than "@>" or "=cs=" - contains
Generated using TypeDoc
True if the value is only an estimation; false otherwise.