Upload
helene-draux
View
265
Download
0
Embed Size (px)
DESCRIPTION
Presentation given at the GISRUK 2012, introducing my research on Participatory GIS to identify land use conflicts. It introduces the methods used to investigate land use conflict in coastal city, focusing primarily on the online survey.
Citation preview
+
PGIS techniques to identify land use conflicts in Portsmouth
Hélène Draux, Cities Institute, London Metropolitan [email protected]
Participatory GIS
= maps to improve participation from ‘silent
majority’
to identify land use conflicts in Portsmouth
+Structure
Case study: Coastal conflicts in Portsmouth
Methods usedFace-to-face surveySummer FairOnline survey
Recommendations
+Case study
+Farlington Marshes
Langstone Harbour
British, European and International designations (SSSI, SPA, SAC, and Ramsar)
Reclaimed three centuries ago
+Farlington Marshes
+Aims
Assess value of vulnerable open spaces
Assess flood knowledge
Understand perception of space regarding flood risks
+Face-to-face methodologies
+Face-to-face survey:Open space users and/or Farlington Marshes users, stakeholders
45 questions
15 minutes
2 types of mapping activities
162 interviews
In-depth qualitative data from each participants
Includes “silent majority”
Time consuming
Surveys only small sample, and quite short survey
Relies on the weather
:(:)
+Summer fair survey:Open space users and/or Farlington Marshes users, stakeholders
Organised by Portsmouth Climate Action Network
1 sunny day
Around 60 participants for each of the 4 activities
+ :(:)
Can reach more diverse population:FamiliesYoung peopleLess frequent park
users ..
Needs lots of people to man the activities
Relies on the fair organisers .. and weather!
Limited data from each participant
+Online survey
+Online surveyGeneral public, open space users and/or Farlington Marshes users and stakeholders
Aims to:
Attract all population in Portsmouth
Potentially get a bigger sample
+www.openspaces-portsmouth.org.uk
+Google Map API v3
Add markers with a click
Capture geolocalised information
Display kml layers..
Fieldwork
+Add markers - WebsiteLocations and flooding
Marker
Tutorial
Instructions
Postcode
+Add markers - Coding
Map:
var map = new google.maps.Map(document.getElementById("map_canvas"), options);
Add marker:
google.maps.event.addListenerOnce(map, "click", function(event)
var latlng = marker.getPosition();
Lat = latlng.lat() / Lon = latlng.lng()
For 1 location only
+Add markers - Database
+Add markers - Database
+Infowindow - Website
+Infowindow - Website
+Infowindow - Website
+Infowindow - Coding
parksLayer = new google.maps.KmlLayer(‘Parks.kml',{ suppressInfoWindows: true, preserveViewport: true }); parksLayer.setMap(map);
infowindow = new google.maps.InfoWindow({}); // Add a listener for the click event google.maps.event.addListener(parksLayer, 'click', showArrays); html describing
the infowindow
+Customised maps: kml and styles
+Customised maps: kml and styles
var myStyle = [ {featureType: "road", elementType: "labels", stylers: [{ visibility: "off" }] },{ featureType: "road.highway", elementType: "geometry", stylers: [ { saturation: -50 }, { lightness: 20 }, { visibility:
"simplified" }] },{ featureType: "road.arterial", elementType: "geometry", stylers: [{ visibility: "off" }] },{ featureType: "road.local", elementType: "geometry", stylers: [ { visibility: "off" } ]
Coding Style
+Quick analysis
+Participation
Background Parks Flood Land Use Willingness to pay Farlington Marshes0
10
20
30
40
50
60
70
80
90
100
18
100
Participants who accessed the page and usable replies
+Participation - map
+Time spent
1 2 3 4 5 6 7 8 9 10 11 12 13 14 1500:00
00:05
00:10
00:15
00:20
00:25
00:30
00:35
00:40
Average=18 minutes
+Flood perception
+Preferred scenario
Hold the line 88%
Managed realignment, loss of 80% 6%
Managed realignment, loss of 50% 6%
For 18 participants
+Issues
+Issues specific to this method
Technical
Extensive time to clear the database
Not enough completed surveys
Loss of some data
Design
Too long survey
Loss of interest
Too many questions:
No clear focus
+Recommendations
+Recommendations/suggestions
Shorter survey (5 minutes)
Focus survey on one issue
Finding gatekeepers while starting the coding
Organise hands-on sessions? (University / community centre)