User`s guide

R2012a
7-2
Data File Removal or Location Change
The following data files have been removed. (The data has been inlined in source code.)
toolbox/map/mapdisp/globedems.dat
toolbox/map/mapdisp/gtopo30s.dat
Also, the usgsdems.dat file has moved from mapdisp:
toolbox/map/mapdisp/usgsdems.dat
to mapformats:
toolbox/map/mapformats/usgsdems.dat
Compatibility Considerations
Before R2011b, you needed to include these three data files:
toolbox/map/mapdisp/globedems.dat
toolbox/map/mapdisp/gtopo30s.dat
toolbox/map/mapdisp/usgsdems.dat
and the –a flag when compiling code that used the functions, globedems, gtopo30s or
usgsdems. You no longer need to do this.
geotiffinfo Now Handles Noncompliant GeoTIFF Files
Changes to the geotiffinfo function allow it to handle non-compliant GeoTIFF files
better than in previous releases. If the GTModelTypeGeoKey is not set, geotiffinfo
now issues a warning, assumes that the model type is 'ModelTypeProjected',
and constructs a spatialRef.MapRasterReference object and a corresponding
RefMatrix. If the GTModelTypeGeoKey is set to the value 3 (geocentric model), then
geotiffinfo sets the ModelType field to 'ModelTypeGeocentric' rather than
empty (as in previous releases). When the ModelTiepointTag contains a nonsensical
corner latitude, geotiffinfo issues a warning and clamps the corner latitude value to
the interval [-90 90].
Compatibility Considerations
Before R2012a, if a GeoTIFF file did not include either the ModelTypeGeographic or
ModelTypeProjected tag, the geotiffinfo RefMatrix and SpatialRef fields were
empty. The empty tags led to the creation of degenerative files.