Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

OSM website Map Key is missing "cliff" #5321

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments
Closed

OSM website Map Key is missing "cliff" #5321

openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments

Comments

@openstreetmap-trac
Copy link

Reporter: quinn[at]strangecode.com
[Submitted to the original trac issue database at 10.39am, Wednesday, 17th June 2015]

The Map Key on www.openstreetmap.org/search is missing the "cliff" line type item. See screenshot for example:

[[Image(http://i.imgur.com/aOUEkQz.png)]]

You can view this map position [https://www.openstreetmap.org/search?query=san%20miguel%20de%20allende#map=16/20.8959/-100.7382 here].

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 11.02pm, Sunday, 21st June 2015]

There are hundreds (maybe even thousands) of different things that we render - only the most common can be included in the key.

@openstreetmap-trac
Copy link
Author

Author: quinn[at]strangecode.com
[Added to the original trac issue at 11.24pm, Sunday, 21st June 2015]

Aha, that explains it.

Is there a definitive list of map elements somewhere? It would be great to have a link at the bottom of the Map Key, View all, which goes to a page listing all elements.

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 11.27pm, Sunday, 21st June 2015]

It's not really that simple - the stylesheet is at https://github.com/gravitystorm/openstreetmap-carto but there are over 6500 lines of carto CSS code and a couple of thousand lines in the project.mml file that defines all the database queries used to select features.

I doubt there is anybody who actually knows the complete set of tag combinations that is rendered!

@openstreetmap-trac
Copy link
Author

Author: quinn[at]strangecode.com
[Added to the original trac issue at 11.58pm, Sunday, 21st June 2015]

I find that a little hard to believe. The software itself needs to know what map elements exist, in order to offer them as available to be added to the map, and then to render them. The map editor's search features interface lists known items, often including a description and even a photo (see [http://i.imgur.com/T8QYNLD.png screenshot]).

I did find the wiki page of [https://wiki.openstreetmap.org/wiki/Map_Features map features], which is mostly what I was looking for (well, at least it has an entry for cliff). The rub is that it is human-generated, so I'm sure it is missing many of the elements defined in those 6500+ lines of css code you mentioned. Programmatically generating a page of all possible features would be pretty cool, and isn't an inconceivably difficult task.

Thanks for your replies and considering the topic.

@openstreetmap-trac
Copy link
Author

Author: woodpeck
[Added to the original trac issue at 6.03am, Monday, 22nd June 2015]

Automatically creating a legend that is as "nice" as the current, hand-curated one, will be difficult. Some work towards that here https://github.com/gravitystorm/mapnik-legendary but remember it needs to be done differently for each zoom level, and a good legend will also attempt to list the more common and/or more important features first (there may be more residential roads in the picture, but still the motorways are listed first; should a feature common in Chile be listed in the legend when you zoom in on the UK; which features make sense to group; etc.etc.)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant