Geoprocessing
PUG List: Geodetics & What’s New in 9.2
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
Geoprocessing
3-1
Overview The
List
What’s
new at 9.2
Create
Custom GeoTransformation tool
Measure
Tool / Calculate Geometry
MGRS/USNG Goode’s
Homolosine
Geodatabase: Vertical
coordinate systems
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
high versus low
2
Geoprocessing
3-2
231/86: Cannot edit a geometric network in a projected ArcMap data view Not
supported yet at 9.2
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
3
Geoprocessing
3-3
ID ?: Datum handling Implement Easier Has
Not
Shell-developed solution
UI to set transformations
defaults based on location
for 9.3; will review for next major release
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
4
Geoprocessing
3-4
232/87: Datum info not exposed Multiple Datum
issues are listed here
transformation management tool
Supporting
info like areas of use and accuracies not currently available
When
we go to DBMS version of library can add this
info GP
Project tool doesn’t show parameter values: NIM005479
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
5
Geoprocessing
3-5
208/60: IDs for custom coordsys (IMS/SDE) PEOBJEDITHOME Environment Uses Will
text files to define coordsys/transformations
slow down software
Longer Want Plan
term
to switch to an EPSG-like database
to allow addition of custom definitions
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
variable
6
Geoprocessing
3-6
253/110: dimensioning tools More May
information requested
include
Dimension Use
in layout mode
geodesic/great circle distances
Dimension
polygons with geodetic areas
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
7
Geoprocessing
3-7
249/106: GRID, workstn vs ArcGIS coordsys GRIDs
use the workstation coordsys format
Spatial
Analyst uses grids internally
Update
to workstation is unlikely
Currently,
we feel that maintaining both definitions is too difficult
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
8
Geoprocessing
3-8
Polynomial transformations Polynomial-based
transformations: post-9.3; in
top 5 issues
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
9
Geoprocessing
3-9
202/50: Predefined datum and proj shift params “Create
Custom Geog Transformation” tool
Requested
Improvements
Make
the .gtf files true ASCII – right now they include binary information so ArcGIS can read/write them
Add
save functionality to the “New” transformation dialog in ArcMap (NIM006269)
Env.
setting to change location of gtf files
Include Ability
a description (if we go to a dbms PE version)
to set a transformation per layer in ArcMap
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
10
Geoprocessing
3-10
46: Projection on-the-fly (ArcPad) Currently,
rasters and GPS tracklog shapefile can be reprojected
ESRI
would like use cases that require vector data to be reprojected (in large scale field work)
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
11
Geoprocessing
3-11
211/64: Projection on the fly very slow Improving For Is If
performance occurs at each release
9.2, added a “projection hint” the data completely within the projection horizon? so, no need to intersect
Rasters:
very fast
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
12
Geoprocessing
3-12
79/23: Projection transformation options ArcIMS:
Allow a mapservice to support multiple co-ordinate systems
Not
planned for ArcIMS
Check
out ArcGIS Server.
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
13
Geoprocessing
3-13
201/49: Store datum/proj shift info in metadata GP
tools now store all messages
Still
to do:
Expose
this information in ArcCatalog
For
other procedures that change coordinate system, also store in the metadata
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
14
Geoprocessing
3-14
Closed issues
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
15
Geoprocessing
3-15
75: Map transformations misleading ArcMap’s
transformation UI will show a ‘default’ one, but must click OK for it to be applied
Default
is now
Closed
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
16
Geoprocessing
3-16
127: Rotate projected images Added
to ArcGIS 9.2.
Closed
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
17
Geoprocessing
3-17
135: Raster reprojection GP
Project raster tool didn’t support datum transformations
Added
to ArcGIS 9.2
Closed
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
18
Geoprocessing
3-18
26: Seamless CAD/GIS integration Georeferencing
toolbar now supports CAD data
Closed
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
19
Geoprocessing
3-19
Changes for ArcGIS 9.2
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
20
Geoprocessing
3-20
Geoprocessing Tools
didn’t support geographic/datum transformations
Use
ArcToolbox environment to set up output coordinate system and geographic transformation
Models
now support iterations
Copyright © 2004-2007 ESRI. All rights reserved.
21
A major change to geoprocessing at 9.2 is a change to the environment settings. It’s not widely enough known, but most of the data conversion tools, or any tool that allows you to set the output coordinate system/spatial reference, generally do not support datum transformations. You might use the Feature Class to Feature Class wizard, set the output coordinate system *here* in the general settings portion of the Geoprocessing environment, this is all you could set, and assume that a datum transformation from NAD27 to NAD83 would occur. That’s not the case before 9.2, and if you don’t set a geographic/datum transformation here, it still would not occur correctly. You can only set a single coordinate system, and a single geographic transformation. This is particularly important because the system does have a ‘default’ transformation between NAD27 and NAD83. Unfortunately, it’s the one for the lower 48, so Alaska and Hawai’i have to do some extra work.
Advanced Analysis with ArcGIS
Geoprocessing
3-21
Tool dialogs All
tools support batch processing at 9.2
More
flexible, as the tool is run for each input
data Right
click the tool to access the batch option
Copyright © 2004-2007 ESRI. All rights reserved.
22
All tool dialogs now support batch processing. There’s a new control that places all the parameters for a tool into a table, and you just fill out the table. This is more flexible than some of the existing batch tools, like the Batch Project Tool. That tool created a list of feature classes as a single string which was a parameter to a special batch project command. There’s a limit on how long that string could be. The batch table control, runs the tool as many times as it needs to, so you don’t have that type of limitation. Right click a tool (open its context menu) to access the batch option.
Advanced Analysis with ArcGIS
Geoprocessing
3-22
Project tool (feature) Input data
Output data Output coordsys Geographic / datum transformation
Copyright © 2004-2007 ESRI. All rights reserved.
23
To give us a starting point, here is the project tool for features. The green dots denote required parameters. For this tool, you have to fill out the input data including path, output path and data name, and the output coordinate system. I haven’t labeled it, but greyed out is the input coordinate system. It will be populated automatically, once you enter the input data. The last parameter is the geographic (datum) transformation. It’s marked optional, which is really confusing. The geoprocessing tool dialogs are really a GUI or user friendly interface to a scripting/command line world. So the parameters here reflect how you would use the tool on the command line. So, if the input and output geographic coordinate systems are the same, no transformation is needed— thus, optional. If the input/output geographic coordsys are different, then it’s a required parameter.
Advanced Analysis with ArcGIS
Geoprocessing
3-23
Required transformation
NAD27
NAD83 Geographic / datum transformation
Copyright © 2004-2007 ESRI. All rights reserved.
24
Now I’ve filled out the input feature class, which is georeferenced to NAD27. The output coordinate system is NAD83. Because they’re different, the ‘optional’ transformation parameter is now required—it has a green dot, and you can use the pull-down to see the possible transformations.
Advanced Analysis with ArcGIS
Geoprocessing
3-24
Project tool (feature) – batch option Input data Output data
Output coordsys
Copyright © 2004-2007 ESRI. All rights reserved.
Geographic / datum transformation
25
Here is the batch option of the Project tool for features. Right-click on the tool to open the batch version. And what you end up with is a table, with all the parameters of the tool. Just like the tool, anything colored green is a required field—input data, output data, output coordinate system. A white field is either truly optional, or like the geographic transformation may become required as you fill in the other fields. Use the plus button to add more rows, and you can copy and paste values between the rows. Select a field, and you can type directly into it, double click, and it will open a tool dialog with just that value, or right click to also open the dialog, fill the fields above or below with the current value, and so on.
Advanced Analysis with ArcGIS
Geoprocessing
3-25
Identify Tool Enhancements
Identify features by dragging a box
Sort Records, Sort Fields and modify Field Visibility
Copy Location X,Y coordinates Alter
Location units (DD, Feet, Meters)
Copyright © 2004-2007 ESRI. All rights reserved.
26
The Identify Tool has had a major overhaul at 9.2 and includes some really nice new functionality. One of the new enhancements is that you can now draw a rectangle and the identify tool will populate the results dialog with a records within the box. The results dialog allows you to sort the records, sort the fields, and even toggle field visibility.
Advanced Analysis with ArcGIS
Geoprocessing
3-26
Navigate to X,Y Location Map
units
Decimal
Degrees
Degrees
Minutes Seconds
Copyright © 2004-2007 ESRI. All rights reserved.
27
A new Zoom to XY Tool has been added to ArcMap making if very easy to zoom directly to a location on the map. Users can easily specify to search for X,Y locations based upon map units, Decimal Degrees, or even Degrees, Minutes, Seconds.
Advanced Analysis with ArcGIS
Geoprocessing
3-27
Measure Tool Enhancements Measure
Area/Length in multiple unit types
Measure
Individual Feature
Snapping Summarize
multiple measures
Copyright © 2004-2007 ESRI. All rights reserved.
28
Like the Identify Tool, the Measure tool has gotten an overhaul at 9.2. A new dialog is presented when using this tool to simplify measuring lines or areas and even provides options for change the units on-the-fly that are reported. Snapping is now available as an option to make measuring more precise. The measure feature option, makes it easier than ever to report the length or area of a specific feature and you can even have the dialog sum the results of multiple measurements!
Advanced Analysis with ArcGIS
Geoprocessing
3-28
Calculating Geometry Area/Length/Centroid/XY Easily
perform Geometry Calculations
Area Perimeter Length X
Location
Y
Location
Centroid
X
Centroid
Y
Copyright © 2004-2007 ESRI. All rights reserved.
29
9.2 Introduces a very powerful and easy way to calculate area and perimeter of polygons, length of lines, and individual X and Y locations for points. The units can be user defined making is easy to calculate acreage for parcels, hectares for agricultural fields, and length in miles of streets. Unlike Geodatabase feature classes, Shapefiles do not natively manage shape/geometry measurements like area and perimeter for polygons or the length for lines. However, the new Calculate Geometry functionality makes it easier than ever to manage this information. Finally, individual X and Y fields can be calculated for point features or polygon centroids in map units, Decimal Degrees or even Degrees/Minutes/Seconds when the Data Frame’s Spatial Reference is set to a Geographic Coordinate System.
Advanced Analysis with ArcGIS
Geoprocessing
3-29
MGRS and USNG New
method in ArcObjects
Calculate
Geometry
Navigate/Go
to X/Y
Identify
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
30
Geoprocessing
3-30
Goode’s Homolosine
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
31
Geoprocessing
3-31
Goode’s Homolosine
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
32
Geoprocessing
3-32
GCS_Assumed_Geographic_1 No
longer supported
Shapefiles
will show up as “Unknown” in
ArcMap
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
33
Geoprocessing
3-33
ArcGIS 9.2 Geodatabase Extended
Geodatabase models
File-based,
High
MS SQL Express-based
Precision Storage (“64 bit”)
Spatial
reference
Vertical
coordinate systems
Enhanced
Transaction Model
History Replication
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
34
Geoprocessing
3-34
Three kinds of Geodatabases
1. Personal Geodatabase
Stored in Access. 2 GB Limit, but effective size is 250 to 500 MB.
2. File
Stored in file folder. Up to 1 TB per dataset. Any platform. Single
Geodatabase
editor and a few readers. Recommended.
3. ArcSDE
Stored in RDBMS (Oracle, SQL Server, DB2, Informix). Uses
Geodatabase
ArcSDE. Versioning and Multi-user Support. Recommended. .
Windows only. Single editor and a few readers. Legacy support.
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
35
Geoprocessing
3-35
File-based Geodatabases
Single user (no replication, versioning, or history)
Better than shapefiles / Access (pGDB) Supports
all features (raster, vector, terrain, annotation, etc.)
Query/draw 1+
faster
TB dataset limit, no overall size limit
Supports Uses
data compression (2:1 with most datasets)
a coverage-like directory structure (no INFO directory!)
Cross platform (Windows, Linux, Solaris)
Access (mdb) based Geodatabases still supported, but not encouraged
After 9.2 publish API for File Geodatabase
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
36
Geoprocessing
3-36
Pre-9.2 geodatabases
Pre-9.2 geodatabases use 32-bit integers
Limited to 0 – 2147483647 integers
Copyright © 2004-2007 ESRI. All rights reserved.
37
How many people here have seen this or a similar error? I think just about all of us have seen it. Well, we’re trying our best to make it go away! Pre-9.2 geodatabases store coordinates as 32-bit integers. You could only store values between zero and 2147483647. To map ‘real world’ coordinates to this range, you would set a domain and precision values. The domain defines the range of coordinate values, while the precision is the number of decimal places. These are all connected. In many of the tools, the default values for the domain and precision values were very generic.
Advanced Analysis with ArcGIS
Geoprocessing
3-37
Pre-9.2 default values
Spatial domain/precision defaults were useless
Doesn’t fit geographic or projected data
Conversion tools were better—checked data extents
Copyright © 2004-2007 ESRI. All rights reserved.
38
In fact, here are the defaults for a new feature class. The domain values are too small for data that’s using a projected coordinate system like State Plane or UTM, and the precision values is barely large enough for geographic coordinate system data. Everyone has problems with this. Even if you remember to open the spatial reference property page and set the coordinate system, it’s really easy to forget update the domain and precision values. Plus you have to figure out what values to use.
Advanced Analysis with ArcGIS
Geoprocessing
3-38
High precision 64-bit
storage
Actually, Range
it’s 53-bits
is 0 to 9007199254740990
ArcSDE
supports it already, ArcGIS couldn’t use
the data Equivalent
to double precision
Copyright © 2004-2007 ESRI. All rights reserved.
39
For version 9.2, we decided that we would change the geodatabase to what we’ve started to call high precision. In the past, you often heard this functionality called 64-bit. As it turns out, we actually use 53 bits which gives a range between zero and nine thousand trillion. ArcSDE has supported high precision data for several releases, but ArcGIS could not use it. High precision is practically equivalent to double precision.
Advanced Analysis with ArcGIS
Geoprocessing
3-39
Upgrading to high precision Two
parts
Upgrade
the geodatabase
Upgrade
feature dataset/class spatial reference
Will
not ‘shake’ the data
Copyright © 2004-2007 ESRI. All rights reserved.
40
You upgrade an existing geodatabase to version 9.2 in two parts. The first updates the database schema. Then if you choose to, you can update feature datasets or standalone feature classes to use a high precision spatial reference. The spatial reference upgrade won’t change your data. It won’t shake it. Even though we’re changing the spatial reference parameters, they’re designed to be compatible with the old values.
Advanced Analysis with ArcGIS
Geoprocessing
3-40
Upgrading to high precision
Black = original grid
Blue = new grid, 4x
Rose = 16x
0.5, 1.0 0.0, 1.0
1.0, 1.0
0.75, 0.75
0.25, 0.75
1.0, 0.5
0.0, 0.5
0.75, 0.25
0.25, 0.25
0.0, 0.0
1.0, 0.0 0.5, 0.0
Copyright © 2004-2007 ESRI. All rights reserved.
41
The pre-9.2 feature class, which is using black, has a resolution of one. Coordinates have to be at least 1 unit apart. Depending on the coordinate system and existing resolution, the new grid will be an exact multiple of the original. In this picture I have two possible 9.2 grids. The blue grid is four times as dense as the original. You can see that it coincides were it can with the original grid. A new coordinate which is being stored in the feature class *here*, would snap to the nearest corner here, at 0.5 units. The new grid could also be 16 times as dense, so that a new coordinate *here* would now snap to 0.75, 0.25.
Advanced Analysis with ArcGIS
Geoprocessing
3-41
Tolerance, resolution, and precision Tolerance—data Minimum:
accuracy
2x resolution value
Resolution—1/precision Minimum In
distance between 2 coordinate values
the units of the coordinate system
Storage
precision
Precision—number
of decimal places
XYUnits
Copyright © 2004-2007 ESRI. All rights reserved.
42
There are two new concepts that you’ll need to learn. The first is that very feature class now has tolerance values. The tolerance values should correspond to the data’s accuracy. They are used when editing data or when comparing features. We’ve also upended the precision/XYunits concept. The resolution is simply the inverse of the precision. It’s in the units of the coordinate system, and it’s the storage precision. If I set the XY resolution for a feature class to 1 meter, I can only store coordinates that are at least 1 meter apart.
Advanced Analysis with ArcGIS
Geoprocessing
3-42
New feature dataset/class wizards Completely Less
reworked
things are hiding on the last panel
Point/line/polygon Spatial
reference
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
43
Geoprocessing
3-43
Create FD/FC wizard DEMO
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
44
Geoprocessing
3-44
Defining a high precision SR ISpatialReference pSR; ISpatialReferenceFactory2 pSRF = new SpatialReferenceEnvironmentClass(); ISpatialReferenceResolution pSRResolution; IControlPrecision2 pControlPrecision2; pSR = (ISpatialReference) pSRF.CreateESRISpatialReferenceFromPRJFile ("C:\\WGS 1984.prj"); pControlPrecision2 = (IControlPrecision2)pSR; pControlPrecision2.IsHighPrecision = true; pSRResolution = (ISpatialReferenceResolution)pSR; pSRResolution.ConstructFromHorizon(); pSRResolution.SetDefaultXYResolution(); Copyright © 2004-2007 ESRI. All rights reserved.
45
Whenever you create a spatial reference, you need to set the spatial domain and resolution or precision, depending on which version you are using. In this case, I’ll show you how to define the values automatically. First I create the coordinate system part of the spatial reference by reading in a WKT version from a file. This is using ISpatialReferenceFactory2. Then I set the precision of the spatial reference—will it be high or low? Is this case, I set it to high precision. I then cast to ISpatialReferenceResolution and use ConstructFromHorizon to set the spatial domain, based on the coordinate system. The horizon is the valid area of use of the coordinate system. I then also set the default XY resolution value. Although I don’t show it, you should also set the XY tolerance value. That’s on ISpatialReferenceTolerance.
Advanced Analysis with ArcGIS
Geoprocessing
3-45
Vertical coordinate systems Can
define on vector data
Transformations Supports
not supported yet
geoid-based and ellipsoid-based
heights Heights/Depths
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
46
Geoprocessing
3-46
WKT version VERTCS["NAVD_1988", VDATUM["North_American_Vertical_Datum_1988"], PARAMETER["Vertical_Shift",0.0], PARAMETER["Direction",1.0], UNIT["Meter",1.0]]
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
47
Geoprocessing
3-47
Creating a vertical coordinate system ISpatialReferenceFactory3 pSRF3 = new SpatialReferenceEnvironmentClass(); IVerticalCoordinateSystem pVCS = (IVerticalCoordinateSystem) pSRF3.CreateVerticalCoordinateSystem( (int)esriSRVerticalCSType.esriSRVertCS_NAVD1988); IGeographicCoordinateSystem pGCS = (IGeographicCoordinateSystem) pSRF3.CreateGeographicCoordinateSystem( (int)esriSRGeoCSType.esriSRGeoCS_NAD1983); ISpatialReference3 pSR3; pSR3 = (ISpatialReference3)pGCS; pSR3.VerticalCoordinateSystem = pVCS; Copyright © 2004-2007 ESRI. All rights reserved.
48
You can use ISpatialReferenceFactory3 to create a vertical coordinate system, just like the other coordinate system types. The method is CreateVerticalCoordinateSystem, and there is an enumeration, esriSRVerticalCSType that contains around 80 entries. You can only combine a VCS with a SpatialReference that is using a GCS or PCS. You can’t have an UnknownCoordinateSystem. Cast to the ISpatialReference3 interface, which has a read/write VerticalCoordinateSystem method.
Advanced Analysis with ArcGIS
Geoprocessing
3-48
Vertical CS and transformations Rasters Add
still need to store VCS
transformation methods
Geoid
models (geoid/ellipsoid height conversion)
VERTCON Single
shift
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
49
Geoprocessing
3-49
Summary PUG
issues
New
or updated features in ArcGIS 9.2
Create
Custom Geographic/Datum Transformation
MGRS/USNG High
precision geodatabases
Vertical
coordinate systems
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
50
Geoprocessing
3-50
New issues or questions?
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
51
Geoprocessing
3-51
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
Geoprocessing
3-1
Overview The
List
What’s
new at 9.2
Create
Custom GeoTransformation tool
Measure
Tool / Calculate Geometry
MGRS/USNG Goode’s
Homolosine
Geodatabase: Vertical
coordinate systems
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
high versus low
2
Geoprocessing
3-2
231/86: Cannot edit a geometric network in a projected ArcMap data view Not
supported yet at 9.2
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
3
Geoprocessing
3-3
ID ?: Datum handling Implement Easier Has
Not
Shell-developed solution
UI to set transformations
defaults based on location
for 9.3; will review for next major release
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
4
Geoprocessing
3-4
232/87: Datum info not exposed Multiple Datum
issues are listed here
transformation management tool
Supporting
info like areas of use and accuracies not currently available
When
we go to DBMS version of library can add this
info GP
Project tool doesn’t show parameter values: NIM005479
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
5
Geoprocessing
3-5
208/60: IDs for custom coordsys (IMS/SDE) PEOBJEDITHOME Environment Uses Will
text files to define coordsys/transformations
slow down software
Longer Want Plan
term
to switch to an EPSG-like database
to allow addition of custom definitions
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
variable
6
Geoprocessing
3-6
253/110: dimensioning tools More May
information requested
include
Dimension Use
in layout mode
geodesic/great circle distances
Dimension
polygons with geodetic areas
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
7
Geoprocessing
3-7
249/106: GRID, workstn vs ArcGIS coordsys GRIDs
use the workstation coordsys format
Spatial
Analyst uses grids internally
Update
to workstation is unlikely
Currently,
we feel that maintaining both definitions is too difficult
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
8
Geoprocessing
3-8
Polynomial transformations Polynomial-based
transformations: post-9.3; in
top 5 issues
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
9
Geoprocessing
3-9
202/50: Predefined datum and proj shift params “Create
Custom Geog Transformation” tool
Requested
Improvements
Make
the .gtf files true ASCII – right now they include binary information so ArcGIS can read/write them
Add
save functionality to the “New” transformation dialog in ArcMap (NIM006269)
Env.
setting to change location of gtf files
Include Ability
a description (if we go to a dbms PE version)
to set a transformation per layer in ArcMap
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
10
Geoprocessing
3-10
46: Projection on-the-fly (ArcPad) Currently,
rasters and GPS tracklog shapefile can be reprojected
ESRI
would like use cases that require vector data to be reprojected (in large scale field work)
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
11
Geoprocessing
3-11
211/64: Projection on the fly very slow Improving For Is If
performance occurs at each release
9.2, added a “projection hint” the data completely within the projection horizon? so, no need to intersect
Rasters:
very fast
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
12
Geoprocessing
3-12
79/23: Projection transformation options ArcIMS:
Allow a mapservice to support multiple co-ordinate systems
Not
planned for ArcIMS
Check
out ArcGIS Server.
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
13
Geoprocessing
3-13
201/49: Store datum/proj shift info in metadata GP
tools now store all messages
Still
to do:
Expose
this information in ArcCatalog
For
other procedures that change coordinate system, also store in the metadata
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
14
Geoprocessing
3-14
Closed issues
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
15
Geoprocessing
3-15
75: Map transformations misleading ArcMap’s
transformation UI will show a ‘default’ one, but must click OK for it to be applied
Default
is now
Closed
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
16
Geoprocessing
3-16
127: Rotate projected images Added
to ArcGIS 9.2.
Closed
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
17
Geoprocessing
3-17
135: Raster reprojection GP
Project raster tool didn’t support datum transformations
Added
to ArcGIS 9.2
Closed
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
18
Geoprocessing
3-18
26: Seamless CAD/GIS integration Georeferencing
toolbar now supports CAD data
Closed
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
19
Geoprocessing
3-19
Changes for ArcGIS 9.2
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
20
Geoprocessing
3-20
Geoprocessing Tools
didn’t support geographic/datum transformations
Use
ArcToolbox environment to set up output coordinate system and geographic transformation
Models
now support iterations
Copyright © 2004-2007 ESRI. All rights reserved.
21
A major change to geoprocessing at 9.2 is a change to the environment settings. It’s not widely enough known, but most of the data conversion tools, or any tool that allows you to set the output coordinate system/spatial reference, generally do not support datum transformations. You might use the Feature Class to Feature Class wizard, set the output coordinate system *here* in the general settings portion of the Geoprocessing environment, this is all you could set, and assume that a datum transformation from NAD27 to NAD83 would occur. That’s not the case before 9.2, and if you don’t set a geographic/datum transformation here, it still would not occur correctly. You can only set a single coordinate system, and a single geographic transformation. This is particularly important because the system does have a ‘default’ transformation between NAD27 and NAD83. Unfortunately, it’s the one for the lower 48, so Alaska and Hawai’i have to do some extra work.
Advanced Analysis with ArcGIS
Geoprocessing
3-21
Tool dialogs All
tools support batch processing at 9.2
More
flexible, as the tool is run for each input
data Right
click the tool to access the batch option
Copyright © 2004-2007 ESRI. All rights reserved.
22
All tool dialogs now support batch processing. There’s a new control that places all the parameters for a tool into a table, and you just fill out the table. This is more flexible than some of the existing batch tools, like the Batch Project Tool. That tool created a list of feature classes as a single string which was a parameter to a special batch project command. There’s a limit on how long that string could be. The batch table control, runs the tool as many times as it needs to, so you don’t have that type of limitation. Right click a tool (open its context menu) to access the batch option.
Advanced Analysis with ArcGIS
Geoprocessing
3-22
Project tool (feature) Input data
Output data Output coordsys Geographic / datum transformation
Copyright © 2004-2007 ESRI. All rights reserved.
23
To give us a starting point, here is the project tool for features. The green dots denote required parameters. For this tool, you have to fill out the input data including path, output path and data name, and the output coordinate system. I haven’t labeled it, but greyed out is the input coordinate system. It will be populated automatically, once you enter the input data. The last parameter is the geographic (datum) transformation. It’s marked optional, which is really confusing. The geoprocessing tool dialogs are really a GUI or user friendly interface to a scripting/command line world. So the parameters here reflect how you would use the tool on the command line. So, if the input and output geographic coordinate systems are the same, no transformation is needed— thus, optional. If the input/output geographic coordsys are different, then it’s a required parameter.
Advanced Analysis with ArcGIS
Geoprocessing
3-23
Required transformation
NAD27
NAD83 Geographic / datum transformation
Copyright © 2004-2007 ESRI. All rights reserved.
24
Now I’ve filled out the input feature class, which is georeferenced to NAD27. The output coordinate system is NAD83. Because they’re different, the ‘optional’ transformation parameter is now required—it has a green dot, and you can use the pull-down to see the possible transformations.
Advanced Analysis with ArcGIS
Geoprocessing
3-24
Project tool (feature) – batch option Input data Output data
Output coordsys
Copyright © 2004-2007 ESRI. All rights reserved.
Geographic / datum transformation
25
Here is the batch option of the Project tool for features. Right-click on the tool to open the batch version. And what you end up with is a table, with all the parameters of the tool. Just like the tool, anything colored green is a required field—input data, output data, output coordinate system. A white field is either truly optional, or like the geographic transformation may become required as you fill in the other fields. Use the plus button to add more rows, and you can copy and paste values between the rows. Select a field, and you can type directly into it, double click, and it will open a tool dialog with just that value, or right click to also open the dialog, fill the fields above or below with the current value, and so on.
Advanced Analysis with ArcGIS
Geoprocessing
3-25
Identify Tool Enhancements
Identify features by dragging a box
Sort Records, Sort Fields and modify Field Visibility
Copy Location X,Y coordinates Alter
Location units (DD, Feet, Meters)
Copyright © 2004-2007 ESRI. All rights reserved.
26
The Identify Tool has had a major overhaul at 9.2 and includes some really nice new functionality. One of the new enhancements is that you can now draw a rectangle and the identify tool will populate the results dialog with a records within the box. The results dialog allows you to sort the records, sort the fields, and even toggle field visibility.
Advanced Analysis with ArcGIS
Geoprocessing
3-26
Navigate to X,Y Location Map
units
Decimal
Degrees
Degrees
Minutes Seconds
Copyright © 2004-2007 ESRI. All rights reserved.
27
A new Zoom to XY Tool has been added to ArcMap making if very easy to zoom directly to a location on the map. Users can easily specify to search for X,Y locations based upon map units, Decimal Degrees, or even Degrees, Minutes, Seconds.
Advanced Analysis with ArcGIS
Geoprocessing
3-27
Measure Tool Enhancements Measure
Area/Length in multiple unit types
Measure
Individual Feature
Snapping Summarize
multiple measures
Copyright © 2004-2007 ESRI. All rights reserved.
28
Like the Identify Tool, the Measure tool has gotten an overhaul at 9.2. A new dialog is presented when using this tool to simplify measuring lines or areas and even provides options for change the units on-the-fly that are reported. Snapping is now available as an option to make measuring more precise. The measure feature option, makes it easier than ever to report the length or area of a specific feature and you can even have the dialog sum the results of multiple measurements!
Advanced Analysis with ArcGIS
Geoprocessing
3-28
Calculating Geometry Area/Length/Centroid/XY Easily
perform Geometry Calculations
Area Perimeter Length X
Location
Y
Location
Centroid
X
Centroid
Y
Copyright © 2004-2007 ESRI. All rights reserved.
29
9.2 Introduces a very powerful and easy way to calculate area and perimeter of polygons, length of lines, and individual X and Y locations for points. The units can be user defined making is easy to calculate acreage for parcels, hectares for agricultural fields, and length in miles of streets. Unlike Geodatabase feature classes, Shapefiles do not natively manage shape/geometry measurements like area and perimeter for polygons or the length for lines. However, the new Calculate Geometry functionality makes it easier than ever to manage this information. Finally, individual X and Y fields can be calculated for point features or polygon centroids in map units, Decimal Degrees or even Degrees/Minutes/Seconds when the Data Frame’s Spatial Reference is set to a Geographic Coordinate System.
Advanced Analysis with ArcGIS
Geoprocessing
3-29
MGRS and USNG New
method in ArcObjects
Calculate
Geometry
Navigate/Go
to X/Y
Identify
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
30
Geoprocessing
3-30
Goode’s Homolosine
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
31
Geoprocessing
3-31
Goode’s Homolosine
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
32
Geoprocessing
3-32
GCS_Assumed_Geographic_1 No
longer supported
Shapefiles
will show up as “Unknown” in
ArcMap
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
33
Geoprocessing
3-33
ArcGIS 9.2 Geodatabase Extended
Geodatabase models
File-based,
High
MS SQL Express-based
Precision Storage (“64 bit”)
Spatial
reference
Vertical
coordinate systems
Enhanced
Transaction Model
History Replication
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
34
Geoprocessing
3-34
Three kinds of Geodatabases
1. Personal Geodatabase
Stored in Access. 2 GB Limit, but effective size is 250 to 500 MB.
2. File
Stored in file folder. Up to 1 TB per dataset. Any platform. Single
Geodatabase
editor and a few readers. Recommended.
3. ArcSDE
Stored in RDBMS (Oracle, SQL Server, DB2, Informix). Uses
Geodatabase
ArcSDE. Versioning and Multi-user Support. Recommended. .
Windows only. Single editor and a few readers. Legacy support.
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
35
Geoprocessing
3-35
File-based Geodatabases
Single user (no replication, versioning, or history)
Better than shapefiles / Access (pGDB) Supports
all features (raster, vector, terrain, annotation, etc.)
Query/draw 1+
faster
TB dataset limit, no overall size limit
Supports Uses
data compression (2:1 with most datasets)
a coverage-like directory structure (no INFO directory!)
Cross platform (Windows, Linux, Solaris)
Access (mdb) based Geodatabases still supported, but not encouraged
After 9.2 publish API for File Geodatabase
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
36
Geoprocessing
3-36
Pre-9.2 geodatabases
Pre-9.2 geodatabases use 32-bit integers
Limited to 0 – 2147483647 integers
Copyright © 2004-2007 ESRI. All rights reserved.
37
How many people here have seen this or a similar error? I think just about all of us have seen it. Well, we’re trying our best to make it go away! Pre-9.2 geodatabases store coordinates as 32-bit integers. You could only store values between zero and 2147483647. To map ‘real world’ coordinates to this range, you would set a domain and precision values. The domain defines the range of coordinate values, while the precision is the number of decimal places. These are all connected. In many of the tools, the default values for the domain and precision values were very generic.
Advanced Analysis with ArcGIS
Geoprocessing
3-37
Pre-9.2 default values
Spatial domain/precision defaults were useless
Doesn’t fit geographic or projected data
Conversion tools were better—checked data extents
Copyright © 2004-2007 ESRI. All rights reserved.
38
In fact, here are the defaults for a new feature class. The domain values are too small for data that’s using a projected coordinate system like State Plane or UTM, and the precision values is barely large enough for geographic coordinate system data. Everyone has problems with this. Even if you remember to open the spatial reference property page and set the coordinate system, it’s really easy to forget update the domain and precision values. Plus you have to figure out what values to use.
Advanced Analysis with ArcGIS
Geoprocessing
3-38
High precision 64-bit
storage
Actually, Range
it’s 53-bits
is 0 to 9007199254740990
ArcSDE
supports it already, ArcGIS couldn’t use
the data Equivalent
to double precision
Copyright © 2004-2007 ESRI. All rights reserved.
39
For version 9.2, we decided that we would change the geodatabase to what we’ve started to call high precision. In the past, you often heard this functionality called 64-bit. As it turns out, we actually use 53 bits which gives a range between zero and nine thousand trillion. ArcSDE has supported high precision data for several releases, but ArcGIS could not use it. High precision is practically equivalent to double precision.
Advanced Analysis with ArcGIS
Geoprocessing
3-39
Upgrading to high precision Two
parts
Upgrade
the geodatabase
Upgrade
feature dataset/class spatial reference
Will
not ‘shake’ the data
Copyright © 2004-2007 ESRI. All rights reserved.
40
You upgrade an existing geodatabase to version 9.2 in two parts. The first updates the database schema. Then if you choose to, you can update feature datasets or standalone feature classes to use a high precision spatial reference. The spatial reference upgrade won’t change your data. It won’t shake it. Even though we’re changing the spatial reference parameters, they’re designed to be compatible with the old values.
Advanced Analysis with ArcGIS
Geoprocessing
3-40
Upgrading to high precision
Black = original grid
Blue = new grid, 4x
Rose = 16x
0.5, 1.0 0.0, 1.0
1.0, 1.0
0.75, 0.75
0.25, 0.75
1.0, 0.5
0.0, 0.5
0.75, 0.25
0.25, 0.25
0.0, 0.0
1.0, 0.0 0.5, 0.0
Copyright © 2004-2007 ESRI. All rights reserved.
41
The pre-9.2 feature class, which is using black, has a resolution of one. Coordinates have to be at least 1 unit apart. Depending on the coordinate system and existing resolution, the new grid will be an exact multiple of the original. In this picture I have two possible 9.2 grids. The blue grid is four times as dense as the original. You can see that it coincides were it can with the original grid. A new coordinate which is being stored in the feature class *here*, would snap to the nearest corner here, at 0.5 units. The new grid could also be 16 times as dense, so that a new coordinate *here* would now snap to 0.75, 0.25.
Advanced Analysis with ArcGIS
Geoprocessing
3-41
Tolerance, resolution, and precision Tolerance—data Minimum:
accuracy
2x resolution value
Resolution—1/precision Minimum In
distance between 2 coordinate values
the units of the coordinate system
Storage
precision
Precision—number
of decimal places
XYUnits
Copyright © 2004-2007 ESRI. All rights reserved.
42
There are two new concepts that you’ll need to learn. The first is that very feature class now has tolerance values. The tolerance values should correspond to the data’s accuracy. They are used when editing data or when comparing features. We’ve also upended the precision/XYunits concept. The resolution is simply the inverse of the precision. It’s in the units of the coordinate system, and it’s the storage precision. If I set the XY resolution for a feature class to 1 meter, I can only store coordinates that are at least 1 meter apart.
Advanced Analysis with ArcGIS
Geoprocessing
3-42
New feature dataset/class wizards Completely Less
reworked
things are hiding on the last panel
Point/line/polygon Spatial
reference
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
43
Geoprocessing
3-43
Create FD/FC wizard DEMO
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
44
Geoprocessing
3-44
Defining a high precision SR ISpatialReference pSR; ISpatialReferenceFactory2 pSRF = new SpatialReferenceEnvironmentClass(); ISpatialReferenceResolution pSRResolution; IControlPrecision2 pControlPrecision2; pSR = (ISpatialReference) pSRF.CreateESRISpatialReferenceFromPRJFile ("C:\\WGS 1984.prj"); pControlPrecision2 = (IControlPrecision2)pSR; pControlPrecision2.IsHighPrecision = true; pSRResolution = (ISpatialReferenceResolution)pSR; pSRResolution.ConstructFromHorizon(); pSRResolution.SetDefaultXYResolution(); Copyright © 2004-2007 ESRI. All rights reserved.
45
Whenever you create a spatial reference, you need to set the spatial domain and resolution or precision, depending on which version you are using. In this case, I’ll show you how to define the values automatically. First I create the coordinate system part of the spatial reference by reading in a WKT version from a file. This is using ISpatialReferenceFactory2. Then I set the precision of the spatial reference—will it be high or low? Is this case, I set it to high precision. I then cast to ISpatialReferenceResolution and use ConstructFromHorizon to set the spatial domain, based on the coordinate system. The horizon is the valid area of use of the coordinate system. I then also set the default XY resolution value. Although I don’t show it, you should also set the XY tolerance value. That’s on ISpatialReferenceTolerance.
Advanced Analysis with ArcGIS
Geoprocessing
3-45
Vertical coordinate systems Can
define on vector data
Transformations Supports
not supported yet
geoid-based and ellipsoid-based
heights Heights/Depths
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
46
Geoprocessing
3-46
WKT version VERTCS["NAVD_1988", VDATUM["North_American_Vertical_Datum_1988"], PARAMETER["Vertical_Shift",0.0], PARAMETER["Direction",1.0], UNIT["Meter",1.0]]
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
47
Geoprocessing
3-47
Creating a vertical coordinate system ISpatialReferenceFactory3 pSRF3 = new SpatialReferenceEnvironmentClass(); IVerticalCoordinateSystem pVCS = (IVerticalCoordinateSystem) pSRF3.CreateVerticalCoordinateSystem( (int)esriSRVerticalCSType.esriSRVertCS_NAVD1988); IGeographicCoordinateSystem pGCS = (IGeographicCoordinateSystem) pSRF3.CreateGeographicCoordinateSystem( (int)esriSRGeoCSType.esriSRGeoCS_NAD1983); ISpatialReference3 pSR3; pSR3 = (ISpatialReference3)pGCS; pSR3.VerticalCoordinateSystem = pVCS; Copyright © 2004-2007 ESRI. All rights reserved.
48
You can use ISpatialReferenceFactory3 to create a vertical coordinate system, just like the other coordinate system types. The method is CreateVerticalCoordinateSystem, and there is an enumeration, esriSRVerticalCSType that contains around 80 entries. You can only combine a VCS with a SpatialReference that is using a GCS or PCS. You can’t have an UnknownCoordinateSystem. Cast to the ISpatialReference3 interface, which has a read/write VerticalCoordinateSystem method.
Advanced Analysis with ArcGIS
Geoprocessing
3-48
Vertical CS and transformations Rasters Add
still need to store VCS
transformation methods
Geoid
models (geoid/ellipsoid height conversion)
VERTCON Single
shift
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
49
Geoprocessing
3-49
Summary PUG
issues
New
or updated features in ArcGIS 9.2
Create
Custom Geographic/Datum Transformation
MGRS/USNG High
precision geodatabases
Vertical
coordinate systems
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
50
Geoprocessing
3-50
New issues or questions?
Copyright © 2004-2007 ESRI. All rights reserved.
Advanced Analysis with ArcGIS
51
Geoprocessing
3-51
