|
Right, the precision coordinate value doesn't increase accuracy it simple provides a higher resolution of the coordinate grid. So features can be as close a nanometers instead, previously I believe it was 2 cm.
|
Precision is somewhat arbitrary -- I could store sub-nanometer data in 9.1 if I wanted, but I didn't want to.
In fact, you get significantly better performance if you don't use the default sub-millimeter precision
(a smaller xyscale is also a smaller delta between vertices, and therefore compresses better, reducing
storage size and improving performance).
|
So recommended testing steps moving forward then would be to utilize the sdequery utility to test to 9.1 tables and the 10.1 tables using the query you noted above. All we would be testing is simple feature classes, non of them participate in relationships, etc.
|
I hesitate to call this a "recommended" procedure, since it is unsupported software, but for simple data
transition, the 'sdequery' utility (with the CTL option to fashion a control file for import), combined with
the 'asc2sde' utility can quickly and efficiently load all your data. You can also use it to control the
resulting coordinate reference parameters, column renaming, column addition, and STRING/NSTRING
transition. The problem is learning to use a new suite of tools (and their quirks), just for transition (new
tools that are now deprecated, since they won't be available at 10.3).
| Question on the non-OBJECTID key, would be put in this non-OBJECTID column manually before the transfer to 10.1? I see where you are going with this..... |
Actually, you can retain the old ID if you use a USER-set rowid at first, then alter it to SDE-set (which
ArcGIS requires), or you can rename the input column and construct a new OBJECTID on the fly.
In the asc2sde control file, this would look like:
OBJECTID Sequence() - 10 N
ORIGID Int32 - 10 Y
I didn't even mention spatial defragmentation, which intentionally reorders data for optimal spatial
query performance (and would therefore hose OBJECTIDs).
|
On the coordinate reference scale side of things....where would we put in this multiplier?
|
You wouldn't. In fact, Desktop makes it very difficult to use your own preferred coordref. But if you're
using 'asc2sde' to load, you could just change the COORDREF_XY from "-210,-120,1000000" to
"-400,-400,10000000" to cut 11cm precision to 1.1cm with more elbow room.
- V
