Before adding strings to the project, I need to make sure that these can be easily translated to other languages by contributors.

Changes to wikimedia_commons tags (#10) should be saved in the app for upload at a later point. An indicator should show how many changes are pending. Users can decide when they want to upload them.

A license for the app needs to be chosen.

In 2012 I was working for a municipality and I asked to code an app that could first show OpenStreetMap, let select an object then the picture could be taken and pushed to Flickr.
Here is the link https://github.com/NaturalSolutions/ImageInOsm

What was really good for me is that Flickr is very easy to move pictures in a folder, add tags, change the name...

When the user decides to upload, the changes in wikimedia_commons tags (#11) should be added to a changeset and then be uploaded to OSM. The app should make sure that linked images or categories do already exist.

Before making Wikimedia uploads possible, the app must inform users about copyright and privacy rules. I must think about where and how regularly users of the app should be made aware of these rules.

Pages that should be linked:

• https://commons.wikimedia.org/wiki/Commons:Licensing
• https://commons.wikimedia.org/wiki/Commons:Photographs_of_identifiable_people

After login to OSM (#9) has been added, the object modal (#6) should have an input field to manually add or edit the value for the wikimedia_commons tag. This will be the foundation for the later automatic editing for the tag.

For example a photo for each bike stand, or each bench is probably too much for wikimedia. So where is the line? Should we maintain a list of tags that are worthy, or a list of unworthy? A list of worthy seems safer, but it's going to be a big one.

In the photo gallery of an object, an automatically created attribution should be shown.

Later, it should be possible to share location (coordinates) with the app and to open geo: links with it.

I must think about how I can make sure that my app as accessible as possible. This is a topic I don't know much about, so any help would be appreciated.

A filter menu should be added to show different types of objects on the in the data layer (#3):

Which kinds of objects are relevant enough should be dicussed in a separate issue (#31).

Query Overpass for all buildings inside the viewport and add them as a layer to the map (#2).

Color codes:

• buildings without wikimedia_commons and without image tag should be colored red.

• buildings with image tag only should be colored orange

• buildings with wikimedia_commons tag should be colored green

• Write query and save response

• Render response as layer on the map

• We need to find out at what zoom levels the query can be activated without a timeout.

• We need to find out if it is possible to circumvent IP quota

The oldest Android version to be supported needs to be chosen.

IDEA :
when we take pictures we may have to add to the pictures some categorizations that would be added in matadata picture, for this some standard profiles would be helpfull : such like the OSM features

The persona would help to quickly switch from one profile to another

At a later stage the viewer should also look for the wikidata-Tag and query if a Wikimedia Commons category or image is attached to the Wikidata object and show them if that is the case.

The editor should semi-automatically add wikimedia_commons tags in such cases.

When taking pictures we may have a lot that do not have the same quality nor usage :

• photo-annotation while walking, or in a train, car... : short term storage if the note is closed
• photo-checking : just to proove that an objetc still exist (recycling, waste basket, fire_hydrant...) : may be usefull to see the object change from one year to another
• photo-illustration : that king of picture is mostly taken for re-use purpose (wikimedia, website, and long term storage)

The app could suggest a way to take picture :

• this note doesn't have picture and is not solved could you add a picture
• this object doesn't have a picture and is important for the OSM community
• this object already has a picture (monument, statue...) : could you take a wide picture, narrow picture, artist name detail... [step by step]

Hi bzw. Hallo Michael

FYI: We at Institute for Software at OST have written a "Commons Uploader" (PhotoUploadApp) in Flutter.
It's a mobile app for uploading images to Wikimedia Commons available in Play Store and open source.
It's "under funded", meaning I'm open to hand it over if someone want's to take over the maintenance job.
See https://github.com/geometalab/PhotoUploadApp .

A gallery with all wikimedia_commons images linked from the object should be shown in the modal (#6).

Configuration should be possible of:

• Keeping photos on phone after upload
• If yes, which storage they should be stored on

Create possibility to log into an OpenStreetMap account and keep logged in.

I have decided to make a prototype of the app with Adobe XD. This will make it easier for others to understand the goals of the project and also help me to refine my concept before actually translating it into code.

When an object on the data layer (#3) is selected, a modal should be opened with information about the item:

• Name

• Type (e.g. "Apartment building")

• Address

• OSM ID (with Link)

• Button for uploading photos

• For type, maybe presets from an OSM editor could be used

• For address, an Nominatem request could be used (if there are no address tags at the object)

A navigation element needs to be added that shows log-in status, pending changes and access to settings.

This is the first step for creating the app. Deciding for a solution for displaying the background map and, later, the data layer (#3).

A link dump for this task:

• https://github.com/osmlab/editor-layer-index
• https://stackoverflow.com/questions/15946316/use-leaflet-in-an-android-application-to-show-online-map
• https://forum.openstreetmap.org/viewtopic.php?id=61005
• https://wiki.openstreetmap.org/wiki/Mapsforge

What needs time is to name each picture. In my idea we could gather the good informations for this :
Adress +number+city+country+ISO date

Here you have an example https://commons.wikimedia.org/wiki/Category:Shops_in_Orange_(Vaucluse)

When importing photos from Gallery, creation date and location needs to be read from the EXIF data of the file.

As the answer of the OSMF states that we cannot automatically create photo description pages out of OSM data, we need to find new ways to reach the goal of fast and easy upload of photos to Wikimedia Commons. These should be collected in this issue.

At a later point, a QA mode could be added. It could compare Commons categories with OSM data and ask the user about missing or inconsistent data. For example:

The photo of this building is in the Wikimedia Commons category Brick buildings in New York City. Do you want to add building:material=brick to the OpenStreetMap object?

See commons-app/apps-android-commons#4371 and commons-app/apps-android-commons#883

Maybe improving existing app would be better idea? More people who can help in maintaining and creation, Commons part is already coded, existing userbase.

Even if they would reject contribution - maybe forking it would be better than work from scratch.

When automatically creating image description pages from OpenStreetMap data, I have to make sure that the app doesn't violate the ODbL license of that data.

Maybe a way could be to add a template to the image description page like

The original description page of this file was created automatically from OpenStreetMap data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF).

But I don't know if that is enough.

Add photography feature. This is only the basic implementation without upload functionality.

• Create button in the object modal (#6) that triggers photo intent with choice between choosing from gallery and launching photo app
• Decide where photos should be stored and if this should be handled differently when photo came from gallery or from photo app (see below)
• Decide file naming scheme. (See below)

It should be possible to share an image from other Android apps with OSM Photos. The app should then ask the user which object the picture belongs to.