HI,
Can anyone suggest how to resolve on below issue, snapshot attached.. is this possible to fix in the database.
This was in sde environment in the server. we are using oracle SQL developer for the database.
Thanks,
Srinivas
there are no coordinates found in the point data and we know the tables which are having issues in sde database but could not get a solution to date, please review what would be the correct solution.
The title indicates that you are using ArcMap, but if you have access to Pro you can use the Check Geometry geoprocessing tool that has an ESRI method and an OGC method (drop-down menu). I have found that the OGC method can find errors that the ESRI method is unable to find. This technique might help to find errors in your data, if there are any.
Feature classes in file geodatabases can be more forgiving with corrupt or invalid geometry data than enterprise geodatabases. I have seen similar issues when some of the geometry data is corrupt or invalid, e.g., are their records that have invalid coordinates for a point? Have you run Check Geometry on the file geodatabase feature class? If so, did it find anything? You could also start by importing chunks of the data in EGDB to isolate which part of the table is causing issues.
yes, same
is the projection in the sde fc the same as that of the local fc.
Geometry type is Point.
No multiple geometries were available for the same table.
Manually importing or copying data to sde schema.
What is the Geometry type (SDO_Geometry, ST_Geometry, etc.) being used in the feature classes with issues?
Is there multiple geometry types (point / line / poly) in the same table?
How are you importing the data into the Oracle Geodatabase?
Whats the coordinate systems/projection? Copying to the sde may be using a configuration keyword or Default which is making funky geometry.
We are not a built-in SQL developer.
We can read the table in SQL dev and ArcCatalog. We cannot preview the geography in Catalog.
This feature was copied or import from the local file geodatabase and we have checked in FGDB that the feature is opening in ArcMap with geometry in local.
Yes, it does work when we export the feature to a local FGDB as it was seen in local.
Was the spatial index built in SQL developer? In SQL developer, does the geometry metadata etc line-up with your projection and extent?
Can you read the table in SQL dev and ArcCatalog? and can you preview the geography in Catalog?
What's the history behind this feature, is it a new import, update, have you done something to it recently etc?
If you export the feature to a local FGDB as a FC does it work ok?
Yes, it is registered and it has got the geometry field and index was there.. any other solution to find out.
without more information this could be caused by many things. Is it registered to the EGDB and has it got a geometry field and spatial index?
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
