You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to promote re-usability of the great work we've done in generating highway shields on maps, we should separate design and presentation details into separate data products that can be used separately. The purpose of this ticket is to capture which details belong in which category and discuss the breakdown of attributes.
I propose as a starting point that there are three categories:
Shield design (kept in JSON):
The shape of the shield (e.g., rectangle, oval, circle, diamond, etc.). This captures cases where the shield is some type of named shape. It is an enumeration that we will define. Rounded corners are defined in this category only if they are a significant design element vice a presentational detail.
A pseudo-human-readable name of the shield design or artwork, in English, with some guidelines to be invented for the naming scheme
The exact real-world color for:
Route number/designator text color
Shield background color
Shield border color
A list of banner placards displayed above the shield with the exact text displayed in the real world
The exact text written on the shield in cases where the text constitutes the equivalent of a ref for numbered routes.
Special cases within the scope of the elements above (for example, "this particular route number is drawn in green")
The list of OSM network values for which this shield design applies to
Where appropriate, linkages to wikidata
Shield description (format TBD and may just be documentation):
For each named shape, an English-language human-readable description of the shape
For each shield artwork, an English-language human-readable description
Where appropriate, linkages to wikidata
Shield presentation (kept in JSON):
The color actually drawn on the digital map for the following categories. This may instead be represented as a discrete list of colors for which the closest color is selected by color distance.
Route number/designator text color
Shield background color
Shield border color
All strategies for laying out text inside shields or for banners, including padding
All strategies for expanding and contracting shapes to fit longer or shorter text
Mappings between real-world banner placard text and the text string displayed on the digital map
Line styles and thicknesses
Fonts
Whether or not corners are rounded and by how much
The decision to draw a pseudo-route designator in place of a graphic design
Special cases within the scope of the elements abo
The text was updated successfully, but these errors were encountered:
In order to promote re-usability of the great work we've done in generating highway shields on maps, we should separate design and presentation details into separate data products that can be used separately. The purpose of this ticket is to capture which details belong in which category and discuss the breakdown of attributes.
I propose as a starting point that there are three categories:
Shield design (kept in JSON):
ref
for numbered routes.network
values for which this shield design applies toShield description (format TBD and may just be documentation):
Shield presentation (kept in JSON):
The text was updated successfully, but these errors were encountered: