Hi Martin, Thank you for your message.
I see where you are coming from, but forcing our contributors who want to take a photo of a fountain via our app to have wikimedia and openstreet map accounts while understandable is a non-starter. We added this image capture feature in large part due to overcome this barrier issue. All fountain images that are captured via other tools, added to wikimedia commons and linked to osm objects are welcome. It seems like the best solution is to keep the geotagged images on our server and serve them with an open license or via Mapillary. For the OSM edits, the only edit I plan to be doing for fountains which I have not visited myself will be adding an image tag ... and this will not be done realtime but only after a manual curation of the images ... (ie weeding out those which don't belong). I like the idea of adding in the future a more complex fountain edit page for fountains which requires an oauth identification. Best regards, Stuart On Tue, 19 May 2020 at 16:30, Martin Koppenhoefer <dieterdre...@gmail.com> wrote: > > > Am Di., 19. Mai 2020 um 13:30 Uhr schrieb European Water Project < > europeanwaterproj...@gmail.com>: > >> Hi Martin, >> >> you can store an image link on the OpenStreetMap object, this is also >> usable to find the object after someone has copied the tags to another >> object (e.g. node-> way/relation transformations), it will break if both, >> the image changes and the OpenStreetMap id changes. Mappers might also >> refrain from transferring the tags to e.g. a building if the image >> explicitly refers to just something inside the building and is not suitable >> for the whole building. >> >> >>>>Agree this is a good solution ... and if I can automate a way to bulk >> move the images to wikimedia commons, after manual curation, and add an >> image link to the photo in the osm object that would be best. >> >> > > ideally your webapp would upload (as the user that is using it) to > wikimedia commons and the name that commons confirms would be added via the > OSM Api (oauth) to the osm object (again as the contributing user). > The problem of batch upload is that a) you would be misrepresenting the > authorship of the image in commons (acting on their behalf), and similarly > b) on OSM it would not be individual users but a collective account which > modifies the data (we prefer the editing user being the author, so that we > ask questions back, and because it might make fighting vandalism easier). > > Cheers > Martin > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
