Sas Report Writing Over the Years

Total Page:16

File Type:pdf, Size:1020Kb

Sas Report Writing Over the Years SAS REPORT WRITING OVER THE YEARS An Exploration Into the Difficult Task of Meeting Everyone's Needs. Written by Richard C Chiofolo, Ph. D. Kaiser Foundation Health Plan Oakland, California 5 July 1 \ 2000 528 Writing reports is not a very esoteric or intellectual task. It lacks glamour. The ability to produce reports isn't something people cite on their resumes. However, it may be one of the most useful functions in any language package because programmer/ analysts often need only put information on a piece of paper as a list or simple comparison of some business function or event. Whether the data is character fields in a list or data points put on a graph_ the intent is the same: put information in a format for presentation. Some level of summarization may be desired, but people are rarely willing to look at final statistical results without seeing some of the detailed information first. Communicating information itself should be the goal, but, in many cases, presentation is as important as the information itself. Finally, how information is presented counts, a lot. Programmers and analysts have their biases about how they want to do their work. At my age a non-graphic PROC CHART is fine, my assistants want to play with WEB ready graphics. We should look at the SAS procedures designed for making reports, but only those that give us the simple ability to present raw or summarized lists and comparisons. How well do they aid us to produce reports, not esoteric statistics, only mundane listings, detailed or summarized records in our workplace. SAS was designed originally by statisticians to prepare data for statistical comparisons. In the 70's, SPSS, BMDP and SAS were strong rivals for the market of statisticians and scientific experiments. By the 80's SAS became a more generally used package for "users" and other non-statistical applications, competing with FOCUS and CICS. Report generation became a more important component of the overall SAS package. Although relatively simple in purpose, attempts by SAS Institute to generate a flexible, coherent, easy to use and efficient SAS procedure for generating reports has actually been fraught with difficulties and mistakes. Since we are concerned only with "reports," not summary statistics or high level analysis, we need to define which SAS Procedures generate reports. Clearly PROC FREQ is less statistical than PROC REG, yet both are analytical in nature. A report is output that lists detailed or summarized data, either as a listing or multi-field comparison, called cross-tabulation. It must show actual data points, not just our conclusions about some data, even if the data points are sununarized data rather than detailed. Cross-tabulation should be included, since it also displays detailed information. Most businesses do not use the refined statistics to test and compare factors affecting their business, like the variance procedures. Business analysts are prone to more basic and obvious comparisons of data, so cross-tabulation is a more common feature in business analysis. ln essence, a report either lists values or compares two or more lists of data values. Lets look at several SAS procedures, over time, as they have evolved since the early stages, and measure them, not by what they accomplish, but by what affects their use, and rate them on these "Report Writer'' dimensions. Here are three dimensions we can use to rate SAS Procedures as Report Writers. 1. A procedure is either algorithmic or textual. Different people prefer one type or the other. People with statistical or heavy third GL backgrounds often prefer very concise, algebraic languages, terse with short names. SAS overall is wordy, like early BASIC, as seen in the logic and controls of a data step, while still retaining the algebraic logic of FORTRAN and PLl, the languages SAS was first written in. Fourth GL' s are usually more wordy than third GL's. SAS has tried to be both. 2. A procedure is either compact and standardized or modular and flexible. Most SAS procedures are standardized packages of code that users never see but will produce consistent preformatted output, as long as the design covers all possible options. Users are constrained by the available options but also aided by simple designs that can produce complicated results. Sometimes users want more flexibility for very customized output, but most procedures follow standard approaches for ease of use. The need for flexibility leads to modular designs that offer more but are harder to master. 529 3. A procedure may be limited in scope or very comprehensive. Most SAS procedures are limited. SAS is written to be a collection of data steps and Procedures, each completing more limited tasks. Over time, SAS has become more comprehensive, becoming more 4th GL with longer more complicated procedures that do more for you. You may or may not include various optional statements that make a report more complex, but you can opt for the very simple and minimal statements. A comprehensive procedure forces users to provide more detailed coding. with a higher learning curve, but allows more features and controls. SAS has always provided both types of procedures. In fact, SAS provides all kinds of methods to complete a report, and we shall find procedures that represent all combinations on these dimensions. It is up to tne user, not the product, to pick what works best for them. There is almost always more than one procedure and more than one method to generate any report. Let's now look at some of those methods used by SAS programmers over the years. T~e Early Years: Using PRINT and NULL Data steps The first attempt to use SAS for generating reports was found in PROC PRINT. This very basic procedure was found in the earliest versions of SAS and was probably the most used. PRINT is essentially a "dump" of raw data points. Each row of the output is a single record or observation in the data. Each field or variable is put on the paper output as a single column. PRINT takes care of several features needed. PRINT provides automated spacing between the columns, labeling variables that become column headings, observation counts, double spacing, enough room to handle wide field values, D and BY statements provide report breaks and subtotals and SUM provides subtotals (with BY) and totals. PAGEBY and SUMBY were added later to allow control over page breaks and specifying which BY variables are used for subtotals. The key was simplicity. PRINT is textual, very standard and limited You simply specify the fields you want listed, in order, on a VAR statement. SAS takes care of the formatting of columns on the paper, and adjusts for pages with wider values. You can standardize column widths for the entire report using UNIFORM. PRINT is comprehensive, even using minimal code, as long as you stay with a simple need to dump the detailed records and fields of a dataset. For example, just: PROCPRINT; Will provide almost entirely what you need. Without any other statement, SAS defaults to dumping the last used dataset, all fields, in the order in which they appear in the dataset. If there are too many fields to fit on a page, SAS automatically "wraps" records, so that you get to see something like a multi-panel spreadsheet. PRINT is so useful as a debugging tool, that it is essential to writing even the most complicated SAS application. It is, on our dimensions, a comprehensive standardized textual procedure. Easy to use, it has filled so many needs it has become the procedure most taken for granted. It is closest to what most analysts are already familiar with, EXCEL and LOTUS. Because PRINT was so standardized, it did not meet many specialized needs. Very often we needed to create a more customized report. There were ways to accomplish this, using PRINT, mostly by preparing other records for the report BEFORE running PRINT. For example, if we wanted "Mean's" on the subtotal lines instead of "Summations," we: 1. Ran PROC SUMMARY first to create subtotal records with Mean values; 2. Marked the new subtotal records with special keys to make them sort correctly when we: 3. Merged the subtotal and original records together. 4. Printed the resulting file, without any SUM statement, since the subtotals already exist. 530 This method took time, and made the programming more complicated, since we've added a SUMMARY procedure to create the subtotal records and a DATA step to merge them back in with the original detail records. False keys have to be invented just so we can sort each subtotal line after the detail lines it belongs to. In sum, PRINT could not be both simple and customizable. Whenever the users requested a more precise layout, we turned to a procedure that was the opposite on all dimensions: Using NULL data steps to generate customized reports. Report Writing a Ia Carte Report Writing is often so complex, with such specialized needs, that SAS had a manual dedicated to using data step processing to produce a custom report. Using a combination of BY statements to keep track of the current record and some sophisticated features of PUT, such as the cursor's specific line number and column on the output page, it was possible to do almost anything COBOOL or EASYTRIEVE could produce. The technique is well described in the SAS Applications Programming manual. This technique treats DATA steps as blocks of output paper. You control directly which record you are reading, and the way in which data is placed on the paper. Like in the days when COBOL was king, this technique allows infinite options and direct control of where each value is placed on the output device.
Recommended publications
  • Show Guideguide Web Searching for GIS Services and Web Mapping Have Been Either Published Or an Introduction Adopted by OGC
    showshow guideguide Web searching for GIS services and Web Mapping have been either published or An Introduction adopted by OGC. Who are OGC’s members? to OpenGIS There are three main levels of OGC membership: Principal, Technical and By Adam Gawne-Cain and Chris Holcroft Associate. The higher membership levels confer more voting rights. There are now OpenGIS is the activity pursued by the Open GIS over 300 members featuring 20 Principal members and 25 Technical members from Consortium (OGC). OpenGIS seeks to achieve around the globe. transparent access to disparate geo-data and geo- The membership of OGC is impressively processing resources in a networked environment by broad. Most major GIS companies are members, along with database companies, providing a rich suite of open interface specifications. operating system companies, national mapping agencies, large government These interface specifications will enable GIS developers departments, universities and research to create inter-operable components that provide this institutes. The membership is international, but mainly focused in North transparency. America and Europe. The difference between OpenGIS and A second advantage of OGC’s interface- How does OGC make Interface previous attempts to standardise GIS is based approach is that users can be sure Specifications? that OGC agrees interfaces, and not that they are looking at genuine, live data, Every two months, the OGC Technical neutral file formats. The problem with and not at a static file generated some time Committee (TC) and Management neutral file formats (e.g. SDTS or NTF) in the past. Committee (MC) meet for a week. was that specifications grew so complex The meetings are held in different that each GIS could only support a sub-set A third, practical advantage of interfaces locations around the world, hosted by one of the format.
    [Show full text]
  • Cityjson: a Compact and Easy-To-Use Encoding of the Citygml Data Model
    CityJSON: A compact and easy-to-use encoding of the CityGML data model Hugo Ledoux Ken Arroyo Ohori Kavisha Kumar Balazs´ Dukai Anna Labetski Stelios Vitalis This is the author’s version of the work. It is posted here only for personal use, not for redistribution and not for commercial use. The definitive version will be published in the journal Open Geospatial Data, Software and Standards soon. H. Ledoux, K. Arroyo Ohori, K. Kumar, B. Dukai, A. Labetski, and S. Vitalis (2018). CityJ- SON: A compact and easy-to-use encoding of the CityGML data model. Open Geospatial Data, Software and Standards, In Press. DOI: http://dx.doi.org/10.1186/s40965-019-0064-0 Full details of the project: https://cityjson.org The international standard CityGML is both a data model and an exchange for- mat to store digital 3D models of cities. While the data model is used by several cities, companies, and governments, in this paper we argue that its XML-based ex- change format has several drawbacks. These drawbacks mean that it is difficult for developers to implement parsers for CityGML, and that practitioners have, as a con- sequence, to convert their data to other formats if they want to exchange them with others. We present CityJSON, a new JSON-based exchange format for the CityGML data model (version 2.0.0). CityJSON was designed with programmers in mind, so that software and APIs supporting it can be quickly built. It was also designed to be compact (a compression factor of around six with real-world datasets), and to be friendly for web and mobile development.
    [Show full text]
  • Understanding and Working with the OGC Geopackage Keith Ryden Lance Shipman Introduction
    Understanding and Working with the OGC Geopackage Keith Ryden Lance Shipman Introduction - Introduction to Simple Features - What is the GeoPackage? - Esri Support - Looking ahead… Geographic Things 3 Why add spatial data to a database? • The premise: - People want to manage spatial data in association with their standard business data. - Spatial data is simply another “property” of a business object. • The approach: - Utilize the existing SQL data access model. - Define a simple geometry object. - Define well known representations for passing structured data between systems. - Define a simple metadata schema so applications can find the spatial data. - Integrate support for spatial data types with commercial RDBMS software. Simple Feature Model 10 area1 yellow Feature Table 11 area2 green 12 area3 Blue Feature 13 area4 red Geometry Feature Attribute • Feature Tables contain rows (features) sharing common properties (Feature Attributes). • Geometry is a Feature Attribute. Database Simple Feature access Query Connection model based on SQL Cursor Value Geometry Type 1 Type 2 Spatial Geometry (e.g. string) (e.g. number) Reference Data Access Point Line Area Simple Feature Geometry Geometry SpatialRefSys Point Curve Surface GeomCollection LineString Polygon MultiSurface MultiPoint MultiCurve Non-Instantiable Instantiable MultiPolygon MultiLineString Some of the Major Standards Involved • ISO 19125, Geographic Information - Simple feature access - Part 1: common architecture - Part 2: SQL Option • ISO 13249-3, Information technology — Database
    [Show full text]
  • Integration of Statistical and Geospatial Information: Metadata Standards and More United Nations Global Forum on Integration of Geospatial-Statistics 4-5 August 2014
    ® Integration of Statistical and Geospatial Information: Metadata Standards and More United Nations Global Forum on Integration of Geospatial-Statistics 4-5 August 2014 Mark E. Reichardt President and CEO, Open Geospatial Consortium [email protected] Copyright © 2014 Open Geospatial Consortium Geospatial Information: Essential to Address Social, Environmental & Economic Issues Logistics & Education & Research Transport Sustainable Development Utilities Health E -Government Emergency and Disaster Mgt / Response Energy Consumer Services Geosciences OGC® Geospatial information via Spatial Data Infrastructures is widely utilized throughout government… …to support broad national objectives such as economic growth, social cohesion and well-being, and environmental management ® Source: GeoConnections Canada OGC 4 The Open Geospatial Consortium Not-for-profit, international voluntary consensus standards organization; leading development of geospatial standards • 20th Anniversary • 470+ members worldwide • Over 40 standards and best University practices 24% Commercial • Hundreds of product 41% implementations Research 7% • Broad user community NGO implementation worldwide 10% Government • Alliances and collaborative activities 18% with many other organizations ® OGC © 2014 Open Geospatial Consortium Metadata • Data about Data “…provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data.” US Federal Geographic Data Committee
    [Show full text]
  • Representing and Reasoning About Changing Spatial Extensions of Geographic Features
    Representing and Reasoning about Changing Spatial Extensions of Geographic Features by Claudio Elizio Calazans Campelo Submitted in accordance with the requirements for the degree of Doctor of Philosophy The University of Leeds School of Computing July 2013 The candidate confirms that the work submitted is his/her own, except where work which has formed part of jointly authored publications has been included. The contri- bution of the candidate and the other authors to this work has been explicitly indicated below. The candidate confirms that appropriate credit has been given within the thesis where reference has been made to the work of others. Some parts of the work presented in this thesis have been published in the following articles. In each case, details are given on the contributions by the other authors and me, as well as details about the chapters which these articles were used within are mentioned. Campelo, C. E. C., Bennett, B. “Representing and Reasoning about Changing Spatial Exten- sions of Geographic Features.”, Proceedings of the Conference on Spatial Information Theory (COSIT 2013), edited by T. Tenbrink, J. Stell and Z. Wood, LNCS 8116, pp. 3352, Springer International Publishing, 2013. My contributions: Principal author, wrote all sections. Implemented the system proto- type. Other author contributions: Overall wording of the paper; discussion on the develop- ment of the formalism. Chapters based upon work: Chapter 4 refers to the logical framework for representing events and processes. Chapter 5 presents the system prototype. Campelo, C. E. C., Bennett, B. “Towards a Comprehensive Framework for Representing and Reasoning about Geographic Phenomena.”, Proceedings of International Workshop: Spatio-temporal Theories and Research for Environmental, Urban and Social Sciences: Where Do We Stand?, held in conjunction with the Conference on Spatial Information Theory (COSIT 2013).
    [Show full text]
  • Map Description and Management by Spatial Metadata: Requirements for Digital Map Legend for Planetary Geological and Geomorphological Mapping
    MAP DESCRIPTION AND MANAGEMENT BY SPATIAL METADATA: REQUIREMENTS FOR DIGITAL MAP LEGEND FOR PLANETARY GEOLOGICAL AND GEOMORPHOLOGICAL MAPPING A. Nass (1,2), S. van Gasselt (3) and R. Jaumann (1,3) (1) Inst. of Planetary Research, German Aerospace Center (DLR), Rutherfordstr. 2, 12489 Berlin (2) Geoinformation Science Research Group, Dept. of Geography, University of Potsdam, Karl-Liebknecht-Str. 24-25, 14476 Potsdam (3) Planetary Sciences and Remote Sensing, Inst. of Geological Sciences, Freie Universit¨at Berlin, Malteserstr. 74-100, 12249 Berlin Contact: [email protected]. KEY WORDS: Planetary Mapping, Metadata, GIS, Database Model ABSTRACT: Instruments carried along on missions to, e.g., Mars, the Moon, Venus, and various Outer-Solar System objects, produce a rich variety of image data recorded in different wavelengths and some of them allow to derive additional datasets (e.g., digital terrain models). These data form the basis for geologically exploring the evolution of planetary bodies by analyzing and geoscientifically interpreting surface structures. By using modern GIS techniques the results are represented in thematic, mostly geological and geomorphological maps and allow to extract additional information, e.g. by means of morphometric measurements. To allow for an efficient collaboration among various scientists and groups, all mapping results have to be uniformly prepared, described, managed and archived. In order to achieve this, GIS-based mapping approaches are currently underway. One of the important aspects in this context is a detailed map description and an efficient management of mapping results by using metadata information. Such data describe, e.g. the geometry, extent, quality, contents and conditions of source data and additionally allow detailed queries for context information.
    [Show full text]
  • Arxiv:2006.16900V1 [Cs.CY] 26 Jun 2020 Resenting Moving Features As Well As Standardized Operations for Manipulating Moving Geometries
    From Simple Features to Moving Features and Beyond? Anita Graser Esteban Zimanyi´ Krishna Chaitanya Bommakanti AIT Austrian Institute of Technology Universite´ libre de Bruxelles Adonmo University of Salzburg Brussels, Belgium HITEC City, Hyderabad, Vienna / Salzburg, Austria ORCID: 0000-0003-1843-5099 Telangana 500081, India ORCID: 0000-0001-5361-2885 Abstract—Mobility data science lacks common data structures Spatial plane and analytical functions. This position paper assesses the current status and open issues towards a universal API for mobility A data science. In particular, we look at standardization efforts revolving around the OGC Moving Features standard which, so far, has not attracted much attention within the mobility data time science community. We discuss the hurdles any universal API B for movement data has to overcome and propose key steps of a roadmap that would provide the foundation for the development of this API. t= 0 t= 1 t= 2 2011-07-14 22:00:00 2011-07-14 22:00:10 2011-07-14 22:00:20 I. INTRODUCTION Fig. 1: Data model of the Moving Features standard illustrated with two moving points A and B. Stars mark changes in Data analysis tools are essential for data science. Robust attribute values. movement data analysis tools are therefore key to advancing mobility data science. However, the development of movement data analysis tools is hampered by a lack of shared understand- API for mobility data science -– if such a thing exists. Based ing and standardization. There are numerous implementations, on these findings, we then propose essential building blocks including dozens of R libraries, as well as Python libraries to advance movement data science.
    [Show full text]
  • Open GIS Consortium, Inc. Opengis Simple Features Test Protocol For
    Open GIS Consortium, Inc. OpenGISÒ Simple Features Test Protocol For OLE/COM 99-037r2 Release Date: August 6, 1999 Conformance Test Guidelines for OpenGIS Simple Features Specification for OLE/COM 99-037r2 Copyright 1999 Cadcorp Ltd Copyright 1999 Intergraph Corporation The companies listed above have granted the Open GIS Consortium, Inc. (OGC) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright, in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification. NOTICE The information contained in this document is subject to change without notice. The material in this document details an Open GIS Consortium specification in accordance with the license and notices set forth on this page. This document does not represent a commitment to implement any portion of this specification in any company’s products. WHILE THE INFORMATION IN THIS PUBLICATION IS BELIEVED TO BE ACCURATE, THE OPEN GIS CONSORTIUM AND THE COMPANIES LISTED ABOVE MAKE NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. The Open GIS Consortium and the companies list above shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this material.
    [Show full text]
  • Microsoft SQL Server/Print Version - Wikibooks, Open Books for an Op
    Microsoft SQL Server/Print version - Wikibooks, open books for an op... https://en.wikibooks.org/w/index.php?title=Microsoft_SQL_Server/Pri... Microsoft SQL Server/Print version Contents 1 System Requirements 1.1 32-bit editions of SQL Server 2005 1.1.1 Enterprise 1.1.2 Standard 1.1.3 Workgroups 1.1.4 Express 1.1.5 Developer 1.1.6 Memory Requirements 1.1.7 Harddisk requirement 1.1.8 Internet 1.2 64-bit editions of SQL Server 2005 1.2.1 Processor 1.3 References 2 Installing 2.1 Understanding SQL Server 2005 Editions 2.1.1 Enterprise Edition 2.1.2 Standard Edition 2.1.3 Workgroup Edition 2.1.4 Developer Edition 2.1.5 Express Edition 2.2 Some hints to remember Features 2.3 How to Install MS SQL Server 2005-2012 2.4 Graphical interface 2.5 References 3 Connecting to MS SQL Server from *nix 3.1 Downloading 3.2 Glossary 3.3 Troubleshooting 3.3.1 Failing to set SYBASE 3.4 External Links 3.5 References 4 Using Instances 4.1 Determining Multiple or Single Instances 5 Installing Instances 5.1 Authentication mode 5.2 Determining Collation Setting 6 Configuring Files 6.1 Data Files 6.2 Log Files 6.3 Filegroups 6.4 Configuring Raid Systems 6.5 Best practices 7 Configuring Mail 1 sur 36 10/01/2016 15:11 Microsoft SQL Server/Print version - Wikibooks, open books for an op... https://en.wikibooks.org/w/index.php?title=Microsoft_SQL_Server/Pri... 7.1 Architecture 7.2 References 8 System databases 8.1 Introduction 8.1.1 Resource [1] 8.1.2 master [2] 8.1.3 tempdb [3] 8.1.4 model [4] 8.1.5 msdb [5] 8.2 Usage 8.3 Summary 8.4 References 9 Table manipulation
    [Show full text]
  • OGC Simple Features For
    PostGIS: A Standards Based Geographic Extension for PostgreSQL Frank Warmerdam President, OSGeo 1 Overview • Brief background • PostGIS Details • PostGIS Examples • Survey of Simple Features 1.1 Geometries • Simple Features 1.2 Geometry • A survey of simple features based software • Commentary 2 Open Source Geospatial Foundation What is a Spatial Database? • Support for a “Geometry” Type • Indexing for the Geometry Type • Functions for the Geometry Type • Database that can answer GIS questions: quickly on large volumes of data 3 Open Source Geospatial Foundation Why a Spatial Database? (instead of just using files) • Transactional Integrity Multiple Users, Multiple Edits • Unified Storage, Management, Access SQL Everywhere • Because Databases are Better than Files NOT! 4 Open Source Geospatial Foundation Unified Storage GIS Database Guys Guys Corporate GIS Database Files 5 PostGIS • Geographic Extension for PostgreSQL • Based on OGC Simple Features for SQL • By Refractions Research (Victoria,BC) • First release in 2001 • GPL licensed (likely why not in main src tree) • R- Tree- over- GiST used for spatial index • Introduces: new geometry types many new functions new support tables http:/ / www.postgis.org 6 Open Source Geospatial Foundation Some Geometry Functions • Area(POLYGON) • Distance(GEOMETRY,GEOMETRY) • Contains(GEOMETRY,GEOMETRY) • Intersection(GEOMETRY,GEOMETRY) • Intersects(GEOMETRY,GEOMETRY) • Union(GEOMETRY,GEOMETRY) • Buffer(GEOMETRY,double) • ConvexHull(GEOMETRY) • Perimeter(GEOMETRY) • Crosses(GEOMETRY,GEOMETRY) • Transform(GEOMETRY,integerSRID)
    [Show full text]
  • The Space Package: Tight Integration Between Space and Semantics
    Transactions in GIS, 2010, 14(2): 131–146 Research Articletgis_1187 131..146 The Space Package: Tight Integration between Space and Semantics Willem Robert van Hage Jan Wielemaker Department of Computer Science Department of Computer Science Vrije Universiteit Amsterdam Vrije Universiteit Amsterdam Guus Schreiber Department of Computer Science Vrije Universiteit Amsterdam Abstract Interpretation of spatial features often requires combined reasoning over geometry and semantics. We introduce the Space package, an open source SWI-Prolog exten- sion that provides spatial indexing capabilities. Together with the existing semantic web reasoning capabilities of SWI-Prolog, this allows efficient integration of spatial and semantic queries and provides an infrastructure for declarative programming with space and semantics. There are few systems that provide indexing and reason- ing facilities for both spatial and semantic data. A common solution is to combine separate semantic reasoning and geospatial services. Such loose coupling has the disadvantage that each service cannot make use of the statistics of the other. This makes optimization of such a service-oriented architecture hard. The SWI-Prolog Space and Semantic web packages provide a native Prolog interface to both spatial and semantic indexing and reasoning, which makes it easy to write combined query optimizers. Another advantage of the Space package is that it allows declarative logic programming, which means in practice that you say what you want to compute instead of how to compute it. The actual indexing machinery is encapsulated inside Prolog predicates. In this article we describe the interface of the Space package, compare its functionality to alternative software libraries, and show how to work with it using three example applications.
    [Show full text]
  • Working with Geodatabases Using SQL and Python Jochen Manegold Gerhard Trichtl Geodatabase Geodatabase – What Is This?
    Working with Geodatabases Using SQL and Python Jochen Manegold Gerhard Trichtl Geodatabase Geodatabase – What is this? • A physical store of geographic data - Scalable storage model supported on different platforms • Core ArcGIS information model - A comprehensive model for representing and managing GIS data - Implemented as a series of simple tables • A transactional model for managing GIS workflows • Set of components for accessing data Tables in Geodatabase - Geodatabase system tables • System tables store definitions, rules, and behavior for datasets • Tracks contents within a geodatabase • Stores some database level metadata - Versions, domains, etc. • Admin operations: - Version management - Connection management - Geodatabase upgrade Tables in Geodatabase - User defined Tables • Stores the content of each dataset in the geodatabase - Datasets are stored in one or more tables • Administrative Operations: - Granting/revoking privileges - Updating statistics/indexes - Registering as versioned - Adding global id’s - Enabling editor tracking Accessing data in a DBMS • You can access spatial or non-spatial data in a DBMS to use in ArcGIS Geodatabase Database – Simple Feature Access DB2 ALTIBASE (deprecated) Informix Dameng ORACLE Teradata PostgreSQL Netezza (deprecated) Microsoft SQLServer DB2, Informix SAP HANA ORACLE, PostgreSQL Microsoft SQLServer, SAP HANA Working with Geodatabases using Python or how you create your own Geodatabase by Jochen Manegold The Scenario • I am the database administrator in our office • I want to create a Geodatabase with featureclass and data • Simon should be the data-owner – responsable for maintenance and data quality • Clare and Richie are responsible to capture the data • They want to edit the data in an isolated editor environment (Versioning) • As this happens in many different ways, I want to automate the setup of this scenario The Scenario – a database, users, a table, data and a version tree sde.Default protected simon.simon public private clare.clare richie.richie private The Tools • Database Server (f.e.
    [Show full text]