In+ersec+ion for Spatial People

Tidbits offers an interesting article comparing Apple Maps with Google Maps.

The article's conclusion: "In the end, I believe that the real area where Google Maps stands out from Apple’s Maps is in transit directions, which I can’t test, but which have been praised by city dwellers like David Pogue of the New York Times, and Jacqui Cheng of Ars Technica, Dan Moren of Macworld, and Andy Ihnatko of the Chicago Sun-Times. Otherwise, both apps do a decent job and do so with entirely reasonable interfaces. Apple’s mapping data undoubtedly isn’t as good as Google’s, overall, but in most cases, I doubt that it will make a significant difference. And it’s now easy enough — thanks to the “via transit” trick — to compare routes in both apps, though I suppose that then raises the issue of which you want to believe."

Related news include:

• MacRumors informing us that Google Maps for iOS Downloaded More than 10 Million Times
• From the same source, Apple Reportedly in Talks for Data-Sharing Deal with Foursquare

[this is old news from July and sharing it with our users to make sure they're aware of it] Spatially Adjusted linked in July to a BostonGIS article named "Cross Compare SQL Server 2008 Spatial, PostgreSQL/PostGIS 1.3-1.4, MySQL 5-6". Previous such comparison is over 1.5 years old, see also related stories below.

From the associated blog entry: "A few people have been asking us what are the pros and cons of using SQL Server 2008 Spatial and PostGIS and as a Windows user, why would you still consider using PostGIS. Rather than simply providing some hand-waving saying "well if you just care about displaying data, then use whatever you feel comfortable with, but if you want to do real intensive sophisticated spatial analysis and geometric processing without having to purchase a bunch of expensive software, then PostGIS is probably better for you. Hell why must you think in either or propositions - just use both using the strengths of each.", we have tried really hard to quantify the similarities and differences between the 2 and to boot - we have also added in MySQL."Story imported from the previous Slashgeo.org Slashcode site, user comments have not been migrated. For more information, please read Welcome to the new Slashgeo.org!. Thank you for your understanding.

[this is old news from July and sharing it with our users to make sure they're aware of it] Spatially Adjusted linked in July to a BostonGIS article named "Cross Compare SQL Server 2008 Spatial, PostgreSQL/PostGIS 1.3-1.4, MySQL 5-6". Previous such comparison is over 1.5 years old, see also related stories below.

From the associated blog entry: "A few people have been asking us what are the pros and cons of using SQL Server 2008 Spatial and PostGIS and as a Windows user, why would you still consider using PostGIS. Rather than simply providing some hand-waving saying "well if you just care about displaying data, then use whatever you feel comfortable with, but if you want to do real intensive sophisticated spatial analysis and geometric processing without having to purchase a bunch of expensive software, then PostGIS is probably better for you. Hell why must you think in either or propositions - just use both using the strengths of each.", we have tried really hard to quantify the similarities and differences between the 2 and to boot - we have also added in MySQL."