LoadPintagWithPosition

Class Description

Receive a (new) Pintag Handle for a 2.5D Address. Pintags will be persistant, so that the same Address always results in the same Pintag.

RPC Configuration

Rpc Name:

Plain: LoadPintagWithPosition
Sha1: 7aab7ccee2b9fb05a71dbcd9f3266c2f7fbcbedc

Rpc Call

RPCs can be called by their plain name or their SHA1 representation.

Rpc Parameters:

"lat" : float,
"lon" : float,
"floor" : int,
"building_id" : int 

Parameter Description

@return string Given a 2.5D Address (latitude, longitude and building-level and building-id), the API will return the Pintag Handle.

Requires Login:

true

Requires Context:

Context

The context providing parameter can either be a contagt-id (8-Bytes, Alphaumeric) or an integer as a building id. The context parameter name should make the choice obviouse, the type has not to be defined manually.

true

Requires contextParamName:

building_id

Requires WriteAccess:

WriteAccess

Only accounts that have an explicit write access to the defined context can execute this RPC, no matter if the authentication level matches or not.

false

Requires AuthenticationLevel:

Context

Authentication levels allow the SuperUser to define a by-RPC granular access configuration. If RPCs are chained in a single unified call and lenient is enabled, all allowed RPCs will be executed, while execution will fail entirely with lenient set to false.

STANDARD_USER

Requires Subbuilding Merge Strategy:

REPLACE

Cache Configuration

Response Cache

All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache and readonly.

Cache enabled:

false

Sample Request

->

{
    "lat": 49.49872,
    "lon": 8.46852,
    "floor": 0,
    "building_id": 131
}

<-

"prepqoujy6"