Connecting the Dots: Landscape Connectivity, Resilient Communities, and a Global Network of Great Mountain Trails

The first part of the KC will briefly review the importance of mountain areas, and the key role of mountain trails as important platforms for expanded mountain connectivity, and improving resilience of mountain ecosystems and communities. Next, an open discussion will focused on why and how a global network on mountain trails may be establish, as a tool to advance mountain cultures and landscapes.

Goal: Explore the relevance of a global network of mountain trails in which trail managers, users, and communities collaborate, share ideas, and new approaches, and interact with international colleagues to increase the impact, public awareness, and value of mountain trails to stakeholders and society at large.

Expected outputs:
i) Assess the interest and commitment for establishment of a global network of mountain trails.
ii) Identify key components of a road map to establish a global network of mountain trails.
iii) Create a list of key people involved in next steps and follow up

Agenda
14:30 -14:35 Welcome, brief introduction of the KC, the host organizations and facilitators
14:35 – 14:40 Explain goal, expected outputs, agenda and rules of the KC
14:40 – 15:00 Visual presentation (poster and explanation)
15:00 – 15:05 Questions for approach
15:05 – 15:50 Round table open discussion
15:50 – 16:00 Presentation of a draft road map of further steps
16:00 – 16:20 Final open discussion
16:20 – 16:30 Summary, closing

Keep in mind
A KC is a round table meeting, designed for a small group of people (10 -12) to have an open exchange of ideas around a specific topic.

KC is not for case study presentation, either speech on experiences, nor long explanations either debate of theories.

Facilitators of the KC will give questions to focus the contributions of each participant (may be using cards), and build up a common output based in an open and inclusive discussion.

This will be a multicultural, multilingual meeting, so to address your point clearly and in short will be of great help.

Geographical scope:

Rating: 
No votes yet
Connection could not be established.
Array ( [0] => Array ( [0] => 28000 [SQLSTATE] => 28000 [1] => 18456 [code] => 18456 [2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'drupal'. [message] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'drupal'. ) [1] => Array ( [0] => 42000 [SQLSTATE] => 42000 [1] => 4060 [code] => 4060 [2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "aspnetdb" requested by the login. The login failed. [message] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "aspnetdb" requested by the login. The login failed. ) [2] => Array ( [0] => 28000 [SQLSTATE] => 28000 [1] => 18456 [code] => 18456 [2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'drupal'. [message] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'drupal'. ) [3] => Array ( [0] => 42000 [SQLSTATE] => 42000 [1] => 4060 [code] => 4060 [2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "aspnetdb" requested by the login. The login failed. [message] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "aspnetdb" requested by the login. The login failed. ) )