Click or drag to resize
Release NotesTelogis Logo
Print This Page
Don't Have the GeoBase SDK? Click Here to Download Now For Free. Learn More About Telogis GeoBase.
Note Note

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 | Telogis GeoBase Developer's Kit | Telogis 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 | GeoBase Release Notes.

4.41

Changes made from version 4.40 to 4.41:

Geocoding

  • Made improvements to the support of the unit portion of an address in the Autocomplete Geocoder. The improvements include:
    • Address units of the form <letter><number> (for example B4) and <letter>-<number> (for example C-134) are now supported.
    • English ordinal units (for example 2nd floor or 3rd flat) are now supported.
    • Address units that are attached to street numbers (for example Flat 5/5 Riccarton Road) are now supported.
    • Numerical unit ranges are now supported (for example 5-7). Non-numeric unit ranges (for example a-c) are not supported.
  • Fixed an issue that caused the Autocomplete Geocoder's post code queries and the Location Search's reverse geocode queries to miss result suggestions, if there was an additional space at the start or end of the queries.
  • Improved the time that it takes to find an intersection between two streets using the Forward Geocoder.

Spatial

  • Increased the limit of GBFS files that can be loaded at the same time from 192 to 256.
  • Improved GeoBase to be able to read polygon height information from new 17Q4 GBFS files. Building height and clearance (height above ground for elevated sections of buildings) are available as a Distance struct on the Polygon that is returned by DataQuery.QueryPolygons.
  • Added a Telogis.GeoBase.Measurement.Distance object to represent a precise distance with a specific unit.

Mapping

  • Added a MiterLimit property to the ArrowRenderer class to better render acute angles.
  • Added a new render_behavior parameter to the point renderer and custom point renderer in Chameleon. It allows you to specify the behavior for rendering the symbol or label or both for a point feature on the map. If you specify ALWAYS_RENDER, the point or label are drawn on the map even if there is not enough space and some clipping might occur.
  • Updated the map display for the French region Corse to use blue route territoriale signs instead of red N road signs.

Routing

  • Made improvements to some long-haul routes. The improved routes use lower functional class roads around the stops, but the routes are more direct.
  • Improved GeoBase to produce around-the-block routes in order to avoid undesired u-turns.

GeoStream

  • Added support for specifying a time limit on all bulk operations. To define a limit, insert the following key into the GeoStream's web.config file with the appropriate time limit value in seconds:

    <appSettings>
      <add key="MultiCallTimeLimit" value="120"/>
    </appSettings>
  • Added a new statistic for JSON request timeouts to the GeoStream statistics page (stats.aspx).
  • Modified the way in which GeoStream records statistics on JSON request cancellations and timeouts:

    • "JSON Requests Failed" records errors and timeouts.
    • “JSON Requests Timed Out” records timeouts only.
    • “JSON Requests Cancelled” records only requests that are aborted because of the client disconnecting.
  • Modified the display of multicall JSON requests, which are bulk requests, on the GeoStream's stats-live.aspx page to show the underlying class used. For example, if you make a bulk geocode request using the Autocomplete Geocoder, the stats-live.aspx page will show "MultiCall (JSONAutocompleteGeocoder.Geocode) ...".
  • Modified JSON requests that exceed their expected processing time to be logged twice, once when they exceed the expected time, and once when they are completed. The former logging behavior is new.
  • Added the optional property preSendCallback to Telogis.GeoBase.MapLayers.ClusterLayer in the GeoStream JavaScript client. It allows operations to be performed on the cluster XMLHttpRequest before it is sent, such as adding headers. preSendCallback is called before the request for clusters is sent, only when the layer's usePost option is set to "true". Its only argument is the request, which is an instance of XMLHttpRequest.
  • Modified tile responses served from a GeoStream to always use a wildcard ("*") for the value of the Access-Control-Allow-Origin header.

Traffic

  • Fixed an issue that caused GeoBase to interpret the fetch times incorrectly for HERE live traffic when fetching directly from a HERE realtime traffic API. This resulted in traffic feeds being incorrectly marked as invalid. Realtime traffic consumed via Geobase traffic APIs was unaffected.

DesktopNav Example Project

  • Fixed a crash that occurred when clicking on the "Enter city in ..." text box while attempting to set a street destination for the first time in a session in the DesktopNav example project.
4.40

Changes made from version 4.39 to 4.40:

Geocoding

  • Updated the behavior of the Autocomplete Geocoder to interpret unit identifiers as street numbers for queries that contain a unit identifier and a street name, but no street number.
  • Improved the Autocomplete Geocoder to give more appropriate confidence calculations for countries that do not have three region levels and for addresses with repeated region names.
  • Added support for the unit types "level" and "lvl" as a substitute for "floor" to the Autocomplete Geocoder.
  • Improved formatting for postcode results from the Autocomplete Geocoder, GeoCoder, and Location Search, to ensure that region names are correctly omitted when not part of the address format for a country.
  • Changed the default mode of GeoCoder.ReverseGeoCodeFull from ReverseGeoCodeMode.AllLinks to ReverseGeoCodeMode.RealLinksOnly, to be consistent with GeoCoder.ReverseGeoCode.

Spatial

  • Improved the error message that is displayed when trying to open historical traffic files without an appropriate license.

Routing

  • Made various improvements to Route Highlighting, including:

    • Simplified the route highlights that are drawn between stops that are further than 13 miles apart to a direct line.
    • Improved the display of routes at highway exits and at their final stops.
    • Corrected an issue that sometimes caused routes drawn using route highlighting to move off the road and back onto it.
    • Corrected an issue that sometimes lead to unnecessary loops to get from one GPS point to another, rather than taking the more obvious route between the points.

GeoStream

  • Updated the URL for the Visible Satellite Cloud Imagery layer in the GeoStream's default layers.config file.

Alchemy

  • Corrected an issue that prevented Alchemy from importing shapefiles with WKT (well-known text) multipoints.
  • Changed the behavior when importing a shapefile into Alchemy, to no longer allow two functions with the same name to be used in the same script.
4.39

Changes made from version 4.38 to 4.39:

Geocoding

  • Corrected an issue that sometimes prevented the Autocomplete Geocoder from finding the location for an address that had the street number after the street name, in countries using this address format. The issue occurred when the truck data files were loaded before the general data files.

Routing

  • Added the constraint type KeepOutArea to the ConstraintBlockType enumeration. This constraint type is used for violations that occur when a route passes through a restricted area, set as a GeoFence in Route.Strategy.KeepOut, and GeoBase cannot find an alternative route.
  • Corrected an issue that sometimes caused routes to pass through a restricted area even when there was an alternative route available.
  • Corrected the routing behavior to always prefer currently applicable live traffic data over historic traffic data.

Spatial

  • Updated GeoBase to be able to read GBFS files that index a larger number of street flag combinations than previously supported. Street flags are characteristics that are applicable to a street, such as functional class, speed limit, or restrictions. Use of the USAEast data file for 17Q2 or later is dependent on this update. USA East coverage using 17Q2 data or later for older versions of GeoBase can be achieved using the regional files USASouthEast, USAGreatLakes, and USANorthWest. These regional files can be combined with the USAWest file of matching data version to create the full USA map. USAWest is not yet large enough to depend on this update (although it might in the future).

Alchemy

  • Made the behavior of specifying IF EXISTS at the end of an Alchemy IMPORT statement consistent between all types of IMPORT statements. The behavior is:
    • If IF EXISTS is used and the import file is not available, builds continue to the end.
    • If IF EXISTS is not used and the file is not available, builds do not continue to the end.
4.38

Changes made from version 4.37 to 4.38:

Routing

  • Corrected an issue where live traffic speed was incorrect for countries using the metric system, because the information was read as kph, but was interpreted as mph.
  • Fixed an issue where getting the speed limit at a particular location or link was not always fetching the link or constraint in the correct direction.
  • Improved the instructions for routing through complex intersections so that they consider the overall turn, give the appropriate number of turn instructions, and treat u-turns properly.
  • Fixed an issue where some instructions did not provide a turn direction, although it was required.
  • Corrected an issue where pedestrian-only streets that were adjacent to the streets along a route sometimes adversely impacted the turn directions for vehicles.
  • Deprecated the method Route.GetVehicleSpeedLimit(link, units). Use the method Route.GetVehicleSpeedLimit(location, linkId, units) instead.

Spatial

  • Added Grams as a unit type to the MassUnit enumeration, for use with MathUtil.ConvertUnits.
  • Added the method FindNearbyPopulationCenter to the DataQuery class. The method returns the address for the nearby population center (usually a city) that best fits the population and proximity criteria indicated in the API call.

GeoStream

  • Added basic HTTP authentication support for GeoStream WMS layers. The attributes Username and Password can now be used within the GeoStream's layers.config file.
  • Added support for specifying a User-Agent HTTP header within the GeoStream’s layers.config file. We recommend adding this header when using National Oceanic and Atmospheric Administration (NOAA) weather layers, because it resolves some reliability issues. The header’s format is <product name>/<version> (<contact email>).
4.37

Changes made from version 4.36 to 4.37:

Geocoding

  • Reduced the default results limit for the Autocomplete Geocoder and Location Search from 20 to 5. To continue using the previous limit, or to set a different limit, use the ResultsLimit property on the AutocompleteGeocoderArgs or LocationSearchArgs classes.
  • Fixed a bug that caused the Forward Geocoder to sometimes return an invalid Intersection point instead of LatLon.Empty for region and postcode results.
  • Altered the confidence calculations for the Autocomplete Geocoder, which leads to improvements in the ordering of results.

Routing

  • Improved the performance of routes that are calculated based on historic traffic data.

GeoStream

  • Fixed an issue that sometimes caused exceptions to be added to the logs when items are removed from the GeoStream's supertile cache.
  • Corrected a thread contention issue with bulk geocoding requests that could cause the requests to run extremely slowly in rare cases.

Mapping

  • Made the following improvements and corrections to the Map and MapCtrl classes to support multiple overlay layers being rendered on a map:
    • Using the new LayersRenderMode property (on the Map or MapCtrl class), you can set the order in which layers are rendered on the map relative to the base map and labels.
    • You can now specify a satellite layer (using MapCtrl.SatelliteLayerName) in addition to GeoStreamRenderer or WMS overlay layers (using MapCtrl.Layers). Previously, setting one type of layer cleared out the other type.
    • MapCtrl.Layers and Map.Layers now support more than one layer. Each layer maps to a separate GeoStream request when used as overlay layers. For some layer types, it is possible to combine the layers by using a single comma-delimited string.
    • MapCtrl.RenderLabels and Map.RenderLabels can now be set when using a remote map. Previously this setting was always "true" for remote maps and labels were always rendered.
    • The default display behavior when using layers with remote maps has changed. Previously the layer was drawn in place of the basemap and without labels. Now the layer is drawn above the basemap with labels on top, which is more consistent with local map behavior. To get the previous behavior, set map.LayersRenderMode to RenderMode.PreMap and map.RenderLabels to "false".
  • Changed the behavior of GeoStream map tile requests when using a custom map style to request basemap and labels as a single layer. This change corrects tile load errors for styles that do not support auxiliary layers.

Map Explorer

  • Added an Overlay Layer Name option to the Map Style menu, which can be used to configure the layers on the MapCtrl.
  • Improved the usability of the Satellite Imagery Layer Name dialog box in the Map Explorer.

Address Formatter

  • Improved address formatting for country names containing the words "and", "of", and "the".
4.36

Changes made from version 4.35 to 4.36:

Routing

  • Fixed a problem where routes calculated for Navigation applications sometimes started in the opposite direction to the vehicle's direction of travel, causing the need for an immediate recalculation.

GeoStream

  • Improved the error handling of the GeoStream statistics page when it encounters a corrupt or missing file.
  • Increased the precision of time measurements in GeoStream tile statistics and geocoding logs.

Map Explorer

  • Corrected an issue that caused the Map Explorer to crash when using the option "Zoom to Route" on a route that contained a "Break" route stop without a location.

Alchemy

  • Added two new Alchemy commands, SAVE LOOKUP and LOAD LOOKUP, which allow you to save and load previously created lookups for later use. The command syntax is:

    SAVE LOOKUP <yourLookup> AS <filename>;

    LOAD LOOKUP <yourLookup> FROM <filename>;

  • Fixed an issue that could cause Alchemy to throw out of memory exceptions when creating large lookups.
4.35

Changes made from version 4.34 to 4.35:

Routing

  • Corrected an issue that negatively impacted routing performance when using GBFS (GeoBase File System) files with data from Q1 2017.

GeoStream

  • Fixed a GeoStream issue that prevented rejected tile requests from being recorded in the GeoStream statistics.
4.34

Changes made from version 4.33 to 4.34:

Geocoding

  • Fixed a performance issue that occurred when the Autocomplete Geocoder searched multiple countries and the queries included a country name and multiple regions.

Routing

  • Added the properties ConcatenatedName and StreetNumberFull, and the methods GetConcatenatedNameWithNumber and GetPrimaryNameWithNumber, to the StreetNameDetails class.
  • Modified traffic data validity to use the time when the traffic conditions were observed rather than the time when the routing request was made.

GeoStream

  • Improved exception handling when deleting local cache files and using a GeoStreamRepository. UnauthorizedAccessExceptions are now caught, and the process will stop trying to delete files when errors are repeated across different files.

Map Explorer

  • Changed the behavior of the Map Explorer to preserve the "Country" selection after adding or removing GBFS files.
  • Added autocomplete search result markers to the map in the Map Explorer. The markers can be toggled on or off using the "Show Result Markers on Map" item in the Search menu. The markers appear when the suggestion list is visible for an autocomplete search, with a more prominent marker for the selected suggestion.
  • Added an option to the Search menu to use the GeoCoder instead of the Autocomplete Geocoder or Location Search. Previously, the GeoCoder was used when pressing the enter key or search button, and the Autocomplete Geocoder or Location Search were used for autocomplete suggestions. Now, the selected geocoder is used in all cases, and no autocomplete suggestions are provided when using the GeoCoder.
  • Corrected an issue that caused an exception to be thrown when performing a Location Search for latitude/longitude coordinates that did not have a corresponding address in the repository file used.
4.33

Changes made from version 4.32 to 4.33:

Geocoding

  • Added the method BulkSearch to the LocationSearch class to allow for bulk search operations and added the method BulkGeocode to the AutocompleteGeocoder class to allow for bulk geocode operations.
  • Fixed an issue that caused the reverse geocoder and pushpin results to not show street numbers for addresses in Ireland.

Spatial

  • Updated the address formats in the AddressFormatter for many European countries to be more regionally appropriate than the default address format.
  • Changed the behavior of the AddressFormatter to no longer insert fields into the middle of a section (where a section is the part of a formatted address between two commas or between a comma and a new-line). New fields are now inserted directly before a section.

GeoStream

  • Fixed a GeoStream resourcing issue that could cause an autocomplete geocode or location search operation to fail when run at the same time as a map tile request.
  • Corrected an issue introduced in GeoBase v4.31 that caused autocomplete geocoder operations to slow down significantly for GeoStream queries.

Chameleon Workbench

  • Fixed an issue that caused an error message to be shown when opening the same script file twice and the same data file twice, and then trying to close the script file.
4.32

Changes made from version 4.31 to 4.32:

Chameleon Workbench

  • Corrected an issue that caused the application to freeze when loading a .csv file with no separator specified, and improved the error message that is presented in this situation.
  • Fixed an issue with importing custom layers into Chameleon Workbench.
  • Fixed an issue that caused an error message to be shown when the same script was opened multiple times in the Chameleon Workbench.
  • Corrected some text errors in the CSV file loader.
4.31

Changes made from version 4.30 to 4.31:

Geocoding

  • Improved the Autocomplete Geocoder to provide better location estimates of a street’s center.
  • Made several minor improvements to Autocomplete Geocoder search quality.
  • Added support for new Autocomplete Geocoder search indexes, which will be available as part of a future data release.
4.30

Changes made from version 4.29 to 4.30:

Geocoding

  • Added support for non-numeric street numbers and unit identifiers to the AutocompleteGeocoder and the LocationSearch APIs. The AutocompleteGeocoderSuggestion and LocationSearchSuggestion classes now have the following new properties:

    • StreetNumberFull: A numeric street number, a non-numeric street number (e.g. 3A), or a street number range (e.g. 10-12)
    • Units: A list of AddressUnit objects, which consist of a UnitType enumeration (e.g. Suite, Unit, or Apartment) and a number (e.g. 3 or 3A)

    The Units property has also been added to the StructuredAddressData class, so that addresses containing unit level identifiers, for example apartment numbers, can be presented correctly by the AddressFormatter.

    Note: Currently only English translations of UnitType can be parsed in AutocompleteGeocoder and LocationSearch queries.

Chameleon Workbench

  • Added the ability to open files in the Chameleon Workbench via drag and drop.

Alchemy

  • Changed Alchemy to support importing more than one street name at a time.