Print This Page
Don't Have the GeoBase SDK? Click Here to Download Now For Free. Learn More About Verizon Connect GeoBase.
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.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.
Changes made from version 4.64 to 4.65:
Fixed an Autocomplete Geocoder issue that could return single street
results instead of cross street results for some queries with street
prefixes, when using 18Q2 data.
Added support for regional speed laws in UK and Canada to the
GetVehicleSpeedLimit method in the Route
Added support for MultiThreadMatrix calculations
to be performed faster in situations where you are interested only
in a subset of the rows and columns of a route matrix. To do this,
use the LocationsToCalculate constructor argument.
An example use case for this feature would be to return distances
and times from one depot to many jobs.
Corrected a bug that did not allow to create a lookup from a list of
files, if the WHERE clause was never true
for the first file.
Fixed an Alchemy problem with importing constraints that have speed
limits in KPH. Alchemy incorrectly treated the speed limits as if they
were in MPH.
Changes made from version 4.63 to 4.64:
Improved cross street support in the Autocomplete Geocoder so that it
includes results where the query for the first street omits the street
type or suffix (for example, "Rhode Island & Massachusetts Ave,
Washington DC" instead of the full names “Rhode Island Ave NW &
Massachusetts Ave NW, Washington, District Of Columbia, USA”).
This feature requires GBFS files from 18Q2 or later.
Fixed an Autocomplete Geocoder issue that previously allowed substitute
values of query terms to be incorrectly joined onto adjacent query
terms in some situations.
Added the method GetLocalizedUnitString to
the class AddressFormatter. This new method
adds the ability to format an array of units as a localized string
using the Address Formatter.
Added support for the arrow rendering properties RenderArrowColor,
and RenderArrowSpacing to the Directions
class, when using a GeoStreamRepository.
Improved repository matching, by allowing "/" and "\" to be interchangeable
in the filepath, when loading more than 100 files.
Changes made from version 4.62 to 4.63:
Improved the locations of some cross street suggestions when searching
for complex intersections (such as highway interchanges) using the
Fixed a problem in the Autocomplete Geocoder that prevented some cross
street results from being found when using street suffix substitutes
and connecting the streets with the keyword "and".
Corrected an issue that could cause searches using LocationSearch
to return a status of "Cancelled" instead of "Timeout".
Added the properties IgnoreDrivingDirection and
IgnoreConstraints to the class RoutingStrategy.
- IgnoreDrivingDirection defines whether to
ignore the direction of one way streets and has a default value of "false".
- IgnoreConstraints defines whether to ignore
all routing constraints and also has a default value of "false".
Added syntax highlighting for the attribute FUNC_CLASS
Added GeoBase and CAM file support for the new polygon type
global_water, which describes the world’s
bays and oceans.
Added Alchemy support for the new polygon type global_water.
Corrected memory leaks in the local repository, geocoding, and mapping.
Changes made from version 4.61 to 4.62:
Corrected an issue in the function HilbertIndex.Query
where ranges that included the entire Hilbert range, to the highest possible
ulong value, were incorrectly set to 0.
Changes made from version 4.60 to 4.61:
Added the property Location to the
GeoCodeFull class. Location is a
LatLon point that can be used to display
a reverse geocoded address on a map. Depending on whether you use
point address data or not, the Location is
either the display point for the point address, or a location that
is slightly offset from the street.
Fixed an Autocomplete Geocoder issue that could omit street numbers
from results in rare cases. The issue is more common when versions
of GeoBase prior to 4.61 are used with GBFS files from 18Q2 (2018,
2nd quarter) or newer.