 |
 |
Hi Helen We created an Archaeological Consultation Trigger Map for Darlington in 2012. It took us a while, but I documented the process to some degree, as we were potentially going to have to do the same for the rest of the County (but that went away - be quiet or we might wake it up again...) Essentially, we mashed together lots of our polygon layers to make bigger polygons - which included SMs buffered by 50 metres World Heritage Site Registered Battlefield Registered Parks and Gardens Conservation areas Local Parks and gardens of interest (produced by Landscape team) HLC historic Cores of villages/towns SHINE polygons Wetland GIS polygons These obviously overlapped in many cases so were just all merged into one big ACT layer. We then Created two other layer - an additions layer and a subtractions layer. This was because if we edited the Mashed layer directly, if we updated it, we would need to re-edit it each time. However, by "storing" the edits in separate layers, we could automate the process a bit - ie create the Broad Mash layer add and subtract the relevant layers and job done. To edit the Addition and Subtraction layers, as most of our HER data is points, we did some other stuff too We did a cluster analysis - ICT generated some data of HER points within 100 metres of another point, the theory being that these might represent different parts of a larger site. We then filtered out the points already in the ACT layer and using other criteria eg Buildings were left out, as were a few other types of Monument such as boundary stones. This left us with a list of records to check. We also did some checking by types eg generated a list of broad site types which were much more likely to be more than just a point eg DMVs/SMVs, Cemeteries Using the Cluster analysis and types list, we then manually checked the relevant HER record and determined if they needed to be included or not, and if they did on an individual basis edited/added polygons using info in reports etc into the relevant addition or subtraction layers. It worked ok, though the manual analysis took a little time. However, we viewed this as a pilot for what we might have to do for the whole county, and based on the pilot, doing the whole county in this way would be time consuming but doable. But thinking about the whole County, another thing we considered (but didn't need to do for Darlo) was that we might focus developing the maps on the areas with most development/planning applications first. Finally, we did ponder a bit on updating. And in theory this would be done annually, in practice it hasn't been. But the thought was largely along the lines of if we added more SHINE records, or more SMs (or Conservation areas etc) were created we would mash them into the layer using the automatic process. We could also add or subtract bits in the relevant layers as information on sites was updated. How well it works in terms of Consultation you would need to ask my DM colleagues, but that's how we created it Hope that's helps Best wishes Nick Boldrini Historic Environment Record Officer Ext 267008 From: Issues related to Historic Environment Records [mailto:[log in to unmask]] On Behalf Of Helen Wells (Archaeology) Sent: 10 September 2014 13:00 To: [log in to unmask] Subject: [MASSMAIL]Constraint and Alert Mapping Hi all, Thought I'd bring this up again (!!!). A while ago we started work on our layers working to the HER21 Guidance: http://www.helm.org.uk/content/docs/HER21_Alerts_and_Constraints_Maps.pdf However, since this Guidance was then withdrawn, what's happening with the idea? Has anyone successfully made some constraint/alert mapping that they're using with district/borough councils as part of the planning process? Would be interested to hear of people's experiences before we start trying to make our own, again... Helen Wells Historic Environment Record Officer Leicestershire County Council Planning, Historic & Natural Environment, Leicestershire County Council, County Hall, Glenfield, Leics, LE3 8RA Telephone: 0116 3058323 / E-mail: [log in to unmask]<mailto:[log in to unmask]> _______________________________________________________________________________________________________________ This e-mail and any files transmitted with it are confidential. If you are not the intended recipient, any reading, printing, storage, disclosure, copying or any other action taken in respect of this e-mail is prohibited and may be unlawful. If you are not the intended recipient, please notify the sender immediately by using the reply function and then permanently delete what you have received. Incoming and outgoing e-mail messages are routinely monitored for compliance with Leicestershire County Council's policy on the use of electronic communications. The contents of e-mails may have to be disclosed to a request under the Data Protection Act 1998 and the Freedom of Information Act 2000. The views expressed by the author may not necessarily reflect the views or policies of the Leicestershire County Council. Attachments to e-mail messages may contain viruses that may damage your system. Whilst Leicestershire County Council has taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. ________________________________ Help protect our environment by only printing this email if absolutely necessary. The information it contains and any files transmitted with it are confidential and are only intended for the person or organisation to whom it is addressed. It may be unlawful for you to use, share or copy the information, if you are not authorised to do so. If you receive this email by mistake, please inform the person who sent it at the above address and then delete the email from your system. Durham County Council takes reasonable precautions to ensure that its emails are virus free. However, we do not accept responsibility for any losses incurred as a result of viruses we might transmit and recommend that you should use your own virus checking procedures.