RE: [fme]ARC OBJECTS ERROR- Reading preceeding 0 in strings

[Raghavendran\(SRG\)]

Hello Balu

This is a question of ArcSDE and Geodatabase.

Geodatabases use a spatial index grid to help improve data retrieval performance.However, there is a geodatabase limitation to how many spatial index grid cells a single feature can span/contain, and when some features are quite large they might require a larger grid.

Check for the optimal spatial index grid size and re run the translation.

Happy FME-ing:-)

Regards

SRG

Bala Murugan <[EMAIL PROTECTED]> wrote:

Dear All

 

When i migrate data from ESRI personal geodatabase to ArcSDE geodatabase using FME, the following error occurred during translation:

 

"An error occurred while attempting to stop an edit operation. The error number from ArcObjects is: '-2147216063'. The error message from ArcObjects is: {Spatial index grid is too small}."

 

If anybody helps to solve this problem, i would be grateful to you

 

Thanks in advance

 

Regards

Balu

 

 

 

Chris Clements <[EMAIL PROTECTED]> wrote:

Thanks for the reply.

 

When the V8 format DGN is read the predeeding 0's are dropped immediately upon reading the file into Workbench, if the file is converted to V7 (via MicroStation) and then read into FME the 0 is not dropped.  I can submit some files to support if it would be of any help. 

This is similar to another issue we had reading V8 text nodes into FME (safe.com #27540) reported Jan.13, that we submitted some sample files with. 

 

Thanks,

Chris

-----Original Message-----
From: fme@yahoogroups.com [mailto:[EMAIL PROTECTED]On Behalf Of Dale Lutz
Sent: January 26, 2006 9:38 PM
To: fme@yahoogroups.com
Subject: Re: [fme] Reading preceeding 0 in strings

Hi,

FME itself shouldn't lose the leading 0 unless the field is ever treated as a number.

You can check this out by using the Logger in workbench and examining the values there.  Perhaps in that way you can determine where in your processing chain the 0 is being dropped and adjust it from there.  The concatenator itself certainly shouldn't drop it, nor should the joiner UNLESS the field its joining to is numeric, then maybe that would happen.

If you're still stumped, please send a repro-package in to [EMAIL PROTECTED]

Dale

On 1/10/06, fme_user <[EMAIL PROTECTED]> wrote:

Hi all,

We are using FME 2006 Pro. Build 2173 reading in MicroStation V8
files.  We are using text nodes inside polygons to build shapefiles and
also link to an access database.  The text node is the link to the
access database and consists of 2 lines of information.  For example:
155
B707

In the workspace these two lines get concatonated to be 155_B707 to
create a link to the access database.

Sometimes the first line starts with a 0 and when FME reads this it
drops the preceeding 0.  For example: 015 would be read as 15, as a
result it does not link to the access database which is looking for
015....

Is there a way to get FME to read the preceeding 0's?

Thanks for any suggestions,
chris








Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team.  Visit www.safe.com/services for details.
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/fme/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

 

---

What are the most popular cars? Find out at Yahoo! Autos

Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team.  Visit www.safe.com/services for details.

---

YAHOO! GROUPS LINKS

•  Visit your group "fme" on the web.
   
•  To unsubscribe from this group, send an email to:
   [EMAIL PROTECTED]
   
•  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

---