Straws in the Wind Blog Articles
• Silence is Golden?
• National Broadband Network, Spatial Data & Processing
• Industry Best Practice?
• Spatial Database Independence
• 2011 Oracle Spatial Excellence Award for Education and Research
• Tiling Very Large Rasters
• Cloud Computing GIS and Standards (OGC/ISO)
• Usefulness of Spatial Metadata as a Foundation for an Australian data.gov and other uses
• Vale Professor Pieter Roelof Zwart 1941-2010
• Interview by Nestoria on Real Estate Mapping
• Mapping surface area of a ruptured pipe in Oracle Spatial
• FOSS4G 2009 Sydney Presentation
• GIS software and Database Primary Keys
• To Constrain or Not to Constrain: There should be NO Question
• The Shapefile 2.0 Manifesto
• Maps of War Website
• Talk on Open GeoData in Australia
• Boarder and District Spatial Information Group Presentation on Spatial Datbases
• Presentations given by myself at the Australian Oracle Spatial Forum, Sydney, Thursday 28th August 2008
• The Sad State of SQL Spatial Standards - Take 2
• Radius Studio and ESRI (Part 2)
• The Sad State of GIS SQL Standards
• Microsoft to release their own spatial capability for SQL Server
• Radius Studio and FDO
• SpatialWare 4.9 Released
• First Radius Studio Certified Practitioner
• Image Catalog Tool - How To Videos
• Latest article published on Directions Magazine
• Image Catalog / GeoRaster Management Tools
• ESRI Ireland - Many Thanks
• PL/SQL Packages for Oracle Sdo_Geometry
• Professor Hanan Samet
• ADF and Spatial
• Bouquets and Brickbats
• Geomatics Degrees, Space Curves and Oracle Spatial
• Non-Persistent Types
• Feature Data Objects - Either/Or?
• A Thank You
There is a useful exchange going on over on the Microsoft Forums in relation to the paucity of information on geographic objects (as against planar objects) in the OGC SQL standard: this is in the context of SQL Server 2008 “Katmai” Spatial implementation. This exchange occured over Microsoft’s reading of the OGC standards in respect of the coordinate ordering of data in their geography data type (as against their geometry planar data type). The upshot is that the Microsoft engineers chose to have the coordinates in a geography ordered Latitude/Longitude which is at odds with how Oracle, PostGIS and many other vendors order the ordinates (they use Longitude/Latitude).
In the exchange I note that Google Maps uses Latitude/Longitude and observe that it is not so much the coordinate ordering that is the issue, or even “standards compliance”, rather it is about the functionality of the implementation.