Barend Gehrels from the Boost.Geometry project has posted an interesting analysis comparing available versions of the same vector data. It is Shapefile with borders of the World countries. The data is the same but different and sometimes the differences are very surprising.
Here is part 1 and part 2 of the excellent comparison made by Barend.
Moreover, Kevin started completing the PostGIS Functions Reference with visual presentation of geometric problems together with SQL commands using various PostGIS functions that can be applied to solve particular situations. For example, what does the ST_Buffer function, how boolean predicates like ST_Contains check spatial relation of two geometries or what’s the difference between ST_Difference and ST_SymDifference.
Clearly, I’ve got way way more than I asked for or I expected. On behalf of myself and users who are about to start their adventure with PostGIS, I’d like to give big kudos to Kevin for this fantastic work!
Interestingly, Bartosz proposes to understand the battle with data races as a discipline-driven programming that helps, mostly C+ programmers, to avoid all this horrible pitfalls. Moreover, Bartosz presents programmers with a well-designed methodology based on types system as a tool that may guard programs against injury from data races problem and with success.
Basically (and not surprisingly) Bartosz recommends think first, act later kind of approach based on detailed analysis of what might be causing data races in your program, on identification of potential sources of data race problems. This approach is a contrary to spending hours searching for data races conditions using debugger.
The data race problem is a complex subject, but – in my opinion – Bartosz explains it in a very accessible step-by-step form. Three words summary of Bartosz’ lecture and the presented methodology is: sharing + mutability + no synchronisation = data race
My friend Joasked on GEOSmailing list for approachable explanation of spatial relations and Dale Lutz from Safe Software suggested something I’ve not came across myself before and what (in generalised form) I’d consider as a great idea for…a book really :-)
It really must be very hot and fresh news, so the virtual devil spirit of social networking hasn’t fished it out yet and also Google (check this if you haven’t heard yet about this local family company) lists less than 15 pages.
PostGIS provides over 300 spatial operators, spatial functions, spatial data types and spatial indexing enhancements. If you add to the mix the complimentary features that PostgreSQL and other PostgreSQL related projects provide, then you’ve got one jam-packed powerhouse at your disposal well suited for hardcore work as well as a valuable training tool for spatial concepts.
Next to the early access, another cool thing about the way Manning Publications release their books is possibility to comment chapters and discuss with authors directly through Manning Sandbox forums. There is no exception for the PostGIS in Action :-)