OK, I had it slightly wrong. -1 means you don't get a spatial index at all - but at least it might stop the error. The ability to automatically calculate the correct index size is something ESRI are helping us to implement in the near future.
Mark Mark Ireland, Product Support Engineer Safe Software Inc. Surrey, BC, CANADA [EMAIL PROTECTED] http://www.safe.com Solutions for Spatial Data Translation, Distribution and Access --- In [email protected], "mark2atsafe" <[EMAIL PROTECTED]> wrote: > > I've recently been told that if you set grid1 to a value of -1 then > arcSDE will calculate the requirements for you, so you don't need to > worry. > > Mark > > Mark Ireland, Product Support Engineer > Safe Software Inc. Surrey, BC, CANADA > [EMAIL PROTECTED] http://www.safe.com > Solutions for Spatial Data Translation, Distribution and Access > > --- In [email protected], "Lars Robertsson" <[EMAIL PROTECTED]> > wrote: > > > > Dear there is a formatparameter called grid 1 increase that so will > itprobably work. If not just add a gridsize in the grid2 parameter. > > > > -----Ursprungligt meddelande----- > > Från: "Bala Murugan" <[EMAIL PROTECTED]> > > Till: "[email protected]" <[email protected]> > > Skickat: 06-01-28 17:57 > > Ämne: RE: [fme] Reading preceeding 0 in strings > > > > 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: > > @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in > 1.0in 1.25in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in > 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: > 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } > DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT- > FAMILY: "Times New Roman" } A:link { COLOR: blue; TEXT- > DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT- > DECORATION: underline } A:visited { COLOR: blue; TEXT-DECORATION: > underline } SPAN.MsoHyperlinkFollowed { COLOR: blue; TEXT- > DECORATION: underline } SPAN.EmailStyle18 { mso-style-type: > personal-compose } DIV.Section1 { page: Section1 } 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: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of > Dale Lutz > > Sent: January 26, 2006 9:38 PM > > To: [email protected] > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > 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. > > > > > > --------------------------------- > > > > > > > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com > > > 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/
