Error: �??the coordinates or measure are out of bound�?�,

365
6
04-23-2014 11:12 AM
Highlighted
Honored Contributor
Error: â??the coordinates or measure are out of boundâ?�,

I wanted to copy features from file geodatabase layer (attached) to enterprise geodatabase layer but I got the error below (knowing that the source and destination layers have the same coordinate system).

[ATTACH=CONFIG]33287[/ATTACH], [ATTACH=CONFIG]33288[/ATTACH], [ATTACH=CONFIG]33289[/ATTACH]


What might be the issue here?

Thank you

Best

Jamal
Reply
0 Kudos
6 Replies
Highlighted
Esri Frequent Contributor
Jamal,

I noticed that in the third image (from the SDE geodatabase) that there are not feature extent coordinates (Top, bottom, left and right). The the second image (from the file geodatabase) has feature extent coordinates. That may be a direction to look into. I did see that the projections are the same.

Just an observation......

George
--- George T.
Reply
0 Kudos
Highlighted
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

Jamal,

I noticed that in the third image (from the SDE geodatabase) that there are not feature extent coordinates (Top, bottom, left and right). The the second image (from the file geodatabase) has feature extent coordinates. That may be a direction to look into. I did see that the projections are the same.

Just an observation......

George


Thanks George.

This is how the ArcGIS behaves by default as new enterprise geodatabse layer is created. It doesn�??t give an extent.

[ATTACH=CONFIG]33291[/ATTACH],[ATTACH=CONFIG]33292[/ATTACH], [ATTACH=CONFIG]33293[/ATTACH], [ATTACH=CONFIG]33294[/ATTACH], [ATTACH=CONFIG]33295[/ATTACH]


Could you please try to create enterprise geodatabse layer at your machine? does it give an extent?
Reply
0 Kudos
Highlighted
Esri Frequent Contributor
Jamal,

I tested in SQL Server and Oracle and got a different message when copying/pasting into the feature class in either. See attached screenshot. This error seems related to the other forum post that you have.

My process was: Start an edit session, open the file geodatabase feature class table, select all features, copy, then paste into the SDE feature class.

Hope this helps.....


George
--- George T.
Reply
0 Kudos
Highlighted
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

Jamal,

I tested in SQL Server and Oracle and got a different message when copying/pasting into the feature class in either. See attached screenshot. This error seems related to the other forum post that you have.

My process was: Start an edit session, open the file geodatabase feature class table, select all features, copy, then paste into the SDE feature class.

Hope this helps.....


George


Thanks George for the help,

I�??m wondering why you have different error message. I�??m using SQL database as well

What might be the issue then?
Reply
0 Kudos
Highlighted
Esri Frequent Contributor
I am wondering if it has to do with the fact that most of the roads are a single polygon and it is creating the errors. There are also a bunch of very small polygons that barely have geometry to them. I think that they may get collapsed when loaded into the SQL geodatabase as part of the check when loading data.

I have read you other post (http://forums.arcgis.com/threads/107598-Error-�??line-string-or-poly-boundary-is-self-intersecting�?...) and think that these issues are all related.

What is you try to split the massive road polygon into smaller pieces for loading?
--- George T.
Reply
0 Kudos
Highlighted
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

I am wondering if it has to do with the fact that most of the roads are a single polygon and it is creating the errors. There are also a bunch of very small polygons that barely have geometry to them. I think that they may get collapsed when loaded into the SQL geodatabase as part of the check when loading data.

I have read you other post (http://forums.arcgis.com/threads/107598-Error-�??line-string-or-poly-boundary-is-self-intersecting�?...) and think that these issues are all related.

What is you try to split the massive road polygon into smaller pieces for loading?


Thanks George,

I never know that an internal checks are applied when copy and paste features from a layer to other. I thought that such checks are applied in purpose when building �??topology�?� with rules, for example. As these features are living currently in enterprise geodatabase layer is expected to be sufficient to be copied to other layer successfully.

These roads are derived from CAD files (one file is attached). We use the FME to convert the CAD hatches to polygons (ArcGIS fails to read hatches).

1. Boundary layer (one polygon)

[ATTACH=CONFIG]33344[/ATTACH]

2. Landuse layer (multiple polygons)

[ATTACH=CONFIG]33345[/ATTACH]

3. The roads are derived by subtracting the Landuse layer from Boundary layer by FME workbench

[ATTACH=CONFIG]33346[/ATTACH]

[ATTACH=CONFIG]33347[/ATTACH]

These features of road layer are fine at the level of FILE GEODATABASE. Issues appear as they are copied and pasted to ENTERPRISE GEODATABASE LAYER
Reply
0 Kudos