Have you specified the coordinate system of the DGN in your Reader?

---

Yes, I have.

 

 

I have a dataset that includes 438 arcs - 7 of which fail to load. I've identified which ones these are by trial and error, but I don't understand how they are different from the other arcs in the dataset.

---

I'm guessing that you want to preserve the arcs? If this is not important, you might be able to circumvent this problem altogether with an ArcStroker.

 

 

If you want to preserve your arcs, you will probably have to delve into those 7 features to see what the problem might be. I suggest outputting these features to the Inspector to check if one or more of the arc-specific attributes (primary axis, start angle, sweep angle, etc) are invalid.

 

 

Also, if you are reprojecting your arcs during your workspace, take a look at this article: http://fmepedia.safe.com/articles/How_To/How-to-keep-arcs-as-arcs-when-reprojecting

 

 

David

---

Thanks for your response David:

 

 

Yes I want to preserve arcs, and no I am not reprojecting my data.

 

 

I'm not seeing any particulary strange values for the arc-specific attributes. I've attached these from the logger output below.

 

 

What sort of values for arc-specific attributes should I look out for? Is there a test I can run the features through beforehand to catch the bad arcs before they crash the data transformation process? It seems to only be an issue with certain elliptic arcs.

 

 

-----------------------

 

|INFORM|Rotation (Degrees CCW): 339.18323431792862

 

|INFORM|(Ellipse) Primary Radius: 0.43133513652379302

 

|INFORM|Secondary Radius: 0.30500000000000088

 

|INFORM|Start Angle (Degrees CCW): -0

 

|INFORM|Sweep Angle (Degrees CCW): -180

 

 

|INFORM|Rotation (Degrees CCW): 339.18323431792862

 

|INFORM|(Ellipse) Primary Radius: 0.43133513652379302

 

|INFORM|Secondary Radius: 0.30500000000000088

 

|INFORM|Start Angle (Degrees CCW): 180

 

|INFORM|Sweep Angle (Degrees CCW): -180

 

 

|INFORM|Rotation (Degrees CCW): 304.16749165041597

 

|INFORM|(Ellipse) Primary Radius: 0.42886098209576523

 

|INFORM|Secondary Radius: 0.30520952624966596

 

|INFORM|Start Angle (Degrees CCW): 263.02865547722467

 

|INFORM|Sweep Angle (Degrees CCW): 193.94268904563538

 

 

|INFORM|Rotation (Degrees CCW): 304.16749165041597

 

|INFORM|(Ellipse) Primary Radius: 0.42886098209576523

 

|INFORM|Secondary Radius: 0.30520952624966596

 

|INFORM|Start Angle (Degrees CCW): 96.971344522775311

 

|INFORM|Sweep Angle (Degrees CCW): 166.05731095436468

 

 

|INFORM|Rotation (Degrees CCW): 304.16749165041597

 

|INFORM|(Ellipse) Primary Radius: 0.42886098209576523

 

|INFORM|Secondary Radius: 0.30520952624966596

 

|INFORM|Start Angle (Degrees CCW): 270

 

|INFORM|Sweep Angle (Degrees CCW): 180

 

 

|INFORM|Rotation (Degrees CCW): 224.37309341287374

 

|INFORM|(Ellipse) Primary Radius: 0.20000000000000018

 

|INFORM|Secondary Radius: 0.099999999999999742

 

|INFORM|Start Angle (Degrees CCW): 0

 

|INFORM|Sweep Angle (Degrees CCW): 180

 

 

|INFORM|Rotation (Degrees CCW): 32.639999966928919

 

|INFORM|(Ellipse) Primary Radius: 0.4285665691581646

 

|INFORM|Secondary Radius: 0.30499999999999999

 

|INFORM|Start Angle (Degrees CCW): 269.99999999998289

 

|INFORM|Sweep Angle (Degrees CCW): 180.0000000000002

---

Hi,

 

Just an idea, can it be that the failure is due to the FGBD feature dataset tolerance?

---

I would try and write the data to a new feature class in an empty FGDB. If that works, it might be a problem with the tolerance or resolution, as Itay suggests.

 

 

If that still doesn't work, your best bet is probably to send your case to Safe support. Remember to include your workspace and a small dataset to reproduce the issue.

 

 

David

---

I wrote the feature out to a new feature class in a new FGDB, the same error occured. So I guess it can't be a tolerance issue? - Where are these set exactly?

 

 

I'll compile a small test data set for FME to look at.

 

 

Thanks

---

Thanks for the link, I'm using ArcGIS 10.0 and apparently the error code -2147220989 is:

 

 

DIM_E_UNSUPPORTED_VERSION

 

The change to the dimension featureclass is not supported in the open geodatabase version.

 

 

http://help.arcgis.com/en/sdk/10.0/arcobjects_net/componenthelp/0012/00120000006q000000.htm

 

 

I'm not sure how dimension feature classes come into this?

---

My guess is that the writer interpratets these annotations as dimension features classes.

---

Very strange. I use a geometry filter early on to remove any text from the workflow.

---

could be a geometry representing text that causes the problems, I would try and find the diferences in attributes between the arcs, so that the attributes responsible for the 'wrong' interpretation could be removed.

---

This issue was fixed with FME 2013.

---