GenerateRoomTemplate

Class Description

Method requires user to be of Type AuthorizationLevel::SUPERUSER
@param array attributeMap expects an associative array[string] = string,

where osm attributes can be allowlisted. the key must be a static string, the value can be regex.
@param ?float minLat

@param ?float minLon

@param ?float maxLat

@param ?float maxLon Optional Boundingbox

RPC Configuration

Rpc Name:

Plain: GenerateRoomTemplate
Sha1: 00881479829e9fd33b72d2e7cc6992d89c168628

Rpc Call

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

Rpc Parameters:

"building_id" : int,
"floor" : int,
"attributeMap" : ?array = [],
"minLat" : ?float = null,
"minLon" : ?float = null,
"maxLat" : ?float = null,
"maxLon" : ?float = null 

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

Has Named Parameters:

true

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.

SUPERUSER

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,
    "floor": 0
}

<-

true