User manual MATLAB MAPPING TOOLBOX RELEASE NOTES

[. . . ] Mapping ToolboxTM Release Notes How to Contact The MathWorks Web Newsgroup www. mathworks. com/contact_TS. html Technical Support www. mathworks. com comp. soft-sys. matlab suggest@mathworks. com bugs@mathworks. com doc@mathworks. com service@mathworks. com info@mathworks. com Product enhancement suggestions Bug reports Documentation error reports Order status, license renewals, passcodes Sales, pricing, and general information 508-647-7000 (Phone) 508-647-7001 (Fax) The MathWorks, Inc. 3 Apple Hill Drive Natick, MA 01760-2098 For contact information about worldwide offices, see the MathWorks Web site. Mapping ToolboxTM Release Notes © COPYRIGHT 2000­2010 by The MathWorks, Inc. The software described in this document is furnished under a license agreement. The software may be used or copied only under the terms of the license agreement. [. . . ] Such an encoding is no longer used internally by Mapping Toolbox functions, as it is not self-documenting and can lead to erroneous computations. For example, two DMS-encoded real numbers cannot be added to obtain a meaningful result. 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 scalar DM and DMS encodings are being eliminated from the toolbox because they were never used for internal computations, and always had the potential to generate serious numerical errors if passed accidently to functions that expected normal latitude-longitude tuples. They also made the functions that accepted them less efficient due to the need to convert from DM or DMS to fractional latitudes and longitudes before processing the input data. The following existing functions (which all use scalar DMS encoding) are being retired. They remain available but now issue warnings that they are obsolete when used: · deg2dm -- Instead use degrees2dm to convert degrees to degrees-minutes vector 52 Version 2. 5 (R2007a) Mapping ToolboxTM Software · deg2dms -- Instead use degrees2dms to convert degrees to degrees-minutes-seconds vector · dms2deg -- Instead use dms2degrees to convert degrees-minutes-seconds vector to degrees · 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: angl2str angledim antipode areaint areamat areaquad axesm azimuth distance eastof elevation ellipse1 epsm eqa2grn gc2sc gcxgc histr imbedm interpm intrplat intrplon mapprofile meanm meshgrat putpole rcurve reckon rhxrh rotatem rsphere scaleruler scircle1 stdist stdm timezone track track1 track2 unitstr westof 53 Mapping ToolboxTM Release Notes convertlat crossfix daspectm departure gcxsc gradientm grn2eqa hista neworig newpole npi2pi org2pol scircle2 scxsc setm smoothlong zero22pi These functions now issue warnings when provided 'dm' or 'dms' for their units argument. Time Conversion Functions to be Removed The following functions to convert between time units and encodings will be removed from a future release of the toolbox: · hms2hr · hms2hm · hms2mat · hms2sec · hr2hm · hr2hms · hr2sec · mat2hms · sec2hm · sec2hms · sec2hr · time2str · timedim Compatibility Considerations These functions remain available, but when they are invoked now issue warnings that they are obsolete. 54 Version 2. 4 (R2006b) Mapping ToolboxTM Software Version 2. 4 (R2006b) Mapping Toolbox Software This table summarizes what's new in Version 2. 4 (R2006b): New Features and Changes Yes Details below Version Compatibility Considerations Yes -- Details in "Changes in Behavior of mapshow and geoshow" on page 56 below. Fixed Bugs and Known Problems Bug reports at Web site Related Documentation at Web Site Printable Release Notes: PDF Current product documentation New features and changes introduced in this version are · "Standard Formulations of Five Major Map Projections" on page 55 · "Two New Geodetic/Geocentric Latitude Conversion Functions" on page 56 · "Accelerated Performance for geoshow, mapshow, and bufferm" on page 56 · "Changes in Behavior of mapshow and geoshow" on page 56 · "dted Automatically Fixes Incorrectly Specified Longitude Directions in DTED Data" on page 60 Standard Formulations of Five Major Map Projections New formulations of five conic map projections are provided. The existing implementations remain available under their old names. The new versions use the same names as the ones they supplement, appended with "std": · Cassini Transverse Cylindrical (cassinistd) · Albers Equal-Area Conic (eqaconicstd) · Equidistant Conic (eqdconicstd) · Lambert Conformal Conic (lambertstd) 55 Mapping ToolboxTM Release Notes · Polyconic (polyconstd) Computations used for the new versions differ from the old ones only when the latitude origin (the first element of the origin vector) is nonzero. In this case, the old versions shift the origin off the equator through a solid body rotation of the sphere (or, for an ellipsoidal earth model, a suitable auxiliary sphere). This is technically correct, but differs from accepted industry standards for these projections. The new versions use the standard formulations and give results that are consistent with projection results from other software packages, regardless of the latitude origin. The old versions are retained in the toolbox, with no change in behavior, to ensure backward compatibility. See the Projections Reference documentation for more information. Two New Geodetic/Geocentric Latitude Conversion Functions Two new functions provide a more direct route to functionality already available via the convertlat function: · geocentric2geodeticlat converts an array of geocentric latitude in radians to geodetic latitude in radians on a reference ellipsoid given a first eccentricity · geodetic2geocentriclat converts an array of geodetic latitude in radians to geocentric latitude in radians on a reference ellipsoid given a first eccentricity. Accelerated Performance for geoshow, mapshow, and bufferm Functions geoshow, mapshow, and bufferm run substantially faster in many cases, especially when vector display is being controlled via symbol specs in mapshow and geoshow. Changes in Behavior of mapshow and geoshow In addition to operating faster, the mapshow and geoshow functions now behave slightly differently regarding their defaults, handles returned, warnings issued, and several other aspects: 56 Version 2. 4 (R2006b) Mapping ToolboxTM Software Default Symbols and Colors · Point marker type changes from 'X' to '+' · Point marker color changes from 'black' to 'red' · Line color changes from 'black' to 'blue' · Polygon facecolor changes from 'black' to pale yellow Polygon edgecolor remains 'black' Contour DisplayType Behavior Changes · The DisplayType option 'contour' now returns an hggroup handle. The children of the hggroup are patches. In prior versions, an array of line handles was returned. · You can specify any contourgroup property as a parameter value pair. In previous versions, mapshow allowed you to set the LineStyle property, but no other contour properties. · Both mapshow and geoshow might return a different number of contour levels by default than in previous versions, in which you could not specify contour intervals; in R2006b, you can control contour intervals and levels via the LevelStep or LevelList contourgroup properties, among others. · In R2006b, when plotting contours on a regular axes (not a map axes), geoshow projects the contour lines using a Plate Carree projection; in previous versions it simply displayed longitudes as x and latitudes as y without doing any trimming or longitude wrapping. Graphic Objects and Return Values for Vector Inputs · Vector coordinate array input (x-y or latitude-longitude pairs) with a DisplayType of 'Line' or 'Point' now generates an ordinary line object instead of a map graphics line. [. . . ] These changes also correct distdim results for both statute miles and feet (assuming U. S. Survey Foot). tigerp Terminates file read properly when an empty data point is encountered (signaling end of data) worldmap No longer generates errors when there is no data to display within the specified latitude/longitude limits; it now displays complete mesh, even for data grids (matrix maps) that span all longitudes 106 Version 1. 3 (R13) Mapping ToolboxTM Software Version 1. 3 (R13) Mapping Toolbox Software This table summarizes what's new in Version 1. 3 (R13): New Features and Changes Yes Details below Version Compatibility Considerations Fixed Bugs and Known Problems Related Documentation at Web Site No Yes -- Details in Fixed Bugs "Compatibility Considerations" on page 108 below. See also Summary. New features and changes introduced in this version are · "New northarrow Annotation Function" on page 107 · "New mlabelzero22pi Axes Label Command" on page 107 · "Enhanced clegendm Contour Annotation Function" on page 108 · "New Interactive Interface" on page 108 · "Updated Atlas Data" on page 108 · "Ellipses Now Drawn More Smoothly" on page 108 · "Compatibility Considerations" on page 108 New northarrow Annotation Function The new northarrow function lets you add a north arrow symbol to a map, pointing to geographic north. You can reposition a north arrow by clicking and dragging it, or adjust other properties such as position, color, and size via alternate-clicking. New mlabelzero22pi Axes Label Command The new mlabelzero22pi command converts meridian labels to use the range 0 to 360 degrees, instead of the default -180 to 180 degrees. 107 Mapping ToolboxTM Release Notes Enhanced clegendm Contour Annotation Function The clegendm function has been enhanced with a new, optional syntax that accepts a string indicating the contour line units. [. . . ]