Project-Plan

Local Wildlife Sites: Project-Plan

BRIGHTON AND HOVE’S WILDLIFE FORUM

www.BHWF.org.uk

Managing the dataset associated with Local Wildlife Sites, displaying this on a map and updating the key information relating to each site.

Discussion between James Newmarch and John Patmore on 29 December 2013 [plus 12 January 2014 update]

Following the 12 October2013 meeting the key points to progress are:

1. Maintaining a list of the local wildlife sites LWSs on a BHWF server/PC. This can be stored as;

• a spreadsheet,
• a database, or
• GIS-linked attributes table.

2. Maintaining a Basic Dataset

Needs to be 'field-tested' by checking that all BHWF members can use it.

Key Data:

- Unique Site Code (6 character: gives unique identifier). This acts as a 'Primary Key' for each site and does not change.

- Site Name (note: this also includes 'New Sites' – see #3 below)

- Grid Reference (for central point, OS as 5---,1--- which equals TQ+6figures)

- Area – for whole site, Areas of sub-features - if useful.

- Primary wildlife/geodiversity features - (see box 1 below), Phase1 habitat type, physical morphology esp. geodiversity features/shape/slope/appearance, and soil type.

- Key Species - Protected, BAP, Interesting Species, A 'Confidential Data' field needed.

- Links to associated web-sites, especially Local Groups.

- Key contact(s) in BHWF for more details

- Date last amended, + by whom (name)

Where to store the BHWF data?

- One option is to use the current BHWF virtual space (on 'Google Drive')

- John and James take primary responsibility for producing and maintaining this dataset.

- John and James to write protocol for arranging the dataset and then discuss this with Bernard Evans.

Others who can amend the core data are: Martin, Bernard Evans. Most critical for the site .shp polygons which are uploaded to the 'Google Map' for BHWF sites.

3. New Sites: There may be only limited information, but the dataset needs to be flexible in being able to add New Sites.

- Railway embankments with vegetation connecting habitats

- 'Wildlife' to also include geological and geodiversity sites

- example: Preston Park as a whole, although eastern side has potential to connect with Surrenden Road central reservation and greenspace near the Surrenden School campus.

- example: Dyke Road Park (opposite Booth Museum) has potential for enhancing native biodiversity.

The council may seek our view in the future on other sites to add to their list.

* ACTION: Add pLWS category = 'potential local wildlife site'.

4. Sites Map: A physical map showing the location of Local Wildlife Sites can be provided through Google Maps.

- This becomes Public Informatione

- Initially central point can be provided with the Unique Site Code.

- Polygons can then be added. eg: see 'Green Ridge' – showing a simplified boundary and colour infill.

* ACTION: Just add the Site Code and Name to the map, no additional information at this stage. Interested viewers can request further details from BHWF. This has been started at the BHWF Sites Map.

* James to move Arrow Pointers into position on BHWF Map with Phil to advise if locations are uncertain. [12i2014 update]

* ACTION: John to provide technical information to Food Partnership to ensure .shp information is obtained. DONE, files sent to John and they work correctly.

* ACTION: James to make second attempt to obtain data from BHCC. Correct GB projection for .shp files will be useful, but mainly the site codes and names plus details as they are held on the BHCC database. NOTE: data has also been downloaded for 62 Local Wildlife Sites/LNRs as held on ‘CityWildlife’. This can be accessed via spreadsheet on BHWF server.

- Key contact(s) in BHWF for more details

- Date last amended, + by whom (name)

Where to store the BHWF data?

- One option is to use the current BHWF virtual space (on 'Google Drive')

- John and James take primary responsibility for producing and maintaining this dataset.

- John and James to write protocol for arranging the dataset and then discuss this with Bernard Evans.

______*: John to produce agreed file structure for all site data in discussion with Bernard Evans, plus structure for GIS files to enable entire directory to be shared.

______ _ Note: Bernard may be able to help inputting data, but is not able to comment on file management applications/structure or standards. [28i2014 update]

Others who can amend the core data are: Martin, Bernard Evans. Most critical for the site .shp polygons which are uploaded to the 'Google Map' for BHWF sites.

Notes from discussion between John Patmore and Dave Moody on 4 February 2014.

*action: Dave – to look into folder options for storing all wildlife site related data in ‘the cloud’ (on-line storage)

Current aim is to use existing BHWF on-line folders for these. Each ‘wildlife site’ will have its own individual folder. A spreadsheet can co-ordinate hyperlinks to these folders. Each folder will have a ‘unique key’ name, matching the spreadsheet I.D Key Reference. on each row, 1 row per unique Key = 1 site. The spreadsheet columns will provide a summary for each site (name/OS ref/area/hyperlinks...)

For relationship between spreadsheet columns and folder contents refer to this document (BHWF WildlifeSites File Structure.pdf)

Standard folder contents for each folder related to each wildlife site.

FOLDER CONTENTS

• locationmap = as .jpg (to show location in surrounding context)
• boundarymap = as .jpg , AND as .shp file exported from GIS
• phase1map = as .jpg , AND as .shp file exported from GIS
• description = as RTF text. Basic description of site and key features.
• managementobjectives = summary as RTF text for ideal management objectives, also threats to site, with details if available
• managementplan = as RTF text, with details if available
• surveyA .... surveyZ = date, name, surveyor details plus the output files
• sitephotoA .... sitephotoZ = as ..jpg or .png files (smaller file size than .tif or .raw image files)

15 May 2014: Dave Moody and John Patmore held follow-up discussion to review progress. Key outcomes:

1. LWS Folders (including LGS, SSIS, pLWS) can be renamed and content edited.

2. The current Key Reference Number (100,000 on) will be transferred to its corresponding 6 Letter code (‘MARINA’)

3. For each Folder there is a ‘README’ document containing the site CODE, NAME and NUMBER

4. Each folder will have a standard set of ‘Default’ files. These can be accessed from the ‘INDEX.htm’ file, which appears as a web-page (See Example Here... )

5. Although still time consuming, the most efficient way to store the Data on Google Drive will be to create a ‘Default’ folder with the standard file names on blank documents. This entire folder and hyperlinked blank documents can then be copied into each of the 70(+) LWS folders.

6. We need to check the relative hyperlink is retained in each case.

7. Then it is simply a matter of replacing the content in each blank document with the live information for each LWS as this becomes available (note: much of the core data was downloaded by Robin in 2013 before ‘citywildlife’ was abandoned by BHCC)

*DECISION NEEDED: The data stored in BHWF’s Goggle space is potentially password protected (view/edit options are available). However it is still stored on a globally based network.

We need to agree as a Forum how much ACCESS to provide (refer to note from meeting dated: 12 October 2013)

This needs to be discussed with Dave, James, Jane, John, Martin, Phil, Pru, (+???)

3 June 2014: Jane, Dave, John, Martin agreed final points for data storage/access:

Initial access is from the BHWF wildlife sites map, blue arrows will be changed to Plain Green arrow for LWS. Yellow arrow for LGS and Mauve arrow for SSSIs. All the LNRs have a local group associated and these are indicated by a Numbered Marker.

Polygons for site boundaries will not be used as there may be unintended legal problems. The Green and Yellow arrows will indicate the central location of each site.

* action: Each arrow position and reference key needs to be checked. Can BHWF members use the same Tetrads as before (ref: https://sites.google.com/site/bhwildlifeforum/localwildlifesites)

On the left side of the ‘Google Map’ is a list showing the site reference key letters (eg: ‘MARINA’) which match a folder containing further details for each site. It was agreed to keep the Index page password protected. BHWF members can view this page and site details.

* action: Provide a ....@gmail.com e-mail address to John who will provide access.

Folders will be renamed with reference key code. Files with the details for each site need to be renamed (as shown on ‘Folder Contents’ above) and uploaded to the correct folder.

* action: Dave and John to prepare folders, Bernard Evans may be able to assist with uploads and data checking [August 2014 update: Bernard emailed he was unable to help, but did return the data CD]

Progress to date will be explained at the 24 June BHWF meeting. All members are welcome to check the site details in their area and to pass on additional information to BHWF for adding to the site folders as it appears.

The Brighton biosphere bid project had prepared a map showing wildlife sites (see: http://zoom.it/uWfW) but the resolution is too low for clarity. It also excludes the Geological Sites!

* action: Everybody to check if wildlife areas indicated on this 'biosphere bid' map are missing from the BHWF sites map.

[end]