Situation:
I work for a company that creates geodatabases for a client that are restricted to a specific boilerplate schema (eg domains, subtypes, etc.). During a recent draft review, the client complained that when zooming to full extent during an ArcMap session, the full extent was too far "out."
Desired solution:
Alter xy domain of empty feature classes (contained in feature datasets) to extent of interest area as they are imported into production geodatabase (I know that a feature dataset destination will ignore the xy domain environment setting).
Problem:
No geoprocessing tool (eg feature class-to feature class, import to geodatabase, project, define projection, etc.) will accomplish the task (inside or outside feature datasets). The domain environment setting (advanced geodatabase) is ignored for all actions I've tried.
I curious how this will affect inclusion into a feature dataset. My understanding is that feature datasets enforce both spatial reference and extent?
– Jim Pollock Jul 18 '15 at 05:06