<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><br><div dir="ltr">sent from a phone</div><div dir="ltr"><br><blockquote type="cite">On 20. Dec 2019, at 00:16, Kathleen Lu via legal-talk <legal-talk@openstreetmap.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">And that is for extracting the entirety of each feature. The Geocoding Guideline states: "Furthermore, if only names are provided in Geocoding Results from OSM -- in particular, latitude/longitude information from OSM is not included in the Geocoding Results -- a collection of such results is not a substantial extract."</div></blockquote><br><div><br></div><div>it should be noted that in the case at hand the intention was to create a new database with translated/adapted OpenStreetMap data. The guideline says: </div><div>“<span style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34); font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Lato, Helvetica, Arial, sans-serif; font-size: 16px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0.2);"> Since individual Geocoding Results are insubstantial extracts, they may be stored and used together with other proprietary or third party data without having a share-alike impact on such other data, provided the Geocoding Results have not been aggregated to create a new database that contains the whole or a substantial part of the OSM database.</span></div><p style="font-size: 16px; margin: 0.5em 0px 1em; padding: 0px; border: 0px; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Lato, Helvetica, Arial, sans-serif; font-stretch: inherit; line-height: inherit; vertical-align: baseline; background-image: none; caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34); -webkit-tap-highlight-color: rgba(0, 0, 0, 0.2);">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. ”</p><p style="font-size: 16px; margin: 0.5em 0px 1em; padding: 0px; border: 0px; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Lato, Helvetica, Arial, sans-serif; font-stretch: inherit; line-height: inherit; vertical-align: baseline; background-image: none; caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34); -webkit-tap-highlight-color: rgba(0, 0, 0, 0.2);"><br></p><p style="font-size: 16px; margin: 0.5em 0px 1em; padding: 0px; border: 0px; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Lato, Helvetica, Arial, sans-serif; font-stretch: inherit; line-height: inherit; vertical-align: baseline; background-image: none; caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34); -webkit-tap-highlight-color: rgba(0, 0, 0, 0.2);">the guideline is about individual results, not about aggregations, for which the share alike provisions persist. From my interpretation this also implies that the attribution requirements persist for individual results, because otherwise it would not be clear that you cannot aggregate them. Do you agree?</p><p style="font-size: 16px; margin: 0.5em 0px 1em; padding: 0px; border: 0px; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Lato, Helvetica, Arial, sans-serif; font-stretch: inherit; line-height: inherit; vertical-align: baseline; background-image: none; caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34); -webkit-tap-highlight-color: rgba(0, 0, 0, 0.2);"><br></p><p style="font-size: 16px; margin: 0.5em 0px 1em; padding: 0px; border: 0px; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Lato, Helvetica, Arial, sans-serif; font-stretch: inherit; line-height: inherit; vertical-align: baseline; background-image: none; caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34); -webkit-tap-highlight-color: rgba(0, 0, 0, 0.2);">Cheers Martin </p></body></html>