span8
span4
span8
span4
What is the ArcSDEGridSnapper?
The ArcSDEGridSnapper transformer is useful in verifying what the data will look like once it is in an ArcSDE.
This transformer simulates the ArcSDE conversion on a feature by performing ArcSDE translation,scaling,and coordinate snapping.It also removes duplicate vertices resulting from snapping multiple formerly separate vertices to the same grid point.These coordinates will also be recorded in a list attribute.
If the feature was an aggregate feature,the ArcSDE conversion is executed individually on each geometry in the aggregate feature.The ArcSDEGridSnapper simulates coordinate transformation and records duplicates.It will snap all feature coordinates to match the precision specified,thus making the feature compatible with your ArcSDE database.It's a much preferable alternative to the CoordinateRounder.
By quickly simulating data conversion to ArcSDE,the ArcSDEGridSnapper allows for the analysis of data accuracy.The problematic data output from the ArcSDEGridSnapper can be further processed in the workspace (removal of dangles/sliver polygons for example) before the data is loaded into SDE.
Writing to SDE is not always simple.Coordinates in low precision are stored in the database as 31 bit positive integers.Features will be rejected where their coordinates have a greater precision than is allowed for in the database.When snapping features to the SDE grid,self-intersections can be introduced by ArcSDE itself!
The ArcSDE simulation is executed only when all coordinates of the geometry are within the valid range defined by the ArcSDE format.Otherwise,the conversion is cancelled and the error attribute '_ArcSDE_Error' is added to the feature.Currently,the only value of the error attribute is 'out of bounds',which occurs when a geometry contains a coordinate that lays outside the calculated domain.
Note that illegal geometries,such as areas with dangles,will not be checked for validity on the ArcSDE format.Arcs and ellipses passed through the ArcSDEGridSnapper will be stroked into lines;this matches the behavior of the ArcSDE writer,which does not support the storage of these types of geometries.
Please refer to the following webpages to see what Esri considers valid geometry in ArcSDE:
As of FME 2013 SP1,the ArcSDEGridSnapper supports the high precision coordinates available in ArcGIS 9.3 or higher.
ArcMap | ArcSDEGridSNapper | Geodatabase (ArcSDE) Writer | ArcSDE Writer |
Domain - Min X | Minimum X | X Origin | X Origin |
Domain - Min Y | Minimum Y | Y Origin | Y Origin |
Resolution - XY Resolution | Scale (inverse of XY Resolution) | X,Y Scale | Scaling Factor |
Domain - Min Z | Minimum Z (if 3D) | Z Origin | Z Origin |
Resolution - Z Resolution | Z Scale (if 3D - inverse of Z resolution) | Z Scale | Z Scaling Factor |
Performing spatial queries on database tables using the FeatureReader
Comparison of FME readers and writers for SDE and Geodatabase
Working with Geodatabase Subtypes: Creating A Subtype
Attribute Table in ArcGIS: "Could Not Load Data"
How do I connect to my ArcSDE Geodatabase using Direct Connect?
Tutorial: Geodatabase Transformations
How to convert Esri Shapefile to Geodatabase
Creating and Associating Geodatabase Domains Dynamically Using A Feature Class and GDB Table
Updating,Inserting and Deleting features in an unversioned Geodatabase
© 2019 亚搏在线Safe Software Inc |Legal