GDAL comes with several utilities that you might find useful in your geospatial explorations. gdalinfo<\/a> will give you information about raster GIS files. ogrinfo will provide information on vector file formats. gdaltranslate<\/a> will convert files to various other formats. gdalwarp<\/a> will let you convert files to another coordinate system or merge multiple files into a single raster data set.<\/p>\n When appropriate, GDAL provides a wrapper to other libraries to access file formats. libtiff<\/a> and libgeotiff<\/a> are used to access the GeoTIFF<\/a> file format. GeoTIFFs are an extension to the TIFF<\/a> standard that allows for spatial data to be included with the file. They are mainly used for raster data such as aerial photographs. However, extensions such as 16-bit GeoTIFFs are used to store elevation data where each pixel encodes a height value. LibKML<\/a> is used to access KML<\/a> files such as those used with Google Earth. Libpng<\/a>, libjpeg<\/a>, and Jasper<\/a> are used for other formats, and so on.<\/p>\n These libraries also provide useful utilities. One example is listgeo<\/a> that I used in the last post in this series. Another is tiffinfo<\/a> that will print out information from standard TIFF tags in a file. tiffcp<\/a> and geotiffcp<\/a> will copy files while preserving TIFF and the extended GeoTIFF tags.<\/p>\n As far as full-featured GIS go, the grand-daddy of them all is the Geographic Resources Analysis Support System (GRASS) GIS<\/a>. GRASS was originally developed from 1982 to 1995 by the US Army Construction Engineering Research Laboratories<\/a> that is a part of the US Corps of Engineers<\/a>. For a while it retained its \u201cold school GIS\u201d roots (like early ESRI<\/a> products) by having everything broken out into programs run from the command line. The Corps ceased developing GRASS around 1995 and it was then taken over by a group of people at Baylor University<\/a>. It now has gone from simple graphics and requiring a lot of command line experience to a modern GUI thanks to an international group of developers. Of all the Open Source GIS tools, it is the closest competitor to a full featured GIS such as ESRI’s ArcGIS<\/a> or ERDAS<\/a> Imagine<\/a>.<\/p>\n <\/p>\n Example of the Modern GRASS GIS GUI<\/p><\/div>\n Another powerful Open Source GIS tool is the Quantum GIS (QGIS)<\/a> project. QGIS started life around 2002 and became a part of the Open Source Geospatial Foundation<\/a>. It was written using the Qt<\/a> widget set and features a plugin architecture that allows users to contribute more features using Python or C++. It uses libraries such as GDAL to access numerous raster and vector formats and even includes a plugin so it can act as a front-end to GRASS. Additionally, it can consume OGC web services<\/a> and interact with Oracle<\/a>, PostGIS<\/a>, and ESRI geodatabases<\/a>. QGIS also features a world-wide group of developers and just recently hit the 2.0 release. For those familiar with ESRI products, it fits in a nebulous area between the old ArcView<\/a> product and ArcMap. In some ways this author believes it outperforms either product thanks to the plugin architecture and its support of web services. In others it lacks many of the geoprocessing<\/a> features of the ESRI products. However, it is easily powerful enough for most users who need to work with geospatial data.<\/p>\n <\/p>\n QGIS 2.0 Running on Fedora 19<\/p><\/div>\n uDig<\/a> is the third GIS tool in the lineup. It was created by the Canadian company Refractions Research<\/a> and is based on the Eclipse<\/a> framework. uDig also features a plugin architecture and can use GRASS for vector processing. Like the others, uDig can ingest OGC web services. Unlike the others, uDig is also used as a base for other GIS applications such as JGrass<\/a> and Arbonaut<\/a>. While not necessarily as full featured as QGIS or GRASS, uDig still has its place among the tools.<\/p>\n <\/p>\n uDIG screenshot Courtesy Wikipedia<\/p><\/div>\n The System for Automated Geospatial Analyses (SAGA)<\/a> GIS is an Open Source GIS originally developed by the Department of Physical Geography at the University of Gottingen<\/a> in Germany and now by a group of international volunteers. SAGA also uses GDAL to read a large number of geospatial file formats. It focuses on geoscientific processing and can be called from the R statistical data analysis system<\/a>. SAGA is similar to QGIS but includes some features not found in that package such as image pattern recognition and more geostatistical functionality. It is still under active development but has not had a new stable release since 2011.<\/p>\n <\/p>\n SAGA GIS Screenshot Courtesy Wikipedia<\/p><\/div>\n For storing geospatial data we have two main contenders. Spatial Databases<\/a> are extensions to traditional relational database systems that allow you to do queries such as \u201cgive me all the points within five miles of this location.\u201d The first, PostGIS<\/a>, is a set of extensions to the PostgreSQL<\/a> database also developed by Refractions Research and released to the world in 2001. PostGIS is probably the most popular Open Source geospatial database in the world, thanks to its functionality and full implementation of many OGC<\/a> standards. It started as storing only vector data but was expanded to include raster in version 2.0. It includes geodatabase and geoprocessing functionality not even found in the commercial database offerings. Today it is used by many projects and has support by both proprietary and Open Source GIS tools. Tools such as QGIS can directly communicate with PostGIS to read and write data.<\/p>\n MySQL<\/a> also has a set of spatial extensions<\/a> and is catching up to PostGIS in functionality, although it still lags in some areas such as geography and 3D types, SRID<\/a> projections, and directly querying by a radius. It is not as fully and directly supported by other Open Source GIS tools. However, it is faster for many operations than PostGIS due to the differences in architecture between the two. MySQL Spatial uses a polygon-based model where functions are implemented by bounding polygons.<\/p>\n This is just a brief introduction to Open Source GIS tools out there. I’d highly suggest poking around with your favorite search engine to learn more about what’s available. If you’re an experienced GIS professional, you could get up to speed with QGIS or GRASS fairly quickly. Next time, we’ll start looking at data and how to process it for your needs, including creating spatial databases.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Today there are a huge amount of Open Source geospatial tools out there. The Open Source GIS movement started with libraries to access data formats and has led to full blown geospatial systems today. We’ll look at a few of … Continue reading ![\"GRASS](\"https:\/\/brian.digitalmaddox.com\/blog\/wp-content\/uploads\/2013\/10\/grassimage-300x187.png\")
<\/a>![\"QGIS](\"https:\/\/brian.digitalmaddox.com\/blog\/wp-content\/uploads\/2013\/10\/qgis2_fedora19-300x182.png\")
<\/a>![\"uDIG](\"https:\/\/brian.digitalmaddox.com\/blog\/wp-content\/uploads\/2013\/10\/960px-UDig-300x240.png\")
<\/a>![\"SAGA](\"https:\/\/brian.digitalmaddox.com\/blog\/wp-content\/uploads\/2013\/10\/SAGA_screenshot-300x234.jpg\")
<\/a>Databases<\/b><\/h2>\n