Team:Terrain
Jump to navigation
Jump to search
| Terrain | |
|---|---|
| Team:Terrein | |
| 1st line contacts: | Gina |
| Is an exclusive team: | No |
| Contact e-mail: | terrain@lists.why2025.org |
| Team members wanted: | 0 |
| Responsible for: | |
| IRC: | #why2025-terrain |
| Contact at projectleiding: | Boekenwuurm |
Team Members
| Name |
|---|
Current State
You want the latest map?
Not final, there will still be changes made (but with reasons).
We work in QGis, some time soon we will explain how to use this to new people. There is a very incomplete intro available here now QGIS Intro.
Introduction
The terrain team is responsible for planning the terrain, not only in space (2D) Height (3D) (producing the data that will make the map), but also in time (4D) (when will stuff be built up and torn down).
Some of the specific tasks:
- Buildings and terrain protections
- Team:Terrain organizes the buildings and terrain protections to be deployed on the field. This includes firehydrants, PowerMushrooms sokcets and all the tents that shelter and form the backbone of the event; toilets and shower facilities portacabins, storage depots, and headquarters, if any; road plates, to protect the fragile grass from heavy vehicles; roads; fences, gates, and bridges; towers and scaffolding constructions; and whatever other heavy metal we may end up needing. The building and arangement of(f) Power infrastructure and plumbing is not included (we have Team:NUTS for that).
- Terrain layout and sitemap
- Team:Terrain organizes the geographical layout of the event terrain. We will need to find a place for all the different things on the field that need some space, be they stages, bars, villages, roads, or whatever, while keeping track of things like traffic flows, terrain restrictions, permit requirements, and whatever other constraints may apply. Part of this is maintaining the overall sitemap, collecting geographical decisions from other teams and adding them to the combined map; part of it is filling in all the details for firelanes,firehydrants and infrastructure routes and emergency exits and the like; and part of it is collecting conflicting location constraints from everyone else by coliding, smashing and massaging them into a coherent design (Dutch=Stampot).
- Buildup coordination.
- Team:Terrain coordinates all the work the week-and-a-bit before the event in which we build and then polish the whole thing, as well as the counterpart the days after the event where we pack everything up again. We will need to maintain an overview of all the work that needs to happen on the field to turn a grassy field into a hacker event, and then back into a field again when the event is over. We need to plan out all this work, keep track of dependencies and deadlines, and work out how many pairs of hands we are going to need to get it all done.
- Teardown coordination.
- In the field, we make sure that everything is going smoothly, keep track of progress so that nothing is forgotten, and intervene when things inevitably go wrong. We will also need to take care of safety surrounding heavy machinery and plan the teardown coordination.
Questions and feedback can be sent to the team: terrain@lists.why2025.org. The archives are publicly available.
Meetings
Meeting minutes can be found on the relevant meeting page
Upcoming meetings
| Name | Start | Location |
|---|---|---|
| Terrain/Meeting-2025-06-30 | 30 June 2025 20:00:00 | https://meet.hack42.nl/teamterrain |
| Terrain/Meeting-2025-07-14 | 14 July 2025 20:00:00 | https://meet.hack42.nl/teamterrain |
Past meetings