You do not have permission to edit this page, for the following reasons:

The action you have requested is limited to users in the group: emailconfirmed.
You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

Team Info[edit]

First line contact(s):
	This field uses autocomplete.
Description: Team:Terrein
Is an exclusive team:
	Team members in an exclusive team only have responsibilities to this team, and cannot be involved in other teams.
Contact:
	The mailing list of the team (like "Terrain@lists.WHY2025.org")
IRC:
	The IRC channel the team uses ("WHY2025-Terrain" becomes #WHY2025-Terrain)
This team is required for the event: Meaning: without the deliverables of this team the event can not continue. For example: team:power is a requirement for lectures, recording, sanitation and so on. Counter example: a badge is a great add on to the event, but even if it fails, the event can continue safely. Crucial teams contribute to safety, essential services, hygiene, health.
Status: Team has contact information: Meaning: a new volunteer or the existing network of volunteers can easily contact this team and ask questions or status information.
Status: Team has informative wiki page: Meaning: the wiki page of the team details a bit of their plans, how they do it and what they provide to others. It contains who the team members are. This is a treasure trove for next events, as well as a way to streamline information to other teams.
Status: Team has meetings are planned until the event: Meaning: the team is in control and regular meetings / gatherings to check progress, todo's, questions and whatever is relevant to the team. Meetings do not always need to be formal or documented in order to set this checkmark of course.
Status: Team has enough orga-volunteers to function: Meaning: there are enough dedicated people on the team that everyone on the team can enjoy at least two days at the camp without doing anything for this team. The stress level is relatively low because work is shared among team members. Angels are excluded in this metric: note that angels often need training, which also takes time which must be allocated. Examples of what this being unchecked can mean: people are not exclusive to this team and thus cannot guarantee time before and during the event, there are tons of plans but no actual work is planned, performed or managed, people are out of reach, there is no backup for crucial team roles, there is no time allocated to instruct and guide angels. There is no tracking of progress.
Status: the team needs x more members to function
Status: Team has drafted a budget: Meaning: there is a table of expected expenses and projected income. This consists of listing of items, with their price. This does not need to be public, but team:finance must know. If there is no budget, the finance team / board will try to determine one: better to be in control yourself, so allocate, estimate and write it down.
Status: Team has informed team:volunteers: Meaning: if there are any angel requirements, or orga-volunteers needed, team:volunteers is aware of their numbers and needed capabilities. Yes you can search yourself, and you can also get more searching capacity if these numbers and skills are shared.
Contact at projectleiding:

Warning: Using this form can break tables further on the page

Team Members[edit]

Add another Member

Free text[edit]

== Current State == You want the latest map? A online map with GPS capabilities: [https://map.why2025.org Get it here] Not final, there will still be changes made (but with reasons). A PDF is found [[File:MapGeneralView.pdf|thumb|alt=MapGeneralView|here]] 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 [[Team:Terrain/QGIS Intro|QGIS Intro]]. Detailed maps are for now in https://cloud.ifcat.org/index.php/apps/files/files/261716?dir=/WHY2025/Terrain/map_exports/permit%20drawings/v13 ==Introduction== [[File:Why2025Map.png|thumb|Map]] 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. [https://lists.why2025.org/pipermail/terrain/ The archives are publicly available]. ==Meetings== Meeting minutes can be found on the relevant meeting page {{MeetingOverview|Team=Terrain}} == Topic Notes == *[[Team:Terrain/Map Data Sources|Map Data sources]] *[[Team:Terrain/Rijplatten|Rijplatten]] *[[Team:Terrain/Mapping Procedure|Mapping Procedure]] *[[Team:Terrain/Permit Maps|Permit maps]] *[[Team:Terrain/Bridges|Bridges]] *[[Team:Terrain/Lounge|Lounge]] *[[Team:Terrain/Tasks|Tasks]] *[[Team:Terrain/Mapping Software|Mapping Software]] *[[Team:Terrain/Slides 7 sept 2024|Slides 7 sept 2024]] *[[Team:Terrain/Tent Internals]]

Summary:

This is a minor edit

Watch this page

Cancel

Edit Team: Team:Terrain

Team Info[edit]

Team Members[edit]

Free text[edit]

Navigation menu

Edit Team: Team:Terrain

Team Info[edit]

Team Members[edit]

Free text[edit]

Navigation menu

Search