Merge: develop
This commit is contained in:
commit
9cffe6814e
154 changed files with 1199 additions and 41754 deletions
|
@ -1,4 +1,3 @@
|
|||
|
||||
[//]: # (WARNING: this file is automatically generated. Please find the sources at the bottom and edit those sources)
|
||||
|
||||
Special tag renderings
|
||||
|
@ -421,10 +420,11 @@ Note that these values can be prepare with javascript in the theme by using a [c
|
|||
|
||||
name | default | description
|
||||
------ | --------- | -------------
|
||||
tags_to_apply | _undefined_ | A specification of the tags to apply
|
||||
tags_to_apply | _undefined_ | A specification of the tags to apply. This is either hardcoded in the layer or the `$name` of a property containing the tags to apply. If redirected and the value of the linked property starts with `{`, the other property will be interpreted as a json object
|
||||
message | _undefined_ | The text to show to the contributor
|
||||
image | _undefined_ | An image to show to the contributor on the button
|
||||
id_of_object_to_apply_this_one | _undefined_ | If specified, applies the the tags onto _another_ object. The id will be read from properties[id_of_object_to_apply_this_one] of the selected object. The tags are still calculated based on the tags of the _selected_ element
|
||||
maproulette_task_id | _undefined_ | If specified, this maproulette-challenge will be closed when the tags are applied
|
||||
|
||||
|
||||
#### Example usage of tag_apply
|
||||
|
@ -437,12 +437,13 @@ id_of_object_to_apply_this_one | _undefined_ | If specified, applies the the tag
|
|||
|
||||
This button will copy the point from an external dataset into OpenStreetMap
|
||||
|
||||
|
||||
Note that the contributor must zoom to at least zoomlevel 18 to be able to use this functionality.
|
||||
It is only functional in official themes, but can be tested in unoffical themes.
|
||||
It is only functional in official themes, but can be tested in unoffical themes.
|
||||
|
||||
#### Specifying which tags to copy or add
|
||||
|
||||
The argument `tags` of the import button takes a `;`-seperated list of tags to add (or the name of a property which contains a JSON-list of properties).
|
||||
The argument `tags` of the import button takes a `;`-seperated list of tags to add (or the name of a property which contains a JSON-list of properties).
|
||||
|
||||
These can either be a tag to add, such as `amenity=fast_food` or can use a substitution, e.g. `addr:housenumber=$number`.
|
||||
This new point will then have the tags `amenity=fast_food` and `addr:housenumber` with the value that was saved in `number` in the original feature.
|
||||
|
@ -489,26 +490,26 @@ icon | ./assets/svg/addSmall.svg | A nice icon to show in the button
|
|||
snap_onto_layers | _undefined_ | If a way of the given layer(s) is closeby, will snap the new point onto this way (similar as preset might snap). To show multiple layers to snap onto, use a `;`-seperated list
|
||||
max_snap_distance | 5 | The maximum distance that the imported point will be moved to snap onto a way in an already existing layer (in meters). This is previewed to the contributor, similar to the 'add new point'-action of MapComplete
|
||||
note_id | _undefined_ | If given, this key will be read. The corresponding note on OSM will be closed, stating 'imported'
|
||||
location_picker | photo | Chooses the background for the precise location picker, options are 'map', 'photo' or 'osmbasedmap' or 'none' if the precise input picker should be disabled
|
||||
maproulette_id | _undefined_ | The property name of the maproulette_id - this is probably `mr_taskId`. If given, the maproulette challenge will be marked as fixed. Only use this if part of a maproulette-layer.
|
||||
|
||||
|
||||
#### Example usage of import_button
|
||||
|
||||
`{import_button(,,Import this data into OpenStreetMap,./assets/svg/addSmall.svg,,5,,photo,)}`
|
||||
`{import_button(,,Import this data into OpenStreetMap,./assets/svg/addSmall.svg,,5,,)}`
|
||||
|
||||
|
||||
|
||||
### import_way_button
|
||||
|
||||
This button will copy the data from an external dataset into OpenStreetMap
|
||||
This button will copy the data from an external dataset into OpenStreetMap, copying the geometry and adding it as a 'line'
|
||||
|
||||
|
||||
Note that the contributor must zoom to at least zoomlevel 18 to be able to use this functionality.
|
||||
It is only functional in official themes, but can be tested in unoffical themes.
|
||||
It is only functional in official themes, but can be tested in unoffical themes.
|
||||
|
||||
#### Specifying which tags to copy or add
|
||||
|
||||
The argument `tags` of the import button takes a `;`-seperated list of tags to add (or the name of a property which contains a JSON-list of properties).
|
||||
The argument `tags` of the import button takes a `;`-seperated list of tags to add (or the name of a property which contains a JSON-list of properties).
|
||||
|
||||
These can either be a tag to add, such as `amenity=fast_food` or can use a substitution, e.g. `addr:housenumber=$number`.
|
||||
This new point will then have the tags `amenity=fast_food` and `addr:housenumber` with the value that was saved in `number` in the original feature.
|
||||
|
@ -570,12 +571,13 @@ snap_to_layer_max_distance | 0.1 | Distance to distort the geometry to snap to t
|
|||
|
||||
This button will modify the geometry of an existing OSM way to match the specified geometry. This can conflate OSM-ways with LineStrings and Polygons (only simple polygons with one single ring). An attempt is made to move points with special values to a decent new location (e.g. entrances)
|
||||
|
||||
|
||||
Note that the contributor must zoom to at least zoomlevel 18 to be able to use this functionality.
|
||||
It is only functional in official themes, but can be tested in unoffical themes.
|
||||
It is only functional in official themes, but can be tested in unoffical themes.
|
||||
|
||||
#### Specifying which tags to copy or add
|
||||
|
||||
The argument `tags` of the import button takes a `;`-seperated list of tags to add (or the name of a property which contains a JSON-list of properties).
|
||||
The argument `tags` of the import button takes a `;`-seperated list of tags to add (or the name of a property which contains a JSON-list of properties).
|
||||
|
||||
These can either be a tag to add, such as `amenity=fast_food` or can use a substitution, e.g. `addr:housenumber=$number`.
|
||||
This new point will then have the tags `amenity=fast_food` and `addr:housenumber` with the value that was saved in `number` in the original feature.
|
||||
|
@ -887,23 +889,7 @@ Id-key | id | The property name where the ID of the note to close can be found
|
|||
|
||||
#### Example usage of add_image_to_note
|
||||
|
||||
The following example sets the status to '2' (false positive)
|
||||
|
||||
```json
|
||||
{
|
||||
"id": "mark_duplicate",
|
||||
"render": {
|
||||
"special": {
|
||||
"type": "maproulette_set_status",
|
||||
"message": {
|
||||
"en": "Mark as not found or false positive"
|
||||
},
|
||||
"status": "2",
|
||||
"image": "close"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
`{add_image_to_note(id)}`
|
||||
|
||||
|
||||
|
||||
|
@ -944,7 +930,23 @@ maproulette_id | mr_taskId | The property name containing the maproulette id
|
|||
|
||||
#### Example usage of maproulette_set_status
|
||||
|
||||
`{maproulette_set_status(,confirm,,1,mr_taskId)}`
|
||||
The following example sets the status to '2' (false positive)
|
||||
|
||||
```json
|
||||
{
|
||||
"id": "mark_duplicate",
|
||||
"render": {
|
||||
"special": {
|
||||
"type": "maproulette_set_status",
|
||||
"message": {
|
||||
"en": "Mark as not found or false positive"
|
||||
},
|
||||
"status": "2",
|
||||
"image": "close"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
@ -1025,7 +1027,7 @@ tagrendering | _undefined_ | An entire tagRenderingConfig
|
|||
|
||||
A button to run many actions for many features at once. To effectively use this button, you'll need some ingredients:
|
||||
|
||||
- A target layer with features for which an action is defined in a tag rendering. The following special visualisations support an autoAction: tag_apply, import_way_button
|
||||
- A target layer with features for which an action is defined in a tag rendering. The following special visualisations support an autoAction: tag_apply, import_way_button, conflate_button
|
||||
- A host feature to place the auto-action on. This can be a big outline (such as a city). Another good option for this is the layer
|
||||
- [current_view](./BuiltinLayers.md#current_view)
|
||||
- Then, use a calculated tag on the host feature to determine the overlapping object ids
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue