Codeberg/Community
54
325
Fork
You've already forked Community
12

Feature Request: Integration of Nearby Parking Lots in CoMaps Navigation #1972

Closed
opened 2025年06月03日 17:06:06 +02:00 by huuhaa · 2 comments

Comment

Description:
I would like to suggest a new feature for CoMaps that could significantly enhance the user experience, especially in urban environments. This feature involves displaying nearby parking lots from OpenStreetMap (OSM) data when a destination is set, allowing users to navigate directly to a preferred parking lot if they choose to.

Use Case:
When navigating to a destination in a big city, it's often challenging to find parking. Currently, navigation apps typically announce the arrival at the destination, which can be in the middle of a road or an area without clear parking options. By integrating nearby parking lots into the navigation system, users can select a parking lot close to their destination and navigate directly there, saving time and reducing stress.

Safety Considerations:

  • Reduce the need for users to search for parking while driving, which can be distracting and dangerous.
  • Minimize the necessity for users to quickly park next to the street to search for parking options, thereby enhancing road safety.

Current Workarounds:

  • Users can currently search for parking lots using the /parking command or simply by searching for "parking" without a slash.
  • Some users plan their trips in advance by adding markers for parking lots.

Suggested Implementation:

  1. Parking Lot Data Integration: Utilize OpenStreetMap (OSM) data to integrate a database of parking lots into CoMaps. This should include public parking lots, private parking garages, and street parking areas.
  2. User Interface Enhancement: When a user sets a destination, provide an option to view nearby parking lots. This could be displayed as icons on the map or as a list that users can choose from.
  3. Navigation Options: Once a user selects a parking lot, CoMaps should provide navigation directly to the entrance of the parking lot. Additionally, users should have the option to skip parking lot navigation and proceed with traditional navigation to the destination.
  4. Additional Information: Provide additional information about the parking lots, such as availability, pricing, and operating hours, if available in OSM data.
  5. Button for Nearby POIs: Add a button to find parking or other points of interest (POIs) near the destination.
  6. Highlighting Parking Lots: During the search for a destination in car mode, nearby parking lots could be displayed with half-transparency to easily navigate to that location instead.

Benefits:

  • Convenience: Users can easily find and navigate to parking lots near their destination.
  • Time-Saving: Reduces the time spent searching for parking, especially in unfamiliar areas.
  • Stress Reduction: Enhances the overall navigation experience by providing clear parking options.
  • Flexibility: Users can choose between navigating to a parking lot or directly to the destination based on their preference.
  • Safety: Enhances road safety by reducing the need for users to search for parking while driving or park hastily on the side of the street.

Example:
Imagine you are navigating to a business meeting in a busy city center. Instead of being dropped off in the middle of a street, CoMaps could show you several nearby parking lots from OSM data. You could select one, and the app would navigate you directly to the parking lot entrance, ensuring you arrive on time and without the hassle of finding parking. Alternatively, you could choose to navigate directly to your destination if you prefer.

Additional Notes:

  • This feature could be implemented without changes to OSM data by allowing users to select from nearby parking lots.
  • Magic Earth, a non-free app based on OSM, has a similar feature, indicating that it is technically possible.

Thank you for considering this feature request. I believe it would be a valuable addition to CoMaps and greatly enhance the user experience.

### Comment **Description:** I would like to suggest a new feature for CoMaps that could significantly enhance the user experience, especially in urban environments. This feature involves displaying nearby parking lots from OpenStreetMap (OSM) data when a destination is set, allowing users to navigate directly to a preferred parking lot if they choose to. **Use Case:** When navigating to a destination in a big city, it's often challenging to find parking. Currently, navigation apps typically announce the arrival at the destination, which can be in the middle of a road or an area without clear parking options. By integrating nearby parking lots into the navigation system, users can select a parking lot close to their destination and navigate directly there, saving time and reducing stress. **Safety Considerations:** - Reduce the need for users to search for parking while driving, which can be distracting and dangerous. - Minimize the necessity for users to quickly park next to the street to search for parking options, thereby enhancing road safety. **Current Workarounds:** - Users can currently search for parking lots using the `/parking` command or simply by searching for "parking" without a slash. - Some users plan their trips in advance by adding markers for parking lots. **Suggested Implementation:** 1. **Parking Lot Data Integration:** Utilize OpenStreetMap (OSM) data to integrate a database of parking lots into CoMaps. This should include public parking lots, private parking garages, and street parking areas. 2. **User Interface Enhancement:** When a user sets a destination, provide an option to view nearby parking lots. This could be displayed as icons on the map or as a list that users can choose from. 3. **Navigation Options:** Once a user selects a parking lot, CoMaps should provide navigation directly to the entrance of the parking lot. Additionally, users should have the option to skip parking lot navigation and proceed with traditional navigation to the destination. 4. **Additional Information:** Provide additional information about the parking lots, such as availability, pricing, and operating hours, if available in OSM data. 5. **Button for Nearby POIs:** Add a button to find parking or other points of interest (POIs) near the destination. 6. **Highlighting Parking Lots:** During the search for a destination in car mode, nearby parking lots could be displayed with half-transparency to easily navigate to that location instead. **Benefits:** - **Convenience:** Users can easily find and navigate to parking lots near their destination. - **Time-Saving:** Reduces the time spent searching for parking, especially in unfamiliar areas. - **Stress Reduction:** Enhances the overall navigation experience by providing clear parking options. - **Flexibility:** Users can choose between navigating to a parking lot or directly to the destination based on their preference. - **Safety:** Enhances road safety by reducing the need for users to search for parking while driving or park hastily on the side of the street. **Example:** Imagine you are navigating to a business meeting in a busy city center. Instead of being dropped off in the middle of a street, CoMaps could show you several nearby parking lots from OSM data. You could select one, and the app would navigate you directly to the parking lot entrance, ensuring you arrive on time and without the hassle of finding parking. Alternatively, you could choose to navigate directly to your destination if you prefer. **Additional Notes:** - This feature could be implemented without changes to OSM data by allowing users to select from nearby parking lots. - Magic Earth, a non-free app based on OSM, has a similar feature, indicating that it is technically possible. Thank you for considering this feature request. I believe it would be a valuable addition to CoMaps and greatly enhance the user experience.

I fear this is the wrong place to open issues for CoMaps, the right spot is here: https://codeberg.org/comaps/comaps/issues

Please open it there and close the one here 🙂

I fear this is the wrong place to open issues for CoMaps, the right spot is here: https://codeberg.org/comaps/comaps/issues Please open it there and close the one here 🙂
Author
Copy link

Right, closing this one.

Right, closing this one.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1972
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?