MasterMap David Medyckyj-Scott Emma Sutton Tim Urwin Aims for the workshop • • • To remind you about OS MasterMap To begin to raise awareness (again) To seek your.
Download ReportTranscript MasterMap David Medyckyj-Scott Emma Sutton Tim Urwin Aims for the workshop • • • To remind you about OS MasterMap To begin to raise awareness (again) To seek your.
MasterMap David Medyckyj-Scott Emma Sutton Tim Urwin Aims for the workshop • • • To remind you about OS MasterMap To begin to raise awareness (again) To seek your input – – – – Are original requirements still valid? Have new requirements appeared? Is the timetable sensible? What sort of support is required? * for users * for support staff • To identify any other issues OS MasterMap – a Framework Digital Terrain Model Imagery Topographic themes Land Use Transport Network (ITN) Admin Boundary Points of Interest Pre-Build OS MasterMap • A seamless database reflecting the real world, with polygons representing man-made and natural features – topographic data have been restructured into a seamless database of 416+ million objects * fundamentally different to tile-based Land-Line data* • • Delivered in new format, Geography Markup Language (GML) Delivered in new ways – by theme – by user defined area – Change only Update (CoU) OS MasterMap - Topography TOIDs – Unique reference IDs • A unique identifier for each object – Allowing individual feature identification • With a defined lifecycle and version number Feature supply – not tile supply! • Builds on object oriented model • Full extent of data crossing the area of interest is supplied • Results in the supply of “hairy” data Chunk Extent Chunk Bounding Box Integrated Transport Network • ITN links reference the Topography Layer TOID Version Change Date 4000001298764523 1 310303 Descriptive Group Descriptive Term Nature of Road Length Road Topology Local Street Single Carriageway 42 Start Node End Node Reference to Topo 4000004756364758 4000009857364528 1000000139421883, 1000000139417597 OS MasterMap - benefits • Access to modern data • Consistent, national framework for referencing geographic information allowing data to be linked more easily – Topographic Identifiers (TOIDs) – data which can be exchanged and shared • Pre built polygons improves quality and means better cartography • Richer attribution, for more versatile classification of features, more intelligent data and better analysis • Greater control over supply e.g. themes and COU • New possibilities in terms of both end use and types of services that can be offered The service Mapping • Digimap Carto and Classic will be modified to serve MasterMap instead of Land-Line • Users must have the ability to – view cartographic quality maps produced using the MasterMap topographic data. – select particular themes of interest and feature type to view in the map – generate and download a cartographic quality map for printing. Formats offered will be GIF, EPS and PDF. – produce a map combining themes and layers from MasterMap Topographic with other OS mapping products – And maybe select a feature on the map and request attribute information, such as its area or when it was last updated Q. What should we do with ITN? Q. Is there a need for maps with Land-Line style cartography? Data supply Must • All data delivery is online • User defines areas of interest either interactively on-screen or using a selected predefined administrative boundary • Large requests are split into manageable "chunks" • All GML provided must be virtually identical to that which would be supplied by OS Should • Option to select one or more themes of data for an area of interest • Option to request changes only once initial supply has been taken • Large requests processed overnight • Requests can be bookmarked to run again at a later date Could • Option to download data in formats other than GML i.e. shape, mif/mid, DXF • Option to take complete re-supply • Access to historic data Support User requirements – have we got them right? • Best delivery method for support? • – e.g. web and paper documentation • Training required for… – site reps – users (this is NEW for EDINA) • Guidance for institutions? – responsibilities – software and data management issues • Awareness raising will be important – importance of local support, local experts Timetable • Jan 2006 – Project Kick off – Re-engagement with user community commences to affirm user requirements. • Autumn 2006 - alpha version available for expert user testing • Early 2007 - beta version available to a wider group (early adopters) • August 2007 - full release • July 2007 – Land-Line withdrawn How you can be involved… • • • • be part of a focus group to verify user requirements be an “expert user” early adopter be an early adopter institution provide feedback on current use of MasterMap – we know OS have provided OSMM for project work… • participate in online discussion forum Issues and implications • • Initial supply online… No more “real time” data delivery for large requests Any other points you want to make? Thank you User consultation and findings in 2002 • Star gazing exercise • Questionnaire survey – Predicted use: Research 86%, Teaching 49% – Update frequency: 40% annual, 38% twice yearly, 15% more frequently – 54% want access to change only updates – strong desire for formats other than GML – 60% felt users would need MM use training – 50% felt users would need MM data management training and 40% support in data management