Hi friends
I'm mining a few actionable nuggets from this discussion.
* Document (or link to documentation) on how the OSMTM works in the wiki,
including structure of changeset comments.* Update guidance to encourage
mappers to add their own insights in changeset comments* Share more the
downstream analysis of changeset comments, like http://osmgeoweek.org/metrics*
Make the point person for an OSMTM visible and contactable for feedback.*
Investigate potential use of other tags in the changeset
Created a GitHub ticket for working through ideas
https://github.com/hotosm/osm-tasking-manager2/issues/703
Mikel
ps For the Argentinian case, has anyone asked the local community there to
reach out? I'm sure they would be able to help them get on the right track. *
Mikel Maron * +14152835207 @mikel s:mikelmaron
On Thursday, November 19, 2015 3:43 AM, Michael Reichert <naka...@gmx.net>
wrote:
Hi,
Am 19. November 2015 01:52:40 MEZ, schrieb john whelan <jwhelan0...@gmail.com>:
> HOT and OSM are slightly different, HOT maps on OSM but uses a simpler
> more
> standardized approach.
HOT uses the OSM database/platform and therefore it has to adapt and follow
OSM's rules. Nobody forces you to use OSM. Why don't you do something like
OpenHistoricalMap and use your own database basrd on OSM software?
> HOT tends to map in areas that do not have a great deal of OSM mapping
> already in place so I don't see that it really matters if they use
> preset
> comments from the tile system. The HOT comment gives you the task and
> tile
> number so you can look up on the tile system where it is and also what
> has
> been asked for.
A mapper should be able to get an idea what has been edited at a given
changeset without decrypting the changeset comment using an external service
(HOT tasking manager in this case). Who guarantees that HOT tasking manager
will still be online in 5 or 10 years?
Best regards
Michael
--
Diese Nachricht wurde auf einem Smartphone verfasst, ist daher nicht
GPG-signiert und enthält Tippfejler.
This message was been written on a smartphone. That's why it is not GPG-signed
and may contain tyops.
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
