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.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.
Changes made from version 4.82 to 4.83:
- Added support for more complex time conditions on Alchemy import constraints using DateTimeType.
For example, 9am-5pm on August 12th every year or all day on the Sunday of the 2nd week of May.
- Corrected an issue where calculating a route matrix ignored link constraints, such as height, weight, or number of trailers,
even if ObeyConstraints was set to true on the RouteMatrix object.
- Fixed a bug that caused Map Explorer to crash on start up when attempting to connect to a GeoStream server with invalid credentials.
Changes made from version 4.81 to 4.82:
- Corrected a fault when reverse geocoding point addresses if the arrival link is an unnamed link.
- Corrected a bug that prevented maps from loading when using a GeoStream with the default server configuration.
- Reduced memory usage of MapCtrl when using GeoStream Repository.
- Fixed an issue where disabling the disk tile cache on a GeoStream Repository that had already loaded some tiles failed to load new tiles.
Changes made from version 4.80 to 4.81:
This release adds support for a new point address file format, which will be available as part of future data releases starting with 19Q3.
- Improved Autocomplete Geocoder suggestions so the Location field is always populated. Previously, it was set to LatLon.Empty for some region results. It is now set to the center of the suggestion’s BoundingBox in these cases.
- Updated the Autocomplete Geocoder and the Reverse Geocoder to support new point address data files being introduced in 19Q3, which will offer the following improvements:
- Correct a bug that prevented point addresses outside the street number range on a StreetLink from being geocoded.
- Improve the Autocomplete Geocoder to support geocoding any non-integral street number (such as W163N7712, 33/2, 84-1, or 71B) as long as a point address with an exact match exists.
- Improve performance when reverse geocoding with point address data.
- Added new statistics to the GeoStream server. Base map tiles, external (WMS/WMTS/satellite) tiles, and traffic tiles now offer statistics that track the number of tiles served from the worker pool and the mean tile serve time (from the worker pool).
- Fixed a GeoStream deserialization issue that could cause a bad response because the server did not recognize unknown types.
Changes made from version 4.79 to 4.80:
Added a new maximum batchSize parameter to the BulkGeoCode, BulkReverseGeoCode, and BulkReverseGeoCodeFull methods. This integer value specifies the maximum number of locations to include in a GeoStreamRepository geocoding request (in GeoStream mode).
For example, with a bulkArgs, LatLons, or bulkReverseGeocodeArgs array containing 52 addresses or locations, setting a batchSize value of '10' will result in 6 separate requests: five including ten locations, and one including two. Previously, all bulk location and address requests were sent to the GeoStream server at the same time, which could result in timeouts.
Changes made from version 4.78 to 4.79:
Improved the Autocomplete Geocoder to find matches where the query
includes spelling mistakes in word substitutes for addresses; for
example, "rosd" instead of "road" for an address containing "rd".
Improved the ranking of Autocomplete Geocoder suggestions when a subset
of suggestions include a prefix match of a word substitute in the address.
Corrected an issue that could stop historical route highlights
accurately snapping to roads in some scenarios.
Changes made from version 4.77 to 4.78:
The GeoBase resource website for downloading the latest SDK, map data,
and other resources has changed from dev.telogis.com to
The website has been improved to make it easier to find and download
the files you need. You can use your existing credentials to sign in.
Fixed an issue with ShapeLayer.QueryShapes
when provided with an IMap parameter. The
issue could lead to an incorrect number of polygons when the map had
a non-zero heading.
Corrected a bug that could prevent requested route highlights from
Improved error messages in Alchemy that are displayed when processing
an unsupported geometry.
Changes made from version 4.76.1 to 4.77:
Fixed cases where route stops were connecting to a restricted road.
Corrected an issue that sometimes prevented GetLatestTraffic
tasks from being removed from a GeoStream server’s work intensive pool.
Changes made from version 4.76 to 4.76.1:
Corrected an issue in Text-to-Speech that caused some abbreviations
to be read out incorrectly, for example an "E" in an address could
be read out as "Estate" instead of "East".
Changes made from version 4.75 to 4.76:
Improved the Autocomplete Geocoder to return results for queries that
contain repeated content.
Corrected an issue with the Reverse Geocoder that caused it to find
addresses on the wrong side of the street in some rare cases when using
point address data.
Improved Location Search to include correct non-numeric street numbers,
for example 18a, in suggestions for queries consisting of a latitude
Improved navigation directions to show full non-numeric street numbers,
for example 18a, and to format addresses correctly for the corresponding
country, for example by correctly ordering street name and number.
Corrected the instructions for directions where multiple route-stops overlap.
Resolved a fitted history bug where the time between two points was
higher than expected.
Fixed a small subset of routes that were unable to connect between
Fixed a threading issue that caused infrequent failures when caching
Changes made from version 4.74 to 4.75:
Added functionality to the GeoBase Address Formatter to support formatting with a LocalizedUnits string. The string can be preformatted using GetLocalizedUnitString and stored in the StructuredAddressData. If present, the LocalizedUnits will be prioritized over formatting the Units array.
Changed the format of Australian addresses so that they now exclude city unless no suburb is specified.
Corrected a bug in Alchemy that caused duplicated street flags.
Fixed an issue with PolygonFence where the wrong map size would be used for headings that were not multiples of 90.
Fixed a bug where route history was not generating enough network candidates to ensure accurate route highlights.
Corrected an issue where route highlights would not snap back to road networks.
Changes made from version 4.73 to 4.74:
As announced in Product Lifecycle Support,
support for the Autocomplete Geocoder and Drill-Down Geocoder using the
latest GeoBase version and data files prior to 17Q3 (2017 3rd quarter)
ended July 1, 2018. To continue using the Autocomplete Geocoder or Drill-Down
Geocoder you must use data files from 17Q3 or later, which require GeoBase
v4.31 or later. For more information see Data
GBFS (GeoBase File System)
Corrected an issue with GBFSVerify, which caused it to fail when
verifying large files.
Added the StreetNumberFull property to the
Address object that is returned by the
Reverse Geocoder. StreetNumberFull is a
String, and it can include non-numeric street numbers, such as 50a
Fixed an issue where satellite imagery was no longer displayed after 30
days of continuous GeoStream uptime.
Corrected a bug where the GeoStream server sometimes threw exceptions
when there were canceled requests.
Fixed a memory leak in GeoStream that occurred when generating tiles
from fallback satellite images.
Added a restriction on the maximum stats file size that can be read
by the GeoStream server to prevent out-of-memory exceptions.
Corrected an error in Alchemy, which caused ferry links to be duplicated
inside bounding boxes.
Fixed an issue in the Alchemy's neigh.gbd file,
which prevented the Forward Geocoder from finding addresses in some regions.