PutRoutesFile
Method requires user to be of Type AuthorizationLevel::SUPERUSER
RPC Configuration
Rpc Name:
Plain: PutRoutesFile
Sha1: 0ac1cb74796aa634f3e37f6dfd7bee23df3baa9f
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"building_id" : int,
"mapfiles" : array,
"startDate" : ?string = null,
"schedule" : bool =
Requires Login:
true
Requires 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:
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:
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
All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache
and readonly.
Cache enabled:
false
File Receiver Configuration
This RPC can receive Files.
Maximum Filesize
4 MB
Accepted File MimeTypes:
"application/vnd.openstreetmap.data+xml"
File Param Name(s):
[]