[openstreetmap/openstreetmap-website] Update to iD v2.13.0 (#2122)

[Quincy Morgan]

> PS: and yes we (as in LWG now) will need to have a look at the data protection implications of the integration.

@simonpoole Sure thing! Take all the time you need.

> So then there won't be any unsolicited call-outs to some radiant/maxar/maprules whatever site, but it's just that you can supply your own JSON file when calling ID, did I get that right? And the only way that radiant/maxar/whoever come into this is not by running a server that we connect to, but just by having defined the format of the JSON file?

@woodpeck That's right. Radiant defined the JSON format and built out the maprules feature on their fork of iD. At the Facebook-hosted meetup, @bhousel and I worked with them to [bring the feature to iD proper](https://github.com/openstreetmap/iD/pull/5617). Facebook personnel were not involved with this work.

The URLs can point to JSON files hosted anywhere, for example by a tasking manager. There are no calls to Radiant servers nor data sent to them. Radiant has solutions on their end for generating JSON files, but those are independent of iD.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/2122#issuecomment-456926088
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190123/c400cf10/attachment.html>