<div dir="ltr"><div>After browing the pages of a company that offers OSM based geocoding, I have been reading again through the geocoding guidelines</div><div><a href="https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines/Geocoding_-_Guideline">https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines/Geocoding_-_Guideline</a></div><div><br></div><div>In particular this part: "If the Geocoder is Publicly Used, then the provider
of the Geocoder ... must provide attribution to OpenStreetMap
as described in Section 4.3 of the ODbL"</div><div><br></div><div>So basically everybody using this geocoder should be made aware that the results are based on data from OpenStreetMap.<br></div><div><br></div><div>I believe this implies that you should not be able to sign up, generate an API key, use the testing tutorials and switch to batch geocoding without necessarily having been presented some kind of note about the data being from OSM and licensed ODbL. The latter, because of:<br></div><div><br></div><div> "If Geocoding Results are used to create a new database that contains the
whole or a substantial part of the contents of the OSM database, this
new database would be considered a Derivative Database and would trigger
share-alike obligations under section 4.4.b of the ODbL." <br></div><div><br></div><div>Creating a database is one of the primary uses of a geocoding service. Of course you could throw the results away, but for many use cases you will keep them.</div><div><br></div><div>What do you think how should appropriate attribution look like when providing geocoding services?</div><div><br></div><div>Cheers,<br></div><div>Martin<br></div><div><br>
</div></div>