User`s guide

16-11
Compatibility Considerations
DM and DMS representations are widely used in published reports and can occur in
geodata that you want to read into the MATLAB workspace. You can still import and
export DM and DMS data, but Mapping Toolbox functions no longer accepts the old
encodings as alternatives to floating-point representations of latitude and longitude for
internal manipulations.
The following functions (which all use scalar DMS encoding) are being retired. They
remain in the product for R2007b, but now generate errors when used. They will be
removed completely in the next version. Use the alternative suggested in lieu of these
functions.
deg2dm — Instead use degrees2dm to convert degrees to degrees-minutes vector.
deg2dms — Instead use degrees2dms to convert degrees to degrees-minutes-seconds
vector.
dms2deg — Instead use dms2degrees to convert degrees-minutes-seconds vector to
degrees.
dms2dm — Instead combine dms2degrees and degrees2dm, as in
degrees2dm(dms2degrees([-29 42 18.7])) to remove the seconds component
from a degree-minutes-second vector.
dms2mat — Instead use degrees2dms to convert degrees to degrees-minutes-seconds
vector.
dms2rad — Instead use dms2degrees to convert degrees-minutes-seconds vector to
degrees and call degtorad or multiply by pi/180.
mat2dms — Instead use dms2degrees to convert degrees-minutes-seconds vector to
degrees.
rad2dm — Instead, call radtodeg or multiply input arguments by 180/pi, and then
call degrees2dm.
rad2dms — Instead, call radtodeg or multiply input arguments by 180/pi, and then
call degrees2dms.
In addition, the axesm and setm functions no longer accept the strings 'dms' and 'dm'
for setting either the AngleUnits or LabelUnits properties of a map axes.
Many other Mapping Toolbox functions optionally accept angle strings for their units
parameter; the following 57 functions now only accept 'degrees' and 'radians',
whereas in prior versions they would also accept 'dm' and 'dms' as values for units: