Gis Data Models

Total Page:16

File Type:pdf, Size:1020Kb

Gis Data Models GIS DATA MODELS CONCEPTUAL MODEL OF SPATIAL INFORMATION 1. Introduction GIS does not store a map in any conventional sense, nor it stores a particular image or view of geographic area. Instead, a GIS stores the data from which we can draw a desired view to suit a particular purpose known as geographic data. There are two types of data in GIS; spatial data and non-spatial data (Attribute data). Non-spatial data include information about the features. For example, name of roads, schools, forests etc., population or census data for the region concerned etc. Non-spatial or attribute data is that qualifies the spatial data. It describes some aspects of the spatial data, not specified by its geometry alone. A geographical information system essentially integrates the above two types of data and allows user to derive new data for planning. Spatial models are important in that way in which information is represented affects the type of analysis that can be performed and the type of graphic display that can be performed and the type of analysis that can be obtained. In GIS systems there is a major distinction between what are usually referred to as vector GIS and raster GIS. These two approaches to spatial data processing, often to be found in the same GIS package, reflect two different methods of spatial modeling: the former focusing on discrete objects that are to be described, and the latter concerned primarily with recording what is to be found at a predetermined set of locations that may be grid cells or points. 2. Spatial Information Spatial characteristics of information can be broadly distinguished between those that describe where things are, using locations consisting of reference positions, spatial units and spatial relationships; those that describe the form of phenomena, using qualitative and quantitative descriptions of shape and structure; and those that describe associations and interactions between different phenomena. All geographical data can be reduced to three basic geographical phenomenon can in principle be represented by a point, line or area plus a label saying what it is. So an oil well could be represented by a point entity consisting of a XY coordinate; a road could be represented by a series of XY coordinates; a floodplain could be represented by an area entity covering a set of XY co-ordinates plus the label ‘floodplain’. The labels could be the actual names as given here, or they could be special symbols. The essential features of any data storage system are that they should be able to allow data to be accessed-and cross-referenced quickly. There are several ways of achieving this, some of which are more efficient than others. Unfortunately, there seems to be no one 'best' method that can be used for all situations. This explains in part the massive investment in labour and money in effective database management systems, which are the computer programs that control data input, output, storage, and retrieval from a digital database. Figure 1: Real world phenomena represented as three basic entities 3. Layers and Coverages The Common requirement to access data on the basis of one or more classes has resulted in several GIS employing organizational schemes, in which all data of a particular level of classification, such as roads, rivers or vegetation types, are grouped into layers or coverages (refer Figure 3.). GIS organize spatial data into layers. Typical layers represent information belonging to particular classes. The layers can be combined with each other in various ways to create new layers that are a function of the individual ones. Any layer does not contain any areal regions that are overlapping, therefore it is possible for each region to have multiple attributes corresponding to multiple perspectives on the meaning of that region. Figure 2. Layers and Coverages 2 4. Data Model In order to represent the spatial information and their attributes, a data model – a set of logical definitions or rules for characterizing the geographical data is adopted. The data model represents the linkages between the real world domain of geographical data and the computer and GIS representation of these features. As a result, the data model, not only helps in organizing the real-world geographical features into a systematic storage/retrieval mechanism, but also helps in capturing the user’s perception of these features. The model : a) Structures the data to be amenable to computer storage/retrieval and manipulation. The data structure is the core of the model and it is based upon this that features of real world are represented. The ability of the data structure to totally represent the real world determines the success of the model. b) Abstracts the real world into properties, which is perceived by a specific application. For example, a Landuse map is perceived to be made up of different classes with symbols and legends. The district information is perceived to be made up of district maps and different attribute tables. c) Helps organize a systematic file structure, which is the internal organization of real world data in a computer. 5. Conceptual Models of Spatial Information There are different models, which have influenced the way in which data are organized and processed within GIS. They are based respectively on objects, networks and fields. Object-based model: Object-based spatial models emphasize individual phenomena that are to be studied in isolation or in terms of their relationships with other phenomena. Any phenomena however big or small may be designated as an object, provided that it can be separated conceptually from neighboring phenomena (refer figure 4). Objects may be composed from other objects and they may have specific relationships with other separate objects. An object-based view is appropriate, though not confined, to phenomena that have well defined boundaries. Hence it is suited to human made phenomena, such as buildings, roads, utilities and administrative regions. Some natural phenomena, such 3 as lakes, rivers, islands and forests, are often represented in object based models because they need to be treated as discrete phenomena for some purposes. Figure 3. The Object based Conceptual View Networks Model: Network based spatial models share some aspects of the object based model in that they often deal with discrete phenomena, but the essential characteristic is the need to consider interactions between multiple objects, often along discrete paths or routes that connect them. The exact shape of the phenomena may not be of much importance. What is more important is some measure of distance, or the impedance, between specified phenomena. Typical examples of applications for which a network model is appropriate are studies of traffic on road sea and air route; and analysis of flow of water, gas and electricity through pipelines and cables (refer figure 4). Fields Model: The field based view is appropriate for modeling phenomena that are regarded as continuously variable across some region of space. Examples of phenomena that may be treated as fields include the concentration of pollutants in the atmosphere, temperature of the ground surface, the moisture levels in soil, and the speed and direction of flow in bodies of air and water. Fields may represent either two or three spatial dimensions, depending on the application. A field based spatial model is often adopted when the data to be modeled are not known in sufficient detail to provide precise boundaries, even though at some resolution they could be said to exist (refer figure 4). 4 5 Figure 4. Conceptual models of spatial Data 6. Spatial Data models for GIS: Representation in computer When Geographical data are entered into a computer the user will be most at ease if the geographical information system can accept the phenomenological data structures that he has always been accustomed to using. But computers are not organized like human minds and must be programmed to represent phenomenological structures appropriately. Moreover, the way the geographical data are visualized by the user is frequently, not the most efficient way to structure the computer database. Finally, the data have to be written and stored on magnetic devices that need to be addressed in a specific way. Geographical information systems provide methods for representing spatial data that allow the user to adopt conceptual models resembling to a large extent the three classes of model as discussed above. There are two broad categories of spatial data models. These are vector data model and raster data models. The data base concept is central to a GIS and is the main difference between a GIS and drafting or computer mapping systems, which can produce only good graphic output. All contemporary Geographic Information system incorporates a data base management system. Data base systems provide the means of storing a wide range of geographic information and Updating it without the need to rewrite program. In GIS, the spatial data models handle where the features are and Non- spatial data models or Data base management system handle the feature description and how each feature is related to other. Two approaches or models have been widely adopted for representing the spatial data within GIS ; The cartographic map model and the geo-relational model. Each of these approaches is based on a specific spatial data model. The Composite Map Model is usually based on a tessellated (raster) representation of space and the Geo-relational model is usually associated with a vector representation of space. Vector data model represents phenomena in terms of the spatial primitives, or components, consisting of point, line, polygon, surfaces and volumes. Raster data model represents phenomena as occupying the cells of a predefined, grid shaped tessellation. 6.1 Raster Spatial Data Model 6 Typically the grid-cell tessellation, widely known as raster structure is the most commonly adopted structure in a GIS package.
Recommended publications
  • Arcgis Marine Data Model Reference
    ArcGIS Marine Data Model Reference ArcGIS Marine Data Model (June 2003) This document provides an Dawn J. Wright, Oregon State U. overview of the ArcGIS Marine Patrick N. Halpin, Duke U. Data Model. This model focuses on Michael Blongewicz, DHI important features of the ocean realm, both natural and manmade, Steve Grisé, ESRI Redlands with a view towards the many Joe Breman, ESRI Redlands applications of marine GIS data. ArcGIS Data Models TABLE OF CONTENTS Acknowledgements ................................................................................................................... 4 Introduction ............................................................................................................................... 5 Why a Marine Data Model?.................................................................................................... 6 Intended Audience and Scope of the Model............................................................................ 8 The Process of Building a Data Model ..................................................................................... 10 Final Data Model Content, Purpose and Use........................................................................ 14 Data Model Description ........................................................................................................... 16 Overview ............................................................................................................................. 16 Conceptual Framework....................................................................................................
    [Show full text]
  • A Model-To-Model Transformation of a Generic Relational Database Schema Into a Form Type Data Model
    Proceedings of the Federated Conference on Computer Science DOI: 10.15439/2016F408 and Information Systems pp. 1577–1580 ACSIS, Vol. 8. ISSN 2300-5963 A Model-to-Model Transformation of a Generic Relational Database Schema into a Form Type Data Model Sonja Ristić, Slavica Kordić, Milan Čeliković, Vladimir Dimitrieski, Ivan Luković University of Novi Sad, Faculty of Technical Sciences, Trg D. Obradovića 6, 21000 Novi Sad, Serbia Email: {sdristic, slavica, milancel, dimitrieski, ivan}@uns.ac.rs ฀ engineering and review different database meta-models Abstract—An important phase of a data-oriented software (MM) that are used in the database reengineering process system reengineering is a database reengineering process and, applied in IIS*Studio. In [5] we propose an MD approach to in particular, its subprocess – a database reverse engineering data structure conceptualization phase of database reverse process. In this paper we present one of the model-to-model engineering process that is conducted through a chain of transformations from a chain of transformations aimed at transformation of a generic relational database schema into a M2M transformations. In this paper we present the final step form type data model. The transformation is a step of the data of the conceptualization phasethe M2M transformation of structure conceptualization phase of a model-driven database a generic relational database schema into a form type model. reverse engineering process that is implemented in IIS*Studio The form type concept and the IIS*Studio architecture are development environment. given in Section 2. Classifications of form types and relation schemes are described in Section 3. The transformation of a I.
    [Show full text]
  • Metamodeling the Enhanced Entity-Relationship Model
    Metamodeling the Enhanced Entity-Relationship Model Robson N. Fidalgo1, Edson Alves1, Sergio España2, Jaelson Castro1, Oscar Pastor2 1 Center for Informatics, Federal University of Pernambuco, Recife(PE), Brazil {rdnf, eas4, jbc}@cin.ufpe.br 2 Centro de Investigación ProS, Universitat Politècnica de València, València, España {sergio.espana,opastor}@pros.upv.es Abstract. A metamodel provides an abstract syntax to distinguish between valid and invalid models. That is, a metamodel is as useful for a modeling language as a grammar is for a programming language. In this context, although the Enhanced Entity-Relationship (EER) Model is the ”de facto” standard modeling language for database conceptual design, to the best of our knowledge, there are only two proposals of EER metamodels, which do not provide a full support to Chen’s notation. Furthermore, neither a discussion about the engineering used for specifying these metamodels is presented nor a comparative analysis among them is made. With the aim at overcoming these drawbacks, we show a detailed and practical view of how to formalize the EER Model by means of a metamodel that (i) covers all elements of the Chen’s notation, (ii) defines well-formedness rules needed for creating syntactically correct EER schemas, and (iii) can be used as a starting point to create Computer Aided Software Engineering (CASE) tools for EER modeling, interchange metadata among these tools, perform automatic SQL/DDL code generation, and/or extend (or reuse part of) the EER Model. In order to show the feasibility, expressiveness, and usefulness of our metamodel (named EERMM), we have developed a CASE tool (named EERCASE), which has been tested with a practical example that covers all EER constructors, confirming that our metamodel is feasible, useful, more expressive than related ones and correctly defined.
    [Show full text]
  • Enterprise Data Modeling Using the Entity-Relationship Model
    Database Systems Session 3 – Main Theme Enterprise Data Modeling Using The Entity/Relationship Model Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences Presentation material partially based on textbook slides Fundamentals of Database Systems (6th Edition) by Ramez Elmasri and Shamkant Navathe Slides copyright © 2011 1 Agenda 11 SessionSession OverviewOverview 22 EnterpriseEnterprise DataData ModelingModeling UsingUsing thethe ERER ModelModel 33 UsingUsing thethe EnhancedEnhanced Entity-RelationshipEntity-Relationship ModelModel 44 CaseCase StudyStudy 55 SummarySummary andand ConclusionConclusion 2 Session Agenda Session Overview Enterprise Data Modeling Using the ER Model Using the Extended ER Model Case Study Summary & Conclusion 3 What is the class about? Course description and syllabus: » http://www.nyu.edu/classes/jcf/CSCI-GA.2433-001 » http://cs.nyu.edu/courses/fall11/CSCI-GA.2433-001/ Textbooks: » Fundamentals of Database Systems (6th Edition) Ramez Elmasri and Shamkant Navathe Addition Wesley ISBN-10: 0-1360-8620-9, ISBN-13: 978-0136086208 6th Edition (04/10) 4 Icons / Metaphors Information Common Realization Knowledge/Competency Pattern Governance Alignment Solution Approach 55 Agenda 11 SessionSession OverviewOverview 22 EnterpriseEnterprise DataData ModelingModeling UsingUsing thethe ERER ModelModel 33 UsingUsing thethe EnhancedEnhanced Entity-RelationshipEntity-Relationship ModelModel 44 CaseCase StudyStudy 55 SummarySummary andand ConclusionConclusion
    [Show full text]
  • The Layman's Guide to Reading Data Models
    Data Architecture & Engineering Services The Layman’s Guide to Reading Data Models A data model shows a data asset’s structure, including the relationships and constraints that determine how data will be stored and accessed. 1. Common Types of Data Models Conceptual Data Model A conceptual data model defines high-level relationships between real-world entities in a particular domain. Entities are typically depicted in boxes, while lines or arrows map the relationships between entities (as shown in Figure 1). Figure 1: Conceptual Data Model Logical Data Model A logical data model defines how a data model should be implemented, with as much detail as possible, without regard for its physical implementation in a database. Within a logical data model, an entity’s box contains a list of the entity’s attributes. One or more attributes is designated as a primary key, whose value uniquely specifies an instance of that entity. A primary key may be referred to in another entity as a foreign key. In the Figure 2 example, each Employee works for only one Employer. Each Employer may have zero or more Employees. This is indicated via the model’s line notation (refer to the Describing Relationships section). Figure 2: Logical Data Model Last Updated: 03/30/2021 OIT|EADG|DEA|DAES 1 The Layman’s Guide to Reading Data Models Physical Data Model A physical data model describes the implementation of a data model in a database (as shown in Figure 3). Entities are described as tables, Attributes are translated to table column, and Each column’s data type is specified.
    [Show full text]
  • An Object Oriented Shared Data Model for GIS and Distributed Hydrologic Models
    An Object Oriented Shared Data Model for GIS and Distributed Hydrologic Models M. Kumar and C. Duffy International Journal of Geographical Information Science, IJGIS-2008-0131 Accepted for publication Sep. 2008 Abstract Distributed physical models for the space-time distribution of water, energy, vegetation, and mass flow require new strategies for data representation, model domain decomposition, a-priori parameterization, and visualization. The Geographic Information System (GIS) has been traditionally used to accomplish these data management functionalities in hydrologic applications. However, the interaction between the data management tools and the physical model are often loosely integrated and nondynamic. This leads to several issues addressed in this paper: a) The data types and formats for the physical model system and the distributed data or parameters may be different, with significant data preprocessing required before they can be shared. b) The management tools may not be accessible or shared by the GIS and physical model. c) The individual systems may be operating-system dependent or are driven by proprietary data structures. The impediment to seamless data flow between the two software components has the effect of increasing the model setup time and analysis time of model output results, and also makes it restrictive to perform sophisticated numerical modeling procedures (sensitivity analysis, real time forecasting, etc.) that utilize extensive GIS data. These limitations can be offset to a large degree by developing an integrated software component that shares data between the (hydrologic) model and the GIS modules. We contend that the pre-requisite for the development of such an integrated software component is a “shared data-model” that is designed using an Object Oriented Strategy.
    [Show full text]
  • DCSA Information Model 3.0
    DCSA Information Model 3.0 December 2020 Table of contents Version history __________________________________________________ 8 1 Introduction __________________________________________________ 9 1.1 Preface ______________________________________________________ 9 1.2 Purpose ______________________________________________________ 9 1.3 Overview _____________________________________________________ 10 1.4 Conformance __________________________________________________ 10 1.5 Supporting publications ___________________________________________ 10 2 DCSA Information Model 3.0 ________________________________________ 13 2.1 Introduction ___________________________________________________ 13 2.2 Selected data modelling terms defined _________________________________ 14 2.3 The DCSA Information Model data types and formats ________________________ 15 2.3.1 Attribute naming conventions ____________________________________ 16 3 Logical Data Model ____________________________________________ 18 4 Logical Data Model usage ________________________________________ 20 4.1 Track and trace (T&T) ____________________________________________ 20 4.2 Operational vessel schedules (OVS) ___________________________________ 21 4.3 eDocumentation _______________________________________________ 23 5 Subject areas in the Logical Data Model _______________________________ 25 5.1 Shipment ____________________________________________________ 26 5.1.1 Shipment reference data _______________________________________ 31 5.2 Transport Document _____________________________________________
    [Show full text]
  • GIS-Based Hydrogeological Platform for Sedimentary Media
    [Annex I: Articles and reports related to the development of this thesis] GIS-based hydrogeological platform for sedimentary media PhD Thesis Domitila Violeta Velasco Mansilla Advisor: Dr. Enric Vázquez Suñè Hydrogeology Group (GHS) Institute of Environmental Assesment and Water Research (IDAEA), Spanish Research Council(CSIC) Dept. Geotechnical Engineering and Geosciences, Universitat Politecnica de Catalunya (UPC), Barcelona Chapter 1: Introduction I. ABSTRACT The detailed 3D hydrogeological modelling of sedimentary media (e.g. alluvial, deltaic, etc) that form important aquifers is very complex because of: (1) the natural intrinsic heterogeneity of the geological media, (2) the need for integrating reliable 3D geological models that represent this heterogeneity in the hydrogeological modelling process and (3) the scarcity of comprenhensive tools for the systematic management of spatial and temporal dependent data. The first aim of this thesis was the development of a software platform to facilitate the creation of 3D hydrogeological models in sedimentary media. It is composed of a hydrogeological geospatial database and several sets of instruments working within a GIS environment. They were designed to manage, visualise, analyse, interpret and pre and post- process the data stored in the spatial database The geospatial database (HYDOR) is based on the Personal Geodatabase structure of ArcGIS(ESRI) and enables the user to integrate into a logical and consistent structure the wide range of spatio-temporal dependent groundwater information ( e.g. geological, hydrogeological, geographical, etc data) from different sources( other database, field tests, etc) and different formats( e.g. digital data, maps etc). A set of applications in the database were established to facilitate and ensure the correct data entry in accordance with existing international standards.
    [Show full text]
  • The Entity-Relationship Model : Toward a Unified View of Data
    LIBRARY OF THE MASSACHUSETTS INSTITUTE OF TECHNOLOGY .28 1414 MAY 18 1977 Ji/BRARie*. Center for Information Systems Research Massachusetts Institute of Technology Alfred P Sloan School of Management 50 Memorial Drive Cambridge, Massachusetts, 02139 617 253-1000 THE ENTITY-RELATIONSHIP MODEL: TOWARD A UNIFIED VIEW OF DATA By Peter Pin-Shan Chen CISR No. 30 WP 913-77 March 1977 .(Vvsi4 M.I.T. LIBRARIES MAY 1 8 1977 RE'JtlvLiJ The Entity-Relationship Model—Toward a Unified View of Data PETER PIN-SHAN CHEN Massachusetts Institute of Technology A data model, called the entity-relationship model, is proposed. This model incorporates some of the important semantic information about the real world. A special diagrammatic technique is introduced as a tool for database design. An example of database design and description using the model and the diagrammatic techniciuc is given Some implications for data integrity, infor- mation retrieval, and data manipulation are discussed. The entity-relationship model can be used as a basis for unification of dilTcrent views of data: the network model, the relational model, and the entity set model. Semantic ambiguities in lhe.se models are analyzed. Po.ssible ways to derive their views of data from the entity-relationship model are presented. Key Words and Phrases: database design, logical view of data, semantics of data, data models, entity-relationship model, relational model. Data Base Task Group, network model, entity set model, data definition and manipulation, data integrity atid consistency CR Categories: S.oO, 3.70, 4.33, 4.34 1. INTRODUCTION The logical view of data has been an important i.s.siie in recent years.
    [Show full text]
  • 3. Data Models for Engineering Data
    3. Data Models for Engineering Data Conventional and Specific Ways to Describe Engineering Data Overview • Conventional Models – Overview of Data Models – Logical Models • Databases and the Relational Data Model • Object-oriented Data Models • Semi-structured Data Models – Conceptual Models • The Entity Relationship Model (ER) • The Unified Modeling Language (UML) • Engineering Data Models – The Standard for the Exchange of Product Model Data (STEP) • STEP EXPRESS as a modeling language • EXPRESS-G as a graphical/conceptual model – STEP files Schallehn: Data Management for Engineering Applications Reminder: Data Model A data model is a model that describes in an abstract way how data is represented in an information system or a database management system. • A data model defines syntax and semantics, i.e. – How can data be structured (syntax) – What does this structure mean (semantics) • Very generic term for many applications – Programming languages have their data models (e.g. C++ and Java have object-oriented data models) – Conceptual design methods (e.g. ER, UML) represent a data model – File formats either apply a data model (e.g. XML) or implement their own – Database management systems implement data(base) models Schallehn: Data Management for Engineering Applications Information System Design Phases Conceptual Models: Requirements ER, UML, EXPRESS-G Analysis Conceptual Logical Models: Design Relational, Object-oriented, Document-oriented, EXPRESS Logical Design Physical Models: SQL-92, SQL:2011, XML, JSON, C++, Physical Java Design
    [Show full text]
  • Introduction to Data Modeling
    Chapter 2 Introduction to Data Modeling Objectives: to understand • Data modeling reduces complexities of database • Data modeling and why data models are design important • Designers, programmers, and end users see data • The basic data-modeling building blocks in different ways • What business rules are and how they influence • Different views of same data lead to designs that database design do not reflect organization’s operation • How the major data models evolved historically • Various degrees of data abstraction help • How data models can be classified by level of reconcile varying views of same data abstraction CS275 Fall 2010 1 CS275 Fall 2010 2 Data Modeling and Data Models The Importance of Data Models • Model: an abstraction of a real-world object or • Facilitate interaction among the designer, the event applications programmer, and the end user – Useful in understanding complexities of the real- • End users have different views and needs for data world environment • Data model organizes data for various users • Data models • Data model is a conceptual model - an abstraction – Relatively simple representations of complex real- • It’s a graphical collection of logical constructs world data structures representing the data structure and relationships • Often graphical within the database. • Creating a Data model is iterative and progressive – Cannot draw required data out of the data model – An implementation model would represent how the data are represented in the database. CS275 Fall 2010 3 CS275 Fall 2010 4 1 Data Model
    [Show full text]
  • Different Data Models and Schemas
    Different Data Models And Schemas Undated Hammad underfeeds chock, he phagocytose his onslaught very immemorially. When Ignaz acquaints his retrieval ticks not next enough, is Hewie jocund? Avocado Florian crossband: he docketing his runkles just and accessibly. We use schemas and allow app development by defining data For example: staff time stamp, user_id, session_id, etc. What Is Cloud Computing? Components of data and into tables. The differences less significant change the pay period until the sales. Data Modelling Conceptual Logical Physical Data Model. Of gesture, we could model it cleanly in ORM first. The data model is a collection of concepts or notations for describing data data. The query is simple and runs faster in a star schema. That means creating and maintaining a mapping layer between your application and your analytics system, with its own internal logic. Relational Data Model in DBMS Concepts Constraints Example. Relationship in report execution of data model does it shows how descriptive a json structure your costs of a much like tree structure in. The data modelling with existing data model composition and millions more legacy database migration life easier. The log you like there dimension table rows and recorded quickly and different types of tables that point to use this part of data model in a given figure. In this blog post we held other important mindset changes in NoSQL data modeling development agility through flexible schemas vs database manageability. We now comment on study specific features pertaining to shave above classes of strategies. As plant are more relationships so wood can through more than one trouble to understand same record.
    [Show full text]