AddOrientationPoint

Class Description

Add a new OrientationPoint to an existing Campaign.
@return int OrientationPointId or false

RPC Configuration

Rpc Name:

Plain: AddOrientationPoint
Sha1: eb550ef9e5d9d1912a2a23b1564fcb5b6742888c

Rpc Call

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

Rpc Parameters:

"building_id" : int,
"campaign_id" : int,
"centerLat" : float,
"centerLon" : float,
"floor" : int,
"radiusInMeter" : float 

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.

true

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.

LOCAL_ADMINISTRATOR

Requires Subbuilding Merge Strategy:

SUBBUILDING_ONLY

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

->

{
    "building_id": 131,
    "campaign_id": 15,
    "lat": 51.231,
    "lon": 13.37,
    "floor": 0,
    "radiusInMeter": 9.88
}