| Author |
Messages |
|
sallie_vaughn
 |
| 07/14/2008 2:50 PM |
 Alert
|
When creating a new personal geodatabase using v. 2.6, I'm been trying to import the spatial reference from an existing layer which lives on SDE.
The existing SDE dataset is selected, and when Build/Generate is clicked, I get the following error: Error getting Feature Dataset.
I have to export from SDE to personal and use that copy to set the spatial reference. It's not a horrible work-around, but it's annoying.
Any ideas?
|
|
|
|
bschimpf
|
| 07/15/2008 6:45 AM |
Alert
|
This particular error is a result of the conversion from low precision to high precision. The existing toolset was written before ArcGIS 9.2. The error was first reported following installation of ArcGIS 9.2 Service Pack 5. This error is generated when the tool attempts to create a Spatial Reference for high precision datasets from low precision datasets.
In the high precision dataset, the concept of the Spatial Domain (the box where the data resides) is much less critical than in earlier structures. Here, at the Help Desk, we create new Spatial References by selection rather than import. We determine the Spatial Reference by querying the Feature Class we want, using the Select and finding the Spatial Reference; e.g. WGS 1984 UTM ZONE 16, and then adjusting the precision (although in most cases it is fine). We have not had any difficultly using this technique, and it does not require export.
|
|
|
|
sallie_vaughn
|
| 07/18/2008 7:53 AM |
Alert
|
| Is this still the case even if the datasets in SDE are high precision? |
|
|
|
bschimpf
|
| 07/18/2008 8:25 AM |
Alert
|
Unfortunately, we believe it is. The problem is in the Builder Software. The government has taken a position that they do not want to update the old software, particularly since there is a workaround.
If you want to add to an existing Feature Dataset, it should work with no problem. That way, you might be able to create the Feature Dataset in ArcCatalog, and then use the Builder to create the classes. Just make sure you have the proper Feature Dataset name. |
|
|
|
|