Print this page
Learn more about Verizon Connect GeoBase.
Get information about the latest release
If the GeoBase version you have installed on your computer is not listed below, refer to
the GeoBase help file (CHM) installed on your computer for its release notes
(All Programs | Verizon Connect GeoBase Developer's Kit | GeoBase Help).
For older SDK installations (release 4.39 and earlier), PDF release notes can be found by
navigating to All Programs | Telogis GeoBase Developer's Kit | Release Notes.
For other SDK versions that are not listed in the PDF or on this page, please contact
Verizon Connect support.
Changes made from version 4.96 to 4.97:
Added two new optional properties to the ReverseGeoCodeArgs
class: FallbackThresholdMeters, the maximum
distance (in meters) within which to find a street link that matches
Mode, and FallbackMode,
an alternative mode that determines what additional types of street
links can be returned when none matching Mode
are found within FallbackThresholdMeters.
Changes made from version 4.95 to 4.96:
Fixed an issue that caused an exception when switching a highly
zoomed-in MapCtrl to GeoStream mode.
Corrected an issue that occasionally prevented map tiles from being
cached to disk.
Changes made from version 4.94 to 4.95:
Updated GeoStream server behavior to provide faster satellite tiles for
legacy 300x300 satellite tile requests at supported zoom levels when
using an XYZ imagery feed from the Verizon Connect imagery cache.
Reduced the file size of GeoStream satellite imagery tiles.
Improved routing behavior by reducing usage of truck restricted roads
near (but not adjacent to) the destination.
Changes made from version 4.93 to 4.94:
Updated GeoStream server behavior to stop checking tile caches for external
layers that have ExpiryMinutes set to -1 and are
therefore configured to expire immediately.
Fixed an issue with the .NET map client that caused map loading to
fail when connecting to a GeoStream server with EnableTilesWithoutAuth
enabled and then creating a GeoStreamRepository
as the authentication mode.
Fixed an issue on the GeoStream server, which prevented timeouts from
applying when fetching external images. The RequestTimeoutSeconds
field configured in the layers.config file
is now used correctly.
Improved detection of street name changes during routing directions,
which improves name change events recorded as a NameChangeNote
and road split movements provided in a SplitMovement.
Changes made from version 4.92 to 4.93:
Added support for satellite imagery provided by XYZ layers. If you use
satellite imagery, please refer to recent email communications for more
Updated the default tile sizes from 300x300 pixels to 256x256 pixels,
and added support for specifying the default tile size in the GeoStream
Updated GeoStream caching logic to stop caching transient tiles.
Added a new statistic for tracking the mean satellite tile generation time
to the GeoStream statistics page (stats.aspx). The new statistic is labeled
"Mean Satellite Tile Serve Time (ms)".
Changes made from version 4.91 to 4.92:
Fixed an issue that caused point addresses to be included in traffic tiles at higher zoom levels.
Changes made from version 4.90 to 4.91:
Improved tolerance of erroneous words in Autocomplete Geocoder queries.
Changes made from version 4.89 to 4.90:
Added a warning for cases when multiple polygons with conflicting names are merged together in Alchemy. When merging polygons with conflicting names, the resulting polygon now uses the name of the largest input polygon.
Changes made from version 4.88 to 4.89:
Corrected an issue where reverse geocoding with point address data sometimes returned addresses from the wrong side of the road.
Changes made from version 4.87 to 4.88:
Corrected an issue that prevented point address data from being used
when reverse geocoding with speed or heading.
Corrected a bug where the display point did not always match the address
when reverse geocoding with a heading.
Fixed an issue that stopped the map from loading when it was maximized
on high resolution screens.
Changes made from version 4.86 to 4.87:
Corrected an issue in the forward geocoder that prevented it from
returning point address results when using 19Q3 data.
Changes made from version 4.85 to 4.86:
Added support for timing out and canceling DataQuery
requests. Added the new web.config option
DataQueryTimeLimit, which limits DataQuery
requests to a specified number of seconds.
Added a limit for the number of results that can be returned for
DataQuery requests that encompass a large
geographical area. When this limit is exceeded, an exception is thrown.
Corrected an issue in route highlighting that sometimes caused
CorruptedStateExceptions, which lead to
crashes on the GeoStream server.
Improved autocomplete geocoding in New Zealand for queries related
to state highways and rural delivery addresses.
Changes made from version 4.84 to 4.85:
Updated the GeoBase SDK to .NET Framework 4.0, which changes the minimum
supported version of the .NET Framework to version 4.0.
Added new method overloads for point, polygon, street, index, point of
interest, link, line, label, and bulk constraint DataQueries
that take a CancellationToken. These methods
allow queries to be canceled before they complete. Canceling a query
throws a DataQueryCanceledException exception.
Changes made from version 4.83 to 4.84:
- Added a new optional abortOnErrors parameter
to bulk geocoding, reverse geocoding, and Location Search methods. When
set to true, the bulk operation aborts with an exception if any individual
geocode fails. When set to false, the bulk operation completes all individual
geocodes and returns all results and exceptions.
Added support for structured arguments to the Autocomplete Geocoder and Location
Search. Note that any custom LocationSearchSource
subclasses must have the following changes made to build and function in
GeoBase 4.84 and later:
Change overridden methods in LocationSearchSource
and LocationSearchOperation subclasses that
take arguments of type LocationSearchArgs
so that they take arguments of type LocationSearchBaseArgs
If sources should not be used with structured arguments, override
IsApplicableToSearch in the LocationSearchSource
subclass and return false if the arguments object is not of type
If sources should support structured arguments, update them
to work correctly with both LocationSearchArgs
Fixed an issue that could prevent the Reverse Geocoder from returning in some
cases when using point address data and when the closest point was near the
maximum distance specified in the reverse geocoding arguments.
- Modified GeoStream behavior when caching satellite tiles.
The server now uses whichever expiration time is greater from its configuration file and the
Cache-Control:max-age header received from
the external tile supplier.