Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal to improve the OSMTracker tool for uploading traces to GitHub repositories #344

Open
JeanMarcoRU opened this issue Dec 14, 2022 · 0 comments

Comments

@JeanMarcoRU
Copy link

OSMTracker is a mature software in terms of development, so it is in the maintenance stage, requiring constant updates and improvements in new tools.
Communities use OSMTracker in their thematic mappings, and new needs arise that must be addressed with improvements to existing functionality or the implementation of new features. In the tool's Github repository users often share their needs for new functionalities, in 2017 two needs were raised [link]: one, to implement a functionality to download and install custom button layouts in a simpler way and the other, to upload traces to a shared folder and not only to OSM. The first of these functionalities was implemented and incorporated into the tool in version 0.7.2. The need to upload traces to a shared folder or repository and not only OSM is still pending to be implemented.

My proposal is to have the possibility to link the GitHub account in OSMtracker to have a NEW FUNCTION to upload GPX traces to an own repository, including the options to create a new repository, create a Fork of an existing repository and create a Pull Request. For this proposal I made the following prototype in Figma [link], currently this prototype only has a Spanish version, but the implementation in OSMtracker will be in English and with support in other languages over time.

Screenshot of the Figma prototype:

Commit

@jamescr jamescr added this to the 1.0.2 milestone Feb 21, 2023
@jamescr jamescr removed this from the 1.0.2 milestone Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants