Geoff Zeiss

June 2019

Sun Mon Tue Wed Thu Fri Sat
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30            

« Spatial Data Infrastructure- A Practical Example | Main | Civil3D Extension for Google Earth »

June 05, 2006

Comments

Vish

Hi,

Great observation on the point that the ArcSDE capabilities might be built into MS SQL Server in the future. In fact i had come across some work that an university reserch team had done for spatial searches in MS SQL Server 2005 already. http://msdn.microsoft.com/sql/learning/prog/clr/default.aspx?pull=/library/en-us/dnsql90/html/tblvalfuncsql.asp

Also, agree with Jason on his views that AutoCAD Map 2007 lacks a lot of GIS analysis functionalities and thus will not replace ArcGIS as is. But our company is a surveying company and mainly deals with data integration and management. We do not really use or do any spatial analysis functionalities. That might actually make ArcGIS more replacable by AutoCAD Map 2007. But we still are very concerned about the fact that features created as ARCs in AutoCAD Map 2007 cannot be stored as is ArcSDE and is automatically intensified into a series of line segments. Currently we are trying to figure our way around this. Any ideas?

Thank You,
Vish

Brad Heasley

Vish,

Correct, if your organization creates and edits GIS data than the best-of-breed product is a CAD application such as Map; especially with the numerous FDO feature source providers. An ArcGIS administrator would therefore only need to create and manage privileges to feature classes in SDE reducing your software cost.

Advance Geometry from SDE:
FDO uses the exposed SDE API to read/write geometry and data through the SDE middleware while advanced geometries and special classes (relationship classes, network topology, etc) are created/manipulated via ArcObjects; requiring, at a minimum, the ArcEditor level licensing where the Geometries are stored as blob data (See your DBTUNE file for db configurations pertaining to data types). That said, since FDO doesn't use ArcObjects it can not access those blobs and instead densifies the arcs. Your organization can probably use a custom process to leverage read/write of those blobs into the FDO API as it is an open format. Theoretical but possibly possible...

Brad

Ajay

yes you are right. There are a lot of persons in this field who have no domain expertise and many non-technical persons have simply intruded in this field by taking advanatge of multi-disciplinary character of GIS filed. With the recent advancements in last few years have made the situation even worse for such persons.
It is time take the corrective actions by accepting the fact that technology needs real experts and improve infrastructure and reources accordingly.

The comments to this entry are closed.

RSS Feed

  • Subscribe

Categories