-
Notifications
You must be signed in to change notification settings - Fork 819
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
Confusing symbol for amenity=ferry_terminal #2785
Comments
I agree with the thread opener. The anchor symbol is confusing and too dominant. Especially at locations where "amenity=ferry_terminal" is similar/identical to a bus stop. |
Even on the sea there's a ferry line attached most of the times, so it should be clear from the context that it's a terminal, not an anchorage place. The initial level was chosen as a middle ground between big ferry stations and small ferry stops, because we have no way to distinguish their size currently, so it's expected to be sometimes too late and sometimes too early. In this case it's the 3 lines name labels which bothers me. You can suggest a solution if you feel this could be improved. |
I don't see a point of breaking an established and reasonable practice. I'm quite confident that for quite a number of people if they see an anchor on a map they'd assume there is an anchorage there. Here is another example http://www.physicalgeography.net/fundamentals/2d.html. Personally when I saw an anchor on the land I've rushed to JOSM to see what's wrong with the map. By the way the anchor symbol has a quite broad connotation in this context. Perhaps it's better to have a vessel to be depicted on the symbol. So, I'm happy to make a suggestion. CEVNI – European Code for Inland Waterways uses this symbol:
You may like its Polish version:
Otherwise here are some options I've found at the Wikipedia commons:
|
It was very late idea, because no vessel icon I've tried was even remotely as recognizable.
It was deliberate choice to use broad symbol, because it was also suggested that not every ferry is a ship. See also my conclusions: #2385 (comment).
Thanks! However I should have said that any proposition needs to look good on 14 px matrix and only last 2 icons are as small. I'm not able to recognize second one of them and the first of them was not recognized by other people. See #2385 for more failed attempts. |
Icons with wavy lines are not likely to be suitable at the size we need. |
Hm, @Klaus-Tockloth case gave me idea to improve rendering a bit - what if we show terminals with area from z14 and terminal nodes from z16? This should be possible with SQL query and could encourage more detailed drawing for bigger ones. There are 11415 such nodes and 1309 ways currently. |
Basic idea: Rationale: Improvement: |
@kocio-pl I've corrected links for the Commons icons. As you'd see the thumbnails are generated by Mediawiki from SVGs, so you'd scale them easily and you'd paint them whatever you like. Perhaps it's better to have bow/stern view of a vessel, so they'd the difference from a bus icon is quite distinct. BTW this is what I've made from the CEVNI ferry symbol: It doesn't look like a bus and it's not dominant either! |
I'm not ready to get back again to the same problem that took me so long at the moment (still you can play with different renderings and post it here). I just wanted to note that Sputnik is using the anchor too. |
Using anchor to demote ferry is actually quite common for tourist city plans. So Sputnik apparently picked up this tendency from there. But this actually this makes their map look amateurish. It's the same with the Yandex maps. But even Google (not a professional map either) use a ship for this purpose, and this brings some consistency to their maps. Funny enough, but no one from them uses a car horn a bus wheel or even a steering wheel to denote a bus stop. Let's look at what real maps do. They've put many years of experience in there. |
I've seen both used in different maps. I'm okay with our current symbol. If someone feels a different symbol would be better, provide an example rendering for comparison, then we can evaluate it. |
Yes, it would help to see the real output, not general ideas, because this issue is about details. Preparing simple rendering/testing environment is documented here: https://github.com/gravitystorm/openstreetmap-carto/blob/master/DOCKER.md |
The icon is probably smaller than 14x14 px and is unreadable for me - at 100% resembles bread (bakery) icon. |
👎 to the small "breadbox" symbol as being unreadable, and 👎 to the triangle. I don't think an abstract symbol works here. |
To distinguish between nodes and areas could be an good idea.
|
sent from a phone
On 9. Sep 2017, at 09:15, printmaps ***@***.***> wrote:
Nodes are small terminals like bus stops with late labeling and small icons or abstract symbols.
Areas are large terminals with early labeling and larger icons.
there is no such difference between small and large, a small thing will often be mapped as area and big terminals can be mapped as nodes as well.
Btw, taggingwise, maybe very small (bus stop like) ferry route endpoints aren't actually "ferry terminals"? Clearly intermediate stops of a ferry route aren't terminals (semantically). The resulting gaps are part of the reason for the seaway proposal
|
The OSM wiki defines "amenity=ferry_terminal" as: A place where people/cars/etc. can board and leave a ferry. |
sent from a phone
On 9. Sep 2017, at 09:36, printmaps ***@***.***> wrote:
The OSM wiki defines "amenity=ferry_terminal" as:
A place where people/cars/etc. can board and leave a ferry.
I know, but everytime the definition is broader as the tag wording, sooner or later it fires back
|
If it's too specific from beginning, it can be also source of troubles (amenity=fast_food/restaurant - and what if you don't know exactly?). But that's the way it is and that's why we have "2.0" specifications: https://wiki.openstreetmap.org/wiki/Proposed_features/Seaway Sadly, it's not approved and not even used: |
Agree with the OP, when I saw the anchor on the map I didn't realise it was a ferry terminal. The second wikimedia icon from @Vadp looks ok at 14px. The iD editor also has a couple of ferry icons. |
OK, so please render them so we could evaluate it. |
Just found some time to play with the thing. 1st one is extracted from CEVNI – European Code for Inland Waterways The next 3 are fond at the Wikipedia and one more from https://wiki.openstreetmap.org/wiki/Map_Icons/Proposed_Icons |
2 is unreadable, 3 is better by a narrow margin, 1 is recognizable, but too cartoonish/geometric, 4 looks the most promising for me for nodes, but I'm afraid of areas. Could you check how would it look here? BTW if you change the icon color, remember to change it also for labels. |
Tell me how to get a pbf for it |
You can just export .osm file from website export, since it's quite small area and can be imported as easily as PBF. There are however additional services like OSMaxx or HOT export tool, which allows you to download data for arbitrary area if they are bigger. |
It looks strange for me. Maybe you should use the existing color, to make it look different than slipways? |
@vss-devel I wanted to revisit this issue, but something bad happened to the images from you - they are not shown on this page and the links to them don't work also. |
@kocio-pl: The images are fixed. Enjoy! |
After some time to keep the perspective, my inspection shows that unfortunately this shape is hard to recognize. I also believe it would be too heavy for small river terminals (example from #2785 (comment) would be even worse than just too much of text). Therefore I close this issue. Thanks for the work with searching for a replacement. |
May I then suggest to use a white anchor on a purple box for a ferry terminal, while a blue anchor can be used to refer to "leisure=marina"? I draw my inspiration from "highway=bus_stop" using a blue bus symbol, while "amenity=bus_station" using a white bus symbol on a blue box. |
Bus/bus station does not sound to me as a parallel to ferry terminal/marina - these are two different uses, not just a bigger/smaller feature, so I don't think it would work. It would be better suited for |
Well, as I associate the anchor icon with a marina, I would then suggest that the anchor icon be moved to "leisure=marina" and that no icon at all be used for a ferry terminal, instead implying a ferry terminal from the ferry routes that land there. |
AFAIR we already render marinas and nobody even reported that's insufficient, so this would be separate change (the issue is not about "this icon is needed elsewhere"). On the other hand general transport rendering was incomplete without a ferry icon and we haven't found anything better. There are also examples where ferry routes are not tagged and terminals are the only thing visible, like here: |
Well, that doesn't change the fact that the use of an anchor to refer to a ferry terminal is still confusing. The vast majority of systems use the pictogram of a ship to refer to a ferry terminal, and whenever I see an anchor picture, I think marina. If you can find the absolute simplest pictogram of a ship that is easily recognized from a distance, please use it for a ferry terminal instead. |
For what it's worth, I have no complaint against the anchor, but the icon No1 here looks perfectly fine to me. I think it's actually a point in favour that it is simple / geometric, just like the icons for buses, taxis etc. |
As discussed at the bottom of #2385, v4.2.0 uses an anchor symbol for the amenity=ferry_terminal which is quite confusing.
It may be not so obvious along the rivers, as depicted at #2385, but at a sea shore it looks weird. Common sense suggests that an anchor is for an anchorage. As a matter of fact, ferries don't usually deploy an anchor to moor at their docks.
Not only nautical, but also some topographic maps modern and historical maps are using an anchor symbol to denote an anchorage.
See, for example, Topografska karta at the https://geoportal.dgu.hr/, Carte littorale https://www.geoportail.gouv.fr/donnees/carte-littorale or as suggested by @imagico: "for example chapter 2, symbol 226 in http://www.lib.berkeley.edu/EART/pdf/soviet.pdf - likewise for some pre-digital German TK100/TK200 (don't have a digitized sample at the moment)."
The text was updated successfully, but these errors were encountered: