nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moving feature classes into a Feature Dataset: Automatically reproject

AlfredBaldenweck

Sometimes I make a series of feature classes, then decide that they'd be better in a feature dataset.

So I make the feature dataset, then try to copy the feature classes into it, only to be met with this error:

So, how about reprojecting it for me? It really shouldn't be this hard to move stuff into a feature dataset.

(Also, more annoyingly, is that the feature dataset is created with the same spatial reference (using WKID< no less) as the feature classes, so I really don't get what the problem is here).

Find more posts tagged with

Geodatabase

Status: Open

Comments

SSWoodward

Thanks for the Idea @AlfredBaldenweck

That's an interesting error. Can you give me a bit more information so I can try to reproduce it? If you can outline your steps in detail it would be a great help. What spatial reference are you in? etc.

AlfredBaldenweck

Yeah, of course:

Create feature dataset (WKID4326)
Click and drag feature class (4326) into it.
Error

I think that it might be an issue of a vertical reference, but I'm not sure how to check. Also, you know, FDs don't have an option for vertical reference when creating them.

Either way, when coding I get the same thing. I understand that the spatial references have to match, but why can't Arc automatically fix them for me instead of throwing an error?

SSWoodward

@AlfredBaldenweck I see the behavior you're seeing. I have to add an additional step to reproduce it.

Create feature dataset (WKID4326)
Create a feature class with 4326 and manually add a VCS
Click and drag feature class into it.
Error

So it does have to do with vertical references.

Also, you know, FDs don't have an option for vertical reference when creating them.

Thankfully, this isn't the case!

When creating a feature dataset in the UI, vertical references can be set by clicking into the globe icon next to the selector, this will open the coordinate system dialog and allow you to set the vertical reference.

If you're looking to do it with code, you can create a spatial reference object to pass as the reference for that call to CreateFeatureDataset(). You are able to set the VCS in the spatial reference object. There are also multiple other ways outlined here.

Projecting data is a fundamental change to the data itself, so projecting data without the user explicitly telling us that's what they want would be an unexpected behavior.

Bud

AlfredBaldenweck

Thankfully, this isn't the case!

Oh, that's good to know. This is data I was given; most of the time I don't deal with vertical spatial references so I'm a little out of water on them.

Projecting data is a fundamental change to the data itself, so projecting data without the user explicitly telling us that's what they want would be an unexpected behavior.

How about a checkbox or something like "This data will be reprojected to [Spatial reference, vertical spatial reference]; is that cool?"

I think also having it as a parameter in the Export Features tool would be nice as well. Like a boolean for if destination is a feature dataset, reproject to match spatial reference (Rather than relying on environment settings).