-
Notifications
You must be signed in to change notification settings - Fork 66
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
Differentiate vehicle ferry routes #719
Comments
It looks like the |
It seems like there isn’t very much precedent for distinguishing ferry lines by their characteristics in print maps, at least in the maps in my collection. I don’t have any examples of maps that give auto ferries a different color or dash pattern than passenger ferries, for instance. In fact, in their maps of New York State and California, Rand McNally treats any ferry as exotic enough to warrant a generic “Ferry” label: In this map of Long Island, the American Map Company labels every passenger ferry as “Passenger Ferry” instead of by its name. They also provide an inset with phone numbers of automobile ferries to call for fares and schedules. The Kentucky Transportation Cabinet’s official state highway map does indicate that the ferries they operate are tolled, while the Louisiana Department of Transportation and Development labels free ferries on their map: Engels Maps, a local publisher in the Cincinnati area, goes a step further, labeling the ferry with the exact fare for cars. This ferry had a famously consistent fare for many years, though they’ve since raised the rate. The Washington State DOT’s official map shows not only state route shields on its ferry lines but also “Passenger Only” and duration labels: |
@1ec5 Thanks for the rundown! Its clear paper maps tend to treat ferries are unusual enough and complicated enough to just describe them with labels. But the labels do specify toll vs. free and vehicle vs. passenger, so I think there's precedent to distinguish them somehow in Americana. Text-only is one option, but I think we can do better with the lines, even if slightly. Here's another example from NPS (no stroke differences): |
Yes, I think there are a few possibilities here:
This possibly calls for several new fields to be exposed through OpenMapTiles. I think it would be the style’s responsibility to come up with the descriptive text, because it needs to be localized and could depend on the available space. We could even decide to represent these attributes using icons beside labels, similar to public transportation maps. |
Since the |
I like this a lot, just have to see if it's useful in dense places with lots of ferries.
I count 381 ferry routes in OSM with
OSM typically just puts "Origin-Destination" (with various formatting) in the
Agreed.
I'd be interested to see what this might look like. We could also adjust the icons for the ferry terminals to indicate access if all the ferries terminating there have the same access. Like this for passenger ferry terminals: |
Similar to how NPS maps append amenity icons to place labels, we could append mode-of-transportation indicators to the ferry labels using a We could keep the icons small and match them to the label color to avoid drawing too much attention. That said, I think glosses would be straightforward enough and well-justified by existing maps. We have a legend now, but we probably shouldn’t rely too heavily on it, since users aren’t guaranteed to consult it. |
Whether or not you can drive onto a ferry is a critically important detail for route-planning and navigation. But OSM maps tend to render all ferry routes the same way. This is a good opportunity to innovate.
In the below example, one route is a massive oceangoing vessel that fits RVs, the other is a motorboat that might fit a couple dozen people, tops. It's impossible to tell the difference in the rendering.
Another consideration is that of tolls. There are a number of toll-free car ferries in the US and Canada, meaning tolls shouldn't be implied. Since toll roads are rendered distinctly in americana, tolled ferries might should be as well.
The text was updated successfully, but these errors were encountered: