shrug-l: Connecting Autodesk Map with SDE 9.2

[Tripp Corbin]

I saw this post on the Autodesk Map Discussion Group and thought some
folks here might find it interesting. See below.
 

Tripp Corbin, MCP, CFM, GISP

Vice President, GIS/Mapping

ESRI Authorized Instructor

Keck & Wood, Inc.

 <http://www.keckwood.com/> www.keckwood.com

(678) 417-4013

(678) 417-8785 fax

 

Keck & Wood, Inc offers a range of GIS services and training.
Please visit  <http://www.keckwood.com/> www.keckwood.com for more
information including a schedule of upcoming classes.


RE: FDO support for SDE 9.2, lessons learned.  

I created this post to consolidate information from several posts
related to ARC SDE 9.2.  The two main issues related to FDO support for
SDE 9.2 are high precision data in ARC and the nvarchar data type on the
server back-end.

I hope this helps someone because I could have used this information six
months ago.

We have are getting ready to move to ARC SDE 9.2 and learned the
following:

FDO in Map 2008 does not support data stored in high precision format in
SDE 9.2.  There is a lot of good information  related to the difference
between high accuracy and high precision data and the pro's and cons.
My SDE administrator now knows not convert our low precision data for
features intended to be extracted by Map users, for now.  I only seem to
have this problem with Map 2008.  Map 2006 and 2007 connected to SDE 9.2
and extracted high precision data for me.  Go figure.

FDO in any release does not support the data type nvarchar used by the
backend database SQL or Oracle.  You do not see this in ArcCatalog, you
need to use the DB tools.  If you convert data to the nvarchar format,
FDO will drop the attribute columns using this data type when you
connect.  I could see my road but not the road names.  My SDE
administrators found that SDE will automatically convert the data from
varchar to nvarchar for you by default during an upgrade.  You can add a
line item to the SDE config file to flag ARC to use the old varchar to
be the default.

FYI nvarchar is the Unicode standard and varchar is the ANSI standard.
The Unicode standard allows for international characters but takes twice
as much memory.

Mark Nelson
Idaho Power. 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.dep.state.fl.us/pipermail/shrug-l/attachments/20071226/bfec6236/attachment.html