Skip to content
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

own colour for each leisure type (sport) #919

Closed
Newbie07 opened this issue Sep 2, 2014 · 8 comments
Closed

own colour for each leisure type (sport) #919

Newbie07 opened this issue Sep 2, 2014 · 8 comments

Comments

@Newbie07
Copy link

Newbie07 commented Sep 2, 2014

I have sports_centre with lots of different pitches and tracks and a stadium. But stadium and sport_centre have the same colour.

  1. Please assign different colours to stadium and sport_centre
  2. Additionally leisure=sports_centre and building=* should be rendered differently than building=yes

Thanks

@HolgerJeromin
Copy link
Contributor

Perhaps an outline for stadium would be sufficient for 1.
For 2: IMHO way 84571675 is rendered different because of the sports_centre tag ...

@Newbie07
Copy link
Author

Newbie07 commented Sep 2, 2014

  1. a outline could work but might also interfere with barrier=fence.
    2a. I see but it is almost not visible.
    2b. For leisure=sports_centre it will covered once icons for sport=* are rendered.
    2c. How about using different outlines for buildings in general ? Could cover both: different values for building and different values for combinations like amenity and leisure.

@HolgerJeromin
Copy link
Contributor

2a: Almost not visible?
Compare the building "gymnastikhalle" with the part on the right (with the N/A entrance). IMO this is a big difference and the label is another color (on a high zoom).

@polarbearing
Copy link
Contributor

@Newbie07 - can you point us to your own example?

The colours are defined here:
https://github.com/gravitystorm/openstreetmap-carto/blob/master/landcover.mss

  • park: #cdf7c9; // also recreation_ground
  • stadium: #3c9; // also sports_centre
  • track: #74dcba;
  • pitch: #8ad3af;

I have not found a specific rule for a building that has a leisure tag, but probably the colours are merged due to opacity, thus the leisure building appears grey and not reddish. Like @HolgerJeromin
I do not see a problem with buildings, however the same colour for stadium and sports_centre leads
to some tagging for the renderer, e.g. here where the sports_centre is tagged as recreation_ground
which should be used for less formal installations:
http://www.openstreetmap.org/#map=17/52.54376/13.40708

@Newbie07
Copy link
Author

Newbie07 commented Sep 3, 2014

  1. stadium: https://www.openstreetmap.org/way/88414030 or https://www.openstreetmap.org/way/116671526 are examples. I often have stadiums with one or two more pitches along side and, yeah, often recreation_ground is used as it gets a higher priority in rendering.
  2. building: https://www.openstreetmap.org/way/301551007, without a name. As it is within a polygon leisure=sports_centre you will not find any differences.

@dkniffin
Copy link
Contributor

dkniffin commented Jun 5, 2015

One thing to note for this issue is some fields support multiple sports. Those can be tagged with either sport=multi or sport=sport1;sport2

@kocio-pl
Copy link
Collaborator

a outline could work but might also interfere with barrier=fence.

They have an outline defined and it's lighter than barriers:

[zoom >= 13] {
line-width: 0.3;
line-color: darken(@stadium, 35%);
}

@kocio-pl
Copy link
Collaborator

kocio-pl commented Dec 7, 2017

I don't think we have enough colors for this, so I will close it. Leisure/sport areas have light green currently and it's not so hard to distinguish them by icon and size most of the time, but it's not possible to use more colors for them. The more important thing is to know that light green is for leisure and sport in general.

@kocio-pl kocio-pl closed this as completed Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants