Version 2.1 (R14SP2) Mapping Toolbox™ Software

This table summarizes what's new in Version 2.1 (R14SP2):

New Features and Changes

Version Compatibility Considerations

Fixed Bugs and Known Problems

Related Documentation at Web Site

Yes
Details below

Yes — Details labeled as Compatibility Considerations below. See also Summary.

Bug reports at Web site

Current product documentation

New features and changes introduced in this version are

New Function Reads Both 5-Minute and 2-Minute ETOPO Data

The new function etopo reads from either the 5-minute (ETOPO5) or the 2-minute (ETOPO2) global terrain data set. This function supersedes function etopo5 and fixes several significant bugs.

Function gshhs Now Returns a Version 2 Geostruct

Function gshhs, which reads the Global Self-consistent Hierarchical High-resolution Shoreline data set, has been upgraded. It now returns a Version 2 geographic data structure (geostruct2) array instead of a Version 1 geostruct. Polygons returned from gshhs now follow the shapefile vertex-ordering convention (supported by functions polybool, shaperead, and shapewrite, for example). Under this convention the coordinates of outer rings (e.g., continent outlines) are given in clockwise order, while counterclockwise ordering is used for inner rings (e.g., lakes and inland seas within a continent). Note that function gshhs does not yet support Version 1.3 of the data set, released on Sept. 27, 2004.

Geodata Can Now Be Exported in Shapefile Format

The new function shapewrite writes a geographic data structure to a shapefile. It exports a Version 2 geographic data structure array (geostruct2), creating .shp, .shx, and .dbf files. Like shaperead, the function supports the Point, MultiPoint, PolyLine, and Polygon shape types. The contents of string-valued attribute fields and scalar numerical attribute fields are written to the dBase (.dbf) file.

Accessing Geodata Resources on the Internet

Links and URLs to documentation and data files for various Internet sources of digital map data are now collected in the following technical note on the MathWorks Web site:

http://www.mathworks.com/support/tech-notes/2100/2101.html

This technical note replaces many individual links formerly scattered across the User's Guide, reference pages, and M-file help. Collecting this information on a Web page rather than on product CDs or printed documentation should substantially mitigate recurrent problems with stale links. Please report any stale links that you might find in the technical note to MathWorks Technical Support (http://www.mathworks.com/contact_TS.html), so that it can be updated promptly.

Compatibility Considerations for Atlas Data and Associated Functions

Through Version 2.0.3, the toolbox included a set of atlas data with global geopolitical data embedded as MATLAB® arrays in four MAT-files: worldlo, worldhi, worldmtx, and worldmtxmed. However, geopolitical data is difficult to keep current, and is subject to inaccuracies and interpretations that can cause contention. Therefore, starting with Version 2.1, Mapping Toolbox™ demo data now excludes geopolitical data that would specify national sovereignty over specific regions of the Earth. The only exceptions are the boundaries of the 50 U.S. states and the District of Columbia.

This change means that the worldlo, worldhi, worldmtx, and worldmtxmed MAT-files are no longer part of the toolbox. However, the nonpolitical data on global coastlines, major lakes and inland seas, major rivers, and major cities and populated places that was in worldlo.mat has been retained in the toolbox and transformed into shapefile format. This includes the addition of name attributes for many previously unnamed features. There are four new shapefiles in this category: landareas.shp, worldlakes.shp, worldrivers.shp, and worldcities.shp.

For consistency, the atlas data for the United States that was originally stored in the usalo and usahi MAT-files has also been transformed, although none has been removed. These data sets now reside in the following shapefiles and MAT-files: usastatelo.shp, usastatehi.shp, conus.mat, and greatlakes.mat.

The toolbox originally included four functions dedicated to extracting data from the atlas data MAT-files: worldlo, worldhi, usalo, and usahi. With the data removal/transformation described above, these functions are no longer needed and have been removed from the toolbox in Version 2.1. You can easily access the new shapefiles using the shaperead function, which includes powerful and flexible options for selecting features and even controlling which attributes are read. In addition, function country2mtx, whose sole purpose was to rasterize the country boundary polygons in worldlo.mat, has been removed.

Related changes extend to the worldmap function, which formerly combined two purposes:

In Version 2.1, worldmap supports only the first of these actions. A call to worldmap constructs a map axes object and can easily be followed with a variety of Mapping Toolbox commands to display the map data of your choice. Because the usamap function is so similar to worldmap, corresponding changes have been made there as well.

To help those who have relied heavily on worldmap and usamap to plot base maps with automatically selected vector map data, examples throughout the User's Guide, reference pages, and M-file Help entries have been updated to illustrate the new behavior of worldmap and usamap, and to show how to create maps including vector shapefile data layers. These examples cover a wide variety of ways to read and subset data with shaperead and display data with geoshow and other Mapping Toolbox display functions. A good place to start is with the examples for the worldmap and usamap functions. Also see example code in Changes to worldmap and usamap Display Types.

To help you update commands, scripts, and data for constructing and maintaining base maps, a recently published technical note on the MathWorks Web site provides links to data and documentation for many sources of vector and raster digital map data that you can access over the Internet:

http://www.mathworks.com/support/tech-notes/2100/2101.html

Compatibility Considerations for worldmap and usamap

worldmap and usamap have been simplified to construct appropriate map axes for a given area without displaying any map data.

In all cases, map frames, latitude-longitude grid lines, meridian labels, and parallel labels are turned on. You can use the following command sequence to remove them:

 framem off; gridm off; mlabel off; plabel off

Other changes include the following:

Changes to worldmap and usamap Display Types

As of this release, the worldmap and usamap functions no longer supports the type input argument. This argument provided an easy way to control display behavior.

The type option in worldmap was a single argument that could be one of the following strings: 'none', 'line', 'lineonly', 'patch', 'patchonly', 'mesh', 'meshonly', 'dem', 'demonly', 'dem3d', 'dem3donly', 'lmesh3d', 'lmesh3donly', 'ldem3d', and 'ldem3donly'. In usamap, type was a subset of the above names (the 3-D options were not supported).

In the current release, the various type display options can be simulated by following a call to worldmap or usamap with an appropriate set of Mapping Toolbox commands. The following table specifies how you can achieve the effects of the old worldmap type argument using such auxiliary methods:

Mapping 1.x to 2.0.x Usage Mapping 2.1 Usage

load topo

worldmap(topo, ...

topolegend, 'dem')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend)

demcmap(topo)

land = shaperead('landareas.shp',...

'UseGeoCoords', true);

geoshow([land.Lat], [land.Lon])

load topo

worlmdap(topo, ...

topolegend, 'demonly')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend)

demcmap(topo)

load topo

worldmap(topo, ...

topolegend, 'dem3d')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend,size(topo),topo)

da = daspect;

pba = pbaspect;

da(3) = 7.5*pba(3)/da(3);

daspect(da);

demcmap(topo)

land = shaperead('landareas.shp',...

'UseGeoCoords', true);

geoshow([land.Lat], [land.Lon])

load topo

worldmap(topo, ...

topolegend, 'dem3donly')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend,size(topo),topo)

demcmap(topo)

load korea

worldmap (map, refvec,...

'mesh')

load korea

worldmap(map, refvec)

meshm(map, refvec)

land = shaperead('landareas.shp',...

'UseGeoCoords', true);

geoshow([land.Lat], [land.Lon])

(Text North Korea and South Korea will be missing)

load korea

worldmap(map, refvec,...

'meshonly')

load korea

worldmap(map, refvec)

meshm(map,refvec)

load topo

worldmap(topo,...

topolegend, 'mesh3d')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend,size(topo),topo)

da = daspect;

pba = pbaspect;

da(3) = 7.5*pba(3)/da(3);

daspect(da);

load topo

worldmap...

(topo,topolegend,...

'mesh3donly')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend,size(topo),top

load topo

worldmap(topo,...

topolegend, 'ldem3d')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend,size(topo),topo)

da = daspect;

pba = pbaspect;

da(3) = 7.5*pba(3)/da(3);

daspect(da);

demcmap(topo)

camlight(90,5);

camlight(0,5);

lighting phong

material([0.25 0.8 0])

load topo

worldmap(topo, ...

topolegend,'ldem3donly')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend,size(topo),topo)

da = daspect;

pba = pbaspect;

da(3) = 7.5*pba(3)/da(3);

daspect(da);

demcmap(topo)

load topo

worldmap(topo,...

topolegend, 'lmesh3d'

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend,size(topo),topo)

da = daspect;

pba = pbaspect;

da(3) = 2*pba(3)/da(3);

daspect(da);

camlight(90,5);

camlight(0,5);

lighting phong

material([0.25 0.8 0])

load topo

worldmap(topo,...

  topolegend,...

  'lmesh3donly')

load topo

worldmap(topo, topolegend)

meshm(topo, topolegend,size(topo),topo)

da = daspect;

pba = pbaspect;

da(3) = 2*pba(3)/da(3);

daspect(da);

load korea

worldmap(map, refvec,...

load korea

worldmap(map, refvec)

land =...

shaperead('landareas.shp',...

'UseGeoCoords', true);

geoshow([land.Lat], [land.Lon])

(Text North Korea and South Korea will be missing. Land area boundaries resolution is lower.)

load korea

worldmap(map, refvec,...

'lineonly')

load korea

worldmap(map, refvec)

land = ...

shaperead('landareas.shp',...

'UseGeoCoords', true);

geoshow([land.Lat], [land.Lon])

load korea

'line')

worldmap(map, refvec,...

'none')

load korea

worldmap(map, refvec)

load korea

worldmap(map, refvec,...

  'patch')

load korea

worldmap(map, refvec)

land = ...

shaperead('landareas.shp',...

'UseGeoCoords', true);

faceColors = ...

makesymbolspec('Polygon',...

{'INDEX', [1 numel(land)],...

'FaceColor', ...

polcmap(numel(land))});

geoshow(land,'SymbolSpec',...

makesymbolspec('Polygon',...

faceColors)

(Text North Korea and South Korea will be missing. Country coloring will be missing.)

load korea

worldmap(map, refvec,...

'patchonly')

load korea

worldmap(map, refvec)

land = ...

shaperead('landareas.shp',...

'UseGeoCoords', true);

faceColors =...

{'INDEX', [1 numel(land)],...

'FaceColor', ...

polcmap(numel(land))});

geoshow(land,'SymbolSpec',...

faceColors)

(Country coloring will be missing.)

Data Files Added in This Release

The following files were added to the mapdemos directory, for use in toolbox demos and examples:

Atlas Data MAT-Files Removed in This Release

MAT-files containing Atlas Data have been removed in Version 2.1. Some of the data has been retained in a different form. The disposition of these data sets and variables is described below.

World MAT-File Data

United States MAT-File Data

Functions Deleted in This Release

The following functions, which performed specific operations on Atlas Data sets, have been removed in Version 2.1:

Functions Made Obsolete in This Release

  


 © 1984-2008- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS