[OSM-talk] Mobile Application for optimizing OSM ski area data

[Nick Whitelegg]

As others have said, users should authenticate with their own OSM accounts so that malicious edits can be detected.


There's a very good Java library - osmapi - which I would strongly recommend for doing editing from within an Android app. It's developed by Tobias Zwick, developer of StreetComplete, and is available here:


https://github.com/westnordost/osmapi

<https://github.com/westnordost/osmapi>

To use OAuth, you can use another very good open source library: Signpost.


I myself have developed a custom editor in recent months, using osmapi and Signpost - it's aimed at allowing England and Wales footpath mappers to add rights of way quickly and easily to OSM. It's a bit rough round the edges, but you might find the code useful for reference. StreetComplete itself is also a good point of reference, though that's a significantly more complex app.


https://gitlab.com/nickw1/mapthepaths-android


Nick




<https://github.com/westnordost/osmapi>


________________________________
From: Valentina Böhm <vbhm at live.at>
Sent: 26 October 2018 13:22:16
To: talk at openstreetmap.org
Subject: [OSM-talk] Mobile Application for optimizing OSM ski area data


I am planning to develop an mobile app to optimize ski area data provided by OSM. The user should be able to use the app for locating him- or herself in a ski area and have a look at all the different slopes and lifts and all their details. But the user should also be able to optimize the data of the ski area. First of all for the better experience when using the app for navigating. But also for providing OSM optimized and more detailed data about ski areas.

If a user wants to optimize the data he or she can either manually change the data, for example, edit the name or reference number of a slope or lift. Or he or she can provide their movement data by tracking it with the application while skiing. The tracked data should, in the end, help to fill gaps between slopes or slopes and lifts. Or even detect new unknown slopes.

What would you recommend regarding authentication? Is it ok if users of my app are committing data on my behalf or should all users have their own OSM account?

If users have their own account, is it possible and ok if I prepare the data with my algorithm and commit the data on their behalf?

In general, what is your recommendation regarding this kind of third-party integration? Are special API tokens provided for third-party apps?

I’m also interested in feedback about the idea. Are there similar projects? What do you think of my idea?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20181026/e93e1b3a/attachment-0001.html>