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.

1. +
PGIS techniques
to identify land use conflicts
in Portsmouth
Hélène Draux, Cities Institute, London Metropolitan University
h.draux@londonmet.ac.uk

2. Participatory GIS
= maps to improve participation
from „silent majority‟
to identify land use conflicts
in Portsmouth

3. +
Structure
 Case study: Coastal conflicts in Portsmouth
 Methods used
 Face-to-face survey
 Summer Fair
 Online survey
 Recommendations

4. +
Case study

5. +
Farlington Marshes
 Langstone Harbour
 British, European
and International
designations
(SSSI, SPA, SAC, a
nd Ramsar)
 Reclaimed three
centuries ago

6. +
Farlington Marshes

7. +
Aims
 Assess value of
vulnerable open
spaces
 Assess flood
knowledge
 Understand perception
of space regarding
flood risks

8. + Face-to-face
methodologies

9. +
Face-to-face survey:
Open space users and/or Farlington Marshes
users, stakeholders
 45 questions
 15 minutes
2 types of mapping
activities
 162 interviews

10. :(
 In-depth :)
qualitative  Time consuming
data from each
participants  Surveys only small
sample, and quite
 Includes “silent short survey
majority”
 Relies on the weather

11. +
Summer fair survey:
Open space users and/or Farlington Marshes
users, stakeholders
 Organisedby
Portsmouth
Climate Action
Network
1 sunny day
 Around 60
participants for
each of the 4
activities

12. +
:(
 Can
:)
reach more  Needslots of people
diverse population: to man the activities
 Families
 Relieson the fair
 Young people organisers .. and
 Less frequent park weather!
users
 ..  Limited
data from
each participant

13. +
Online survey

14. +
Online survey
General public, open space users and/or
Farlington Marshes users and stakeholders
Aims to:
 Attract all population in Portsmouth
 Potentially get a bigger sample

15. +
www.openspaces-portsmouth.org.uk

16. +
Google Map API v3
 Add markers with a click
 Capture geolocalised
information
 Display kml layers..
Fieldwork

17. +
Add markers - Website
Locations and flooding
Marker
Tutorial
Instructions
Postcode

18. +
Add markers - Coding
Map:
var map = new
google.maps.Map(document.getElementById("map_canva
s"), options);
For 1 location
only
Add marker:
google.maps.event.addListenerOnce(map, "click", function(
event)
var latlng = marker.getPosition();
Lat = latlng.lat() / Lon = latlng.lng()

19. +
Add markers - Database

20. +
Add markers - Database

21. +
Infowindow - Website

22. +
Infowindow - Website

23. +
Infowindow - Website

24. +
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

25. +
Customised maps: kml and styles

26. +
Customised maps: kml and styles
Coding Style
var myStyle = featureType: "road.arterial",
[ elementType: "geometry",
{featureType: "road", stylers: [{ visibility: "off" }]
elementType: "labels", },{
stylers: [{ visibility: "off" }] featureType: "road.local",
},{ elementType: "geometry",
featureType: "road.highway", stylers: [
elementType: "geometry", { visibility: "off" }
stylers: [ ]
{ saturation: -50 },
{ lightness: 20 },
{ visibility: "simplified" }]
},{

27. +
Quick analysis

28. +
Participation
100
100
90
80
70
60
50
40
30
20 18
10
0
Background Parks Flood Land Use Willingness to pay Farlington Marshes
Participants who accessed the page and usable replies

29. +
Participation - map

30. +
Time spent
00:40
00:35
00:30
00:25
00:20
Average=
00:15
18 minutes
00:10
00:05
00:00
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

31. +
Flood perception

32. +
Preferred scenario
Hold the line 88%
Managed
realignment, loss of 6%
80%
Managed
realignment, loss of 18 participants
For 6%
50%

33. +
Issues

34. +
Issues specific to this method
Technical Design
 Extensivetime to clear  Too long survey
the database
Loss of interest
 Notenough completed
 Too many questions:
surveys
No clear focus
 Loss of some data

35. +
Recommendations

36. +
Recommendations/suggestions
 Shorter survey (5 minutes)
 Focus survey on one issue
 Finding gatekeepers while starting the coding
 Organise
hands-on sessions? (University /
community centre)

37. Thanks!
+
Hélène Draux, Cities Institute
h.draux@londonmet.ac.uk
http://www.openspaces-portsmouth.org.uk