| 13 | | * make a permanent record of the editing time for each changeset, in the form of **automatically created Rovas work report**, |
| 14 | | * **earn the NEO currency Chron** for the JOSM work. Use the currency to reward other volunteers, or convert it in Rovas into Euros. |
| | 13 | * make a permanent record of the editing time for each changeset, in the form of an **automatically created Rovas work report**, |
| | 14 | * Rovas issues a reward for verified time reported in the work reports created by this plugin — either **Chrons** (10 Chron = 1 hour) — which can be exchanged for certain benefits in Rovas — or the same amount of **Merits** — a measure of economic value you **donated** to the commons. All work reports are verified by other Rovas users, or auto-approved once user reaches the **Trusted user** status. |
| 17 | | * One of the NEO rules is that the time reported in each work report must be verified. To do so, Rovas selects two verifiers and sends them verification requests that include links to a Web page (such as osmcha.org), showing the changes made in the changeset. This allows each changeset to be seen by at least two users, increasing the likelihood of detecting any mapping errors. This should lead to **improvement of the data quality** in the OSM database. |
| 18 | | * having a reliable and verified record of time spent by OSM mappers can **improve funding of the whole OSM ecosystem**. For example, the total labor time, tallied from the individual work reports as shown on the [https://rovas.app/openstreetmap/ Openstreetmap project page in Rovas] can be used to provide potential sponsors with verified data about mapping effort exerted by volunteer mappers. The time record can also serve as an instrument to incentivize commercial consumers of the OSM data to reciprocate and reward the OSM community with much needed funds. These can be used to improve the server infrastructure or financially support mapping efforts across the globe. |
| | 17 | * One of the NEO rules is that the time reported in each work report must be verified. To do so, Rovas selects two verifiers and sends them verification requests that include links to a Web page (such as osmcha.org), showing the changes made in the changeset. This allows each changeset to be seen by at least two users, increasing the likelihood of detecting any mapping errors. This should lead to **improvement of the data quality** in the OSM database. |
| | 18 | * having a reliable and verified record of time spent by OSM mappers can **inform funding discussions** across the OSM ecosystem. For example, the total labor time, tallied from the individual work reports as shown on the [https://rovas.app/openstreetmap/ OpenStreetMap project page in Rovas], can give potential sponsors verified data about mapping effort by volunteer mappers. That record can also help make the case for commercial consumers of OSM data to support the community (for example server infrastructure or mapping efforts). It does not by itself promise or guarantee any payout. |