InteractiveApi | @here/olp-sdk-ts
Namespace InteractiveApi
Index
Interfaces
- Api
Health Status - Api
Version - Feature
- Feature
Collection - Feature
Collection Iterable - Feature
Collection Modification - GeoJSON
- Geometry
- Line
String - Model
Error - Multi
Line String - Multi
Point - Multi
Polygon - Point
- Polygon
- Statistics
- Statistics
Bbox - Statistics
Count - Statistics
Geometry Types - Statistics
Properties - Statistics
Properties Value - Statistics
Tags - Statistics
Tags Value
Type Aliases
Functions
Type Aliases
Estimated
Get Features By Spatial Body
Search Params
Functions
delete Feature
Deletes an existing feature.
Parameters
builder: RequestBuilder
params: { featureId: string; layerId: string }
feature
Id: string layer
Id: string
Returns Promise<Response>
delete Features
The wildcard sign(*) could be used to delete all features in the layer.
Parameters
builder: RequestBuilder
params: { id?: string[]; layerId: string }
Optional id?: string[]
layer
Id: string
Returns Promise<Response>
get Api Version
Retrieves API Specification version information.
Parameters
builder: RequestBuilder
Returns Promise<ApiVersion>
get Feature
Retrieves the feature with the provided identifier.
Parameters
builder: RequestBuilder
params: { featureId: string; force2D?: boolean; layerId: string; selection?: string | string[] }
feature
Id: string Optional force2D?: boolean
layer
Id: string Optional selection?: string | string[]
Returns Promise<Feature>
get Features
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.
Parameters
builder: RequestBuilder
params: { force2D?: boolean; id: string | string[]; layerId: string; selection?: string | string[] }
Optional force2D?: boolean
id: string | string[]
layer
Id: string Optional selection?: string | string[]
Returns Promise<FeatureCollection>
get Features ByBBox
Return the features which are inside a bounding box stipulated by bbox parameter.
Parameters
builder: RequestBuilder
params: { bbox?: number[]; clip?: boolean; clustering?: string; clusteringParams?: {}; force2D?: boolean; layerId: string; limit?: number; params?: SearchParams; selection?: string | string[]; skipCache?: boolean }
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_1For 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_2The resulting Features list will contain all elements havingvalue_1ORvalue_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=10The 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
Optional bbox?: number[]
Optional clip?: boolean
Optional clustering?: string
Optional clustering
Params?: {} [key: string]: string | number
Optional force2D?: boolean
layer
Id: string Optional limit?: number
Optional params?: SearchParams
Optional selection?: string | string[]
Optional skip
Cache?: boolean
Returns Promise<FeatureCollection>
get Features By Spatial
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.
Parameters
builder: RequestBuilder
params: { force2D?: boolean; lat?: number; layerId: string; limit?: number; lng?: number; params?: SearchParams; radius?: number; refCatalogHrn?: string; refFeatureId?: string; refLayerId?: string; selection?: string | string[]; skipCache?: boolean }
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_1For 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_2The resulting Features list will contain all elements havingvalue_1ORvalue_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=10The 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
Optional force2D?: boolean
Optional lat?: number
layer
Id: string Optional limit?: number
Optional lng?: number
Optional params?: SearchParams
Optional radius?: number
Optional ref
Catalog Hrn?: string Optional ref
Feature Id?: string Optional ref
Layer Id?: string Optional selection?: string | string[]
Optional skip
Cache?: boolean
Returns Promise<FeatureCollection>
get Features By Spatial Post
List the features which are inside the specified radius. The origin point is calculated based on the geometry provided as payload.
Parameters
builder: RequestBuilder
params: { body?: Feature | FeatureCollection | Geometry | LineString | MultiLineString | MultiPoint | MultiPolygon | Point | Polygon; force2D?: boolean; layerId: string; limit?: number; params?: SearchParams; radius?: number; selection?: string | string[]; skipCache?: boolean }
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_1For 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_2The resulting Features list will contain all elements havingvalue_1ORvalue_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=10The 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
Optional body?: Feature | FeatureCollection | Geometry | LineString | MultiLineString | MultiPoint | MultiPolygon | Point | Polygon
Optional force2D?: boolean
layer
Id: string Optional limit?: number
Optional params?: SearchParams
Optional radius?: number
Optional selection?: string | string[]
Optional skip
Cache?: boolean
Returns Promise<FeatureCollection>
get Features By Tile
Get features in tile
Parameters
builder: RequestBuilder
params: { clip?: boolean; clustering?: string; clusteringParams?: {}; force2D?: boolean; layerId: string; limit?: number; margin?: number; params?: SearchParams; selection?: string | string[]; skipCache?: boolean; tileId: string; tileType: string }
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_1For 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_2The resulting Features list will contain all elements havingvalue_1ORvalue_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=10The 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
Optional clip?: boolean
Optional clustering?: string
Optional clustering
Params?: {} [key: string]: string | number
Optional force2D?: boolean
layer
Id: string Optional limit?: number
Optional margin?: number
Optional params?: SearchParams
Optional selection?: string | string[]
Optional skip
Cache?: boolean tile
Id: string tile
Type: string
Returns Promise<FeatureCollection>
get Health
Tests basic health of the service.
Parameters
builder: RequestBuilder
Returns Promise<ApiHealthStatus>
get Statistics
Returns statistical information about this layer.
Parameters
builder: RequestBuilder
params: { layerId: string; skipCache?: boolean }
layer
Id: string Optional skip
Cache?: boolean
Returns Promise<Statistics>
iterate Features
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.
Parameters
builder: RequestBuilder
params: { force2D?: boolean; layerId: string; limit?: number; pageToken?: string; part?: number[]; selection?: string | string[]; skipCache?: boolean; sort?: string | string[] }
Optional force2D?: boolean
layer
Id: string Optional limit?: number
Optional page
Token?: string Optional part?: number[]
Optional selection?: string | string[]
Optional skip
Cache?: boolean Optional sort?: string | string[]
Returns Promise<FeatureCollectionIterable>
patch Feature
Patches an existing feature.
Parameters
builder: RequestBuilder
params: { body: Feature; featureId: string; layerId: string }
body: Feature
feature
Id: string layer
Id: string
Returns Promise<Feature>
post Features
Create or patch features.
Parameters
builder: RequestBuilder
params: { body: FeatureCollection; layerId: string }
body: FeatureCollection
layer
Id: string
Returns Promise<FeatureCollectionModification>
put Feature
Creates or replaces a feature in the layer.
Parameters
builder: RequestBuilder
params: { body: Feature; featureId: string; layerId: string }
body: Feature
feature
Id: string layer
Id: string
Returns Promise<Feature>
put Features
Create or replace the provided features.
Parameters
builder: RequestBuilder
params: { body: FeatureCollection; layerId: string }
body: FeatureCollection
layer
Id: string
Returns Promise<FeatureCollectionModification>
search 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.
Parameters
builder: RequestBuilder
params: { force2D?: boolean; layerId: string; limit?: number; params?: SearchParams; selection?: string | string[]; skipCache?: boolean }
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_1For 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_2The resulting Features list will contain all elements havingvalue_1ORvalue_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=10The 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
Optional force2D?: boolean
layer
Id: string Optional limit?: number
Optional params?: SearchParams
Optional selection?: string | string[]
Optional skip
Cache?: boolean
Returns Promise<FeatureCollection>
Generated using TypeDoc
True if the value is only an estimation; false otherwise.