Hi Felix Not sure if I can help much more than previous suggestions.
I tried what you explained using the workspace wizard you were doing using the workspace wizard and had no problems. - You may want to look at the software build you are using. - Pay particular attention to geometry types. - If you have a current AMC I suggest you log a call with [EMAIL PROTECTED] I have attached FME documentation that explains what GEODB_AVG_NUM_POINTS is ... after reading that it seems kind of weird a default of 40 is being set. I had a quick look to see if the format attribute could be forced to a value but you do not appear to be able to expose the format attribute in workbench ... you may be able to in scripting. Anyway, I'm not sure that the GEODB_AVG_NUM_POINTS attribute is used for in the geodatabase anymore as you better parameter controls over the spatial index stuff. -------------------------------------------- GEODB_AVG_NUM_POINTS This optional field specifies the estimated average number of points per feature. It is used in the creation of the spatial index for the feature class. If this configuration parameter is not specified, then a default value will be assigned to the feature class, depending on its geometry type. If the geometry is a point or multipoint, the default value will be 1; if the geometry is a polyline, the default value will be 2; if the geometry is a polygon, the default value will be 4. This parameter must be an integer. For example, if a new feature class called Roads is to be created and we believe that the average number of points for a feature from the Roads feature class will be 3, then on the DEF line for the Roads feature class, we would find the following: GEODB_AVG_NUM_POINTS 3 ------------------------------------------------- Regards Garry --- In [email protected], "reichert" <[EMAIL PROTECTED]> wrote: > hello > > > We just have to convert a geodatabase in a new geodatabase for converting > the datum and projection, but without success, there is always an > error-announcement like > > > > The configuration parameter 'GEODB_AVG_NUM_POINTS' for the feature class > 'xxxxxxxxx' contains either an invalid value (i.e. integer less than zero) > or no value. A default value of '40' will be used. > > Cannot write a non-poly feature to a polgon feature class. A fatal > error has occured in one of the FME plugins. Terminating...Error encountered > During writer shutdown. > > > > > Garry, we've this problem using the workbench wizard. > > If the 'GEODB_AVG_NUM_POINTS' is optional, how is it possible to influence > this parameter? > > Thanks > felix > > > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[EMAIL PROTECTED] Im Auftrag von > garry_christoffersen > Gesendet: Donnerstag, 23. Juni 2005 23:27 > An: [email protected] > Betreff: [fme] Re: geodatabase to geodatabase > > Felix > > To me it sounds like a geometry setting thing. Whenever I have got this > message, I've found it to always be that I've set the wrong geometry. > > Things to try: > > - Have a look at the log and see what dataset it is failing on and check its > geometrys > - Try setting up a new fmw using the workspace wizard and look at the > geometrys it sets. > - Big hammer approach, use GEOMETRYCOERCER > > Cheers Garry > > --- In [email protected], "reichert" <[EMAIL PROTECTED]> wrote: > > hello, > > > > we have to convert a personel geodatebase to a personal > geodatabeas in a > > different datum and projection. the conversion always stops with > > Cannot write a non-poly feature to a polgon feature class A fatal > error has > > occured in one of the FME plugins. Terminating...Error encountered > during > > writer shutdown. > > > > in the table I can't find neither a value less than zero nore a no > value > > data. the geometry types in the properties of datasource and > datadestination > > seams to be okay. > > > > > > > > does anybody have an idea? > > > > > > > > felix reichert > > > > > > > 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 <*> 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/
