When I create the new feature class, the folder does not appear in Catalog nor Map. If I try recreating the folder, it tells me the folder already exists. I can't find the folders anywhere in Catalog nor Map. I tried fixing this issue by removing the folders using access as a tool, but the folders seem to still exist in ArcGIS. Has anyone encountered a similar problem?
Solved! Go to Solution.
"Right click > New > Feature class > Name: N_20_07_16 (ex.) > Point Features > Next: I import the projection from my street frame > Next : I click next until finish (tolerance is imported to be the same as the street frame). "
Why are you importing a projection into an existing feature dataset? By definition, a feature dataset already has the projection defined and all feature classes within are the the same.
Hi Juliette,
Can you provide a walk through of your workflow? For example, right-click on a File Geodatabase > New > Feature Class. Screen shots will be helpful too.
Of course,
First (in Catalog), I open a Geodatabase (personal), in which there are several featuredatasets. I open one of those, in which I:
Right click > New > Feature class > Name: N_20_07_16 (ex.) > Point Features > Next: I import the projection from my street frame > Next : I click next until finish (tolerance is imported to be the same as the street frame).
I then proceed to wait. The folder does not appear.
When I try creating it again, it says the folder already exists.
I have been able to see the folders in access, but not to delete them.
Will mostly likely need to trouble shoot this a bit to see if it's something with ArcGIS or the personal geodatabase. As a test, can you try creating a new Personal Geodatabase and see if the issue is reproducible?
Also, are you able to work with a File Geodatabase rather than a Personal Geodatabase? A File Geodatabase has greater benefits (i.e. not limited to 2 GBs of data, can publish data to ArcGIS Server).
By 'folders' are you referring to a Feature Class?
Can you also post a Screenshot of the Geodatabase in ArcCatalog and what you are looking for, along with the info that Jake requested.
"Right click > New > Feature class > Name: N_20_07_16 (ex.) > Point Features > Next: I import the projection from my street frame > Next : I click next until finish (tolerance is imported to be the same as the street frame). "
Why are you importing a projection into an existing feature dataset? By definition, a feature dataset already has the projection defined and all feature classes within are the the same.
Good catch Joe
If we try creating a Feature Class inside a Feature Dataset, it actually doesn't even give you the option to select\define a Projection. It will automatically take the projection of the Feature Dataset.
So, it seems that she might be creating a standalone Feature Class or a new Feature Dataset....which needs to be confirmed.
Yes, you all are right, Except that it was my mistake: I am not setting projections again.
I think that the answer to my problem might be solved by this extremely basic information: personal geodatabases are set to a maximum of 2GB of data. I am quite certain I exceeded this amount of data. That would have been solved by Jake.
I will try and reproduce the same problem in another personal geodatabase, and if it does not occur / works normally, I would tend to think the problem is the geodatabase type itself.
Thanks to all of you very much, this is most likely to be a quite simple problem in the end...
Hello all,
After letting this rest for a while, I went back and tried the following:
I transfered the content from the Personal Godatabase to a File geodatabase.
In this new File geodatabase, I did the following:
New > Feature data set > (Name:NRMV_ETE, Projection imported from another feature class) > Finish.
I then tried to create a new feature class inside this feature dataset:
New > Feature class > Name:N_20_07_16C > Next > Finish.
The feature class did not appear in the Feature data set.
In another geodatabase (personal), I tried creating a new feature class, which properly worked. The problem does not seem to be the maximal capacity of the geodatabase, and is still unresolved.
I do no seem to be doing anything unsusual, although this still does not work.
Anyone having an idea on what could be going wrong?
You should guve tech support a call and do a screen share. Without seeing what's going on I can't even venture a guess....