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

Feature request for enhancing workflow for traffic signal mapping #100

Closed
poornibadrinath opened this issue Dec 7, 2016 · 8 comments
Closed

Comments

@poornibadrinath
Copy link

poornibadrinath commented Dec 7, 2016

For the purpose of the trial run, the initial traffic signal and stop sign map was sufficient. Now since this map is going to be used by the team to start on the navigation assets mapping task, it would be great to include a few feature requests that would help in easier understanding and better mapping.

What is needed on the map:

  • A pop up when clicked on a junction/object, showing the following options:

    • Reviewed
    • Added
    • No signal
  • This overpass query highlights all the intersections. To have these as a point or a marker would help in going to that particular junction easily. This could help us prioritise major roads.

    • Ideally this marker would be contrasting the red and blue circles on the base map.

cc: @ajithranka @planemad @bsrinivasa

@planemad
Copy link
Contributor

planemad commented Dec 7, 2016

@poornibadrinath there is no overpass query that could highlight all the junctions. @oini has previously attempted to locate all road intersections using tile-reduce and maybe worth a look.

Why can we not do this with just map styling, what if all the minor roads are hidden from the map?

@ajithranka
Copy link
Contributor

ajithranka commented Dec 7, 2016

👍 on the features.

Ok if we keep this separate from osm-navigation-map for now? The workflow for traffic signals is different from what we have right now for rest of the traffic signs. Adding that to the osm-navigation-map without breaking the old workflow is going to be hard.

@poornibadrinath
Copy link
Author

@ajithranka separate map as in? Having a new map for traffic signals only, separate from that of this map

@planemad There are few junctions where minor roads meet major ones. Not sure if hiding minor roads completely would be a good idea.

@ajithranka
Copy link
Contributor

Yes. The traffic-signs map ^ is from this repository. It's separate from OSM navigation map for now and any feature requests should go there.

Let's keep these two projects separate until I figure out a good way to integrate the traffic signals workflow into OSM navigation map.

@poornibadrinath
Copy link
Author

@ajithranka oh ok. I should have opened this issue in that repository then. My bad. Anyway, I can create another issue in that repository there and link it to this.

What my question was, are you thinking of a separate map for traffic signals only, separate from that of what we already have in the traffic surge map http://traffic-signs.surge.sh/#20/37.78648/-122.42988.

@ajithranka
Copy link
Contributor

ajithranka commented Dec 7, 2016

It's the same :-)

@poornibadrinath
Copy link
Author

Continuing the discussions pertaining to traffic signs and stop signs mapping in this issue

@ajithranka
Copy link
Contributor

Thank you @poornibadrinath. Closing this issue.

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

3 participants