Ah,... yes. Well, this is more a religious issue than a technical one. I am not among those who value precision because it is possible, rather than needed. I do see significant performance benefits from my somewhat heretical techniques, though not as much in native RDBMS geometry storage, because non-Esri geometry' doesn't see the same storage reduction found in file geodatabase or ST_GEOMETRY. If your data is only accurate to 1-inch, then 1/0.01' or 1/0.005' could be reasonable XY scalefactors,
The general tools don't make it easy to be consistent in non-default coordinate references, but I've found that using a "Transfer" FeatureDataset with the desired coordref constants as an intermediary for creation, then immediately dragging the newly created FCs out of that FDS to be effective. I usually script my creation utilities, which allows for more flexibility in SpatialReference definition and application, but the FDS technique works quite well for ad-hoc geoprocessing outputs.
- V
