[OSM-dev] Use of OSM API for non-editing third party applications

[Simon Poole]

There is a large amount of precedent, for example mapillary, maproulette
and lots that I've forgotten. So the answer is likely that while the
website-devs are not in love with it, it is perfectly acceptable.


Simon


Am 01.08.2019 um 13:52 schrieb Nick Whitelegg:
>
> Hi,
>
>
> I'm just asking something which was raised as an issue in my Gitlab
> repository for OpenTrailView (www.opentrailview.org
> <http://www.opentrailview.org>; fully FOSS 360 panorama site which
> uses OSM ways to connect panoramas together).
>
>
> The person who raised the issue requested that OSM logins be used on
> OpenTrailVIew rather than (as currently) its own login system. I
> suspect the reason is security-related as it allows users to use an
> existing trusted authentication system.
>
>
> As OpenTrailView does not include provision for editing OSM data, I
> suspect the answer is no - but is it acceptable for third-party
> OSM-related sites which do not edit the data to 'piggyback' on OSM's
> authentication system like this?
>
>
> Thanks,
>
> Nick
>
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20190801/36471996/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20190801/36471996/attachment.sig>