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

Simple location search and routing / navigation feature in-app #6026

Closed
mcliquid opened this issue Nov 25, 2024 · 2 comments
Closed

Simple location search and routing / navigation feature in-app #6026

mcliquid opened this issue Nov 25, 2024 · 2 comments
Labels
wontfix idea rejected because it is out of scope or because required work is not matching expected benefits

Comments

@mcliquid
Copy link
Contributor

User Story:
As a user, I would like StreetComplete to navigate me to a previously searched destination so that I don't have to switch apps while solving quests to reach my destination.

Use Case:
When being in a foreign city/region, you almost always need a navigation app to reach a specific destination in the city. The route calculation and route display directly in the app makes it very easy for the user to follow a route and complete quests at the same time.

Function description:
StreetComplete has an integrated magnifying glass symbol that can be used to access a search function. This searches the OSM database in the same way as the search on osm.org. When you select a result, the route to this result is calculated and then the route to it is displayed on the map as a discreet line.
To limit the function, only destinations within a certain radius can be selected.
Furthermore, it does not require any navigation instructions, distance information or similar. The function should only require the display of a line on the map to just follow virtually.

Things to Discuss:

  • Does it require re-routing if you stray from the path?
  • What is the maximum length of the route? (Target group: pedestrians, possibly cyclists - approx. 50-100km?)

It's similar to #3950 , #1757 , #5369 and others but with direct routing approach in the app itself.

@matkoniecz
Copy link
Member

I would say it is going onto "it is mapping app, not navigation app". Starting to add navigation features and associated interface complexity seems clearly out of scope.

"Does it require re-routing if you stray from the path?" alone has a lot of complexity, but main risk is going further into OSMAND-type interface where you can do anything but new user can do nothing.

@matkoniecz matkoniecz closed this as not planned Won't fix, can't repro, duplicate, stale Nov 25, 2024
@riQQ riQQ added the wontfix idea rejected because it is out of scope or because required work is not matching expected benefits label Nov 25, 2024
@mnalis
Copy link
Member

mnalis commented Nov 26, 2024

Yeah, geocoding is a big task in itself, and routing is doubly so. It would be an incredibly huge task (even more so if it supported multiple navigation modes/vehicles and/or route deviation detection / route recalculation).

  • As a possible workaround, you can create route in .gpx format (in OsmAnd on mobile, or brouter, or graphhopper on desktop or whatever) and use SCEE to display that track (as requested in Import and display GPX track #1757) and even preload quests alongside it (as requested in [Feature Request] Preload Quests by gpx route #473)

  • Another alternative is using your Android built-in split-screen or picture-in-picture functionality and display both StreetComplete and e.g. OsmAnd (or simpler app like Luftlinie) at the same time (either on equal screen split, or giving navigation app little or much smaller space).
    E.g. like this (but removing panels/buttons from OsmAnd profile, which is left as an exercise for the reader as I can't be bothered to nuke my configs):

small_Screenshot_20241127_002137_Organic Maps small_Screenshot_20241127_002340_OsmAnd~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix idea rejected because it is out of scope or because required work is not matching expected benefits
Projects
None yet
Development

No branches or pull requests

4 participants