Enhancing Ordnance Survey Meridian 2 with FME: A Case Study by Dotted Eyes Ltd
160 likes | 290 Vues
At the FME Worldwide User Conference in Vancouver (Sep 21-22, 2006), David Eagle from Dotted Eyes Ltd shared insights on the production of Ordnance Survey's Meridian 2 using FME technology. Established in 1989, Dotted Eyes is a UK-based authorized reseller and expert in FME solutions. This presentation detailed the methodologies and innovations that ensure high-quality data management and integration from various sources, highlighting the critical quality assurance processes facilitated by FME. Discover how Dotted Eyes successfully transforms complex geographical data into reliable mapping products.
Enhancing Ordnance Survey Meridian 2 with FME: A Case Study by Dotted Eyes Ltd
E N D
Presentation Transcript
v FME Worldwide User Conference - Vancouver Sep. 21-22, 2006 Production of Ordnance Survey Meridian 2 David Eagle – Consultant / Trainer Dotted Eyes Ltd, UK david.eagle@dottedeyes.com
Who are Dotted Eyes? • Authorized Reseller based in Birmingham, England • Established in 1989; now 28 people • Working with Safe Software for 10 years • UK distributor of ‘all things’ FME! • Stock and sell Safe Software products • FME training – two-day course • Consultancy projects using FME • Support by phone & e-mail (support@dottedeyes.com) • Embed FME Objects into our own software products
Strategic Partnerships • MapInfo • Premier partner • Oracle • Partner specialising in Spatial and Locator applications • Ordnance Survey • Platinum partner; supplier of consultancy and software • Safe Software (FME and SpatialDirect) • Reseller & OEM using FME Objects
What Else Do We Do? • Development and consultancy services in GI • Rich internet applications – ResponseMX • AJAX or Flash for cross-browser compatibility • Java EE n-tier architecture on the server • Developer framework with sample applications • Used in banking, local and central government, emergency services, crime and disorder reduction • www.dottedeyes.com\rmx
What is Meridian 2? • Ordnance Survey vector topography products: • OS MasterMap formerly Land-Line (1:1,250 & 1:2,500) • Meridian 2 (about 1:50,000 or 1:100,000) • Strategi (1:250,000) • Mini-Scale (1:1,000,000) • Digital representation of Great Britain • Road, rail, coast, hydrology, woodland, positioned text • Admin boundaries, developed land use areas (DLUA) • Topologically structured polygons, polylines & points geometry with positioned text features • Supplied as tiles in NTF and GIS / CAD formats
What’s Our Role? • We created the product in the year 2000 • Contributed to discussions about content and form • Final decisions on specification rested with OS • Finished roads data supplied by Ordnance Survey • We’ve produced annual ‘refreshes’ since then • The content is entirely renewed every year • Well accepted by the market, so specification changes are now resisted • Conflation of data from a variety of sources • Strategically the process is a stop-gap measure • Long-term aim is to use automated generalisation • Major challenge, as the factor of scale change is 20x
Derived From: • Several OS products are the source for Meridian 2 OSCAR Route-Manager Roads Meridian 2 Land-Line Railway & stations Boundary-Line County, District, Unitary Strategi DLUA, Woodland, Hydrology, Text LandForm PANORAMA Coastline
OS Hierarchy of Feature Type Positional Quality Important Less Important
The Annual Refresh of Meridian 2 • Compare updated sources againstthe mid-scale database we maintain • Apply changes to meet specification • Quality Assurance on edited data • Build the topological structure of nodes, edges and faces • Write NTF (National Transfer Format) • Convert to MID/MIF (including styling), ESRI Shape and DXF
History • No FME workbench available in 2000 • Semantic mapping files were created • Workflow was imported when workbench became available • Subsequently enhancedand made more efficient • Refined each year with experience
QA with FME • Example rule 1… • Polygon layers must not overlap each other • Edges can snap • FME finds overlaps • Woodland extent is clipped • Coastline overlap is resolved DLUA Woodland Coast
QA with FME • Example rule 2… • New connectivity nodes if new rivers are captured • New nodes introduced where rivers join coast
NTF Preparation • Create link and node network Lake Node.tab Lake Link.tab Lake Seed.tab (Lake Tiled.tab) Lake.tab
NTF to supply formats • Translate from NTF to: • DXF • MID/MIF • ESRI SHAPE • Using TranspOSe • Includes embeded FME technology
Meridian 2 Transformers Hall of Fame • PolygonBuilder to construct features 2. LineOnAreaOverlayer to produce neat lines Input: Tile lines & Lake polygons 1. Tester – Simple yet effective!
Summary • We use FME for format translation, but… • It saves us time and money in the QA routines that it performs on project data • Ordnance Survey customers receive a product of high quality and integrity • Dotted Eyes customers efficiently and quickly manage data from National Mapping Agencies, with FME Objects offering many output formats