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.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.
Changes made from version 4.72 to 4.73:
Improved the quality of results returned by the Autocomplete Geocoder
for queries using country-specific address aliases and formats when
used with GBFS files from 18Q3 or later.
Improved some truck routes to avoid unsuitable roads and to favor
Updated some routes to avoid undesirable route diversions along side roads.
Improved truck routing around route stop locations.
Enhanced the routing module to use vehicle speed units (metric or imperial)
available from the real time traffic fetcher.
Changes made from version 4.71 to 4.72:
Added the QuerySpeedLimit method to the
DataQuery class. This method returns
the speed limit at a given location, and for other parameters
including heading, vehicle specification, and time.
Corrected traffic direction inaccuracies in real-time traffic,
and incorrect unit interpretations for Canadian live traffic.
GBFS (GeoBase File System)
Made various improvements to the superlink routing network,
including removing redundant links and splitting some superlinks
up to allow for more entry and exit points to the links.
Removed support for negative buffers when using the
IMap.ZoomToBoundingBox method, which
was added in GeoBase release 4.69.
Changes made from version 4.70 to 4.71:
Modified the weighted utilization statistics on stats.aspx
to display the square root of the mean weighted utilization. This leads to
the displayed weighted utilization being closer to 1 for more uneven loads.
Changes made from version 4.69 to 4.70:
Corrected a bug where the MessagesBundle was
sometimes not set correctly on a Navigator,
and the resulting directions where shown in English instead of in
the language defined by the MessagesBundle.
Reduced the size of the neigh.gbd file in
some GBFS files produced by Alchemy.
Changes made from version 4.68 to 4.69:
Fixed a bug where MultiThreadMatrix would
throw errors when using a GeoStreamRepository.
Added a new overload of the method ZoomToBoundingBox,
which allows you to specify buffer sizes independently for each side of the map.
Modified the GeoStream statistics page (stats.aspx)
to select the secondary tag SuperTiles by default.
Resolved an issue causing cancelled JSON routing requests to be recorded
in GeoStream stats as JSON request failures instead of JSON request
Added support for querying GBFS file vendor versions of
GeoStreamRepositories and MultiRepositories
using the VendorVersion property.
Changes made from version 4.67.1 to 4.68:
Added support for dotted file names, for example "RED.USA.shp", to Alchemy.
Changes made from version 4.67 to 4.67.1:
Added FIPS (Federal Information Processing Standards) compliance to
GeoBase and GeoStream. When using GeoStream, both client and server
must be updated for FIPS compliance.
As part of FIPS compliance, cache paths in the GeoStream tile cache
are changed, invalidating any current cache. To maintain previous
cache paths, if FIPS compliance is not needed, add a
UseLegacyDatasetHashes key with a value of "true" to
the GeoStream web.config file.
Some tools, such as Alchemy, GBFSDecompressor, and GBFS Tool, might
experience issues when run with Microsoft Windows’ FIPS compliance settings
Changes made from version 4.66 to 4.67:
Improved the consistency and accuracy of route highlighting when
routes include dead-end streets.
Removed several minor memory leaks related to geocoding and repositories,
and in the DataQuery class.
Changes made from version 4.65 to 4.66:
Fixed an issue where LocationSearch returned
results for invalid LatLons when the latitude
value in the search query was invalid.
Corrected a problem in the Autocomplete Geocoder that could lead to
no results being returned when searching for cross streets with a
query that contains a country but no other regions.
Corrected an Autocomplete Geocoder bug in the confidence calculations
for queries that omit the suffix of the first street in a cross street
query and that result in both cross street and non-cross street results.
In these situations, the ranking of the results could be incorrect.
Improved the formatting of addresses on BalloonPushPins
that are created from region suggestions made by a Location Search.