Il ven 27 mar 2020, 22:03 Andrea Musuruane <[email protected]> ha scritto:
> > On Fri, Mar 27, 2020 at 9:30 PM Francesco Ansanelli <[email protected]> > wrote: > >> >> >> Il ven 27 mar 2020, 11:28 Martin Koppenhoefer <[email protected]> >> ha scritto: >> >>> Am Fr., 27. März 2020 um 11:22 Uhr schrieb Francesco Ansanelli < >>> [email protected]>: >>> >>>> The wiki states: "*Importing* is the process of uploading external >>>>> data to OSM." >>>>> https://wiki.openstreetmap.org/wiki/Import >>>>> >>>>> To me it seems that you are proposing to import external data, which >>>>> implies you would have to follow the usual import procedures. >>>>> >>>> >>>> Please also be aware that users are free to not accept in part or >>>> completely the suggestions and that Osmose itself is equiparabile to a Map >>>> Layer. >>>> >>> >>> >>> I am perfectly aware of this. Any import works like this. People decide >>> what to take and what not. The question is not about the nature of Osmose >>> but from where the data is derived. If it is _external_ data, it is an >>> import. >>> >> >> Ok. So when you use mapillary as source for OSM imports you have a >> documented procedure and a special account, right? >> > > The usage of Mapillary images to derive data is not different from the > usage of aerial images such as Bing or Maxar to derive data. We have > special permissions for this kind of usage (and it is not an import). > > You want to perform something different. You want to grab data from an > external database and put them in OSM (and this is an import). > > Please also note that images and databases are covered by different > rights, at least in the EU. > Mapillary also provides recognised objects from an API that is implemented also by iD editor and associates a mapillary=* tag.... It's an external dataset. Francesco > > BR, > > Andrea > >
_______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
