This release eliminates a performance degradation in function avhrrgoode. The ultimate problem, a bug involving inappropriate use of rhumb line distance calculations, had inconsequential effects in Version 2 and earlier but caused performance to slow drastically when combined with recent rhumb line improvements in Version 2.0.1.
It's now straightforward to use function axesm with 'MapLonLimit' values spanning the 180-degree meridian, such as [120 -60], without manually unwrapping the longitude (as in [120 300]). In this example, the western edge will be at 120 degrees east longitude and the eastern edge will be at 60 degrees west longitude (or, equivalently, 300 degrees east longitude). As a minor consequence, the value provided for 'MapLonLimit' should now always have the form [west east], even if east < west numerically. The form [east west] is no longer supported.
Functions contourm and contour3m now wrap contour and contour3, respectively, and no longer draw overlapping or intersecting lines at some contour levels.
Function elevation now reshapes its vector outputs to match the shape of its input coordinates, just like functions distance and azimuth.
Function elevation can now compute a line-of-sight azimuth that is appropriate to use with its elevation angle and slant range outputs. In earlier releases, one could only approximate the line-of-sight azimuth, using the geodesic or rhumb line azimuths provided by function azimuth.
Function ellipse1 now selects a point density based directly on the local curvature of the ellipse, with more points in areas of greater curvature. The new algorithm has a firm mathematical footing and, in the degenerate case of zero eccentricity, produces results identical to scircle1.
Functions framem, gridm, mlabel, and plabel now return handles consistently.
In earlier releases function gtopo30 was hard to use because data had to reside on disk in a directory structure that paralleled precisely the directory structure on a GTOPO30 CD-ROM. Now data can be read from a much more general directory structure.
Revisions to function gtopo30 correct errors reading multiple tiles near Antarctica and crossing the International Date Line (180-degree meridian).
Function inputm now allows three output arguments instead of up to two. The third output argument, button, makes it similar to ginput.
The altitude inputs, alt1 and alt2, to function los2 are now allowed to be vectors with sizes matching the latitude-longitude input vectors, as well as scalars.
Functions mapshow and geoshow now allow graphics to be saved into a FIG-file or MAT-file.
Function patchm now accepts a numeric scalar as its CDATA argument, just like patch, interpreting it as a index into the figure's color map.
This release fixes a problem with the and operation in function polybool, which implements set operations on polygonal regions, replacing it with a more robust and faster approach. In earlier releases over-sensitivivity to round-off error, when some vertices were very close together compared to other vertices, sometimes caused polybool to exit with an error.In addition (see the following three notes), Mapping 2.0.3 fixes other major problems with the polybool function. All these fixes rely on a major re-implementation which includes incompatible data structure and syntax changes. See the following section, "Upgrading from an Earlier Release," if you have existing applications that use polybool.
Function polybool now produces consistent output when computing intersections, with results no longer depending on the order of its inputs.
Function polybool now operates correctly on polygons with collinear edges.
This release corrects an inconsistency in the output of polysplit that could cause polybool to generate a vertcat error given certain inputs.
This release corrects an error in function polymerge which sometimes caused it to join segments incorrectly.
Functions polysplit and polyjoin now accept row vectors as well as column vectors.
Function shaderel no longer produces a divide-by-zero error when given a colormap with more than 128 values.
This release corrects a problem that caused function vmap0ui to error because it was unable to find private function vmap0do code>.

Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2010- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |