Changes between Version 20 and Version 48 of Help/Preferences/RemoteControl


Ignore:
Timestamp:
(multiple changes)
Author:
(multiple changes)
Comment:
(multiple changes)

Legend:

Unmodified
Added
Removed
Modified
  • Help/Preferences/RemoteControl

    v20 v48  
    1 [[TranslatedPages(outdated=This page is missing some new options and the list of commands is probably better situated on a separate page.)]]
     1[[TranslatedPages(outdated=This page is incomplete. Options description is missing.)]]
    22= Preferences > Remote Control =
    33
    4 [[Image(source:trunk/images/preferences/remotecontrol.png)]] **Settings for the remote control feature.**
     4[[JOSMImage(preferences/remotecontrol,middle,,48,link=,margin-right=20)]] **Settings for the remote control feature**
    55
    6 Remote Control allows JOSM to be controlled from other applications, e.g. from a web browser, by opening a listening TCP port (8111) on localhost where it accepts commands.[[BR]]
    7 Since JOSM version 6941 it is also listening for HTTPS on port 8112.[[BR]]
    8 **Note**: Due to security reasons this feature is disabled in the default settings and has to be enabled manually.
     6Remote Control allows JOSM to be controlled from other applications, e.g. from a web browser, by opening a listening TCP port (8111) on localhost where it accepts commands. \\
     7From JOSM version r6941 through r15469 it was also listening for HTTPS on port 8112. \\
     8**Note**: Due to security reasons the Remote Control is disabled in the default settings and has to be enabled manually.
    99
     10For JOSM version r6941 through r15469, if you access a website via HTTPS and use the Remote Control it will also use HTTPS to control your JOSM. If it does not work, note that your browser, security addons/plugins and firewalls may block this access (you may be able to whitelist/allow it inside these tools) – check your logs. In addition you may need to tell your browser to accept the self-signed JOSM HTTPS certificate. More details on some of these issues: [https://help.openstreetmap.org/questions/2208/how-do-i-enable-the-remote-control-in-josm How do I enable the "remote control" in JOSM?] (on the OSM help site).
    1011
    11 The following control options are available:
     12After JOSM r15469, websites cannot use HTTPS to control JOSM. Safari is the only major browser known to have issues with remote control commands on HTTPS websites.
    1213
    13 [[Image(RemoteControl6767.png)]]
     14**See the list of [wikitr:/Help/RemoteControlCommands Remote control commands].**
    1415
    15 
    16 * **Enable remote control** allows to switch the remote control feature on or off.
    17  * **Load data from API**
    18  * **Import data from URL**
    19  * **Load imagery layers**
    20  * **Change the selection**
    21  * **Change the viewport**
    22  * **Create new objects**
    23  * **Read protocol version**
    24 
    25 * **Confirm all Remote Control actions manually**
    26 
    27 == List of Commands ==
    28 
    29 A complete list of commands and mandatory/optional parameters is shown at http://127.0.0.1:8111/ (when JOSM is running).
    30 
    31 === {{{load_and_zoom}}} ===
    32 Instructs JOSM to download a bounding box from the API, zoom to the downloaded area and optionally select one or more objects.
    33 {{{
    34 GET /load_and_zoom?left=...&right=...&top=...&bottom=...&select=object[,object...]
    35 }}}
    36 where
    37 ||= **Parameter** =||= **Required/Optional** =||= **Meaning** =||
    38 || `left` || R || minimum longitude ||
    39 || `right` || R || maximum longitude ||
    40 || `bottom` || R || minimum latitude ||
    41 || `top` || R || maximum latitude ||
    42 || `select` || O || comma-separated list of objects that should be selected. Object specifiers are combinations of the words "way", "node", or "relation", and the numerical object id. Example: {{{select=way38473,node12399,node54646}}} ||
    43 || `addtags` || O || Optional parameter to add tags. The key and value is separated by "=" and multiple tags can be separated by a Pipe "|". See [#addtags details]. ||
    44 || `new_layer` || O || If true, downloads to a new layer ||
    45 
    46 ==== Example ====
    47 
    48 Start JOSM (don't forget to enable the !RemoteControl feature), then click on:
    49 
    50 [http://127.0.0.1:8111/load_and_zoom?left=8.19&right=8.20&top=48.605&bottom=48.590&select=node413602999]
    51 
    52 JOSM should now load an area in the German Schwarzwald and have the specified node selected.
    53 
    54 === {{{zoom}}} ===
    55 Instructs JOSM to zoom to the specified area and optionally select one or more objects.
    56 {{{
    57 GET /zoom?left=...&right=...&top=...&bottom=...&select=object[,object...]
    58 }}}
    59 Accepts the same parameters as the {{{load_and_zoom}}} command and uses the same code for zoom and selection. The only difference is that no data will be loaded from the API.
    60 
    61 **Hint**: This command can also be used to select objects only. Just enter a small arbitrary area to the left..bottom entries and add the object list to the select= option.
    62 === {{{import}}} ===
    63 Instructs JOSM to download the specified OSM file and add it to the current data set.
    64 {{{
    65 GET /import?url=...
    66 }}}
    67 
    68 
    69 
    70 === {{{imagery}}} ===
    71 Instructs JOSM to add an imagery (WMS/TMS) layer.
    72 {{{
    73 GET /imagery?title=...&type=...&url=...
    74 }}}
    75 where
    76 ||= **Parameter** =||= **Required/Optional** =||= **Meaning** =||
    77 || `title` || O || The display name of the layer ||
    78 || `type` || O || Type of the layer. Possible values are `wms`, `tms` and `bing` [[BR]] (since !RemoteControl Version 1.3) ||
    79 || `min_zoom` || O || The minimum zoom level [[BR]] (since !RemoteControl Version 1.4) ||
    80 || `max_zoom` || O || The maximum zoom level. For higher scales, the images of the maximum level is enlarged [[BR]] (since !RemoteControl Version 1.4) ||
    81 || `url` || R || The Request URL, including patterns. Must be the last parameter, everything after "&url=" is interpreted as URL, even if it contains "&" characters.  ||
    82 
    83 ==== Examples ====
    84 * TMS layer "osm" {{{http://tile.openstreetmap.org/{zoom}/{x}/{y}.png}}}
    85 
    86 [http://localhost:8111/imagery?title=osm&type=tms&url=http://tile.openstreetmap.org/%7Bzoom%7D/%7Bx%7D/%7By%7D.png]
    87 
    88 * WMS layer "landsat" {{{http://irs.gis-lab.info/?layers=landsat&SRS={proj}&WIDTH={width}&HEIGHT={height}&BBOX={bbox} }}}
    89 [http://localhost:8111/imagery?title=landsat&type=wms&url=http://irs.gis-lab.info/?layers=landsat&SRS=%7Bproj%7D&WIDTH=%7Bwidth%7D&HEIGHT=%7Bheight%7D&BBOX=%7Bbbox%7D]
    90 
    91 === {{{load_object}}} ===
    92 
    93 Instructs JOSM to download objects with a given id.
    94 {{{
    95 GET /load_object?new_layer=true|false&objects=...
    96 }}}
    97 where
    98 ||= **Parameter** =||= **Required/Optional** =||= **Meaning** =||
    99 || `objects` || R || Comma separated list of object ids, e.g. "{{{n1234,n1235,w84,r958493}}}" ||
    100 || `new_layer` || O || If true, downloads to a new layer ||
    101 || `addtags` || O || Optional parameter to add tags. The key and value is separated by "=" and multiple tags can be separated by a Pipe "|". See [#addtags details]. ||
    102 
    103 ==== Example ====
    104 
    105 [http://localhost:8111/load_object?new_layer=true&objects=w106159509]
    106 
    107 === {{{add_node}}} ===
    108 
    109 Instructs JOSM to create a new node at the given coordinates.
    110 
    111 **Note**: This action requires the permission ''Create new objects'' which is disabled by default.
    112 
    113 {{{
    114 GET /add_node?lon=...&lat=...
    115 }}}
    116 where
    117 ||= **Parameter** =||= **Required/Optional** =||= **Meaning** =||
    118 || `lon` || R || The longitude of the node ||
    119 || `lat` || R || The latitude of the node ||
    120 || `addtags` since v1.5|| O || Optional parameter to add tags. The key and value is separated by "=" and multiple tags can be separated by a Pipe "|". See [#addtags details]. ||
    121 
    122 ==== Example ====
    123 http://localhost:8111/add_node?lon=13.3&lat=53.2
    124 
    125 === {{{add_way}}} ===
    126 
    127 Instructs JOSM to create a new way with new way nodes at given coordinates.
    128 
    129 **Note**: This action requires the permission ''Create new objects'' which is disabled by default.
    130 
    131 {{{
    132 GET /add_way?way=lat1,lon1;lat2,lon2;...
    133 }}}
    134 where
    135 ||= **Parameter** =||= **Required/Optional** =||= **Meaning** =||
    136 || `way` || R || Pairs of latitude, longitude coordinates separated by semicolon. ||
    137 || `addtags` since v1.5|| O || Optional parameter to add tags. The key and value is separated by "=" and multiple tags can be separated by a Pipe "|". See [#addtags details]. ||
    138 
    139 ==== Example ====
    140 
    141 http://localhost:8111/add_way?way=53.2,13.3;53.3,13.3;53.3,13.2
    142 
    143 
    144 === {{{version}}} ===
    145 This command returns the current protocol version of the installed !RemoteControl interface. Developers can use it to query for a running instance of JOSM and also determine whether the requested functionality is available in the client.
    146 {{{
    147 GET /version[?jsonp=callback]
    148 }}}
    149 
    150 The command returns a json object containing an application identifier that is always "JOSM !RemoteControl", a major number and a minor number. Compatible protocol changes result in an increase of the minor number. Incompatible changes increase the major number. So a client application knowing of protocol version 1.0 can still talk to JOSM having 1.1. But it's not guaranteed to be working with 2.0. So the client should verify the major number.
    151 
    152 A typical output looks like this:
    153 {{{
    154 #!js
    155 {
    156    "protocolversion": {
    157       "major": 1,
    158       "minor": 0
    159    },
    160    "application": "JOSM RemoteControl"
    161 }
    162 }}}
    163 For older browsers not implementing [http://en.wikipedia.org/wiki/Cross-Origin_Resource_Sharing Cross-Origin Resource Sharing (CORS)] the command provides the possibility for jsonp callback. Load the URL in a script tag and supply the name of a callback that will receive the JSON data.
    164 
    165 Following is some sample code that checks for CORS capabilities and uses [http://en.wikipedia.org/wiki/JSONP JSONP] as a fallback solution.
    166 {{{
    167 #!js
    168 // in addition to the CC-BY-SA of the wiki feel free to use the following source for any purpose without restrictions (PD)
    169 // credits and additions appreciated: http://wiki.openstreetmap.org/wiki/User:Stephankn
    170 
    171 function checkJOSM(version){
    172    alert(version.application + " uses protocol version " + version.protocolversion.major + "." + version.protocolversion.minor);
    173    // do something useful, maybe showing edit button
    174 }
    175 
    176 var url = "http://127.0.0.1:8111/version";
    177 var useFallback = false;
    178 // currently FF3.5, Safari 4 and IE8 implement CORS
    179 if (XMLHttpRequest) {
    180    var request = new XMLHttpRequest();
    181    if ("withCredentials" in request) {
    182       request.open('GET', url, true);
    183       request.onreadystatechange = function(){
    184          if (request.readyState != 4) {
    185             return;
    186          }
    187          if (request.status == 200) {
    188             checkJOSM(eval('(' + request.responseText + ')'));
    189          }
    190       };
    191       request.send();
    192    }
    193    else if (XDomainRequest) {
    194       var xdr = new XDomainRequest();
    195       xdr.open("get", url);
    196       xdr.onload = function(){
    197          checkJOSM(eval('(' + xdr.responseText + ')'));
    198       };
    199       xdr.send();
    200    } else {
    201       useFallback = true;
    202    }
    203 }
    204 else {
    205    // no XMLHttpRequest available
    206    useFallback = true;
    207 }
    208 
    209 if (useFallback) {
    210    // Use legacy jsonp call
    211    var s = document.createElement('script');
    212    s.src = url + '?jsonp=checkJOSM';
    213    s.type = 'text/javascript';
    214    
    215    if (document.getElementsByTagName('head').length > 0) {
    216       document.getElementsByTagName('head')[0].appendChild(s);
    217    }
    218    
    219 }
    220 }}}
    221 
    222 
    223 === Adding, changing or deleting tags === #addtags
    224 Try this example: 
    225 [http://localhost:8111/load_and_zoom?addtags=wikipedia:de=Wei%C3%9Fe_Gasse|maxspeed=5&select=way23071688,way23076176,way23076177,&left=13.739727546842&right=13.740890970188&top=51.049987191025&bottom=51.048466954325].
    226 (Works also with the zoom-command)
    227 
    228 The user must review the tags and the selection before the tags are applied to the selected objects.
    229 If the tag exists on some objects, it will be can be replaced.
    230 
    231 Since protocol version 1.5
    232 - `add_node` and `add_way` commands support `addtags` parameter
    233 - It is possible to use `=` character in value and all leading/trailing spaces are trimmed.
    234 [http://localhost:8111/add_node?lon=13.3&lat=53.2&addtags=natural=tree|name=%20%20%20==Great%20Oak==] (creates node with natural=tree an name="==Great Oak==")
    235 - If empty value is found, tag is to be deleted from objects (checkbox-confirmation is needed)
    236 [http://localhost:8111/load_and_zoom?addtags=wikipedia:de=|maxspeed=&select=way23071688,way23076176,way23076177,&left=13.739727546842&right=13.740890970188&top=51.049987191025&bottom=51.048466954325].
    237 
    238 === Other commands ===
    239 Remotecontrol allows other plugins to add additional commands. The other registers a RequestHandler class and specifies a command to be handled by this class. The command syntax has to be defined by the other plugin.
    240 
    241 Reverter plugin since version 27091 makes use of this feature.
    242 
    243 == See also ==
    244 [http://wiki.openstreetmap.org/wiki/JOSM/Plugins/RemoteControl Old JOSM Remote-Plugin page at OSM wiki]
     16[[Image(PreferencesRemoteControl.2.png​,link=,800)]]
    24517
    24618----
    247 Back to [wiki:Help/Action/Preferences Preferences][[Br]]
    248 Back to [wiki:/Help Main Help]
     19Back to [wikitr:/Help/Action/Preferences Preferences] \\
     20Back to [wikitr:/Help Main Help]