Store 
| Products & Services | Solutions | Academia | Support | User Community | Company |
 |
Download Product Updates | | |  |
Get Pricing | | | |
Trial Software |
| Documentation → Mapping Toolbox |
| 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.4 (R2006b):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
Yes | Yes — Details in Changes in Behavior of mapshow and geoshow below. See also Summary. | Bug reports at Web site | Printable Release Notes: PDF Current product documentation |
New features and changes introduced in this version are
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)
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 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.
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.
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:
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'
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.
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.
For geostruct input, an hggroup object is constructed; its handle is returned instead of an array of handles to map graphic objects:
For polygon geostructs, map graphics polygon objects are still constructed, but become children of the hggroup.
For point, multipoint, and line geostructs, the children of the hggroup are ordinary line objects; map graphics objects are no longer constructed.
In both cases each child of the hggroup, rather than each element in an array of handles, corresponds to a distinct feature in the geostruct.
Geostruct inputs result in an hggroup handle containing either line objects (for point, multipoint, and line inputs) or modified patch objects (for polygon inputs) as their children.
Coordinate arrays (x,y pairs) displayed as lines now result in ordinary line objects.
Geostructs containing lines result as ordinary line objects within hggroups.
mapshow and geoshow now warn when given a geostruct within which the Geometry field differs from a specified 'DisplayType' parameter.
mapshow will warn if it is given a geostruct containing Lat and Lon fields instead of X and Y fields.
geoshow will warn if it is given a geostruct containing X and Y fields instead of Lat and Lon fields.
geoshow now projects vector and raster inputs using a default projection (Plate Carree) if the parent axes is not a map axes. The axes itself is unchanged (it is not modified to become a map axes), but the scale factor of the projection is set such that latitudes and longitudes in degrees can be read directly from the axes ticks and grid lines.
mapshow no longer errors or warns if given duplicate Parameter/Value pair inputs; in such circumstances, mapshow now uses the last value (even with SymbolSpecs)
geoshow now creates a true 3-D surface if given a 'surface' DisplayType rather than setting the ZData values to 0.
The 'texturemap' DisplayType now uses the pixel edges to create XData and YData grids rather than using the pixel centers, which correctly registers the display to map coordinates. The ZData contains an array of zeros having the same dimensions as the XData and YData arrays, which exceed the input grid in size by one in both the x and y dimensions.
You should use'texturemap' displays when the attribute being displayed is coded by color (i.e. 2-D displays); use 'surface' displays when you need to show data with relief (nonzero ZData).
All Handle Graphics® patch properties are now supported for polygon inputs.
All Handle Graphics line properties are now supported for point and line inputs, except that 'linestyle' is ignored for point inputs.
geoshow is now capable of accepting any referencing matrix. Previously it could only accept those referencing matrices that were convertible to referencing vectors.
In previous versions, mapshow and geoshow would throw errors when provided with empty ([]) arrays. This behavior could be inconvenient when running these functions via scripts. The new behavior is also more consistent with that of MATLAB plotting functions such as plot, surf, mesh, and contour.
Some DTED level 0 files available via the National Geospatial-Intelligence Agency's (NGA) web interface may have minor errors. Specifically, Level 0 data for cells just to the east of the prime meridian may have longitude coordinate strings with 'W' substituted for 'E'. The dted function now detects and automatically corrects this data error.
 | Version 2.5 (R2007a) Mapping Toolbox Software | Version 2.3 (R2006a) Mapping Toolbox Software |  |
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 |
