<div dir="ltr">How do people feel about ref:GB:givefood to link back to Jason's datafeed or site? e.g. from <a href="https://www.openstreetmap.org/node/8429813322">https://www.openstreetmap.org/node/8429813322</a> ref:GB:givefood=the-whitehawk An app could connect to <a href="https://www.givefood.org.uk/api/2/foodbank/{ref:GB:givefood}/">https://www.givefood.org.uk/api/2/foodbank/{ref:GB:givefood}/</a> or <a href="https://www.givefood.org.uk/needs/at/{ref:GB:givefood}/">https://www.givefood.org.uk/needs/at/{ref:GB:givefood}/</a> ?<div><br></div><div>An alternative is to create Wikidata records then get givefood's id/slug onto there.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 2, 2021 at 3:29 PM Russ Garrett via Talk-GB <<a href="mailto:talk-gb@openstreetmap.org">talk-gb@openstreetmap.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Jason,<br>
<br>
Firstly I just have to say that we're not always fun-hating lawyers<br>
here but we have to try and be as meticulous as possible about<br>
preventing incorrectly-licensed data from entering OSM.<br>
<br>
On Thu, 2 Dec 2021 at 15:11, Jason Cartwright <<a href="mailto:jason@givefood.org.uk" target="_blank">jason@givefood.org.uk</a>> wrote:<br>
> However, the coordinates are derived from Google Maps' geocoder<br>
<br>
Unfortunately I must introduce you to the hilariously restrictive<br>
terms of the Google Maps Geocoding API:<br>
<br>
<a href="https://developers.google.com/maps/documentation/geocoding/policies" rel="noreferrer" target="_blank">https://developers.google.com/maps/documentation/geocoding/policies</a><br>
<br>
"It is prohibited to use Geocoding API data on a map that is not a Google map."<br>
"If your application displays data from the Geocoding API on a page or<br>
view that does not also display a Google Map, you must show a Powered<br>
by Google logo with that data."<br>
<br>
This particular issue should be a relatively easy fix - I would<br>
recommend re-geocoding using the OpenCage geocoder (<a href="http://opencagedata.com" rel="noreferrer" target="_blank">opencagedata.com</a>),<br>
which should cover your usage under the free tier. The resulting data<br>
will need to be released under a license which attributes<br>
OpenStreetMap, however.<br>
<br>
Cheers,<br>
<br>
-- <br>
Russ Garrett<br>
<a href="mailto:russ@garrett.co.uk" target="_blank">russ@garrett.co.uk</a><br>
<br>
_______________________________________________<br>
Talk-GB mailing list<br>
<a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-gb" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><br>
</blockquote></div>