| Contents | Index |
This table summarizes what's new in Version 3.2 (R2010b):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems |
|---|---|---|
Yes | Yes — Details labeled as Compatibility Considerations in descriptions of changes, below. See also Summary. | Bug Reports at Web site |
New features and changes introduced in this version are:
Support for Retrieving Web Map Service Data in Image/BIL Format
polyxpoly Now Issues Warning when 'unique' Option Combined with Segment Indices
The Plot Selector workspace tool creates graphs of workspace variables. The mapshow and geoshow functions have been added to the list of possible plotting functions available in the Plot Selector. For more information about the Plot Selector, see Enhanced Plot Selector Simplifies Data Display.
Some servers render layers in the 'image/bil' format as a single band with a class type of int16 or int32. You can now use the wmsread function to retrieve this data.
The mapshow and geoshow functions now have expanded class support for raster data display.
The WMS Database changes on a release-to-release basis, as some new servers are added and some unavailable servers are removed. A total of 244 servers (10.4% of the number of servers listed in R2010a) and 111,514 layers have been removed from the database. A total of 380 new servers, with 65,834 layers, have been added. The new database contains a total of 2,502 servers and 300,848 layers. Some notable new servers in the database are:
242 new WMS servers from NOAA's Environmental Research Division Data Access Program (ERDDAP) (http://coastwatch.pfeg.noaa.gov/erddap/wms). These servers provide oceanographic data, and additional information about them may be found at http://coastwatch.pfeg.noaa.gov/erddap/info/index.html.
A server from the European Space Agency, removed in R2010a but now back in the Database (http://ssems1.esrin.esa.int/mapServer/mapServer?).
115 new servers from the DataFed Web Map Server (http://webapps.datafed.net).
Two new servers from NASA WorldWind WMS (http://www.nasa.network.com/elev? and http://www.nasa.network.com/wms?). The 'elev' server provides data in the 'image/bil' format.
Two new servers from the USGS dedicated to emergency operations. These servers provide imagery of the 2010 oil spill in the Gulf of Mexico:
http://hdds.usgs.gov/arcgis/services/... 201004_OilSpill_GulfOfMexico/MapServer/... WMSServer
and the 2010 earthquake in Haiti:
http://hdds.usgs.gov/ArcGIS/services/... 201001_Earthquake_Haiti/MapServer/... WMSServer?
The KML schema has been updated to Version 2.2.
The usastatelo shapefile now contains average population density data by state for the year 2000 from the U.S. Census Bureau Web site.
In the korea.mat file, the numbers in the referencing vector (the refvec) were very nearly integer valued. Elements of these variables have been rounded slightly to become exact integers, as follows:
[12 45 115]
If you use the new version of the korea.mat file, your results will be slightly different than those obtained with the older version of the file.
Due to a recent bug fix, the contouring functions now exhibit many improvements. The bug fix in question, Bug 192285, addressed problems with contours displayed by contourm, contour3m, and contourfm. The following figure illustrates filled contours produced by the contourfm function in R2010b, as compared to R2010a and earlier releases.
figure('Color','white');
worldmap world;
load geoid;
contourfm(geoid, geoidrefvec)

If you call any of the contouring functions, expect the behavior changes described in the following table.
| Summary | New Behavior | Compatibility Considerations |
|---|---|---|
Handles | Each of the three contouring functions now returns a handle to an hggroup object as its second output. | In previous releases, contourm returned a handle to a MATLAB contourgroup object as its second output, while contourfm and contour3m each returned an array of patch handles. |
Contour lines and levels | The contouring functions now produce one line per contour level. The hggroup returned by contourm has exactly one line child per contour level. | The contouring functions now construct an equivalent (or better) display using fewer graphics objects than in previous releases. |
Default contour levels | In contourfm and contour3m, the default contour levels are now consistent with contourm, as well as the MATLAB contour and contourf functions. | The default contour levels have changed from those in previous releases. |
Non-positive contour levels | If you supply 0 or a negative number for V in the syntaxes contourm(Z,R,V) or contourm(lat,lon,Z,V), contourm creates a plot with a single contour at that level. | In previous releases, if you supplied 0 or a negative number for V, the contourm function drew no contour lines, returned an empty contour matrix, and constructed a contourgroup with no children. |
Parameter settings | The parameter settings for contourm and contourfm are both more selective and more fully documented. You can set only the parameters described in the contourm reference page. | In previous releases, you could set any valid contourgroup property (possibly with unexpected results). |
Contour level tag | In R2010b, each contour line has its Tag property set to a string representation of its contour level, preceded by 'contour line:'. These tags display in the lower left of the axes when you click on a contour line. | In previous releases, the tags contained only the contour level strings. |
Filled area tag | In R2010b, each fill polygon (patch) has its Tag property set to a string beginning with 'contour interval:' and followed by its minimum and maximum levels (as strings) in square brackets. These tags display in the lower left of the axes when you click within a fill polygon. | In previous releases, the tags in patches created by contourfm contained the string 'Cpatches' and did not display when you clicked. |
AppData and UserData | Each contour line object now has a contour Level field in its AppData property, and the patches representing fill polygons have 'MinLevel' and 'MaxLevel' AppData fields. contourm and related functions no longer set the UserData property of any graphics object. | Previously, UserData was set to the contour level value for each line and to a minimum contour level value for each patch. If you have an application or GUI that checks UserData values for individual lines or patches, work with the getappdata function instead. |
Contours separating filled areas | By default, the contourfm function now draws black contour lines to separate filled areas of different colors. | In previous releases, the function did not draw lines by default. To suppress the lines, specify 'LineColor','none'. |
Border of data | When 'LineColor' is set to a value other than 'none', the contourfm function no longer draws lines around the boundary of the data. The data boundary is not a contour, so it is not treated as such. The only lines drawn are true contours. | In previous releases, the function drew lines around the boundary of the data, in addition to the contour lines themselves. |
Line colors | If you set 'LineColor' for contourm or contour3m to 'auto' or 'flat', the line colors come from the figure's colormap, as always. But, as of R2010b, if you change the figure's colormap after creating the contours, the line colors do not change. | In previous releases, if you changed the figure's colormap after creating the contours, the line colors changed. To change the line colors, use contourcmap. |
Fill colors | When you call contourfm, the fill colors are derived from the figure's colormap, as in previous releases. As of R2010b, if you change the figure's colormap after calling contourfm, the fill colors are not affected. | To change the fill colors after plotting the filled contours, call contourcmap. |
Globe map display | You can now use the globe map display with the contouring functions. The contour3m function warns, but if you are careful to scale your input data correctly relative to the radius of your reference sphere, you can still use it. | In previous releases, you could not use the globe map display with the contouring functions. |
Now that contourfm produces correct results more consistently, it also takes somewhat longer to run.
In previous releases, the clabelm function broke contour lines to display the contour level tag. The breaks failed to scale appropriately during zooming or when the figure size changed. Now, instead of breaking the contour line, the clabelm function sets the color of the background where the tag is inserted to the color of the ancestor axes or line.
If you want to display the contour labels without a background color, as in previous releases, use set to specify 'BackgroundColor','none' on the text object handle array returned by clabelm.
Many aspects of the fix to Bug 192285 apply to geoshow contouring options as well as to contourm. When applied to a data grid with the DisplayType parameter set to 'contour', geoshow now contours the grid in the same way that contourm would, constructs a handle to the same sort of hggroup, and accepts the same set of optional parameters (as documented on the contourm reference page).
When used with 'DisplayType','contour' in previous releases, geoshow constructed a MATLAB contourgroup and returned its handle. In previous releases, you could set any contourgroup property via geoshow (possibly with unexpected results); you can now set only the parameters described in the contourm reference page—a useful, relevant, and validated subset.
When applied to a data grid with the 'DisplayType' parameter set to 'surface', geoshow now sets the 'FaceColor' property to 'interp', unless the 'CData' property is also passed into the function. In that case, the 'FaceColor' is set to 'texturemap'.
When used with 'DisplayType', 'surface', in previous releases, geoshow set the 'FaceColor' property to 'texturemap'.
The 'Cpatches' option has been removed in R2010b and replaced by 'fillcontour'.
In earlier versions of MATLAB, you could do the following:
load geoid
worldmap world
contourfm(geoid, geoidrefvec, 10)
h = handlem('Cpatches'); (The output h is an array of patch object handles.)
In R2010b, to achieve a comparable result, you can use either:
h = handlem('fillcontour');or
h = handlem('contour');(The output h is a handle to an hggroup.)
In cases where hggroups with both filled and unfilled contours exist, use the 'fillcontour' syntax to return only handles to the hggroups with filled contours. If you use the handlem('contour') syntax, you will return handles to all hggroups containing contours generated by Mapping Toolbox functions.
The 'contour3d' syntax has been removed in R2010b and replaced by 'contour'.
In earlier versions of MATLAB, you could do the following:
load geoid
worldmap world
contour3m(geoid, geoidrefvec, 10)
h = handlem('contour3d');
(The output h is an array of patch object handles.)
In R2010b, to achieve a comparable result, you can use:
h = handlem('contour');
(The output h is a handle to an hggroup.)
The documentation in R2010a noted 'clabels' as the string to use in finding contour labels. This is incorrect and should be 'clabel'. The documentation has been changed to 'clabel' in R2010b.
In previous releases, the contourcmap function had the following syntax:
contourcmap(cdelta,cmapstr)
Now, contourcmap accepts the colormap string by itself:
contourcmap(cmapstr)
Or the colormap string with cdelta:
contourcmap(cmapstr,cdelta)
Notice that the position of the two input arguments has changed. The cdelta argument now appears after the colormap string.
In addition to this change in syntax, the contourcmap function exhibits some changes in behavior:
When the axes contains Mapping Toolbox contour objects, cdelta is ignored and the resultant colormap contains the same number of colors as the original colormap. The ColorAlignment is set to 'center' for contour lines and 'ends' for filled contours and cannot be modified.
After you have created a contourcmap, if you change the figure's colormap, the colorbar will change colors. The contourlines and the fill will not change colors. To work around this problem, do not set the figure colormap directly; set contourcmap.
You can now set the 'Colorbar' parameter to 'off' to remove it from your map.
The original syntax, with the colormap string and cdelta in the reverse order, still works. In a future release, this undocumented syntax will be removed.
If you specify 'out' for the direction string when calling the bufferm function, the returned buffer zone will include all points outside the polygon within a specified distance of its edge. In previous releases, the returned buffer zone also included the points within the polygon.
If you have code that specifies 'out' for the direction string, you now receive only the region outside the polygon but not the polygon itself. If you want to receive the union of the polygon and the buffer zone, as you did in previous releases, use the polybool function.
In previous releases, you could call maptrims with an input value for latlim or lonlim that corresponded to a parallel or meridian that ran precisely along a cell boundary. However, when you did so, the cells adjacent to that boundary would be trimmed off even if they fell completely within the requested limits. Now, if latlim or lonlim corresponds to a cell boundary, the output grid extends all the way to that limit. If a limiting parallel or meridian cuts through a column or row of input cells, the limit is truncated to avoid partial cells.
The WMSMapRequest and WMSLayer objects now accept longitude limits from [0 360] or from [-180 180]. In previous releases, longitude limits had to be from [-180 180].
If you attempt to use the following syntax:
[xi,yi,ii] = polyxpoly(x1,y1,x2,y2,'unique')
polyxpoly issues a warning and ignores the 'unique' flag.
![]() | Version 3.3 (R2011a) Mapping Toolbox Software | Version 3.1 (R2010a) Mapping Toolbox Software | ![]() |

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