Olly and Liam got to grips with linking ArcGIS and MySQL server last week, essentially they have created a method to allow ArcGIS to talk directly to the HALOGEN data without the need to export data (e.g. as a csv or tab delimited text file). So far it looks like we can query directly on the database. Why is this great news you ask? Before I created an events theme in ArcGIS which was then converted to a shapefile, unfortunately with large volumes of data we exceeded the maximum size of shapefiles and therefore could not query the data any further without a crash. We still need to test and see if relational databases work though, watch this space...
Andrew.
Showing posts with label projectmethodology. Show all posts
Showing posts with label projectmethodology. Show all posts
Monday, 8 August 2011
Tuesday, 2 August 2011
Plotting aggregated points over Google Earth satellite images
Olly has created a web interface that plots our data on to Google Earth satellite images. Our data is aggregated to the centre of BNG 1km squares to preserve confidentiality and to standardise the resolution of our database as there are several different data sources to compare. I am concerned that end users may forget / not read the project documentation and think that a point marks the exact location of data when in reality it could be anywhere in a km square around the point. Does anyone else share these concerns - or have a way of reminding an end user of this?
Andrew.
Andrew.
Labels:
halogen2,
jisc,
jiscgeo,
products,
projectmethodology,
riskanalysis,
users
Wednesday, 9 March 2011
Project Plan Post 6 of 7: Projected Timeline, Workplan & Overall Project Methodology
Work Plan The high level workplan is outlined below. Listed against each workpackage are the initials of the principal team member(s) responsible for its delivery.
Workpackage ò | 02 11 | 03 11 | 04 11 | 05 11 | 06 11 | 07 11 | 08 11 | 09 11 | 10 11 | ||
WP1 - Set-up and governance (DC) | |||||||||||
Project set-up, induction and PID | |||||||||||
Steering and project group meetings | |||||||||||
JISC Programme level activity and reporting to funder | |||||||||||
WP2 – Data sources (AB, OB, LG) | |||||||||||
Extend coverage of PAS data | |||||||||||
Additional data sources - establish detailed requirements and investigate feasibility for 2 new sources. | |||||||||||
Extract, clean, transform and load new data sources | |||||||||||
Update data glossary and system documentation | |||||||||||
WP3 – Update HALOGEN data management plan (DC) | |||||||||||
Review and update DMP | |||||||||||
WP4 – Data Extraction Tool (AG, MW) | |||||||||||
Establish and document requirements | |||||||||||
Evaluate tools and select preferred supplier | |||||||||||
Procure and produce implementation plan for preferred tool/supplier | |||||||||||
WP5 – Web Enquiry Facility (OB) | |||||||||||
Establish requirements | |||||||||||
Investigate options and feasibility of delivery | |||||||||||
Document and publish findings | |||||||||||
WP6 – Develop & Disseminate HALOGEN Case Study (DC, OB, AB) | |||||||||||
Prepare case study re:community syntheses input | |||||||||||
Disseminate to stakeholders | |||||||||||
WP7 - Project Evaluation (DC) | |||||||||||
Develop interim and final project reports (see evaluation milestones below) | |||||||||||
WP8 – Dissemination (DC, OB, AB) | |||||||||||
Maintain project blog, halogen web site and run briefing sessions | |||||||||||
Project Approach
When identifying and evaluating specific tools and technologies, open source solutions will be considered alongside those which are already licensed by the University, the aim being to reduce the ‘barrier to entry’ for other institutions wishing to adopt the approaches used by UoL.
The evaluation will involve some desk based research but will be heavily biased towards the building of 'prototypes' using different tools.
Subscribe to:
Posts (Atom)