Working with Geodatabases Using SQL and Python Jochen Manegold Gerhard Trichtl Geodatabase Geodatabase – What Is This?
Total Page:16
File Type:pdf, Size:1020Kb
Load more
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. -
Chapter 2: the Arcgis Server Architecture
The ArcGIS Server 2 architecture ArcGIS Server is an object server for ArcObjects. The ArcGIS Server software system is distributed across multiple machines. Each aspect of ArcGIS Server plays a role in managing GIS functionality and data and making that functionality useful to end users. This chapter provides an overview of the ArcGIS software architecture and details of the ArcGIS Server architecture, specifically the various aspects of the server and how they interact, including: • the role of the GIS server • the server object manager • server object containers • GIS server objects • the Web application server Chapter2.pmd 27 10/12/2004, 4:01 PM ARCGIS SOFTWARE ARCHITECTURE Before discussing the details of the ArcGIS Server architecture, it’s important to discuss the ArcGIS system architecture as a whole. The ArcGIS architecture has evolved over several releases of the technology to be a modular, scalable, cross- platform architecture implemented by a set of software components called ArcObjects. This section focuses on the main themes of this evolution at ArcGIS 9 and introduces the reader to the libraries that compose the ArcGIS system. The ArcGIS software architecture supports a number of products, each with its unique set of requirements. ArcObjects components, which make up ArcGIS, are designed and built to support this. This chapter introduces ArcObjects. ArcObjects is a set of platform-independent software components, written in C++, that provides services to support GIS applications on the desktop in the form of thick and thin clients and on the server. For a detailed explanation of COM see the As stated, the language chosen to develop ArcObjects was C++; in addition to Microsoft COM section of Appendix D, this language, ArcObjects makes use of the Microsoft Component Object Model. -
Arcsde Microsoft SQL Server Database Requirements
ArcSDE Microsoft SQL Server Database Requirements Supported Database Versions Supported Operating Systems Operating System Limitations Supported Database Versions Standard/Enterprise Editions: Microsoft SQL Server 2000 SP4 (32-bit) Microsoft SQL Server 2005 SP2 & SP3 (32-bit & 64-bit) Microsoft SQL Server 2008 Final - R2 (32-bit & 64-bit) Express Editions: Microsoft SQL Server 2005 SP2 & SP3 (32-bit) Microsoft SQL Server 2008 Final - R2 (32-bit) Supported Operating Systems Database Supported Operating System(s) Windows 2003 SP2 (32-bit) Server Standard, Enterprise & Microsoft SQL Server Datacenter 2000 (32-bit) Windows 2008 SP2 (32-bit) Server Standard, Enterprise & Datacenter Windows 2003 SP2 (32-bit) Server Standard, Enterprise & Microsoft SQL Server 2005 Datacenter (32-bit) Windows 2008 SP2 (32-bit) Server Standard, Enterprise & Datacenter Windows 2003 SP2 (64-bit - EM64T) Server Standard, Enterprise Microsoft SQL Server 2005 & Datacenter (64-bit) Windows 2008 Final - R2+ (64-bit - EM64T) Server Standard, Enterprise & Datacenter Windows 2003 SP2 (32-bit) Server Standard, Enterprise & Microsoft SQL Server 2008 Datacenter (32-bit) * Windows 2008 SP2 (32-bit) Server Standard, Enterprise & Datacenter Windows 2003 SP2 (64-bit - EM64T) Server Standard, Enterprise Microsoft SQL Server 2008 & Datacenter (64-bit) * Windows 2008 Final - R2+ (64-bit - EM64T) Server Standard, Enterprise & Datacenter Limitations SQL Server 2008 * SQL Server 2008 Spatial Types (Geography and Geometry) are supported with 9.3 SP1, binary supported at 9.3 Final. Windows 7, Vista and XP Windows 7, Vista Sp2, and XP Sp3 are supported for basic testing and application development use only. They are not recommended for deployment in a production environment. Windows XP only supports the Developer Edition of SQL Server. -
GIS Migration Plan
Dane County Land Information Office July 2003 Dane County Enterprise GIS Migration Plan The Dane County Land Information Office is committed to the development of GIS technology to aid in the delivery of information and services to county departments, communities, and the residents of our county. As part of our ongoing efforts to develop a robust and efficient GIS infrastructure, the Land Information Office has begun a project to migrate to a next generation geographic information system. Workplan activities include an upgrade of the technical infrastructure (hardware and software), implementation of new ESRI GIS products, a review and re-modeling of enterprise GIS datasets, workflow analysis and process changes to maximize service delivery and staff efficiencies. This plan summarizes migration activities to-date, as well as outlining a workplan to complete the remaining tasks. ESRI's next generation product line revolves around three primary products: ArcGIS, ArcSDE and ArcIMS. ArcGIS and its related extensions and modules comprise the desktop GIS software suite. ArcSDE supports spatial and tabular database integration. ArcIMS supports the delivery of web-based geographic information and map services. The Dane County ArcGIS migration project includes converting current ArcInfo users to the ArcGIS product. The longer term goal will be to move the viewing, printing, and basic GIS operation users to ArcIMS applications that can be run from a browser or thin client. Current ArcView 3.2 users will be migrated to either thin client ArcIMS applications or ArcGIS 8.x software. All applications will utilize geographic information stored in ArcSDE. Training requirements will be focused on technical staff to build and maintain applications with user friendly tools to minimize intense end user training. -
Georover® Flexrt Software Extension
GeoRover® FlexRT Software Extension MISSION PLANNING TO GIS – DATA INTEROPERABILITY FOR THE ANALYST The GeoRover FlexRT extension provides the capability to import and export critical data between the commercial Esri® ArcGIS® for Desktop and the FalconView™ applications with the ability to maintain consistent data symbology. The extension is a plug-in to the Esri ArcGIS Desktop application (Basic, Standard, Advanced). The toolbar provides interoperability tools for converting data between common FalconView formats such as Local Point and Draw files and common GIS formats such as shapefiles and feature classes (personal, file, enterprise ArcSDE®). The toolbar also provides the option to apply FalconView Local Point symbology to point layers in the ArcMap™ application. The FlexRT extension allows for quick, user-friendly import and export wizards to simplify data exchange between platforms allowing users to share and disseminate data easily. FEATURES Import FalconView Local Point or Draw fi les into new shapefi les or existing feature layers (shapefi le and personal, fi le, and enterprise ArcSDE® feature classes) Export shapefi les or feature classes from ArcGIS Desktop to FalconView as Local Point or Draw fi les Apply and maintain Local Point symbology for point feature layers in ArcMap Match imported attribute fi elds with existing attribute fi elds to Copyright © 2009 AEX. Source: ArcGIS Online Apply FalconView™ Local Point minimize redundancy in data symbology to any point feature layer in Search directory for custom FalconView stylesheet -
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. -
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 -
Data Sharing and Spatial Query Technical Memorandum
Technical Memorandum No. 2 DATA SHARING AND SPATIAL QUERY Raghavan Srinivasan Spatial Sciences Laboratory Texas Agricultural Experiment Station, Texas A&M University Submitted to El Paso Water Utilities Through Paso del Norte Watershed Council February 2005 Table of Contents Summary............................................................................................................................. 2 Data Transfer and Sharing .................................................................................................. 2 FTP.................................................................................................................................. 2 HTTP............................................................................................................................... 3 Difference between FTP and HTTP ............................................................................... 3 GNU WGET ................................................................................................................... 3 ArcIMS and DDE ........................................................................................................... 4 Spatial Query ...................................................................................................................... 5 Discussion and Recommendations ..................................................................................... 6 Glossary of Terms Used...................................................................................................... 6 1 Technical -
Introduction to Arcview GIS 3.X
Introduction to ArcView GIS 3.x School of Agriculture and Natural Resources An Introduction to ArcView® GIS Developed By Dr. Walid H. Shayya Table of Contents About GIS About ArcView® GIS Version 3.x Getting Started with ArcView® GIS Version 3.x Projects Views and Themes Types of Themes Tables Charts Scripts Making Simple Thematic Maps Using ArcView® GIS Version 3.x Adding Themes to a View Moving Around in a View Redefining a Theme Projections Working with Theme Attributes Working with Tables Labeling Features in Views http://people.morrisville.edu/~shayyaw/ArcView/IntroArcView.htm (1 of 36)12/19/2006 11:09:07 PM Introduction to ArcView GIS 3.x Adding One's Own Features Layouts Concluding Remarks About GIS A geographic information system (GIS) is a system of computer software, hardware, data, and personnel to help manipulate, analyze, and present information (visualization of data analysis) that is tied to a spatial (geographic) location. In other words, GIS is a computerized data management system designed to store, manipulate, update, and output geographically- referenced spatial data. In addition to producing basic maps (quickly, accurately, and update-to-date), GIS software nowadays are capable of performing basic to advanced analysis, varying from measuring distances, perimeters, and areas to dealing with proximity, connectivity, and containment as well as networking, buffering (flood zones, address notification), line of site (slope), and spatial analysis. Thus, GIS is capable of numerous tasks including (but not limited) to the following: ● Input and update spatial and attribute (e.g., plot owner) data. ● Combine data from different sources. ● Link spatial data with attribute data. -
Understanding Arcsde®
Understanding ArcSDE® GIS by ESRI ™ Copyright © 1999, 20012002 ESRI All rights reserved Printed in the United States of America The information contained in this document is the exclusive property of ESRI This work is protected under United States copyright law and the copyright laws of the given countries of origin and applicable international laws, treaties, and/or conventions No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying or recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI All requests should be sent to Attention: Contracts Manager, ESRI, 380 New York Street, Redlands, CA 92373-8100, USA The information contained in this document is subject to change without notice US GOVERNMENT RESTRICTED/LIMITED RIGHTS Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement In no event shall the US Government acquire greater than RESTRICTED/LIMITED RIGHTS At a minimum, use, duplication, or disclosure by the US Government is subject to restrictions as set forth in FAR §52227-14 Alternates I, II, and III (JUN 1987); FAR §52227-19 (JUN 1987) and/or FAR §12211/12212 (Commercial Technical Data/Computer Software); and DFARS §252227-7015 (NOV 1995) (Technical Data) and/or DFARS §2277202 (Computer Software), as applicable Contractor/Manufacturer is ESRI, 380 New York Street, Redlands, CA 92373-8100, USA ESRI, SDE, ArcView, MapObjects, the ESRI globe logo, ArcInfo, -
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. -
Getting Started with Arcims Copyright © 2004 ESRI All Rights Reserved
Getting Started With ArcIMS Copyright © 2004 ESRI All Rights Reserved. Printed in the United States of America. The information contained in this document is the exclusive property of ESRI. This work is protected under United States copyright law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying or recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI. All requests should be sent to Attention: Contracts Manager, ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. The information contained in this document is subject to change without notice. U. S. GOVERNMENT RESTRICTED/LIMITED RIGHTS Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. In no event shall the U.S. Government acquire greater than RESTRICTED/LIMITED RIGHTS. At a minimum, use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR §52.227-14 Alternates I, II, and III (JUN 1987); FAR §52.227-19 (JUN 1987) and/ or FAR §12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (NOV 1995) (Technical Data) and/or DFARS §227.7202 (Computer Software), as applicable. Contractor/Manufacturer is ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. ESRI, ArcExplorer, ArcGIS, ArcPad, ArcIMS, ArcMap, ArcSDE, Geography Network, the ArcGIS logo, the ESRI globe logo, www.esri.com, GIS by ESRI, and ArcCatalog are trademarks, registered trademarks, or service marks of ESRI in the United States, the European Community, or certain other jurisdictions.