SaveOrUpdateArea

RPC Configuration

Rpc Name:

Plain: SaveOrUpdateArea
Sha1: 75ee360e9924d4bc1478d8a9f544dee6a426e417

Rpc Call

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

Rpc I18n Name:

saveOrUpdateI18n

Rpc Parameters:

"bid" : int,
"rid" : int,
"name" : string,
"desc" : string,
"vertices" : array 

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:

bid

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

->

{
    "bid": 131,
    "rid": -1,
    "name": "Region added by Test",
    "desc": "The region by Test",
    "vertices": [
        {
            "lat": 49.4987963273435,
            "lng": 8.468922078609468
        },
        {
            "lat": 49.49848625067144,
            "lng": 8.46939414739609
        },
        {
            "lat": 49.49881374732299,
            "lng": 8.469716012477877
        },
        {
            "lat": 49.49892349305105,
            "lng": 8.469506800174715
        }
    ]
}

<-

{
    "vrId": 3
}