forked from MapComplete/MapComplete
Themes(benches): more work on integrating openbenches, polish a bit more
This commit is contained in:
parent
87823caabc
commit
11ab4965c6
6 changed files with 212 additions and 221 deletions
|
@ -12,7 +12,35 @@ A perfect example of this is to setup such a challenge to e.g. import new points
|
|||
|
||||
## Preparing the data
|
||||
|
||||
Convert your source data into a geojson. Use *`tags`* as field where all the OSM-properties should go. Make sure to include all tags there.
|
||||
Convert your source data into a geojson. Use *`tags`* as field where all the OSM-properties should go. Make sure to include all tags that should be imported there and stringify it.
|
||||
|
||||
You have quite some freedom for the other tags. Make sure to add an *id* tag. Other tags (e.g. images, metadata) may go into the properties as well.
|
||||
However, do _not_ add the generic tags for the layer to import into, to avoid that the maproulette challenges are loaded by the target layer.
|
||||
|
||||
|
||||
```
|
||||
{
|
||||
"type": "FeatureCollection",
|
||||
"features": [
|
||||
{
|
||||
"type": "Feature",
|
||||
"geometry": {"type": "Point", "coordinates": [1.234, 5.678]},
|
||||
"properties": {
|
||||
"id": ..., # Especially important when you want to rebuild the data
|
||||
"image": ...,
|
||||
"lastModifiedBy": ..., # from the source data, just to help
|
||||
"tags": "foo=bar;name=xyz;image=...", # To be imported
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
]
|
||||
}
|
||||
|
||||
```
|
||||
|
||||
Then, create a challenge on https://maproulette.org/admin/projects (or, if you want to test first, on https://staging.maproulette.org/)
|
||||
|
||||
|
||||
Hint: MapRoulette has a button 'rebuild task', where you can first 'remove all incomplete tasks'. This is perfect to start over in case of small data errors.
|
||||
|
||||
|
@ -127,35 +155,3 @@ The following example uses the calculated tags `_has_closeby_feature` and `_clos
|
|||
The easiest way is to reuse a tagrendering from the [Maproulette-layer](./Docs/Layers/maproulette.md) (_not_ the `maproulette-challenge`-layer!), such as [`maproulette.mark_fixed`](./Docs/Layers/maproulette.md#markfixed),[`maproulette.mark_duplicate`](./Docs/Layers/maproulette.md#markduplicate),[`maproulette.mark_too_hard`](./Docs/Layers/maproulette.md#marktoohard).
|
||||
|
||||
In the background, these use the special visualisation [`maproulette_set_status`](./Docs/SpecialRenderings.md#maproulettesetstatus) - which allows to apply different status codes or different messages/icons.
|
||||
|
||||
## Creating a maproulette challenge
|
||||
|
||||
A challenge can be created on https://maproulette.org/admin/projects
|
||||
|
||||
This can be done with a geojson-file (or by other means).
|
||||
|
||||
MapRoulette works as a geojson-store with status fields added. As such, you have a bit of freedom in creating the data, but an **id** field is mandatory. A **name** tag is recommended
|
||||
|
||||
To setup a guided import, add a `tags`-field with tags formatted in such a way that they are compatible with the [import-button](./Docs/SpecialRenderings.md#specifying-which-tags-to-copy-or-add)
|
||||
|
||||
|
||||
(The following example is not tested and might be wrong.)
|
||||
|
||||
```
|
||||
{
|
||||
"type": "FeatureCollection",
|
||||
"features": [
|
||||
{
|
||||
"type": "Feature",
|
||||
"geometry": {"type": "Point", "coordinates": [1.234, 5.678]},
|
||||
"properties": {
|
||||
"id": ...
|
||||
"tags": "foo=bar;name=xyz",
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
]
|
||||
}
|
||||
|
||||
```
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue