Differences

This shows you the differences between two versions of the page.

Link to this comparison view

wiki:02:book [2013/08/03 23:34]
damien clochard created
wiki:02:book [2013/08/03 23:44] (current)
damien clochard
Line 10: Line 10:
 ''​TEXT''​ : ''​TEXT''​ :
  
-I must confess to being something of a “book guy.” I like having a book on my lap as I work through a problem (using my multiple monitors for actual implementation). “PostGIS in Action” puts most of what I need between one set of covers. +"PostGIS in Action" ​addresses a problem I have run into repeatedly in my consulting work: educating database professionals (DBAs, developers, etc.) on working with spatial data in a manner that they are familiar with. The authors are extremely knowledgeable about database technologies of all kinds and it comes through here.
- +
-This book addresses a problem I have run into repeatedly in my consulting work: educating database professionals (DBAs, developers, etc.) on working with spatial data in a manner that they are familiar with. The authors are extremely knowledgeable about database technologies of all kinds and it comes through here.+
  
 Since PostGIS extends PostgreSQL, it is impossible to separate the two when discussing good data design and implementation. The “Data Modeling” chapter provides a good discussion of various considerations when working with spatial data (use of complex geometries vs. points, homogeneous vs. heterogeneous geometry columns, etc.) but it also provides one of the best discussions of PostgreSQL table inheritance and partitioning that I have found in one place. Each topic, as throughout the book, is backed up by SQL examples and succinct discussion of the pros and cons of each approach. Since PostGIS extends PostgreSQL, it is impossible to separate the two when discussing good data design and implementation. The “Data Modeling” chapter provides a good discussion of various considerations when working with spatial data (use of complex geometries vs. points, homogeneous vs. heterogeneous geometry columns, etc.) but it also provides one of the best discussions of PostgreSQL table inheritance and partitioning that I have found in one place. Each topic, as throughout the book, is backed up by SQL examples and succinct discussion of the pros and cons of each approach.
Line 18: Line 16:
 The design consideration regarding storing geometry as points versus storing lines or polygons may seem basic to a GIS professional but is a discussion I have had repeatedly throughout my career with database designers who are new to spatial data. Many times, their initial instinct is to store X and Y values in separate columns in a table. This may be a perfectly valid approach for a given data set and how it is to be used but many design considerations come into play. “PostGIS In Action” does a good job of encapsulating those considerations in a manner that is consistent with how most database professionals approach database design. The design consideration regarding storing geometry as points versus storing lines or polygons may seem basic to a GIS professional but is a discussion I have had repeatedly throughout my career with database designers who are new to spatial data. Many times, their initial instinct is to store X and Y values in separate columns in a table. This may be a perfectly valid approach for a given data set and how it is to be used but many design considerations come into play. “PostGIS In Action” does a good job of encapsulating those considerations in a manner that is consistent with how most database professionals approach database design.
  
-Another concept that typically confounds database professionals on their first exposure to spatial data is the spatial reference system. ​“PostGIS In Action” ​has a chapter dedicated ​to spatial ​reference systemsIt discusses various common ​spatial ​references ​and their pros and cons as well as the components of spatial reference ​(ellipsoiddatumprojectionetc.). This is a complex ​topic and the purpose of this book is not to “teach GIS” but it is a crucial topic when working ​with spatial dataThe chapter gives a good overview of the concepts ​and considerations surrounding spatial references. If you are starting to work with spatial data, you will leave the chapter with an understanding of their importance and the fact that you should probably dig into them further.+“PostGIS In Action” ​continues on to discuss using PostGIS to perform ​spatial ​analysisAs always, real SQL samples are used so that a database professional will become comfortable with the use of spatial ​joins, spatial indexing, the many spatial functions built into PostGIS ​and many other concepts ​and techniques. Throughout the book, the authors return to few examples ​(the fictional “Hello Town”San FranciscoWashingtonDCso that each topic is discussed within ​problem set with which we become familiarAdditionally,​ tools such as OGR and QGIS/​SPIT ​are also discussed ​with examples.
  
-“PostGIS In Action” continues on to discuss using PostGIS to perform spatial analysis. As always, real SQL samples are used so that a database professional will become comfortable with the use of spatial joins, spatial indexing, the many spatial functions built into PostGIS and many other concepts and techniques. Throughout the book, the authors return to a few examples (the fictional “Hello Town”, San Francisco, Washington, DC) so that each topic is discussed within a problem set with which we become familiar. Additionally,​ tools such as OGR and QGIS/SPIT are also discussed (with examples).+''​SUB-HEADER''​ :  FIXME
  
-''​SUB-HEADER''​ :  +From the solid foundation it provides, the book delves into advanced topics and techniques that will enable the reader to become productive with PostGIS. A programmer can also benefit from the practical SQL examples in the book to write better applications (regardless of language) on top of of PostGIS/​PostgreSQL. I also think database professionals working on other platforms (such as Oracle Spatial) could benefit from the better understanding of the unique characteristics of spatial data that can be achieved with this book. They will also begin to see how well PostgreSQL stacks up against commercial RDBMS platforms in terms of capability.
- +
-I could go on but I will summarize what I like about “PostGIS In Action”: it provides a solid foundation for an experienced database professional who needs to begin working with spatial data using PostGIS and PostgreSQL. +
- +
-Throughout this article, I have used the term “database professional” to describe who I think will benefit from this book. It is not for beginners or the faint of heart. You should be very comfortable with your knowledge of relational databases, SQL and (optionally) PostgreSQL before diving into the book. “PostGIS in Action” does not teach RDBMS basics, nor should it. +
- +
-From the solid foundation it provides, the book delves into advanced topics and techniques that will enable the reader to become productive with PostGIS. A programmer can also benefit from the practical SQL examples in the book to write better applications (regardless of language) on top of of PostGIS/​PostgreSQL. I also think database professionals working on other platforms (such as Oracle/Oracle Spatial) could benefit from the better understanding of the unique characteristics of spatial data that can be achieved with this book. They will also begin to see how well PostgreSQL stacks up against commercial RDBMS platforms in terms of capability.+
  
 The subject of spatial data, as well as its implementation in PostGIS, is too big for one book to attempt to handle in a “one-stop shop” manner. “PostGIS In Action” wisely avoids trying to do this. It is a good starting point to begin building expertise if you are new to spatial data and, if you are experienced with it, you will probably learn a few things you didn’t know. I recommend checking out “PostGIS In Action” if you are or will be working with PostGIS or spatial data. The subject of spatial data, as well as its implementation in PostGIS, is too big for one book to attempt to handle in a “one-stop shop” manner. “PostGIS In Action” wisely avoids trying to do this. It is a good starting point to begin building expertise if you are new to spatial data and, if you are experienced with it, you will probably learn a few things you didn’t know. I recommend checking out “PostGIS In Action” if you are or will be working with PostGIS or spatial data.
Line 56: Line 48:
 > Format : Hard copy and Epub (512 pages) > Format : Hard copy and Epub (512 pages)
 > ISBN : 9781935182269 > ISBN : 9781935182269
-