-
Notifications
You must be signed in to change notification settings - Fork 4
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
UX problems with routes #102
Milestone
Comments
For the second, maybe just adding circular end caps with a faint outline would help. I tried in Felt and geojson.io, and both have the same problem right now |
dabreegster
added a commit
that referenced
this issue
Apr 11, 2023
Merged
dabreegster
added a commit
that referenced
this issue
Apr 13, 2023
dabreegster
added a commit
that referenced
this issue
Apr 14, 2023
dabreegster
added a commit
that referenced
this issue
Apr 14, 2023
Both issues fixed. We still saw some people in the UX study get confused after successfully using the split route tool; the circle outline wasn't clear enough. But in lieu of better design ideas, marking done for v2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The way we draw currently, you can't see the basemap underneath drawn routes. So the road names aren't visible! https://maplibre.org/maplibre-gl-js-docs/example/geojson-layer-in-stack/ could help.
And when two separate routes meet at a point, the boundary between them is unknowable until you click one and see waypoints:
The text was updated successfully, but these errors were encountered: