| Products & Services | Solutions | Academia | Support | User Community | Company |
| Download Product Updates | | | Get Pricing | | | Trial Software |
| Documentation → Mapping Toolbox |
| Contents | Index |
| Learn more about Mapping Toolbox |
This table summarizes what's new in Version 2.7.1 (R2008b):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
Yes | Yes — Details labeled as Compatibility Considerations in descriptions of changes, below. See also Summary. | Bug Reports at Web site | Printable Release Notes: PDF Current product documentation |
Changes and enhancements have been made to axesm, setm, and defaultm with respect to map axes properties that affect the fundamental display geometry:
MapProjection
Zone
Origin
FLatLimit
FLonLimit
MapLatLimit
MapLonLimit
The changes result in the following improvements:
The use of the map limit properties to set up a map axes is more intuitive.
The way in which defaultm resolves possible inconsistencies between these properties is now consistent with the behavior of axesm and setm.
The map limit properties (MapLatLimit and MapLonLimit), the frame limit properties (FLatLimit and FLonLimit), and the Origin, MapProjection, and Zone properties interact in a more clear and predictable fashion.
For more information, see the section Using the Map Limit Properties in the Mapping Toolbox™ User's Guide and bug report 319891 on the MathWorks Web site.
In previous releases, calling the setm function to change the MapProjection property of a map axes, especially when switching between an azimuthal and non-azimuthal projection (e.g., a conic or cylindrical projection), often resulted in the following types of problems:
The modified map axes might cover a different part of the Earth.
The map frame and graticule might fail to update properly.
Map limit properties changed at the same time as the projection might not have the proper effect.
The setm function now more effectively resets the projection, clearing out settings that were specific to the earlier projection, updating the map frame and graticule, and staying in the same general part of the world (even when switching between azimuthal and non-azimuthal projections).
You may need to change the way in which you reset various map axes properties, such as Origin, FLatLimit, and FLonLimit after changing projections, as discussed in the section Switching Between Projections in the Mapping Toolbox User's Guide. In many cases it will no longer be necessary to reset as many properties.
The default FLatLimit for lambert and lambertstd has been changed to [-45 45]. In previous releases, axesm produced huge map frames, due to the FLatLimit default of [-90 90].
The function gridm now returns handles to the line objects used to display the parallels and meridians. In previous releases, a call to gridm using linespec or property name/property value syntaxes returned empty.
The function geotiff2mstruct no longer sets the maplatlimit and maplonlimit fields.
A reference ellipsoid set to a non-default value (via the geoid property) no longer reverts to the default when the UTM zone is reset. For more information, see bug report 459353 on the MathWorks Web site.
The daspectm function now works for azimuthal projections and units of radians.
Portions of the global coastline latitude-longitude vectors in the coast.MAT data file have been revised to ensure proper polygon topology. The data edits comprise the following:
Replacing or removing various "bow-tie" and degenerate linear (non-polygonal) island features.
Opening a "pinched" section in the middle of Lake Balkhash in Central Asia.
Merging the eastern and western sections of Wrangel Island near the Bering Strait (cut by the 180-degree meridian) into a single polygon with longitudes ranging from slightly less than 180 to slightly greater than 180.
Eight additional edits to pull apart landmasses with points of contact and remove coastal "spikes."
The following syntaxes are obsolete. An error occurs if you use them.
pcolorm(Z)
pcolorm(Z,gratsize)
surfacem(Z)
surfacem(Z,gratsize)
surflm(Z)
surflm(Z,s)
surfm(Z)
surfm(Z,gratsize)
These syntaxes displayed a data grid with geographic limits that matched the map latitude and longitude limits in the current map axes. Using the old syntaxes correctly involved knowing the latitude and longitude limits of your data and matching them to the values listed under maplatlimit and maplonlimit in the map axes properties. We have replaced these syntaxes with a more direct approach that requires you to enter the latitude and longitude limits for the data grid.
The table below suggests alternative code to replace the obsolete syntaxes. In the following table, Z is a regular data grid (a 2-D array of class double) and gratsize is a two-element vector specifying the size of the graticule on which Z displays:
gratsize = [number_of_parallels number_of_meridians]
h is a handle to the surface that is displayed. And latlim and lonlim are the geographic limits of the data grid (in degrees):
latlim = [southern_limit northern_limit]
lonlim = [western_limit eastern_limit]
| Original Syntax | Replacement Syntax |
|---|---|
h = pcolorm(Z) constructs a surface using the regular data grid Z and a graticule mesh (using meshgrat) with size equal to size(Z) and with geographic limits that match the map latitude and longitude limits in the current map axes. | [lat,lon] = meshgrat(latlim,lonlim,size(Z)); h = pcolorm(lat,lon,Z) |
h = pcolorm(Z,gratsize) uses a graticule mesh with size equal to gratsize. | [lat,lon] = meshgrat(latlim,lonlim,gratsize); h = pcolorm(lat,lon,Z) |
h = surfacem(Z) constructs a surface using the regular data grid Z and a graticule mesh (using meshgrat) of size 50-by-100. The geographic limits match the map latitude and longitude limits in the current map axes. | h = surfacem(latlim,lonlim,Z) |
h = surfacem(Z,gratsize) uses a graticule mesh with size equal to gratsize. | [lat,lon] = meshgrat(latlim,lonlim,gratsize); h = surfacem(lat,lon,Z) |
h = surflm(Z) constructs a surface using the regular data grid Z and a graticule mesh (using meshgrat) with size equal to size(Z) and with geographic limits that match the map latitude and longitude limits in the current map axes. It is displayed with a default light source. | h = surflm(latlim,lonlim,Z) |
h = surflm(Z,s) specifies the direction of the light source. s is a two- or three-element vector that specifies the direction from the surface map to the light source as defined in the documentation for surfl. | h = surflm(latlim,lonlim,Z,s) |
h = surfm(Z) constructs a surface using the regular data grid Z and a graticule mesh (using meshgrat) with size equal to size(Z) and with geographic limits that match the map latitude and longitude limits in the current map axes. | h = surfm(latlim,lonlim,Z) |
h = surfm(Z,gratsize) uses a graticule mesh with size equal to gratsize. | [lat,lon] = meshgrat(latlim,lonlim,gratsize); h = surfm(lat,lon,Z) |
![]() | Version 2.7.2 (R2009a) Mapping Toolbox Software | Version 2.7 (R2008a) Mapping Toolbox Software | ![]() |

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