Gcc Data Maintenance From Nov42010


Published on

A review of topographic database maintenance options

Download available upon request

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Information sharing between two individuals not belonging to the same information community is usually impeded by any of three conditions.
    1. Ignorance of the existence of information outside one’s own information community.
    2. Modeling of phenomena not of mutual interest.
    3. Modeling of phenomena in two representations different from each other such that each is not recognized by the other.
    The third condition is very, very typical in the geospatial community. Continuing our example of roads, different users of street Departments of Transportation (different information communities) define and collect road features differently. The result is that a State boundary, a road may have different names, different semantics, different accuracy metadata and so forth.
    The first five layers, from the Real World to the Project World, deal with the abstraction of real world facts, and are not modeled in software.
    The final four layers, from Points to Feature Collections, deal with mathematical and symbolic models of the world and are meant to be modeled in software.
    Even so, this Essential Model of the final four layers assumes that they are real-world objects, and gives no specification, however abstract, for their implementation. The final layer is the abstraction of reality specified in the language an information – the geometric and semantic description of a set of features or Feature Collection.
  • Geospatial information is anything that you can learn by looking at maps -- not just traditional maps, but new, creative, digital maps and earth visualization systems. A map, after all, is simply a metaphor for the Earth itself. We therefore accept raster Earth imagery as a kind of map, and even less structured collections of samples of Earth phenomena with any kind of instrumentation as acceptable maps. For the purposes of this presentation, we use the term “map” in a very broad sense – encompassing all earth metaphors from traditional paper maps to 3d earth visualization systems.
    We can learn about phenomena that vary with time by looking at special maps designed to reveal temporal differences and events. For now, we will assume that phenomena do not change, or that temporal aspects of geospatial information can be held as attributes of features. (a curb is a solid feature and its shape remains the same … whereas a cloud – shape varies over time)
    The fundamental unit of geospatial information is called a feature. Features may be defined recursively, so there can be considerable variation in feature granularity.
    The collection and use of geospatial information has one purpose: to communicate knowledge about phenomena that have location.
    For example, the knowledge imparted by the map answers two kinds of questions: "where" and "what."
    Maps can tell us where things are, both in relation to other nearby things.
    Maps also can tell us what things are, either through symbology (e.g., by use of color or line pattern whose meaning is explained in a legend) or through text or tabular annotations or multi-media links.
    The same goes for attributes that modify or extend our knowledge of things.
    Digital geospatial information is geospatial information that has been encoded into a digital form. The encoding is done so that computer resources can be applied to automate the business of geospatial information processing: storage, transmission, analysis, visualization and so forth.
    There are many different ways to create digital representations of geospatial information. This richness of alternatives is more a curse than a blessing since it has created the confusing and apparently chaotic variety of Geographic Information System (GIS) data structures and formats now confronting GIS users.
  • Gcc Data Maintenance From Nov42010

    1. 1. Bob Gaspirc Geospatial Competency Centre November 5, 2010 Geospatial Services in GCC Data Maintenance – Data Triggers Overview for EGP
    2. 2. 2 September 30, 2010 meeting - Topics • Data Content in IGE <<< Summary • IGE Data Repository <<< Summary • Data Maintenance Solutions <<< Today • Access Solutions • Web Mapping – iMapit • Infrastructure Architecture • Enterprise Viewpoint
    3. 3. 3 Data Content - Operational Information/Needs –Linked to Addresses, Segments, Intersections, Administrative Areas, Parcels, topo features, imagery –Secured and under the stewardship of the Business Unit. –Stored on Geospatial or Business Server –Linkage allows Business Units to spatially analyse, strategically plan, operationally plan and financially analyse operations. –Linkage Tools – GCC-GS –Feed, Link, Display, Analyze operational information
    4. 4. Accessible, timely relevant, accurate data • Authenticated and tagged data • Content • Coverage • Completeness • Currency • Spatial Accuracy • Works with my application
    5. 5. How is it used within your system Tax Assessment Catchbasin Cleaning Parking Tags – Handheld Work OrdersPlanning Traffic Counts Health Visits Street Furniture Solid Waste Demand Solid Waste Routes Traffic Lights Road Salt Traffic Restrictions Traffic Flow Pedestrian Crossings 311 Service Requests 211 Services
    6. 6. Problems - 9 levels of abstraction 6 The OpenGIS® Abstract Specification
    7. 7. How does the feature need to be described Geospatial Competency Centre 7
    8. 8. 8 General Data Life Cycle Data Collection Repository Process Dissemination Triggers Continuous
    9. 9. 9 Data Life Cycle Map general Feature Update Notification Forms tables Specific Feature Update By area User Data Entry Temp DB/ Other Business Centric Feature Update Integrity Reporting •Spring, summer, fall, winter •BW, Colour, IR, scale •Aerial, satellite, LiDAR •Other sources • Query Markers • CWP • Permits • Business transaction • Catchbasins, park features • Above ground As-builts •Flush, replace Data Collection Repositories DisseminationProcesses Imagery Soft copy photogrammetry ESM tables User tables DEM/DTM Imagery Library Topo-db Features Objects Attributes • feature recognition • edge detection • Line following • manual
    10. 10. 11 Data Maintenance Solutions • Business processes identified • Steward – clearly defined business roles • Source – authorization for changes • Work flow of tasks – controlled activities, steward driven • Transaction – long transaction management • Multi-user editing – version and conflict management • History & Lineage maintained • Validation and audit – transaction and database level • Distributed Maintenance encouraged • Software version control (CVS) • Problem/issue tracking (iTracker) • Multiple environments – Development, integration testing, QA, user acceptance testing, staging, production (CM) • Application Design – five tiered component architecture – Web based – Presentation – Web Interface, ArcGIS server ADF, my faces, JSP, … – Application – Java manager classes - Reusable – Services – ArcGIS server and server objects, SDE (Spatial Database Engine) - Shared – Business – Oracle stored packages - Reusable – Data – Oracle database objects • Application Security – LDAP authentication – Application authorization
    11. 11. Questions 12
    12. 12. 13 Land Structure Entrance or Land Entrance Structure Data Content - One Address Repository (OAR) 23 18A 18 20 • ½ million Authorized Municipal Address Numbers, all unique ids, under daily maintenance – GCC MS • Edit tool – GCC GS • Full history and lineage • Classified (Land, Structure, Structure Entrance, Land Entrance) feature coded as to general use • Address Family • Positioned within parcel/structure • Linked to Centreline, derives street name • Stage is Reserved prior to plan registration/deposition, Regular after plan registration/deposition • TBI: Business status records current status as planned, approved, demolished, foundations underway, ready for occupancy, occupied, …
    13. 13. 14 Data Content - Transportation Centreline • ~ 50,000 segments, ~ 35,000 intersections, unique IDs, under daily maintenance – GCC-MS • Edit tool – GCC GS • Includes road, highway, ramp, river, railway, hydro line, trail, pathway, laneway • Full history and lineage • Feature coded according to Transportation (arterial, local, …) • Authorized names, operational in absence of authorized • Address ranges derived from OAR • One-way, overpass/underpass, restricted turn and time limited turn Maintenance triggered from by-laws GCC-GS • TBI: Business status according to planned, constructed, dedicated, assumed, … Derived Address Ranges
    14. 14. 15 Data Content – Cadastral Plans, Parcels, Easements • 700,000 parcels – Survey accuracy, unique ids, under daily maintenance – GCC-MS • Parcels – Municipal (corridor, condo, standard), Tax • Easements • Plans – Subdivision, Reference, … • UD: History and lineage • Maintenance is tightly tied to business processes in the City, in MPAC and in Land Registry/Titles
    15. 15. 16 Forestry Regions Data Content - Administrative Areas • ~200 (growing as needed) Administrative Areas – integrated with Centreline, OAR and Parcels • Generally loaded as needed/requested by BUs. Sometimes created by GCC-GS on behalf of Bus. Load Tool – GCC-GS • Each with dedicated business steward, e.g. – Elections for Voting Subdivisions, Voting locations – online editing by Election Services Edit Tool – GCC-GS – Parks, Forestry & Recreation for Forestry Regions – Toronto Police Services for Police Zones – Solid Waste Management for Solid Waste Management District … • Each immediately associated with associated addresses, streets and parcels City Wards Police Zones
    16. 16. 17 Data Content - Background Layers – loaded as available • GTA Centreline from MOH • 75,000 street segments, names & address ranges (equivalent of 3.1 million addresses) covering Burlington to Clarington to Brock in the north TBI: extension to cover Windsor, to Kingston to Kawarthas & Muskokas in north • Imagery • Currencies include 1999 50cm color, 2002 20cm color, 2003 7.5cm BW, 2005 20cm color, TBI 2009 20cm color • Topographic Mapping • Curbs, buildings, fences, trees, pools, … Maintained by GCC-MS
    17. 17. 18 IGE Data Repository • Maintenance Repository & Viewing/Access Repository – Transaction based ETL • Security – As appropriate & Oracle role based Maintenance • Normalized for integrity • Business hours • No failover • Tuned for maintenance • MTM NAD27 View for Access • Denormalized for ease of use • 24/7 Accessibility • Implemented for 311, available to all • Failover • Isolation • Highly tuned for Viewing/access Performance • Oracle Spatial with ESRI SDE, MapInfo, … access • Multiple Coordinate Systems • WGS84 for Web mapping and interchange • MTM NAD27 for maintenance & other City use • Enterprise Applications • 311, TMMS, Hansen, RACS, IBMS ETL GCC-GS