|This article does not cite any references or sources. (April 2012)|
||The topic of this article may not meet Wikipedia's general notability guideline. (April 2012)|
Spatial ETL, also known as Geospatial Transformation and Load (GTL), provides the data processing functionality of traditional Extract, Transform, Load (ETL) software, but with a primary focus on the ability to manage spatial data (which may also be called GIS, geographic, or map data).
A Spatial ETL system may translate data directly from one format to another, or via an intermediate format; the latter being more common when transformation of the data is to be carried out.
The transformation phase of a Spatial ETL process allows a variety of functions; some of these are similar to standard ETL, but some are unique to spatial data.
Spatial data commonly consists of a geographic element and related attribute data; therefore Spatial ETL transformations are often described as being either geometric transformations - transformation of the geographic element - or attribute transformations - transformations of the related attribute data.
Common Geospatial Transformations
- Reprojection: the ability to convert spatial data between one coordinate system and another.
- Spatial transformations: the ability to model spatial interactions and calculate spatial predicates
- Topological transformations: the ability to create topological relationships between disparate datasets
- Resymbolisation: the ability to changes the cartographic characteristics of a feature, such as colour or line-style
- Geocoding: the ability to convert attributes of tabular data into spatial data
Desirable features of a Spatial ETL application are:
- Data comparison: Ability to carry out change detection and do incremental updates
- Conflict management: Ability to manage conflicts between multiple users of the same data
- Data dissemination: Ability to publish data via the internet or deliver by email regardless of source format
- Semantic processing: Ability to understand the rules of different data formats to minimize user input whilst preserving meaning
Spatial ETL Uses
Spatial ETL has a number of distinct uses to which it is put.
- Data cleansing: The removal of errors within a dataset
- Data merging: The bringing together of multiple datasets into a common framework - conflation is a good example of this
- Data verification: The comparison of multiple datasets for verification and quality assurance purposes
- Data conversion: Conversion between different data formats.
Spatial ETL - Origins and History
Although ETL tools for processing non-spatial data have existed for some time, ETL tools that can manage the unique characteristics of spatial data only emerged in the early 1990s.
Spatial ETL tools emerged in the GIS industry to enable interoperability (or the exchange of information) between the industry’s diverse array of mapping applications and associated proprietary formats. However, Spatial ETL tools are also becoming increasingly important in the realm of Management Information Systems as a tool to help organizations integrate spatial data with their existing non-spatial databases, and also to leverage their spatial data assets to develop more competitive business strategies.
Traditionally, GIS applications have had the ability to read or import a limited number of spatial data formats, but with few specialist ETL transformation tools; the concept being to import data then carry out step-by-step transformation or analysis within the GIS application itself. Conversely, Spatial ETL does not require the user to import or view the data, and generally carries out its tasks in a single predefined process.
With the push to achieve greater interoperability within the GIS industry, many existing GIS applications are now incorporating Spatial ETL tools within their products; the ArcGIS Data Interoperability Extension being a good example of this.
- "Data Transformation/Spatial Extract, Transform, and Load". Retrieved 5 July 2012.
- "Unleash the Power of Your Spatial Data with Spatial ETL Technology". Retrieved 5 July 2012.