I've encountered a glitch which could become problematic somewhere down the line for me.
I run ArcMap 10.2.1 on windows 7.
Let's say you have a global dataset of 1000s of point features. This single feature class includes wells in every ocean of the world. Now when you click zoom to layer, your view extent will be on a worldwide, scale. Fine.
Now let's say you want to edit this feature class and delete every well outside of the North Sea (for example). I select the wells i want to keep, reverse the selection, delete the wells I don't want, click save/stop editing. ok.
Now when I click 'zoom to layer', I should be taken to the North Sea where all my point features are. But no! the view extent is still the entire world! (having just this single layer in an MXD and clicking the view full extent globe gives you the same issue btw).
so even when deleting features, the feature class seems to retain it's original extent properties. I won't go into it here, but this can create problems for me, having a view extent 100s of time larger than what it should be...
anyone else seen this?
further info: after the editing was done and dusted, the extent properties under the 'source' tab of the feature class would display the original extent numbers (worldwide scale in this case), not the updated ones.
I run ArcMap 10.2.1 on windows 7.
Let's say you have a global dataset of 1000s of point features. This single feature class includes wells in every ocean of the world. Now when you click zoom to layer, your view extent will be on a worldwide, scale. Fine.
Now let's say you want to edit this feature class and delete every well outside of the North Sea (for example). I select the wells i want to keep, reverse the selection, delete the wells I don't want, click save/stop editing. ok.
Now when I click 'zoom to layer', I should be taken to the North Sea where all my point features are. But no! the view extent is still the entire world! (having just this single layer in an MXD and clicking the view full extent globe gives you the same issue btw).
so even when deleting features, the feature class seems to retain it's original extent properties. I won't go into it here, but this can create problems for me, having a view extent 100s of time larger than what it should be...
anyone else seen this?
further info: after the editing was done and dusted, the extent properties under the 'source' tab of the feature class would display the original extent numbers (worldwide scale in this case), not the updated ones.