As I understand, school stadiums in Rīga (or at least reconstructed ones?) allow public use.
Usually, they have an infoboards at the gates, stating times when stadium open for public.
Examples here and here
It's easy in case if stadium is standalone, like in case of https://www.openstreetmap.org/way/1090616108, but what to do with those embedded in the school grounds like this or this?
Should whole school ground be tagged with opening_hours and access? Or gates? Or something else?
Yeah, this is something I saw too that has "appeared" in last 5-10 years and I haven't really figured out how to tag it. Whole school grounds should probably not be tagged. In fact, this should probably be a separate area within the school grounds as leisure=sports_centre and tags go onto that plus whatever ways are needed to access it (other ways being private in schoolyards by default).
This makes sense, but taking Dārzciema vidusskolu as an example: they have infoboards with working hours at both entrances from Sesku.
And entrance near https://www.openstreetmap.org/node/13531587990 is way to far from stadium part to consider it part of this whole system, but it has infoboard too.
It's probably going to have to be something like access=permissive
For whole school grounds?
No, I mean for the footways intended to access the sports complex during public hours.
Sure. But this minor concern)
I'm just not very happy with yet another seemingly randomly defined object to be drawn.
Sorry, what did you mean then by the entrances?
I think it's perfectly valid per "one feature, one element" principle. It has specific purpose (shared in this case, but so are many feature), different access and rules, different opening hours, potentially its own name. I mean, it's no different than having multiple schools share a single yard or having like a library in a school area or something.
I mean, it's somewhat unusual with multiple areas, but as an example, you can have a playground area and an excercise area area within a recreation area within a park area or some such. What I'm saying is that multiple areas by themselves are not a problem if they represent concrete real features.
HellMap said:
Sorry, what did you mean then by the entrances?
I meant that if we draw leisure=sports_centre, and tag "whatever ways are needed to access it", then gate closest to main building entrance, and paths there, is not in that group.
But next to that gate there is also an infoboard with working hours.
I don't know why that board is there. Maybe School admin thinks that it's main entrance and it should be there.
Just thought that maybe this might also indicate that admin considers whole grounds except for building itself publicly accessible at the outlined time.
Ahh, well, yeah. For such a specific query, you would have to ask the admin themselves ;) I imagine your answer will be - "sports area is public and you can use the footways to access it". I don't think there is any solution here other than to apply some subjective common sense and tag whatever direct ways are used to access the actual area within. In your example, I would tag any footways from entrances with infoboards as intended access ways.
HellMap said:
I think it's perfectly valid per "one feature, one element" principle. It has specific purpose (shared in this case, but so are many feature), different access and rules, different opening hours, potentially its own name. I mean, it's no different than having multiple schools share a single yard or having like a library in a school area or something.
100%
My problem is with defining that area) Like where it starts and ends? How to draw it?
I understand this is not a court or cadastr. But I like it when there is clear rules for those kind of things.
What about opening hours?
At https://www.openstreetmap.org/way/1090616108 I used combination of opening_hours=* and access:conditional=*
With rationale, that during school time it's open and operational, just not accessible to general public.
But it feels somewhat cumbersome. And I'm not sure it would be clear in different clients.
So for example, CoMaps sadly only shows opening hours.
You can forget the vast majority of apps understanding :conditional stuff for probably decades. It's still ok to map if there's no simpler way, but it's up to them to implement.
I have to think about whetehr access or opening_hours or how to really tag this, I don't rightly know. It's probably also different for "embedded" areas versus this stand-alone one (mostly it's how it's presented tho).
Last updated: Apr 27 2026 at 09:12 UTC