Customer Reviews

Designing Geodatabases: Case Studies in GIS Data Modeling

5 star:		(1)
4 star:		(4)
3 star:		(0)
2 star:		(0)
1 star:		(0)

 

 

This book provides a good introduction of steps and principles in designing geodatabases and the importance of information products and identifying thematic layers. The book presents 7 complex models: streams and river networks, census units and boundaries, addresses and locations, parcels and cadastre, surveying federal lands, using raster data, cartography and the base map. For each model they present the features, feature data sets, relationships, and topology rules. Readers working in these 7 areas will probably gain most from the book.

I would have also liked simpler examples and more design principles on grouping features into feature data sets. One of the strengths of this book is in stressing the value of topology rules, and feature data sets are needed for topology rules. With a database background, I would have liked fuller exploration of database relationships and normality contrasted with GIS relationship classes, relates, and joins, since data is often "flattened" when put into GIS. Readers of this should probably start with Modeling Our World: The Esri Guide to Geodatabase design by Michael Zeiler.

All chapters are clearly developed, explained, organized and illustrated.

It is worth reading either as a first try into GIS database design or as an authoritative source for on-going model design appraisal.

It only lacks a chapter devoted to network modeling such as those employed by electric, water or gas utilities. The water hydro model does address 'networks' but it is of a very different sort and is not apt for utility modeling.

The subject is considerably more specialised that designing a relational data base. The book is part of ESRI's ongoing way to publicise geodatabases, and hence ultimately drive demand for their products. So keep in mind that what is really being sold here is not the book but mindshare. Yours.

The text has extensive explanations as to what you might need in a geodatabase, as well as what is technically feasible to put in it. It also suggests that you consider what you want your users to be able to do. And use this in no small way to drive the design requirements. Software developers will recognise this as the gathering of scenarios from stakeholders. So you probably should canvas your potential users, if this is at all possible.

I used this book for developing GIS data layers. The book explains geodatabase relationships and concept very well. It also provides a lot of case studies and examples on how to create parcel, street, census, etc. geodatabase schemas. I highly recommend this book for someone who has a basic understanding of RDBMS and geodatabase design.

Green Bay, WI

la forma de desarrollo de cada tema esta muy bien explicado, mas alla de como armar una base de datos el libro proporciona un conocimineto claro para entender de los elementos en una base de datos y su relaciones. Da un esquema amplio que puede ser replicado para otros topicos donde sea necesario implementar sistemas parecidos.