Thanks Dale, Can't seem to get it to log all features but som edigging on Friday afternoon has helped highlight the root cause of the problem.
The spatial object for some of the point data is actually a rendition of the relevent symbology for the point (e.g. arrows, meering sysmbols etc). Seems out ETL software is a bit too helpful and assumptions I'd made that data contained in the table 'TOPO_POINT' was point geometries is flawed :) Just need to convert it all into points on input and it'll be fine! Thanks, Iain --- In [email protected], "Dale Lutz" <[EMAIL PROTECTED]> wrote: > > Hi Ian, > > I think the KEY information in the log is this line here: > > > 2006-07-13 17:14:42|1335.6| 0.0|INFORM|Suppressed logging of 39 > feature(s) > > If the logging wasn't suppressed, you'd be able to see exactly which > feature was causing the problem because it would be logged for you. > And then you'd be better able to filter it ahead of time, or otherwise > figure out what is going on. > > So how to fix? I think the only way right now is to resort to the > "edit header" menu option in Workbench and insert a line in there that > says: > > LOG_MAX_FEATURES -1 > > That instructs FME to log ALL the features (don't suppress any) that > come through. (By default we log the first 20, then assume that folks > have seen enough...maybe not such a good assumption .. this was done > to stop runaway logging from creating multi-megabyte log files. > > Looking through the docs I found a vague reference to this but I think > I'll ask for a bit more explanation of this to be added. And probably > this could be added to the advanced settings for a Workspace too. > > Good luck! Hope this helps you narrow down the culprit. > > Dale > > > > I've hit a problem with a translation (reading from Oracle spatial > writing to IGDS/DGN). On our test sets of data it's running fine but on > the full dataset we've hit the following problem with some features > we're trying to write as cells: > > > > 2006-07-13 17:14:41|1335.3| 0.0|INFORM|MULTI_WRITER: multi_writer_id > `TQ3081SW': Writing feature 0 > > 2006-07-13 17:14:41|1335.3| 0.0|ERROR |IGDS Cell can only have 1 > coordinate. > > 2006-07-13 17:14:42|1335.3| 0.0|ERROR |... Last line repeated 2 times > ... > > 2006-07-13 17:14:42|1335.3| 0.0|STATS |Stored 288521 features to FME > feature store file file `C:\Temp\FME_FEATVDb01108' > > 2006-07-13 17:14:42|1335.6| 0.3|ERROR |IGDS Cell can only have 1 > coordinate. > > 2006-07-13 17:14:42|1335.6| 0.0|INFORM|Suppressed logging of 39 > feature(s) > > 2006-07-13 17:14:42|1335.6| 0.0|INFORM|FME Session Duration: 2106.5 > seconds. > > > > Initially we had a problem because some output levels have both line > and cell features in them. We resolved this by adding an attribute that > directly specified the igds_type (either igds_line or igds_cell). This > works fine on the test area of data. > > > > If I filter out features identified as cells prior to writing the > translation runs through to completion so it's definately the above > errors that are halting progress. > > > > I've tried to identify/exclude the offending features using a > CoordinateCounter and AttributeFilter then routing features that don't > have 1 coord to the vizualiser. This isn't catching any features and > the translation still fails > > > > I'm pretty stumped on this! > > > > Cheers, > > > > Iain > Join us at the FME Worldwide User Conference Sept. 21-22, 2006 Vancouver BC Canada. For more information, visit www.safe.com/2006uc. 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/
