Monday, May 26, 2008

Why use ArcSDE?

Those not on the PostGIS users mailing list will have missed an interesting thread that pulled together some good comments from both the usual suspects and some unexpected participants.

Some choice quotes:
"Yes, using SDE effectively castrates the spatial database. It still walks and talks, but it's a shell of the man it was before. "yours truly

"The 'economical' route for those that want to use PostGIS and have edit capabilities inside ArcGIS desktop would be to use the ZigGIS professional which (from my understanding) implements an editable PostGIS layer in ArcGIS desktop."Rob Tester

"If you compare [pricing] with Oracle then yes probably so... But honestly if you are talking about SQL Server vs. PostgreSQL, I think the savings you get from running PostgreSQL would be dwarfed by the cost of SDE."Regina Obe

"Spatial databases are being commoditized, but SDE is not a spatial database, it's a revenue enhancer for ArcMap, and ArcMap is *not* being commoditized."yours truly

"A few disclaimers and background : Until last year, I worked at ESRI. I contributed with some of bug fixes for the PostgreSQL/PostGIS support in the ArcObjects side of things."Ragi Burhum (read this one!)

"There is one thing to note in a mixed-client environment and that is this: if a non-ESRI client writes an invalid geometry to a the database then when ArcSDE constructs a query over an area that includes this feature ArcSDE will discover the error (as it passed all queried features into its own shape checking routines) and stop the query"Simon Greener (read this one!)
I'm thinking of becoming an instigator. Apparently there's money in p***ing people off.
 

1 comment:

Sean G said...

I don't get Ragi Burhum's comment about his code that I am likely using. If it's open source, stolen or not, can he not cite it?

And no, there's really not much money in being an instigator.

About Me

My Photo
Victoria, British Columbia, Canada

Followers

Blog Archive

Labels

bc (33) it (27) postgis (19) icm (11) video (10) enterprise IT (9) sprint (9) open source (8) osgeo (8) cio (6) management (6) enterprise (5) foippa (5) foss4g (5) gis (5) spatial it (5) foi (4) mapserver (4) outsourcing (4) bcesis (3) oracle (3) politics (3) COTS (2) architecture (2) boundless (2) esri (2) idm (2) natural resources (2) ogc (2) open data (2) opengeo (2) openstudent (2) postgresql (2) rant (2) technology (2) vendor (2) web (2) 1.4.0 (1) HR (1) access to information (1) accounting (1) agile (1) aspen (1) benchmark (1) buffer (1) build vs buy (1) business (1) business process (1) cathedral (1) cloud (1) code (1) common sense (1) consulting (1) contracting (1) core review (1) crm (1) custom (1) data warehouse (1) deloitte (1) design (1) digital (1) email (1) essentials (1) evil (1) exadata (1) fcuk (1) fgdb (1) fme (1) foocamp (1) foss4g2007 (1) ftp (1) gds (1) geocortex (1) geometry (1) geoserver (1) google (1) google earth (1) government (1) grass (1) hp (1) iaas (1) icio (1) industry (1) innovation (1) integrated case management (1) introversion (1) iso (1) isss (1) isvalid (1) javascript (1) jts (1) lawyers (1) mapping (1) mcfd (1) microsoft (1) mysql (1) new it (1) nosql (1) opengis (1) openlayers (1) oss (1) paas (1) pirates (1) policy (1) portal (1) proprietary software (1) qgis (1) rdbms (1) recursion (1) regression (1) rfc (1) right to information (1) saas (1) salesforce (1) sardonic (1) seibel (1) sermon (1) siebel (1) snark (1) spatial (1) standards (1) svr (1) tempest (1) texas (1) tired (1) transit (1) twitter (1) udig (1) uk (1) uk gds (1) verbal culture (1) victoria (1) waterfall (1) wfs (1) where (1) with recursive (1) wkb (1)