DOCSLIB.ORG

Maa-123.2441 GIS Software Development 4 Op 4 Op Data And

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Maa-123.2441 GIS Software Development 4 Op 4 Op Data And Maa-123.2441 GIS Software Development 4 op Data and databases 10/27/2013 Jari Reini GIS – in 4 categories •Categories based on competences – Data collection and management – Spatial data analysis – Software development – GIS Solutions • Today concentrating on data collection, management and analysis (and partly SW development) Jari Reini 10/27/2013 Architectural choices in GIS (simplified) Desktop Client-Server Internet Application Server Database Jari Reini Database 10/27/2013 Principles •Re-use, Keep it simple •Use COTS as much as possible –Less in-house development –Less maintenance –Already includes a lot of required functionality •For example –Storage: Oracle Spatial database –Editing: ESRI ArcGIS –Quality checking: Radius, JavaML, JTS –Product Creation: FME and own tools 10/27/2013 Architecture and flow Data Sourcing Editing Conversion Products Public Comm upload Delivery unity Database Server Other Rule engine Quality Pre-filter checks Specs Jari Reini 10/27/2013 Content types •Maps (2D) •Voice-Enabled Maps •Address Points •Points of Interest •City Guides •Landmarks •3D maps Jari Reini 10/27/2013 Content gategories •Business content Guide –Office locations, factories, stores … -Voice Maps –Environmental data -Speed Cameras –Etc -Traffic •Find -Logistics –POIs Display –Address Points -2D/3D City Maps –Locality Index -3D Landmarks -3D Terrain Model Jari Reini 10/27/2013 Tele Atlas:Mobile Mapping Vans •Faster data collection •Superior accuracy •Advanced image collection for richer, more accurate content –Renders texture to buildings –Provides back up system for reported issues 10/27/2013 Databases •PostgreSQL/PostGIS •Oracle Spatial •SQL Server / ArcSDE •Etc •Note: in exercises we're using only files (due to some IT issues), think OrbisGIS as a database Jari Reini 10/27/2013 Concepts •relational database management system (RDBMS) •a system for managing data stored in relations –relation is essentially a term for table –Table has a collection of rows –Row has a set of columns –Tables are grouped into databases •A more modern development is the object-oriented database Jari Reini 10/27/2013 Example •CREATE TABLE cities ( –name varchar(80), –Int temperature –location point –); •INSERT INTO cities VALUES ( –‘Helsinki', –-10, –'(60.16, 24.94)‘ –); •SELECT * from cities; •UPDATE cities set temperature=3 where name=‘Helsinki’; Jari Reini 10/27/2013 Spatial SQL • the need for spatial query formalism has been clearly identified by and answered in – Spatial SQL (Max J. Egenhofer, 1994), ● geoPOM (Nittel and al., 1997), ● GeoSQL (Wang and al., 2000)... • SQL spatial has been standardized : – SQLMM : ISO/IEC 13249l – Simple Features Specification for SQL, OGC • efficient implementations that spatially enabled RDBMS (PostgreSQL/PostGIS, Oracle Spatial, SQLite-spatial...). Jari Reini 10/27/2013 OrbisGIS SQL • Portable spatial processor. No RDMS needed • Deals with several formats • Generic datasource model • Multisources language : – able to deal with geometries, raster, TIN and Remote data (WFS, WCS). – Match SQL and OGC standards – Great extensibility and customization ability. Jari Reini 10/27/2013 Put screenshots from spatiallanguage pdf Jari Reini 10/27/2013 Jari Reini 10/27/2013 Geometry functions in databases • Relationship – True or false • Processing – Gives you a new geometry • Measurement – Calculates something Jari Reini 10/27/2013 Geometry relationship functions •Distance(geometry, geometry) •Equals(geometry, geometry) Covers(geometry A, geometry B) •Disjoint(geometry, geometry) CoveredBy(geometry A, geometry B) •Intersects(geometry, geometry) Intersects(geometry, geometry) •Touches(geometry, geometry) Relate(geometry, geometry) •Crosses(geometry, geometry) •Within(geometry A, geometry B) •Overlaps(geometry, geometry) •Contains(geometry A, geometry B) Jari Reini 10/27/2013 Geometry processing functions •Centroid(geometry) •Area(geometry) •PointOnSurface(geometry) •Boundary(geometry) •Buffer(geometry, double, [integer]) •ConvexHull(geometry) •Intersection(geometry, geometry) •SymDifference(B,A). •Union(geometry, geometry) •Union(geometry set) 10/27/2013 Measurement functions •ST_Area(geometry) •ST_distance_sphere(point, point) •ST_distance_spheroid(point, point, spheroid) •ST_length2d(geometry) •ST_length3d(geometry) •ST_length_spheroid(geometry,spheroid) •ST_length3d_spheroid(geometry,spheroid) •ST_distance(geometry, geometry) •ST_max_distance(linestring,linestring) •ST_perimeter(geometry) •ST_perimeter2d(geometry) •ST_perimeter3d(geometry) •ST_azimuth(geometry, geometry) 10/27/2013 Server programming •Extending SQL •Triggers •PL/SQL 10/27/2013 GIS Objects •"Simple Features" defined by the OpenGIS Consortium (OGC) –OGC "Simple Features for SQL" specification. •Expression of spatial objects –Well -Known Text (WKT) –Well-Known Binary (WKB) •include a spatial referencing system identifier (SRID) 10/27/2013 Examples: WKT •POINT(0 0) •LINESTRING(0 0,1 1,1 2) •POLYGON((0 0,4 0,4 4,0 4,0 0),(1 1, 2 1, 2 2, 1 2,1 1)) •MULTIPOINT(0 0,1 2) •MULTILINESTRING((0 0,1 1,1 2),(2 3,3 2,5 4)) •MULTIPOLYGON(((0 0,4 0,4 4,0 4,0 0),(1 1,2 1,2 2,1 2,1 1)), (( -1 -1, -1 -2, - 2 -2,-2 -1,-1 -1))) •GEOMETRYCOLLECTION(POINT(2 3),LINESTRING((2 3,3 4))) •INSERT INTO geotable ( the_geom, the_name ) • VALUES ( GeomFromText('POINT(63.34 23.39)', 312), 'A Place'); 10/27/2013 SQL-MM Part 3 •SQL Multimedia Applications Spatial specification •extends the simple features for SQL spec by defining a number of circularly interpolated curves •SQL -MM used by many databases (e.g PostGIS, Oracle Spatial etc.) 10/27/2013 SQL-MM3 ST_Area ST_AsBinary ST_ExteriorRing ST_MPointFromText ST_SRID ST_GeometryN ST_MPointFromWKB ST_StartPoint ST_AsText ST_GeometryType ST_MPolyFromText ST_SymDifferenc ST_Boundary ST_GeomFromText ST_MPolyFromWKB e ST_Buffer ST_GeomFromWKB ST_NumGeometries ST_Touches ST_Transform ST_Centroid ST_InteriorRingN ST_NumInteriorRing ST_Intersection ST_NumPoints ST_Union ST_Contains ST_Intersects ST_OrderingEquals ST_Within ST_ConvexHull ST_IsClosed ST_Overlaps ST_WKBToSQL ST_CoordDim ST_IsEmpty ST_Perimeter ST_WKTToSQL ST_Crosses ST_IsRing ST_Point ST_X ST_Y ST_Difference ST_IsSimple ST_PointFromText ST_IsValid ST_PointFromWKB ST_Dimension ST_Length ST_PointN ST_Disjoint ST_LineFromText ST_PointOnSurface ST_Distance ST_LineFromWKB ST_PolyFromText ST_EndPoint ST_MLineFromText ST_PolyFromWKB ST_MLineFromWKB ST_Polygon ST_Envelope ST_Relate ST_Equals 10/27/2013 Loading/retrieving GIS data •Loading –Using SQL –Using the loader •Retrieving –Using SQL –Using dumper –Using e.g ODBC/JDBC 10/27/2013 Data Cities and countries Shape files 10/27/2013 Databases: PostGIS 10/27/2013 PostGIS data upload and use Create user 10/27/2013 PostGIS data upload and use Convert and upload shape files using shp2pgsql C:\Tools\PostgreSQL\8.3\bin>shp2pgsql.exe -c c:\temp\data-v1_1\countries.shp tkk.countries > countries.sql 10/27/2013 PostGIS data upload and use C:\Tools\PostgreSQL\8.3\bin>psql -U tkk -d postgis -f countries.sql 10/27/2013 10/27/2013 10/27/2013 PostGIS usage Using SQL INSERT INTO gtest (ID, NAME, GEOM) VALUES ( 1, 'First Geometry', GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1)); SELECT * FROM geotable WHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0); 10/27/2013 PostGIS from Java •Use JDBC •Class.forName("org.postgresql.Driver"); String url = "jdbc:postgresql://localhost:5432/database"; conn = DriverManager.getConnection(url, "postgres", ""); Statement s = conn.createStatement(); ResultSet r = s.executeQuery("select AsText(geom) as geom,id from geomtable") 10/27/2013 Oracle Spatial Spatial operators Network Management Geocoder Geo Raster Topology Spatial Data Mining 3D 10/27/2013 Geometric Types Polygon Point Line string Polygon with hole Self --crossing Self --crossing line strings polygons Valid Not valid 10/27/2013 Spatial Data Model Spatial layer Geometries Elements Point Line Polygon 10/27/2013 Elements •Basic building block of a geometry •Element types Element 6 –Point (1) Element 5 –Line (2) Element 4 –Polygon (3) Element 7 Element 2 •Constructed Element 1 using coordinates Element 3 •No limit on number of coordinates Hawaii , USA 10/27/2013 Geometry Geometry 1 Geometry 2 California Texas •Represents a spatial feature •Consists of an ordered set of primitive elements Geometry 3 Geometry 4 •Uniquely identified Florida Hawaii with a geometry identifier 10/27/2013 Layers •Consist of geometries that share a common set of attributes States layer 10/27/2013 Spatial Indexing •Provides an exclusive and exhaustive coverage of spatial objects •Indexes points, lines, and polygons •Fixed tiling or hybrid tiling 10/27/2013 Spatial Queries •Issued through SQL •Contains a locational constraint, for example: –Find all insurance holders in the projected path of a hurricane –Find all ATMs in my area 10/27/2013 Spatial Joins •A join of two layers based on the spatial component of the layers •Implemented using spatial index and spatial operators •Example: –Find all the wetlands within the national parks 10/27/2013 Java-based geometries 10/27/2013 Java Topology Suite (JTS) •The JTS Topology Suite is an API of 2D spatial predicates and functions •Based on Simple Features Specification for SQL (OGC) 10/27/2013 10/27/2013 Example •Geometry g1 = new WKTReader().read("LINESTRING (0 0, 10 10, 20 20)"); •Geometry buffer = g1.buffer(100.0); 10/27/2013 Javasacript in geometries 10/27/2013 Geoscript •http://www.geoscript.org •GeoScript adds spatial capabilities to dynamic scripting languages – JavaScript – Python – Scala – Groovy 10/27/2013.
Load more

Recommended publications
  • Development of an Extension of Geoserver for Handling 3D Spatial Data Hyung-Gyu Ryoo Pusan National University
    Free and Open Source Software for Geospatial (FOSS4G) Conference Proceedings Volume 17 Boston, USA Article 6 2017 Development of an extension of GeoServer for handling 3D spatial data Hyung-Gyu Ryoo Pusan National University Soojin Kim Pusan National University Joon-Seok Kim Pusan National University Ki-Joune Li Pusan National University Follow this and additional works at: https://scholarworks.umass.edu/foss4g Part of the Databases and Information Systems Commons Recommended Citation Ryoo, Hyung-Gyu; Kim, Soojin; Kim, Joon-Seok; and Li, Ki-Joune (2017) "Development of an extension of GeoServer for handling 3D spatial data," Free and Open Source Software for Geospatial (FOSS4G) Conference Proceedings: Vol. 17 , Article 6. DOI: https://doi.org/10.7275/R5ZK5DV5 Available at: https://scholarworks.umass.edu/foss4g/vol17/iss1/6 This Paper is brought to you for free and open access by ScholarWorks@UMass Amherst. It has been accepted for inclusion in Free and Open Source Software for Geospatial (FOSS4G) Conference Proceedings by an authorized editor of ScholarWorks@UMass Amherst. For more information, please contact [email protected]. Development of an extension of GeoServer for handling 3D spatial data Optional Cover Page Acknowledgements This research was supported by a grant (14NSIP-B080144-01) from National Land Space Information Research Program funded by Ministry of Land, Infrastructure and Transport of Korean government and BK21PLUS, Creative Human Resource Development Program for IT Convergence. This paper is available in Free and Open Source Software for Geospatial (FOSS4G) Conference Proceedings: https://scholarworks.umass.edu/foss4g/vol17/iss1/6 Development of an extension of GeoServer for handling 3D spatial data Hyung-Gyu Ryooa,∗, Soojin Kima, Joon-Seok Kima, Ki-Joune Lia aDepartment of Computer Science and Engineering, Pusan National University Abstract: Recently, several open source software tools such as CesiumJS and iTowns have been developed for dealing with 3-dimensional spatial data.
    [Show full text]
  • The State of Open Source GIS
    The State of Open Source GIS Prepared By: Paul Ramsey, Director Refractions Research Inc. Suite 300 – 1207 Douglas Street Victoria, BC, V8W-2E7 [email protected] Phone: (250) 383-3022 Fax: (250) 383-2140 Last Revised: September 15, 2007 TABLE OF CONTENTS 1 SUMMARY ...................................................................................................4 1.1 OPEN SOURCE ........................................................................................... 4 1.2 OPEN SOURCE GIS.................................................................................... 6 2 IMPLEMENTATION LANGUAGES ........................................................7 2.1 SURVEY OF ‘C’ PROJECTS ......................................................................... 8 2.1.1 Shared Libraries ............................................................................... 9 2.1.1.1 GDAL/OGR ...................................................................................9 2.1.1.2 Proj4 .............................................................................................11 2.1.1.3 GEOS ...........................................................................................13 2.1.1.4 Mapnik .........................................................................................14 2.1.1.5 FDO..............................................................................................15 2.1.2 Applications .................................................................................... 16 2.1.2.1 MapGuide Open Source...............................................................16
    [Show full text]
  • Gvsos: a New Client for Ogc® Sos Interface Standard
    GVSOS: A NEW CLIENT FOR OGC® SOS INTERFACE STANDARD Alain Tamayo Fong i GVSOS: A NEW CLIENT FOR OGC® SOS INTERFACE STANDARD Dissertation supervised by PhD Joaquín Huerta PhD Fernando Bacao Laura Díaz March, 2009 ii ACKNOWLEDGEMENTS I would like to thank to professors Joaquin Huerta and Michael Gould for their support during every step of the Master Degree Program. I would also like to thanks the Erasmus Mundus Scholarship program for giving me the chance to be part of this wonderful experience. Last, to all my colleagues and friends, thank you for making this time together so pleasant. iii GVSOS: A NEW CLIENT FOR OGC® SOS INTERFACE STANDARD ABSTRACT The popularity of sensor networks has increased very fast recently. A major problem with these networks is achieving interoperability between different networks which are potentially built using different platforms. OGC’s specifications allow clients to access geospatial data without knowing the details about how this data is gathered or stored. Currently OGC is working on an initiative called Sensor Web Enablement (SWE), for specifying interoperability interfaces and metadata encodings that enable real‐time integration of heterogeneous sensor webs into the information infrastructure. In this work we present the implementation of gvSOS, a new module for the GIS gvSIG to connect to Sensor Observation Services (SOS). The SOS client module allows gvSIG users to interact with SOS servers, displaying the information gathered by sensors in a layer composed by features. We present the detailed software engineering development process followed to build the module. For each step of the process we specify the main obstacles found during the development such as, restrictions of the gvSIG architecture, inaccuracies in the OGC’s specifications, and a set of common problems found in current SOS servers implementations available on the Internet.
    [Show full text]
  • (Iso19107) of the Open Geospatial Consortium
    Technical Report A Java Implementation of the OpenGIS™ Feature Geometry Abstract Specification (ISO 19107 Spatial Schema) Sanjay Dominik Jena, Jackson Roehrig {[email protected], [email protected]} University of Applied Sciences Cologne Institute for Technology in the Tropics Version 0.1 July 2007 ABSTRACT The Open Geospatial Consortium’s (OGC) Feature Geometry Abstract Specification (ISO/TC211 19107) describes a geometric and topological data structure for two and three dimensional representations of vector data. GeoAPI, an OGC working group, defines inter- face APIs derived from the ISO 19107. GeoTools provides an open source Java code library, which implements (OGC) specifications in close collaboration with GeoAPI projects. This work describes a partial but serviceable implementation of the ISO 19107 specifi- cation and its corresponding GeoAPI interfaces considering previous implementations and related specifications. It is intended to be a first impulse to the GeoTools project towards a full implementation of the Feature Geometry Abstract Specification. It focuses on aspects of spatial operations, such as robustness, precision, persistence and performance. A JUnit Test Suite was developed to verify the compliance of the implementation with the GeoAPI. The ISO 19107 is discussed and proposals for improvement of the GeoAPI are presented. II © Copyright by Sanjay Dominik Jena and Jackson Roehrig 2007 ACKNOWLEDGMENTS Our appreciation goes to the whole of the GeoTools and GeoAPI communities, in par- ticular to Martin Desruisseaux, Bryce Nordgren, Jody Garnett and Graham Davis for their extensive support and several discussions, and to the JTS developers, the JTS developer mail- ing list and to those, who will make use of and continue the implementation accomplished in this work.
    [Show full text]
  • Centre for Geo-Information Thesis Report GIRS-2018-06 Managing Big Geospatial Data with Apache Spark Msc Thesis Hector Muro Maur
    Centre for Geo-Information Thesis Report GIRS-2018-06 Managing Big Geospatial Data with Apache Spark MSc Thesis Hector Muro Mauri March 2018 Managing Big Geospatial Data with Apache Spark MSc Thesis Hector Muro Mauri Registration number 920908592110 Supervisors: Dr Arend Ligtenberg Dr Ioannis Athanasiadis A thesis submitted in partial fulfillment of the degree of Master of Science at Wageningen University and Research Centre, The Netherlands. March 2018 Wageningen, The Netherlands Thesis code number: GRS80436 Thesis Report: GIRS 2018 06 Wageningen University and Research Centre Laboratory of Geo-Information Science and Remote Sensing Contents 1 Introduction 3 1.1 Introduction & Context.........................................3 1.2 Problem definition & Research questions................................5 1.3 Structure of the document........................................5 2 Methods & Tools 6 2.1 Methods..................................................6 2.2 Tools....................................................7 3 Tests Design & Definition 9 3.1 Functionality Test............................................9 3.2 Performance Benchmark Test...................................... 17 3.3 Use Case................................................. 19 4 Functionality Test Results 21 4.1 Magellan.................................................. 21 4.2 GeoPySpark................................................ 25 4.3 GeoSpark................................................. 28 4.4 GeoMesa................................................. 31 5 Results
    [Show full text]
  • Client-Side Versus Server-Side Geoprocessing
    CLIENT-SIDE VERSUS SERVER-SIDE GEOPROCESSING Benchmarking the performance of web browsers processing geospatial data using common GIS operations. by Erin L. Hamilton A thesis submitted in partial fulfillment of the requirements for the degree of Master of Science (Cartography and Geographic Information Systems) at the UNIVERSITY OF WISCONSIN–MADISON 2014 i Acknowledgements The completion of this thesis could not have been accomplished without the help and support of many people. Thank you to Jim Burt for serving as my advisor. Your ability to see the big picture and ask hard questions made my work infinitely stronger. Your feedback on my drafts pushed me to produce my best work and I am thankful for that. Thank you to Qunying Huang and David Hart for serving on my committee. Your feedback on this thesis was much appreciated. More importantly, the support you provided me in improving my programming skills over the past three years enabled me to execute the technical pieces of this research. I am extremely grateful for that. Thank you to the members of the GIS group. The questions asked during my research progress presentations over the last year were significant in shaping and refining my work. Big thank you to the people in the Cartography Laboratory. Your guidance, support, and friendship were critical in keeping me moving forward. I especially want to thank Tanya Buckingham and Daniel Huffman for providing me with so much insightful perspective and advice along the way and Bill Buckingham for providing tremendously helpful recommendations on my writing. Thank you to my Mom and Dad for being my cheer team across the country.
    [Show full text]
  • Handling Data Consistency Through Spatial Data Integrity Rules in Constraint Decision Tables
    Handling Data Consistency through Spatial Data Integrity Rules in Constraint Decision Tables Fei Wang Vollständiger Abdruck von der Fakultät für Bauingenieur- und Vermessungswesen der Universität der Bundeswehr München zur Erlangung des akademischen Grades eines Doktor- Ingenieurs (Dr.-Ing.) genehmigten Dissertation. Vorsitzender: Univ.-Prof. Dr.-Ing. Wilhelm Caspary 1.Berichterstatter: Univ.-Prof. Dr.-Ing. Wolfgang Reinhardt 2.Berichterstatter: Univ.-Prof. Dr.-Ing. Anders Östman Diese Dissertation wurde am 31. Jan. 2008 bei der Universität der Bundeswehr münchen eingereicht. Tag der Mündlichen Prüfung: 13. Mai 2008 2 3 Abstract With the rapid development of the GIS world, spatial data are being increasingly shared, transformed, used and re-used. The quality of spatial data is put in a high priority because spatial data of inadequate quality is of little value to the GIS community. Several main components of spatial data quality were indentified by international standardization bodies such as ISO/TC 211, OGC and FGDC, which consists of seven usual quality elements: lineage, positional accuracy, attribute accuracy, semantic accuracy, temporal accuracy, logical consistency and completeness (two different names for similar aspects of quality are grouped in the same category). In this dissertation our work focuses on the data consistency issue of the spatial data quality components, which involves the logical consistency as well as semantic and temporal aspects. Due to complex geographic data characteristics, various data capture workflows and different data sources, the final large datasets often result in inconsistency, incompleteness and inaccuracy. To reduce spatial data inconsistency and provide users the data of adequate quality, the specification of spatial data consistency requirements should be explicitly described.
    [Show full text]
  • The Decision Table Template for Geospatial Business Rules
    The Decision Table Template For Geospatial Business Rules Alex Karman CTO and Co-Founder Revolutionary Machines, Inc. www.rev-mac.com San Jose, Oct 13-15, 2014 1 OpenRules Now Supports Spatial Rules • Leverages the popular JTS Topology Suite (“JTS”) • Supports the Egenhofer Relationships (“DE9-IM”) for 2D points, polygons and line strings – Contains, touches, crosses, overlaps, disjoint, etc. • Supports distance and area calculations; and ranking by distance or area • Supports aggregates (max/min) of spatial rules • Supports non-spatial mereological rules – Part of/comprises • Loads Geographic Markup Language (GML) from text files with a GeometryDatabaseBuilder utility Motivation • Last year, we used OpenRules to handle business rules related to security constraints and service level agreements in a data center management project. • This year, the customer asked us if OpenRules could manage fraud detection and privacy rules in a healthcare project in the same data center. • We looked at the problem domain and saw a large number of spatial rules. Spatial Business Rules Are Everywhere • Healthcare – Hospital Referral Region, Hospital Service Area, Hospital, Patient, Emergency Routes • Sales – Supplier and buyer territories, census block demographics • Utilities – Markets are usually defined geographically • Local government – Cadasters, zones, counties, municipalities Most Spatial Business Rules Only Require a Simple Vocabulary • Describe how simple points, polygons and lines interact • Describe distances between them • Describe “at least” or “no more than” rules (aggregate spatial rules) Most Spatial Business Rules Never Use Most GIS Features • Continuous field data – Weather, climate, netCDF, raster • Slope and aspect – Digital elevation model, bathymetry, viewshed • Topology – The shoreline borders the shore • Spatial statistics – Autocorrelation, Moran’s I, Geary’s C, etc.
    [Show full text]
  • Development of a Query Language for GML Based on Xpath∗
    Development of a Query Language for GML based on XPath∗ Jes´usM. Almendros-Jim´enez,Antonio Becerra-Ter´onand Francisco Garc´ıa-Garc´ıa University of Almer´ıa Almeria, Spain fjalmen,abecerra,[email protected] Abstract Geography Markup Language (GML) has been established as the standard language for the transport, storage and modelling of geographic information. In this paper we study how to adapt the XPath query language to GML documents. With this aim, we have defined a semantic based XPath language which is not based on the (tree-based) syntactic structure of GML documents, instead it is based on the \semantic structure" of GML documents. In other words, the proposed XPath language is based on the GML schema. We have developed a system called UALGIS, in order to implement the approach. Such system stores GML documents by means of the PostGIS RDBMS. In order to execute semantic-based XPath queries we have defined a translation of the queries into SQL. Such translation takes into account the GML schema. Finally, the system allows to visualize the result. With this aim, the result of a query is exported to the Keyhole Markup Language (KML) format. 1 Introduction The Geography Markup Language (GML) [7, 20, 21, 8] has been established as the standard language for the transport, storage and modeling of geographic information. GML is a dialect of the eXtensible Markup Language (XML) [27], which adapts XML to Geo-spatial data. XML allows to describe the structure of Web data by means of a tree. The tree structure is used to describe relations between data: for instance, a paper tag contains author, title and publisher as subtree tags and the subtree publisher can be described by means of name of the journal, country, editors, etc.
    [Show full text]
  • A Mobile Application for Geographical Data Gathering And
    A Mobile Application for Geographical Data Gathering and Validation in Fieldwork (Invited Talk) Karine Reis Ferreira, Cláudio Henrique Bogossian, Lúbia Vinhas, André F. Araújo de Carvalho National Institute for Space Research (INPE), Brazil Foundation of Science, Technology and Space {karine, lubia}@dpi.inpe.br Applications (FUNCATE), Brazil {claudio.bogossian, andre.carvalho}@funcate.org.br ABSTRACT Therefore, an essential feature of geographical data collection and Mobile devices, such as smartphones and tablets, are useful tools validation mobile systems is the capability of working offline. To for in situ collecting information about spatial locations. In this meet the demands of these two projects, this paper presents an paper, we describe the architecture of a mobile application for ongoing work on designing and implementing a mobile geographical data gathering and validation in fieldwork. This application for geographical data gathering and validation in application is being developed based on well-established fieldwork. Section 2 presents its architecture and section 3, its standards in order to assure spatial data interoperability between implementation issues. existing Spatial Data Infrastructures (SDI) and mobile systems. 2. ARCHITECTURE Categories and Subject Descriptors TerraMobile App is the name of the mobile application for D.2.11 [Software Engineering]: Software Architecture – domain- geographical data gathering and validation in fieldwork developed specific architectures. in this work. Figure 1 presents its general architecture. TerraMobile App has two modules for accessing geographical Keywords data, “Online Data Access” and “Offline Data Access”. The Mobile application, spatial data, interoperability “Online Data Access” module accesses geographical data from Spatial Data Infrastructures (SDI) through two kinds of well- 1.
    [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]
  • Geospatial Processing in Basex
    Geospatial Processing in BaseX Master Thesis in fulfillment of the requirements for the degree of Master of Science (M.Sc.) submitted from Masoumeh Seydi Gheranghiyeh in the Department of Computer and Information Science Chair of Database and Information Systems Group 1.Supervisor: Prof. Dr. Marc H. Scholl 2.Supervisor: Prof. Dr. M. Grossniklaus Konstanz, 2014 Abstract Geospatial information has been growing rapidly and has been used in variety of applications such as Geographic Information Systems, bioinformatics, and decision support systems. Variety of applications have demanded efficient approaches of data manipulation to cover their requirements. The XML-based data representation and manipulation in this field is one of these approaches that also has been considered and applied by databases, especially native XML databases. This work tries to investigate the challenges of geospatial data processing in BaseX [26], an open-source native XML database, by discussing the issues in geo- spatial querying, geospatial functionality, and query efficiency. At first, this thesis starts with introducing a number of indexing approaches as various ways of effi- cient geospatial data manipulation. Next, general geospatial functionality in some similar databases are investigated. Then, the geospatial features for Geography Markup Language (GML) [23] data representation are added to BaseX, using the Java Topology Suite (JTS) library [66] and based on the EXPath specification. To improve the performance of spatial queries, an indexing structure is applied as an external library. At the end, we have tried another querying approach by con- necting to MongoDB, a powerful document-based database system, through BaseX as an effort to find other efficient ways.
    [Show full text]