New Features
The following table lists new features in the current release.
Release 7.152
| Ticket Number | Description |
|---|---|
| GSQ-7917 | Geocode, Reverse Geocode, Lookup: HERE Geocoding and Search API v7 option addressNamesVariant[city]=administrative provides the administrative city name instead of the postal city name for address result in USA. |
| GSQ-11211 | Geocode: Improved search relevance: queries using the term “Korea” now correctly return South Korea rather than unrelated results from other regions. |
| GSQ-11338 | Geocode: The /geocode endpoint's support for abbreviations and omission of less relevant words in street names - such as person first names or titles - has been extended to Austria. The same approach for scoring penalties is applied as for previously supported countries. |
| GSQ-1066 | Autosuggest, Discover: Improved Australian address search for common street abbreviations. Australian address queries now better recognise and resolve frequently used street‑type abbreviations (for example, APP, CR, PDE, ESP). |
| GSQ-11391 | Autosuggest, Discover: Polish queries such as “BMW Dealerzy” now correctly match BMW dealer chain results. |
| GSQ-10862 | Autosuggest, Discover: Improved A&W brand search coverage in Canada and near the US–Canada border. |
| GSQ-11505 | Autocomplete: A new ranking engine has been introduced for autocomplete, delivering more accurate and intuitive suggestions. The updated logic improves prioritization of highly relevant results to better match user intent, while reducing low‑relevance suggestions for a more consistent text‑completion experience. As a result, changes in suggestions may be observed - especially for short queries where multiple results have similar relevance. These changes may include not only differences in ordering, but also different results appearing among the top suggestions. |
| GSQ-10586 | Autocomplete: Result type filters types=address, types=street and types=houseNumber are released as STABLE. |
Release 7.151
| Ticket Number | Description |
|---|---|
| GSQ-11290 | All endpoints: For address and place results in the United Arab Emirates, HERE Geocoding and Search API v7 now returns an additional administrative level - subdistrict - when available in the map data. Subdistricts represent community‑level identifiers (for example, “Mohammad Bin Zayed East 12”, “The Springs 9”, “Community 244”) and form the lowest level of the administrative hierarchy, below districts or neighborhoods within municipal regions. |
| GSQ-11284 | All endpoints: For address and place results in Saudi Arabia, HERE Geocoding and Search API v7 now returns an additional administrative level - subdistrict - when available in the map data. The subdistrict represents a block or subdivision within a neighborhood (district). |
| GSQ-3632, GSQ-3642 | Geocode: The /geocode endpoint's support for abbreviations and omission of less relevant words in street names - such as person first names or titles - has been extended to Germany. Because omitting these elements can increase ambiguity, a small penalty of 0.1 is applied to the street field score and 0.01 to the query score. Abbreviating them to the first letter does not add any extra penalty. |
| GSQ-7154 | Geocode: Improved support for address resolution in villages without street names, particularly through qualified partial queries, where only the locality and house number are provided as input. |
| GSQ-10311 | Geocode: In the USA, the /geocode endpoint now parses and interprets the keywords “county” and “city” together with administrative area names without applying penalties. For example, a query such as “Mercer County, NJ, USA” now correctly returns the county result “Mercer,” with the word “County” parsed as part of the county name. |
| GSQ-10775 | Autosuggest, Discover: Improved support for spelled out house numbers in English ("one" to "ten", "twenty", "thirty" to "hundred") and in in German ("eins" to "zwanzig"). |
| GSQ-2261 | Autosuggest, Discover, Lookup, Geocode, RGC/MRGC; Autocomplete: Australian postal code results now include the district name in both the result title and the addresslabel. Autocomplete is partially impacted: its address.label includes the district, while its custom result‑title format already included the district and remains unchanged. Example: 3141, South Yarra, Melbourne, Victoria, Australia. |
Release 7.150
| Ticket Number | Description |
|---|---|
| GSQ-10579 | Reverse Geocode: Result type filters types=houseNumber and types=place are released as STABLE. |
| GSQ-10749 | Autosuggest, Discover: Improved category/location search in Tokyo/Japan. Example: "Hotels in Tokyo". |
| GSQ-10634 | Autosuggest, Discover: Improved support for 8 digits postal codes in Brazil. |
| GSQ-10420 | Autosuggest, Discover: Queries in USA and Canada for highway entrances, for example: "highway", "highway entrances", "autopista", "autoroute", are now supported. |
| GSQ-9437 | Autosuggest, Discover: Improved search support for Shell charging stations and pertrol stations (such as, for example, "shell recharge", “shell charging stations”, "shell petrol stations"). |
| GSQ-9314 | Autosuggest, Browse, Discover, Lookup: Added references to the following parking places suppliers: hereParking, truckParkingClub and tollCollect. |
| GSQ-637 | Autosuggest, Browse, Discover, Lookup: show=referenceCategories adds the related category IDs to place results references. |
| GSQ-8109 | Autosuggest, Browse, Discover: Added evStation[maxPower] filter to the already existing evStation[minPower] filter. |
| GSQ-636 | Autosuggest, Browse, Discover, Signals: CORS for POST method is now supported. |
Release 7.149
| Ticket Number | Description |
|---|---|
| GSQ-666 | Signals: Added the new /signals endpoint as a RESTRICTED feature. |
| GSQ-10299 | Autosuggest, Discover: Improved country search in Chinese. |
| GSQ-9842 | Autosuggest, Discover: Improved quality of queries for recycling centers in Germany. |
Release 7.148
| Ticket Number | Description |
|---|---|
| GSQ-3223 | Geocode: Improved address matching quality in small villages of Poland, where the street names are identical to the locality names. |
| GSQ-650 | Browse: Project-scoped authentication tokens are now supported on POST requests. |
Release 7.147
| Ticket Number | Description |
|---|---|
| GSQ-9955, GSQ-9648 | All endpoints: HERE Geocoding and Search now exclusively uses 7-digit postal codes from the Postal Addressing product for address and place results in Portugal. For street and area results, HERE Geocoding and Search returns 4-digit “area” postal codes. For queries with only a 7-digit postal code, it now returns the results with a type postalCodePoint, while for 4-digit "area" postal code queries, it returns the results with a type locality with localityType=postalCode. |
| GSQ-9826 | Autocomplete: Similarly to the /geocode endpoint, the /autocomplete endpoint in Portugal now exclusively uses 7-digit detailed postal codes sourced from the Postal Addressing product due to their higher reliability. |
| GSQ-10095 | Geocode: The feature to return an additional block containing the normalized unit type and unit value for each recognized unit designator, such as a suite or a floor, is extended to Puerto Rico. This feature is activated with the show=secondaryUnitInfo parameter. |
Release 7.146
| Ticket Number | Description |
|---|---|
| GSQ-9641, GSQ-9643, GSQ-4464, GSQ-9390 | All endpoints: HERE Geocoding and Search API v7 had improved support for postal code–only queries, added postalCodePoint results for Taiwan and Israel, expanded coverage for the Isle of Man, in the United Kingdom expanded coverage to the Northern Ireland, and increased coverage for the USA, Canada, the Netherlands and the other parts of the United Kingdom; The Reverse Geocoder continues to return postalCodePoint results only in a limited set of countries, with this release providing minor coverage increases. |
| GSQ-10043, GSQ-9629 GSQ-9630 GSQ-9631 | Geocode, Reverse Geocode, Multi-Reverese Geocode, Autocomplete, Lookup: The HERE Geocoding and Search API v7 endpoint features related to Micro Point Addresses (MPA) have been extended to Austria, currently covering the city of Vienna only. As in other countries, the feature to retrieve MPA content is only available to authorized customers. |
| GSQ-9308 | Autosuggest, Browse, Discover, Lookup: The show=truck option enables authorized customers to get details about available truck amenities: carWash, chemicalToiletDisposal, highCanopy, idleReduction, nightParkingOnly, paidParking, parking, powerSupply, reservableParking, secureParking, truckScales, truckService, truckStop, truckWash, wifi. |
| GSQ-663 | Autosuggest, Browse, Discover, Lookup: The show=fuel option enables authorized customers to get fuel types details in the gas station results. The show=fuelPrices option enables authorized customers to get the fuel prices in gas station results. Autosuggest, Browse, Discover: The fuelStation option enables authorized customers to set some constraints on potential gas station results (for instance only serving Diesel, or E5/E10 fuel type). |
| GSQ-9236 | Geocode, Lookup, Reverse Geocode, Multi-Reverese Geocode: Added attribution to an address to identify if an address is a residential address or a commercial (business) address with the parameter: show=addressUsasge. Note: The feature is released as ALPHA with a restricted access to authorized customers only. |
| GSQ-9790 | Autosuggest, Discover: Requests for "baumarkt" in Germany now return hardware store places belonging to the well known German hardware store chains (like Bauhaus, Obi, Hornbach, etc.). |
Release 7.145
| Ticket Number | Description |
|---|---|
| GSQ-9463, GSQ-4370 | All endpoints: In the USA, HERE Geocoding and Search API v7 already applies logic to set the default city name for address and place results based on USPS definitions. This logic has been extended to include street segments not covered by USPS data, ensuring consistency with the majority of nearby addresses. |
| GSQ-9164 | Geocode: The /geocode endpoint in Portugal now prioritizes 7-digit detailed postal codes sourced from the Postal Addressing product over those from the Core Map due to their higher reliability. In future releases, HERE Geocoding and Search API v7 will transition to exclusively using 7-digit postal codes from the Postal Addressing product for address and place results. |
| GSQ-9119 | Geocode: The /geocode endpoint logic has been enhanced to reflect the high reliability of "short addresses" in Saudi Arabia. For queries containing a short address, the /geocode endpoint now more consistently returns a matching house number result - even when large part of the query does not align with the result. |
| GSQ-8718 | Geocode: Enhanced /geocode endpoint behavior for Japanese addresses to prevent incorrect matches when block or house numbers are invalid, ensuring consistent results across both hyphen and Chome (丁目) formats. |
| GSQ-8474 | Geocode: In the Netherlands, hyphenated house numbers are commonly used to indicate subdivisions within a main building. The /geocode endpoint now supports matching queries where the end user has omitted the hyphen in the house number to corresponding hyphenated entries in the map data. In cases of ambiguity, the /geocode endpoint prefers matches that retain the original format. |
Release 7.144
| Ticket Number | Description |
|---|---|
| GSQ-9132 | Reverse Geocode, Multi-Reverese Geocode: Match the input location to the nearest Micro Point Address (MPA), enhancing Reverse Geocoder accuracy in compounds where multiple buildings share the same address. The feature is released as STABLE in the /revgeocode and the /multi-revgeocode endpoint. The access to MPA content is restricted to authorized customers only. Parameter with=MPA returns the MPA closest to the input location. Parameter showRelated=parentPA returns the related Point Address to which the MPA belongs. Parameter showMapReference=microPointAddress returns the MPA identifier for the MPA result. |
| GSQ-9097 | Reverse Geocode, Multi-Reverse Geocode: When bearing is provided in the request, the road that allows automobiles is preferred among roads in the same direction by default. |
| GSQ-8756 | Reverse Geocode, Multi-Reverse Geocode: Return the locally preferred street name if the street has multiple names across different route types. |
| GSQ-9208 | Autosuggest, Discover: Improved search support for the chain 99 Ranch Market. |
| GSQ-8542 | Autosuggest, Discover: Improved support of rest areas search in Malaysia. For instance "RnR" is treated as a synonym for Rest And Relaxation when such places are searched by name. |
| GSQ-8007 | Discover, Search: Thai language support: introduced phonetic tokenizer based on Introduced Royal Thai Latin System. |
| GSQ-9127 | Geocode: In the United States, HERE Geocoding and Search API v7 now includes all city names recognized for a postal code by USPS - additionally to overlapping cities from map data - to improve geocoding results for queries with unmatched address details. These additional city names are used for matching only and are not shown in results. |
Release 7.143
| Ticket Number | Description |
|---|---|
| GSQ-647 | Discover, Browse, Lookup: The queries with show=tripadvisorImageVariants parameter, now return the URLs of images in various sizes. |
| GSQ-8966 | Autosuggest, Discover: Improved support for ALDI chain in the french language. |
| GSQ-8475 | Geocode: Adjusted the scoring for postal codes in Portugal to align with other countries that use similarly detailed postal codes: 90% of the total score is now assigned to the "base" area part of the postal code, and 10% to the "extension" part. |
| GSQ-8470 | Geocode: The /geocode endpoint now can recognize and parse, without additional penalties, house number prefixes in Brazil, such as, for example, "casa": ""casa 52" in the query is now parsed as a house number and matched to the house number "52" in the query. |
| GSQ-8465, GSQ-8466 | Geocode: Parsing additional information (additionalInfo block) extracted from the query that does not correspond to any recognized address components in the map data is now extended to "house grouping" information in Brazil. |
Release 7.142
| Ticket Number | Description |
|---|---|
| GSQ-8428, GSQ-8302, GSQ-8681, GSQ-8302 | Geocode, Lookup: Extended map reference information for related Micro Point Addresses (MPA). When the parameter showMapReference set to links or segments, the /geocode and /lookup endpoints now include links and segments map reference information also for MPAs in the related block - for MPA records that are related to a Point Address result - related MPA records are returned when the showRelated=MPA parameter is set. Retrieving map references is generally supported, but the feature to retrieve MPA content is only available to authorized customers. |
| GSQ-8300 | Autocomplete: When show=hasRelatedMPA is set, a flag is provided for a Point Address result in the /autocomplete endpoint to indicate that sub-premises (referred to as Micro Point Addresses in HERE terminology) are associated to the house number. This flag can be used to trigger a follow-up call to the /lookup endpoint using the corresponding id and the showRelated=MPA parameter to retrieve the Micro Point Address (MPA) list and details. Note that the feature is released as ALPHA, and the access to MPA content is restricted to authorized customers only. |
Release 7.141
| Ticket Number | Description |
|---|---|
| GSQ-8306 | Autosuggest: Improved terms suggestions monotonicity when termsLimit is set to a non-zero value. |
| GSQ-8408 | Autosuggest, Discover: Queries for places serving a certain cuisine (for example, pizza) return related places ranked by popularity when the with=recommendPlaces parameter is used. |
| GSQ-8642 | Autosuggest, Discover: Improved the support of chains named "Union Bank Of <Country name >;". |
| GSQ-8305 | Autosuggest, Discover: The postal code results for USA postal code queries do not include a street name anymore. For example, a query "53547" returns "53547, Janesville, WI, United States" instead of "53547 Milton Ave, Janesville, WI, United States". |
| GSQ-6795 | Geocode, Reverse Geocode: When the showRelated=intersections parameter is set, an improvement has been made to the existing nearby intersection feature: nearby intersections are now returned even if they belong to a different administrative hierarchy. |
| GSQ-8294, GSQ-8046 | Geocode: Postal codes in Brazil are now scored as "high precision" postal code: ninety percent of the total postal code field score is assigned to the 5-digit base part, while the remaining ten percent is allocated to the 3-digit extension. |
Release 7.140
| Ticket Number | Description |
|---|---|
| GSQ-7700 | all endpoints: In the West Bank, HERE Geocoding and Search API v7 results do not show country name and country code. The state is shown as "West Bank". |
| GSQ-6953 | Geocode, Lookup: Support for showMapReferences=microPointAddress. The HERE Geocoding and Search API v7 /geocode and /lookup endpoints now support a new value for the showMapReferences parameter: microPointAddress. When this parameter is set, the endpoints now include references to the Micro Point Address (MPA) in the following cases: For the results with resultType=houseNumber and houseNumberType=MPA - this result type is returned only if with=MPA parameter is specified; In the related block, for MPA records that are related to a Point Address result - related MPA records are returned when the showRelated=MPA parameter is set. This feature is available only to customers authorized to MPA features in general. |
| GSQ-3614 | Geocode, Discover, Autosuggest: Existing functionality to avoid candidates matching only on stop words or frequent terms is now extended to the rest of world, bringing performance and quality improvements. |
| GSQ-7898 | Geocode: The /geocode endpoint now supports directional abbreviations in street names in Mexico, for example "nte" for "Norte", without additional penalties on street or query scores. |
| GSQ-6984 | Geocode: Improved support of house number formats in Brazil. |
| GSQ-6719 | Geocode: Improved detection of secondary unit designators in Brazil. |
| GSQ-4463 | Geocode: In Colombia, the /geocode endpoint now tolerates the omission of key words identifying districts, such as Vereda (including abbreviated form Vda), Villa and Urbanizacion, with a 10% penalty on the corresponding field score and a 1% penalty on the query score. |
Release 7.139
| Ticket Number | Description |
|---|---|
| GSQ-7368 | all endpoints: For Puerto Rico, HERE Geocoding and Search API v7 now exposes additional administrative level - "sub barrios" - mapped to "subdistrict" address field. |
| GSQ-3806 | Geocode: The /geocode endpoint is now more resistant to replacing character "O" with digit "0" in the queries. |
| GSQ-7486 | Geocode: The /geocode endpoint now supports flexible word order in the street names in Israel, also for Hebrew in addition to the already supported English and Arabic street name variants. |
| GSQ-6720 | Geocode: HERE Geocoding and Search API v7 feature to detect and parse secondary unit designators from queries — such as suite or floor numbers — and, upon request, include them in the response in normalized form has been extended to Mexico |
| GSQ-1918 | Geocode: The /geocode endpoint now returns business-related names (such as, company names, building names, or floor information for delivery), along with their corresponding addresses, from 7-digit postal code input for Japan using the show=postalCodeDetails parameter. Feature maturity: ALPHA. |
| GSQ-7817 | Geocode: Parsing information now includes the additionalInfo block, which contains additional information extracted from the query that do not correspond to any recognized address components in the map data. Currently it is populated for Mexico with "house grouping" information such as, for example, "manzana" or "supermanzana". |
Release 7.138
| Ticket Number | Description |
|---|---|
| GSQ-698 | Discover, Autosuggest, Browse, Lookup: The driveThrough response parameter is now released as STABLE with general availability. It is set to true if the related business allows customers to purchase products (or use the service provided by the business) without leaving their cars. |
| GSQ-7568 | Geocode: Improved handling of numeric address elements in Romania: added support for leading zeros omission in postal codes; improved handling of address formats where the district is referenced with the number preceding "București" (e.g., "3 București") in Bucharest Numbered Districts; and added support for "nr" (short for "număr") as a prefix for house numbers. |
| GSQ-7334 | Geocode: In case of ambiguity, the /geocode endpoint in Switzerland now prefers results with matching postal code to results with matching district. The results with matching postal codes are expected to be more relevant due to higher accuracy and reliability of the postal code data. |
| GSQ-6424 | Geocode: Map data in Mexico may include "Fraccionamiento" ("residential subdivision") as a part of district name, which may be omitted in the query. The /geocode endpoint now treats omitting of this word in the query as less important, similarly to omitted street types, by reducing corresponding field score by 10% and query score by 1%. |
Release 7.137
| Ticket Number | Description |
|---|---|
| GSQ-6982 | Geocode Autocomplete, Discover, Autosuggest: HERE Geocoding and Search API v7 now supports all house number formats in Austria, available in the HERE Map Content. |
| GSQ-6869 | Geocode Autocomplete, Discover, Autosuggest: HERE Geocoding and Search API v7 now supports all house number formats in Puerto Rico, available in the HERE Map Content. |
| GSQ-6717 | Geocode: Improved detection of secondary unit designators in Austria. |
| GSQ-3598 | Geocode: Improved support of street type abbreviations for street types attached to the street base name in Scandinavian countries. |
| GSQ-7167 | Geocode: Qualified geocoding query 'Tokyo', and its variants in Korean and Japanese in the city field, return the Tokyo prefecture, the capital administrative unit of Japan. |
| GSQ-2239 | Autosuggest: Coordinate search returns an empty response if the request contains a country filter parameter, and the position is not in any country specified by that filter. |
Release 7.136
| Ticket Number | Description |
|---|---|
| GSQ-6512 | Geocode, Autocomplete, Discover, Autosuggest: For the multilingual countries, there may be two Point Addresses for the same house number - one for each language. HERE Geocoding and Search API v7"forward" endpoints now consistently return the result id and pointAddress.hmcId in mapReferences block that corresponds to the Point Address for the country default language. The /revgeocode endpoint, in case of ambiguity, continues returning the result id and pointAddress.hmcId in mapReferences block consistent with the response language. |
| GSQ-4967, GSQ-5445 | Geocode, Reverse Geocode: The position of the street result is now calculated considering attribution and functional class of the part of the road where it is located. |
| GSQ-1639 | Geocode: The /geocode endpoint now tolerates omission of leading zeros in postal codes, with the exception of Romania. |
| GSQ-6429 | Geocode: The /geocode endpoint now supports new value of types filter: types=place, which allows restricting results to result type: place. For the /geocode endpoint, place geocoding is treated as an alternative form of addressing. This allows, for example, geocoding business locations, including business names, in the same way as residential addresses. As a result, the place types filter is typically used in combination with other filters such as address or houseNumber, for example: types=address,place. Specifying types=place can be useful when the goal is to identify specific places or landmarks. Note that address results are not returned, and address queries may produce unexpected partially matching place results. |
Release 7.135
| Ticket Number | Description |
|---|---|
| GSQ-6085, GSQ-6641, GSQ-6395 | all endpoints: HERE Geocoding and Search API v7 has significantly increased coverage of building names in Hong Kong by integrating data from Building Footprints and places with category "residential area-building" as "building names". All the HERE Geocoding and Search API v7 endpoints return building names as a part of address results for addresses which have associated building name. Additionally, the /geocode endpoint now offers comprehensive support of building names in Hong Kong: you can search for an address by its building name. To avoid ambiguity it is better to additionally include into the query the street name and administrative names or spatial context. |
| GSQ-6386 | Geocode: In Hong Kong, many building names include sub-premise information, such as numbered "block" or "phase". For Latin language queries, the /geocode endpoint now supports flexibility in writing the building sub-premise information in the query: swapped order of building name and sub-premise number in the query - without penalty; omission of sub-premise information - with penalty of 0.1 on building field score. |
| GSQ-6365 | Geocode: The /geocode endpoint now supports commonly used abbreviations in building names in Hong Kong. |
| GSQ-6177 | Geocode: In addition to already supported omission of key words identifying administrative places in Taiwan, the /geocode endpoint now supports cases where the locality prefix used in the query differs from such in the map data. For example, "town" is used instead of "township". The /geocode endpoint tolerates it with a 10% penalty on the corresponding field score and a 1% penalty on the query score. |
| GSQ-5094 | Geocode: There are many romanization systems used in Taiwan, with the most commonly used also for administrative names and for use on signs: Wade-Giles, Hanyu Pinyin and Tongyong Pinyin. The /geocode endpoint now can find the matching result independent on which kind of romanization system is used in the query, and which kind of romanization system is used in the map data. |
| GSQ-4271 | Geocode: Street naming in most of Taiwan follows a hierarchical model in which the main roads have descriptive names (for example, Yuan Dong Rd.) and are often divided into multiple sections along their length (for example, Sec 2, Yuan Dong Rd.). Minor roads that intersect these main roads have the same name as the main road, including the section number, with an additional lane number (for example, Lane 423, Sec 2, Yuan Dong Rd.). Minor roads that intersect the lane additionally have the alley number (for example, Alley 31, Lane 423, Sec 2, Yuan Dong Rd.). The /geocode endpoint now supports this hierarchical model, preferring the result on correct alley/lane/section, where the section part may be omitted. If the address on the correct street is not available in the map data, the geocode prefers house number fallback on the correct street or up-hierarchy fallback along the streets hierarchy to an address result on a wrong alley/lane/section. For Latin script queries, the /geocode endpoint supports flexibility in the form and order of alley/lane/section parts. |
| GSQ-6794 | Geocode: In Taiwan, an address query may contain a group of hyphen (“-” or “之”) separated numbers. This group may represent a number of an individual building, or a house number accompanied by a sub-premise numbers. For the second case, the /geocode endpoint now correctly matches first number as an exact matching house number without any penalty on house number field score. For the first case, the /geocode endpoint continues matching the group of numbers to a hyphenated Point Address. |
| GSQ-6699 | Geocode: The /geocode endpoint now supports common abbreviations for names of administrative places in Hong Kong, for example: "HKI", "H.K." for "Hong Kong Island"; "KLN" for "Kowloon"; "NT" for "New Territories". |
| GSQ-6484 | Geocode: In Hong Kong, Arabic numbers are used along with Chinese numbers for the numeric part of building names in Chinese. The /geocode endpoint now considers them equivalent, and can find the matching building name independent on which kind of numbers is used in the query and which kind of numbers is used in the map data. |
| GSQ-1621 | Geocode, Reverse Geocode: Nearby crossings are returned if the input is near the unnamed street or the arrival street of the house number is on an unnamed street. The parameter is showRelated=intersections. The feature is currently supported in the following countries/regions: Australia, Austria, Belgium, Brazil, Canada, Denmark, Finland, France, Germany, Hong Kong, Indonesia, Italy, Luxembourg, Macau, Malaysia, Mexico, Netherlands, New Zealand, Norway, Poland, Portugal, Singapore, South Africa, Spain, Sweden, Switzerland, Taiwan, Thailand, Turkey, United Kingdom, United States, Vietnam. |
| GSQ-5706 | Geocode, Reverse Geocode: showRelated=intersections parameter is released as STABLE. |
| GSQ-6284, GSQ-6283 | Geocode, Autocomplete, Discover, Autosuggest: Since Hong Kong is modeled in HERE Map Data as a multilingual country, there may be two Point Addresses for the same house number - one for each language. HERE Geocoding and Search API v7 "forward" endpoints now consistently return the result id and pointAddress.hmcId in mapReferences block, that corresponds to the Point Address for the Chinese language. The /revgeocode endpoint, in case of ambiguity, continues returning the result id and pointAddress.hmcId in mapReferences block consistent with the response language. |
Release 7.134
| Ticket Number | Description |
|---|---|
| GSQ-1825 | all endpoints: In Canada, the locality name used for addressing according to postal conventions may differ from the administrative city name. To ensure that result titles and address labels are both recognizable and accurate for local users, HERE Geocoding and Search API v7 now incorporates postal municipality names in these fields. The names in the address block of a HERE Geocoding and Search API v7 response reflect the administrative perspective. |
| GSQ-4197 | all endpoints: In Hong Kong, the names of the buildings are included into the result title and address label (in case of the /autocomplete endpoint only into the address label). Note that with this release, the coverage and overall support of building names for Hong Kong has not changed and is rather limited. |
| GSQ-5507 | Geocode: The addressNamesMode feature of the /geocode endpoint, which enables users to choose between displaying normalized or matched address fields in the response, is extended to support not only the option to show normalized names, but also matched names: addressNamesMode=matched, affecting the names in the address block, the address label, and the result title. This option is relevant when there is a difference between administrative naming and postal or common naming conventions, or when addressing with alternative street names. By default, geocoding results provide matched names for administrative places, and normalized (official) names for street names. |
| GSQ-4135 | Geocode: In Hong Kong, in otherwise Chinese address queries, the end users now can use either Arabic or Chinese numbers as house numbers. The /geocode endpoint now supports both representations, and can match them to the Arabic house number representations in the map data. |
Release 7.133
| Ticket Number | Description |
|---|---|
| GSQ-5807 | all endpoints: In the United Kingdom, in areas where there is a difference between postal and administrative districts, the administrative one is now consistently used as the default one for address and place results. The postal one is only returned by the /geocode and /autocomplete endpoints for address and place results if it matches the query. |
| GSQ-5715 | Geocode: showTranslations feature is released as STABLE. |
| GSQ-5859 | Geocode: Further improvements of the feature that resolves the ambiguity in house numbers in the query by using the country's typical address format. The work on this improvement will be continued as it does not yet cover all scenarios. |
Release 7.132
| Ticket Number | Description |
|---|---|
| GSQ-5320 | Autosuggest, Discover: "truck EV stations" and "LKW Ladestation" queries return places with categories 700-7600-0323. "bike EV stations", "scooter EV stations", and "Motorrad Ladestation" queries return places with categories 700-7600-0324. |
| GSQ-5284 | Geocode: The feature that resolves the ambiguity in house numbers in the query by using the country's typical address format is now extended to a big set of countries, but still does not address all possible situations. The work will be continued. |
| GSQ-5240 | Geocode: In Taiwan, the /geocode endpoint now treats 台 and 臺 for Chinese character for 'Tai' as equivalents. |
| GSQ-4768 | Geocode: In Taiwan, the /geocode endpoint now tolerates the omission of key words identifying administrative places in Chinese, such as 縣 (county), 市 (city), 鄉 (township), 區 (district), 鎮 (town), with a 10% penalty on the corresponding field score and a 1% penalty on the query score. |
| GSQ-4198 | Geocode: Improved secondary unit designators detection in Hong Kong. |
Release 7.131
| Ticket Number | Description |
|---|---|
| GSQ-951 | Autosuggest, Discover: "yang" requests in USA and Canada now get more local results. |
| GSQ-4992 | Autosuggest, Discover: Improved searchability of delivery entrance places. |
| GSQ-5322 | Geocode: The reverse geocode endpoint BETA feature showRelated=intersections to include a block containing a list of intersections nearest to the address for the result items with resultType=houseNumber or resultType=street is now extended to the /geocode endpoint. |
| GSQ-4187 | Geocode: Improved secondary unit designators detection in Taiwan. |
| GSQ-4134 | Geocode: In Taiwan, in otherwise Chinese address queries, the end users now can use either Arabic or Chinese numbers as house numbers. The /geocode endpoint now supports both representations, and can match them to the Arabic house number representations in the map data. |
Release 7.130
| Ticket Number | Description |
|---|---|
| GSQ-4927 | Geocode, Autocomplete: All the known minor issues for features postalCodeMode=cityLookup and postalCodeMode=districtLookup have been fixed. The features are promoted from BETA to STABLE. |
| GSQ-3365 | Autocomplete: Improved success rate and monotonicity for short queries starting with house number and first letters of the street name. |
| GSQ-949 | Geocode: Improved support of queries where street type in the query differs from street type in the map data. For example for query "72 wakis street randburg south africa" geocode now successfully returns "72 Wakis Ave, Randburg, 2194, South Africa". |
| GSQ-5011 | Geocode: The /geocode endpoint now considers the pound symbol (#) in the USA as a valid normalized secondary unit designator. For example, for queries like "4212 Medical Dr, #1712, San Antonio, TX 78229", "#1712" it is not only successfully parsed as secondary unit, but with 'show=secondaryUnitInfo' parameter pound symbol '#' is also included into secondaryUnitInfo as normalizedUnitType. |
| GSQ-4739 | Geocode: The feature that resolves ambiguity in house numbers in the query by using the country's typical address format is now extended to Argentina. In case of Argentine, the expected position of house number is after the street name. |
| GSQ-4475 | Geocode: The feature to return the normalized form of secondary unit designators is extended to IND, in addition to the already supported AUS, AUT, BRA, CAN, ESP, FRA, GBR, IDN, NZL, TUR, TWN and USA. |
| GSQ-4459 | Geocode: The feature that resolves ambiguity in house numbers in the query by using the country's typical address format is now extended to Australia. In case of Australia the expected position of house number is in front of street name. |
| GSQ-4120 | Geocode: From version 7.130, the /geocode endpoint enables users to choose between displaying normalized or matched address fields in the response, affecting the names in the address block, the address label, and the result title. This option is relevant when there is a difference between the administrative naming and postal or common naming conventions. By default, geocoding results provide matched names for administrative places and normalized (official) names for street names. The feature is activated by parameter: addressNamesMode=normalized. |
| GSQ-1645, GSQ-4738 | Geocode: The /geocode endpoint now supports more commonly used abbreviations in the Portuguese language such as, for example, "Cde" for "Conde". And for Spanish language, for example "Cnel" for "Coronel". |
| GSQ-4841 | Geocode: Improved support of tokenization for Latin script (Pinyin) queries - additionally to already supported case when the street name in the map data is tokenized, and in the query is not, the /geocode endpoint now also supports more seldom opposite case. |
| GSQ-4823 | Reverse Geocode, Multi-Reverse Geocode: The feature showRelated=nearbyAddress is promoted to STABLE. |
Release 7.129
| Ticket Number | Description |
|---|---|
| GSQ-4029 | All endpoints: Adapted representation of administrative structure in Dominican Republic. "Provincia" is now mapped to "state", "Municipio" to "county", this allows settlements, such as for example "Punta Cana", to be mapped to "city" administrative level. |
| GSQ-734 | Autosuggest, Browse, Discover, Lookup: Added support of HERE API keys for the show=ev option. |
| GSQ-3214 | Autosuggest, Browse, Discover: Restrict the route query parameter width to max 50km. |
| GSQ-3866 | Autosuggest, Discover: Cardinal and ordinal numbers within street, place, and area search queries are now supported in the following languages: English, French, German, Italian, Japanese, Portugese, Spanish, and Turkish. |
| GSQ-4260 | Geocode: Improved support of tokenization for Latin script (Pinyin) queries - now it also works when street name in the map data is tokenized and in the query it is not. For example, for a query "No. 9, Pucheng St, Da’an District, Taipei City, Taiwan 106" the geocode endpoint now successfully returns address result: "No. 9, Pu Cheng St., Daan District, Taipei City, 106, Taiwan". |
| GSQ-4474, GSQ-4472, GSQ-4210, GSQ-4208, GSQ-4206, GSQ-4160 | Geocode: The feature to return the normalized form of secondary unit designators is extended to AUS, AUT, BRA, ESP, FRA, GBR, IDN, NZL, TUR, TWN, in addition to the already supported CAN and USA. |
| GSQ-4037 | Geocode: In Taiwan, Arabic numbers are used along with Chinese numbers for the numeric part of street names in Chinese. The geocode endpoint now considers them as equivalent, and can find the matching street independent on which kind of numbers are used in the query, and which kind of numbers is used in the map data. For example, for the following query: '新北市新店區北新路1段14號1樓", the geocode endpoint now returns "台灣231003新北市新店區北新路一段14號" (No. 14, Sec 1, Bei Shin Rd., Xindian District, New Taipei City, 231003, Taiwan), where the Arabic “1” in the street name in the query is now matched to the Chinese “一” in the street name in the map data. |
| GSQ-1885 | Geocode: The feature to tolerate omitted low relevant words in street names, such as names of a person or stop words, is now extended to Basque language. |
| GSQ-3752 | Reverse Geocode: The reverse geocode endpoint now returns the address using the "official" street name, meaning the name linked to the house number in the map data. |
Release 7.128
| Ticket Number | Description |
|---|---|
| GSQ-3485 | Geocode: Improved tolerance of the geocode endpoint to incorrect street type also when the street type is attached to the street base name. For example, "Semperallee" instead of "Semperstraße". |
| GSQ-1676 | Geocode: Added missing common street type abbreviations for Albania and Azerbaijan. |
| GSQ-1672 | Geocode: Added missing common street type abbreviations for Romania. |
| GSQ-1671 | Geocode: Added missing common street type abbreviations for Laos. |
| GSQ-1670 | Geocode: Added missing common street type abbreviations for Bonaire, Sint Eustatius and Saba. |
| GSQ-1669 | Geocode: Added missing common street type abbreviations for North Macedonia. |
| GSQ-1668 | Geocode: Added missing common street type abbreviations for Ukraine. |
| GSQ-1657 | Geocode: Added missing common street type abbreviations for Czechia. |
| GSQ-2758, GSQ-2757, GSQ-4205, GSQ-1972 | Geocode: For each recognized unit designator, such as suite or floor, the geocode endpoint provides an option to returns an additional block containing the normalized unit type and unit value. Currently supported countries: CAN, USA. This feature is activated with show=secondaryUnitInfo parameter. |
| GSQ-1950 | Autocomplete: The feature of the autocomplete endpoint postalCodeMode=cityLookup to return multiple results in areas where a postal code is associated with more than one city area is extended to the district administrative level. When a postal code spans multiple districts (within one city or across multiple cities), with postalCodeMode=districtLookup, the autocomplete endpoint returns all possible combinations of the postal code with the corresponding district and city names. Note that the feature is released as BETA. |
| GSQ-1938 | Geocode: The geocode endpoint now provides an option to return multiple results in areas where a postal code is associated with more than one district or city area. Without these options, the system only provides one result and may leave the district or city name blank or use a default name, potentially omitting relevant districts of cities. The feature is activated by parameter postalCodeMode. Supported values: cityLookup, districtLookup. Note that the feature is released as BETA. |
| GSQ-4167 | Autocomplete: For results with resultType: "locality" and localityType: "postalCode", HERE Geocoding and Search API v7 now includes into the address 'label' district information if it can be unambiguously defined for this postal code. |
Release 7.127
| Ticket Number | Description |
|---|---|
| GSQ-3811 | Reverse Geocode, Multi-Reverse Geocode: Request parameter showRelated=nearbyAddress, adds a nearby address as an additional reference to the street level results in Reverse Geocode or Multi-Reverse Geocode, the feature is only available with parameter bearing or types=street. The feature is released as a BETA feature. |
| GSQ-3629 | All endpoints (except Autocomplete): For results with resultType: "locality" and localityType: "postalCode", HERE Geocoding and Search API v7 now includes into the result 'title' and address 'label' district information, if it can be unambiguously defined for this postal code. |
| GSQ-1667 | Geocode: In Belgium, the /geocode endpoint now tolerates the omission of key words identifying states, such as "Région"/"Région de" or "“Gewest” - with 10% penalty on state field score. |
| GSQ-1662 | Geocode: In Bulgaria, the /geocode endpoint now supports spelled out dates in street names - without additional penalties. For example, it recognizes "Osmi Mart" as a synonym of "8-mi Mart”. |
| GSQ-3888 | Autosuggest, Discover: "tesla" queries return both EV stations and car dealers for that brand. |
Release 7.126
| Ticket Number | Description |
|---|---|
| GSQ-2859 | Geocode: HERE Geocoding and Search API v7 now tolerates better different forms of street types in Norway. This includes different definite forms, definite, and indefinite forms, and "vei" to "veg" ("veien" to "vegen"). |
Release 7.125
| Ticket Number | Description |
|---|---|
| OSQ-41710 | all endpoints: HERE Geocoding and Search API v7 improved admin classifications in Vietnam. |
Release 7.124
| Ticket Number | Description |
|---|---|
| OSQ-41468 | all endpoints: Timezone library is updated to version 2023b.21. |
| OSQ-39705, OSQ-40961 | all endpoints: Thailand: Improved representation of administrative structure, address label, and result title formats. |
| OSQ-39647 | Geocode, Reverse Geocode, Multi-Reverse Geocode, Lookup: Parameter showMapReferences=links is promoted to STABLE. |
| OSQ-34679 | Autosuggest, Browse, Discover: Support for http POST method is promoted as a RESTRICTED BETA feature. |
| OSQ-41461 | Autosuggest, Browse, Discover: Results of requests with both a route and a ranking=excursionDistance parameters are sorted by increasing distance from the route polyline. This feature can be used to get results spread all along the route. This is a BETA feature. |
| OSQ-39202 | Autosuggest: Responses for queries with parameter show=details contain address details, places contact information, and places opening hours. |
| OSQ-35964 | Geocode: Improved support of queries with missing dividing spaces between individual tokens. |
| OSQ-40718 | Geocode: Added missing common street type abbreviations for the following languages: en-AE - English (Arabic), eu - Basque, ca - Catalan, nl - Dutch, en - English, fr - French, de - German, gl - Galician, it - Italian, pt - Portuguese, es - Spanish. |
Release 7.123
| Ticket Number | Description |
|---|---|
| OSQ-41137 | Geocode, Lookup: Micro Point Address (MPA) support in Australia, Canada, New Zealand, USA and Puerto Rico is promoted from ALPHA to STABLE. |
| OSQ-40086 | Geocode: In the United Kingdom,HERE Geocoding and Search API v7 /geocode endpoint now returns full postal code suggestions also when they do not perfectly match to the postal code in the query. |
| OSQ-39428 | Geocode: For results with resultType=street, HERE Geocoding and Search API v7 /geocode endpoint now includes postalCode and district name even if the street spawns multiple postal codes or districts. In such cases the /geocode endpoint returns postal code and district aligned with the coordinate position which it returns for the street result. Note: This is not supported for street name only queries without any locality indication. |
| OSQ-40953 | Geocode: For Latin script queries in Taiwan, HERE Geocoding and Search API v7 /geocode endpoint now consistently recognizes "No." as valid house number prefix. |
Release 7.122
| Ticket Number | Description |
|---|---|
| OSQ-40945 | Geocode, Discover, Autosuggest, Autocomplete: HERE Geocoding and Search API v7 now supports addressing via alternative street names. When a street has multiple names, HERE Geocoding and Search API v7 can locate an address using any of the street names. Supported countries: Australia, Brasilia, Indonesia, the Netherlands, Poland, Portugal, Romania, Slovakia, USA (since version 7.108). In cases of ambiguity, the /geocode, /discover, and /autosuggest endpoints return the address with the "official" street name, i.e. the name associated with the house number in the map data. The /autocomplete endpoint will continue returning the address with the matched street name. |
| OSQ-40566 | Geocode: The /geocode endpoint has extended Micro Point Address related features support to Canada and Puerto Rico. These features are released as restricted. |
| OSQ-38778 | Geocode: If a query contains postal code and/or administrative place name which can be matched, but street or place name in the query do not match to the map data, thr /geocode endpoint now prefers up-hierarchy fallback to the matching area result with low query score, instead of no result or a result far away without any (or very bad) match on postal code or administrative area name. |
| OSQ-37925 | Autosuggest, Browse, Discover: EV station filter added for e-mobility service providers (eMSP). |
Release 7.120
| Ticket Number | Description |
|---|---|
| OSQ-39802 | Autosuggest: Increased likelihood of chain suggestions for perfect matches even in areas with much users engagement. |
Release 7.119
| Ticket Number | Description |
|---|---|
| OSQ-32520 | Geocode, Lookup, Autocomplete, Reverse Geocode, Discover, Autosuggest, Browse: In the USA, for address and place results, by default (when no city name is in the query), HERE Geocoding and Search API v7 now returns city name as defined by USA USPS for this specific address or majority of address on the street block. If the end-user specifies city name in the query and it is not the preferred one for the address or place, HERE Geocoding and Search API v7 still will return the matched city name to follow the end-user view. |
| OSQ-25272 | Geocode, Lookup, Autocomplete, Reverse Geocode, Multi-Reverse Geocode: HERE Geocoding and Search API v7 response for these endpoints may now include additional flag: estimatedPointAddress - if true, it indicates that the coordinates of 'position' and 'access' points of the Point Address are estimated. |
| OSQ-27394 | Reverse Geocode: The house number interpolation logic in Reverse Geocode has been enhanced. When multiple types of address ranges exist on a street, house numbers are now only interpolated from the actual address range, as it provides higher accuracy compared to the logic address range. However, if only a logic address range is available on the street, it will still be used for house number interpolation. |
| OSQ-39955 | Autosuggest, Browse, Discover, Geocode, Lookup: Added high precision postal code to some place results in Canada. |
| OSQ-39397 | Autosuggest: Tokyo University can be found with its abbreviated University name "東大" |
| OSQ-39704 | Autosuggest, Discover : Enhanced the Thai support for places category search |
| OSQ-39437 | Autosuggest, Discover : Improved search-ability of Urgent Care centers |
| OSQ-39788 | Autosuggest, Discover, Browse, Geocode, Lookup, Reverse Geocode : Increased coverage of street names translations for places in the followingcountries: ARE, BHR, DZA, EGY, HKG, JOR, KWT, LBY, MAC, MAR, OMN, QAT, SAU, THA, TUN |
| OSQ-39590 | Geocode: Improved ranking of results in countries with detailed postal codes, like Great Britain or Canada. In case of an ambiguous query or incomplete map data, Geocoder ranks results in the following order: address result if house number, street and at least base part of postal code match; exactly matching postal code point result; house number fallback, or street results. |
| OSQ-38909 | Geocode: The /geocode endpoint now parses hash (#) as valid house number prefix in few more languages/countries, including Spain, Mexico, and New Zealand. |
| OSQ-37901 | Geocode: Thailand: for the query which includes street name and a number, the /geocode, additionally to a house number result, now returns a street result with a suffix number as part of street name, since both results are equally relevant. |
Release 7.118
| Ticket Number | Description |
|---|---|
| OSQ-34936 | all endpoints: Thailand: Improvement of address labels and titles for postal code results. |
| OSQ-38471 | Discover: Improved search quality for "roth" chain queries. |
Release 7.117
| Ticket Number | Description |
|---|---|
| OSQ-38454 | Autosuggest, Discover: "aldi" chain search improvement: "aldi" requests only return groceries of this chain instead of both the groceries and the EV stations. |
| OSQ-38337 | Autosuggest, Discover, Browse, Lookup: Added access restriction details to Parking place results. |
Release 7.116
| Ticket Number | Description |
|---|---|
| OSQ-36248 | Autosuggest: Improved support for house number suggestions in the Czech Republic. For instance, a request "Vinohradska 30" returns both results in Prague: Vinohradska 30/75 and Vinohradska 34/30. |
| OSQ-38931 | Autosuggest : Improve searchability of Starbucks near Seattle Pike St and Pike drive. |
| OSQ-38372 | Autosuggest, Discover : Added the support for EWIVA EV station places chain EWIVA (ID 303044). |
| OSQ-38911 | Autosuggest, Discover : Bulgarian requests "ПАРКИРАНЕ" now return parking places. |
| OSQ-38469 | Autosuggest, Discover : Requests "Toom der Baumarkt" now return places from the German chain Toom Baumarkt. |
| OSQ-38475 | Discover : Places chains names that include an article can be searched by using the chain name with and without the article. Chain names in German, French, Italian, Spanish, and Portuguese can be searched with or without their respective prefix articles, with special rules for French and Italian names depending on whether the name begins with a consonant or vowel. |
| OSQ-38600 | Autosuggest, Discover Added the support for Amazon Hub places chain (ID 303034). |
Release 7.115
| Ticket Number | Description |
|---|---|
| OSQ-38486 | Geocode: Map data in some countries may include region or municipality identifiers, like synonyms of "state", "county" or "city" in the local languages. Geocode endpoint now treats omission of the region identifiers in the query as less important, similarly to omitted street types, by reducing corresponding field score on 10% and query score on 1%. |
| OSQ-38376 | Lookup: A flag closedPermanently is added in the /lookup endpoint response for a place which is permanently closed or maybe closed. Feature maturity: ALPHA. |
Release 7.114
| Ticket Number | Description |
|---|---|
| OSQ-38350 | Geocode: "types" filter is promoted from "beta" to stable. |
| OSQ-38376 | Geocode: parameter "showTranslations" with supported values "state", "county", "city", "district", is released as ALPHA. With this parameter, Geocode shows translations and alternative names of the provided fields in all available languages. |
| OSQ-38350 | Autocomplete: postalCodeMode=cityLookup is promoted from "alpha" to stable. |
| OSQ-38350 | Geocode, Lookup: show=postalCodeDetails is now supported. For each result item of types postalCodePoint renders a block with additional information about this postal code. This feature is currently available only in the countries which are using ZIP codes - USA, PRI, VIR, GUM, MNP and ASM. |
| OSQ-37505, OSQ-37507 | Geocode: Indonesia: Queries for Rukun Tetangga (RT, Neighborhood Unit) in combination with Rukun Warga (RW, Community Unit) are now supported, for example: "DKI Jakarta Cilandak Jakarta Selatan RT09/RW10". The results are returned with resultType: "addressBlock", addressBlockType: "block". The /geocode may return results of this type for queries targeting Rukun Warga (RW, Community Unit), or as up-hierarchy fallback for address queries, when street name in the query cannot be matched to the map data. Queries targeting Rukun Warga (RW, Community Unit) are not supported. HERE Geocoding and Search API v7 /lookup endpoint supports returning RT/RW block results by id. |
| OSQ-34490, OSQ-38677 | Geocode: The feature of the /geocode endpoint to treat omission of the region identifiers in the query as less important, similarly to omitted street types, by reducing corresponding field score on 10% and query score on 1%, is extended to next set of countries: TWN, NZL, BIH, BLR, CZE, EST, HRV, HUN, KAZ, KOS, LTU, LVA, POL, RUS, SRB, SVK, SVN, UKR, UZB. |
| OSQ-36694 | Geocode: HERE Geocoding and Search API v7 map data in some countries may include region or municipality identifiers, for example synonyms of "state", "county" or "city" in local languages. HERE Geocoding and Search API v7 /geocode endpoint now treats omission of the region identifiers in the query as less important - similarly to omitted street types: reduce corresponding field score on 10% and query score on 1%. Country: Vietnam; city and district administrative levels. Municipality identifiers city: "Quận", "Huyện"; district: "Phường", "Xã". |
| OSQ-38247 | Geocode: HERE Geocoding and Search API v7 map data in some countries may include region or municipality identifiers, like synonyms of "state", "county" or "city" in the local languages. HERE Geocoding and Search API v7 /geocode endpoint now treats omission of the region identifiers in the query as less important - similarly to omitted street types: reduce corresponding field score on 10% and query score on 1%. Country: Estonia; county administrative level. Region identifier "Maakond". |
| OSQ-38265 | Geocode: HERE Geocoding and Search API v7 map data in some countries may include region or municipality identifiers, like synonyms of "state", "county" or "city" in the local languages. HERE Geocoding and Search API v7 /geocode endpoint now treats omission of the region identifiers in the query as less important - similarly to omitted street types: reduce corresponding field score on 10% and query score on 1%. Country: Poland; state administrative level. Region identifier "Woj." ("Voivodeship"). |
Release 7.113
| Ticket Number | Description |
|---|---|
| OSQ-37983 | Geocode, Lookup: Micro Point Address (MPA) support in Australia, New Zealand, and USA as RESTRICTED ALPHA. |
| OSQ-38103, 38104 | Multi-Reverse Geocode: Multi-Reverse Geocode is released as stable. |
Release 7.110
| Ticket Number | Description |
|---|---|
| OSQ-36619 | All endpoints: Enhanced address search in South Africa: Building names in address queries are now being recognized and matched. In South Africa, building names exist for Erf numbers and other property designations. In results, building names are included in the building address attribute. The Geocoder endpoint can recognize and match building names. Note that searching for building names is not supported by other endpoints, including Autocomplete, Autosuggest, and Discover Search. |
| OSQ-37147 | All endpoints: Improved naming of district municipalities in South Africa: In district municipalities of South Africa, the default county naming convention is enhanced. Now, the default county name includes the name of the local municipality. The name of the district municipality is coded as an alternative county and will only be displayed in the response if it matches the query. |
| OSQ-36579 | Reverse Geocode: Change in the way results are prioritized by the Reverse Geocoder when the input coordinate falls on a street segment with no known addresses in the map data. Before: If the input coordinate was on a street segment without any addresses in the map data, the Reverse Geocoder would prioritize returning the closest house number as the first result, even if that house number was located on a different street. Now: The Reverse Geocoder now prioritizes returning the street itself as the first result when the input coordinate is on a street segment with no known addresses. House number results on different streets will still be provided, but they are now returned at lower positions in the results list, meaning they are considered less relevant. This change ensures that when you provide a coordinate on a street segment with no known addresses, the Reverse Geocoder will first return the street name itself as the top result, rather than immediately jumping to the closest house number on a different street. This can be particularly useful for users looking for information about the street itself, rather than specific house numbers. |
| OSQ-37407 | Reverse Geocode: Release of the with=estimatedAreaFallback parameter with a maturity level ALPHA in the Reverse Geocoder.
|
| Reverse Geocode: Multi-Reverse Geocoder endpoint released with restricted access. The HERE GS7 Multi-Reverse Geocoder endpoint is designed to increase the throughput performance of Reverse Geocoding requests. The endpoint allows the retrieval of the addresses of up to one hundred locations with one multi-reverse geocoding request. Please contact your Sales account manager if you are interesting in using the new endpoint. |
Release 7.109
| Ticket Number | Description |
|---|---|
| OSQ-36627 | Geocode: The Geocoder now matches zero-leading ZIP codes in the USA also for queries with omitted leading zeros. Example: 'q=1905 cooper st lynn' matches to 'Cooper St, Lynn, MA 01905, United States' with fieldScore postalCode of 100%. |
| OSQ-36956 | All endpoints: Enhanced address search in South Africa: Refined administrative level representation. Now, the city administrative level accurately reflects actual cities and towns, which are identified as KA zones, KD zones, or built-up areas with assigned population values in the HERE map. Other built-up areas are mapped to the district level. This adjustment has substantially improved the success rate of address searches and geocoding in South Africa. |
| OSQ-34868 | All endpoints: Enhanced address search in South Africa: In South Africa, residents often use the name of a metropolitan municipality seat for address or place searches within the entire metropolitan municipality. For instance, searching for addresses in the complete eThekwini Metropolitan Municipality with the city name Durban. Now, all endpoints support this addressing style. The response displays the address with the actual city or town name, providing users with more accurate and relevant results. |
All endpoints: Japan: enhancements to address and place results in Japan. Previously, the access coordinates for address results were identical to the position coordinates and did not represent points on the road. With this update, we have rectified this by providing accurate access coordinates on navigable road segments. Moreover, we have significantly expanded the coverage of access coordinates for place results in Japan. Previously, access coordinates were only available for large area facilities. This update ensures that more locations in Japan now benefit from precise access coordinates, enhancing the accuracy and usefulness of our services in the region. | |
| All endpoints: Japan: phonemes have been added to results for administrative areas, addresses and places. The phonemes for Japan results are in JEITA format and not in NT-SAMPA format as it is the case for all other regions. Phonemes are only available for Japanese language results. |
Release 7.108
| Ticket Number | Description |
|---|---|
| OSQ-36826 | Geocode: Geocode enhancement for INWANI: This update builds upon OSQ-34742 (Release 7.104) and further enhances the Geocoder's support for INWANI numbers in Qatar. The Geocoder now accommodates a wider range of query formats commonly used for INWANI numbers. Whether you input the query as "15700350035," "157-35-35," "157 35 35," or "Building No 35, Zone 57, Street 35, Doha, Qatar," the Geocode endpoint will yield accurate results by returning the corresponding house number based on the provided INWANI number. |
| OSQ-36216 | Geocode, Discover, Autosuggest: Geocoder and Search v7 endpoints have been updated to support the matching of complete 6-digit postal codes for addresses in Taiwan. Until now these more precise postal codes were available in as part of address and Place results. With this update, Geocoder and Search v7 can also recognize and match these 6-digit postal codes, further enhancing result disambiguation. Address queries with 3-digit postal codes continue to function as usual, with Geocoder and Search v7 rendering results that match the 3-digit postal code. |
| OSQ-36251 | All endpoints: All endpoints: Improved zip code coverage in Puerto Rico, similar to how it works in the USA. The coverage now includes two types of zip codes: those unique to a specific address and PO Box zip codes. Previously, Geocoder and Search v7 primarily returned 'area' zip codes that encompassed multiple addresses, and these were categorized under resultType=locality and localityType=postalCode. With this update, the coverage is expanded to include zip codes assigned to individual addresses or locations. These are now returned with resultType=postalCodePoint, similar to zip+4 postalCodePoint results. |
Release 7.107
| Ticket Number | Description |
|---|---|
| OSQ-36532 | All endpoints: Enhancements for PO Box search. This update builds upon OSQ-34193 (Release 7.107) and further enhances the coverage of PO Box zip codes. |
| OSQ-36563 | All endpoints: South Africa: Added building names for Erf numbers and other property designations to building address attribute. |
Release 7.106
| Ticket Number | Description |
|---|---|
| OSQ-36345 | Reverse Geocode: Improve road matching accuracy by considering the travel direction (aka track position). The new 'bearing' parameter expresses the direction of an asset's heading in degrees, starting from true North and continuing clockwise around the compass. The values range from 0 degrees (North) to 359 degrees (just before North again). For reference, East corresponds to 90 degrees, South to 180 degrees, and West to 270 degrees. Only integer values within the range of [0;359] are allowed for the 'bearing' parameter. Other values result in a 400 error response. The feature maturity level is BETA. |
| OSQ-36351 | Autosuggest, Discover, Browse: Japan: Added three Places categories that are commonly being used in Japan: Family Restaurant, Hot Springs, Roadside Station. The Place category names (engl.) and IDs are: "Family Restaurant", id: "100-1000-0050"; "Hot Spring", id: "300-3000-0450"; "Roadside Station", id: "400-4300-0251". Places coverage for these categories is currently limited to Japan. |
| OSQ-35455 | Autosuggest, Discover, Browse: Japan: For a small number of gas stations that are accessible via a highway, multiple routing points (access points in the API) are now available. In some cases, gas stations located near highways may have separate access points or entrances depending on the direction of travel. For example, a gas station may have different entry points for vehicles traveling west-bound and east-bound on a highway. Having multiple routing points or access points for these gas stations is important because it allows for more accurate and precise routing guidance. By providing separate access points based on the direction of travel, navigation systems can guide drivers to the appropriate entry point based on their intended direction. This helps ensure that drivers can easily and safely access the gas station from the correct direction of travel on the highway. |
| OSQ-34193 | All endpoints: Improved zip code coverage in the USA now includes three types of zip codes: those unique to an address, PO Box zip codes, and military postal codes. In the past, GS7 primarily returned 'area' zip codes with multiple addresses assigned to them, which were categorized under resultType=locality, localityType=postalCode. However, with the latest update, we have expanded the coverage to encompass zip codes assigned to individual addresses or locations, which are now returned with resultType=postalCodePoint, similar to zip+4 postalCodePoint results. |
Release 7.105
| Ticket Number | Description |
|---|---|
| OSP-6760, OSQ-35838, OSQ-35840 | Geocode: In cases where a query matches the same street name in different parts of the city, the geocoder now prioritizes results in the central part of the city over results in districts with different names. This ranking change aims to align with user expectations, as it is anticipated that if an end-user is searching for an address in a specific district, they would typically include the district name in their search query to further refine the results. For example, when searching for the address 'Serbia, Loznica, Vere Blagojevic,' the geocoder will now return the street 'Ulica Vere Blagojevic' located in the 'Loznica' district of the city 'Loznica' as the top result, instead of the one in the 'Lesnica' district. |
| OSP-6622, OSQ-35353 | Discover: Improved the search functionality for EV charging stations in Thailand, specifically focusing on improving the search experience in the Thai language. As part of this improvement, we have added Thai language-specific category translations. |
| OSQ-35026 | Geocode: Enhanced ability to recognize and interpret abbreviated street names. Geocoder now includes an expanded list of abbreviations in street names for the United States. These abbreviations align with the commonly used and standardized abbreviations published by the United States Postal Service (USPS). This enhancement applies to all street names with the language code set to "en" globally. |
Release 7.104
| Ticket Number | Description |
|---|---|
| OSQ-35333 | Reverse Geocode: New parameter with=unnamedStreets released as alpha feature. With this parameter, nearby unnamed streets are considered in the response. By default, Reverse Geocode suppresses streets for which the map does not provide a name. This is a parameter name change. The feature has been available with alpha status before. The previous parameter includeUnnamedStreet=true is deprecated and will not be supported anymore by end of August 2023. Please be aware that only the Reverse Geocode endpoints accept the with=unnamedStreets parameter. All other endpoints will respond with a HTTP 400 error (bad request) if this parameter is included in the request. |
| OSQ-35562 | Geocode: The Geocoder now offers comprehensive support for addressing with MAKANI numbers, including the concatenated format. This means that you can obtain accurate house number results by querying with MAKANI numbers in formats such as "14070 76513", "14070-76513", or "1407076513". However, it's important to note that while the GS7 geocode endpoint fully supports MAKANI numbers, other endpoints in the GS7 API, except for geocode, do not yet provide indexing for MAKANI numbers. This means that although MAKANI numbers will be included in the response from these endpoints, you cannot use MAKANI numbers alone to retrieve the desired result. For example, the autocomplete endpoint will not return any results for queries that include MAKANI numbers. |
| OSQ-34742 | Geocode: The Geocoder now offers support for addressing with INWANI numbers. This allows the Geocoder to find house number results using an INWANI-only query in the 10-digit format. However, other formats of INWANI numbers are not yet supported. For instance, if you submit a query as "15700350035" using the Geocode endpoint, it will now return a house number result based on the provided INWANI number. However, queries in formats such as "57-35-35" or "57 35 35" will still not yield any results at this time. |
| OSQ-35731 | Geocode: The Geocoder now provides improved handling of encoding issues, treating them as any other misspellings in search queries. This ensures a more robust and accurate geocoding experience for our users. The Geocoder now recognizes and treats encoding-related anomalies, such as the presence of "%EF%BF%BD" or similar encodings, as potential misspellings. Previously, these encodings may have caused unexpected search results or errors. |
| OSQ-35808 | Geocode: The Geocoder now has the capability to recognize and extract PO BOX numbers from queries specifically in the United States. When a query lacks detailed address information but includes a PO BOX number, the geocoder now prioritizes returning a postal (zip) code result. For instance, if the query is "1624 PO BOX, TRAVIS AFB, CA, 94535," the Geocoder will now return the postal code result as "94535, Travis Air Force Base, CA, United States." It's important to note that the inclusion of the PO BOX keywords and number does not impact the query score and is preserved within the parsing block as secondaryUnit. |
| OSQ-34680 | Autosuggest, Discover, Browse: Additional response element called excursionDistance for queries with a "route" parameter. When making a query that includes a route parameter, the service will now provide an extra response element called excursionDistance. This element represents the distance or deviation from the specified route for the given location or address. By including the excursionDistance element in the response, users can gain valuable information about how far the returned result is from the intended route. This can be particularly useful in scenarios where precise route adherence is critical, such as navigation or logistics applications. |
| OSQ-35432 | Autosuggest, Discover, Browse: Improvement for opening hours crossing midnight. Changes only apply to the structured block of opening hours. Previously, opening hours that crossed midnight were provided in two parts. These are combined to one time frame now. Example, previously: From 9 for the duration of 15 hours (14:59) and from 0 (midnight) for the duration of 2 hours. New: From 9 for the duration of 17 hours (16:59) |
Release 7.103
| Ticket Number | Description |
|---|---|
| OSP-6515, OSQ-35571 | Geocode: Improved support for Italy address matching. The Geocoder now supports permutations in the word order of street names. Example: In 'q=Mazzocchi Alessio Via 34, 80141 Napoli' now matches to 'Via Alessio Mazzocchi, 34, 80141 Napoli NA, Italia' with high confidence. In the query, the street type (Via) was moved to the end of the street name, and the first name Alessio was placed after the surname. |
| OSQ-35027 | All endpoints: Turkiye label format improvement: The label format for addresses in Turkiye has been adapted to reflect the standard local addressing format. The new format: <street> <houseNumber>, <postalCode>, <district>, <city>/<county>, <country>. For example: 'Kapalı Çarşı Caddesi 69, 16010, Nalbantoğlu, Osmangazi/Bursa, Türkei'. |
| OSQ-35000 | All endpoints: Turkiye administrative area leveling has been changed to align with the HERE map data. In the new representation, the state administrative level is not used. Level 2 - Il - is mapped to county, level 3 - Ilce - is mapped to city. Level 4 - built-up - is mapped to district. Metropolitan municipalities, such as İstanbul or Bursa, are coded in the HERE map data as KD zones (known-as zones) and mapped as alternative cities. KD zones representing historical neighborhoods are mapped to alternative districts. |
| OSQ-19432 | Autocomplete: Autocomplete now matches spelled-out numeric representations of numbers in street names and vice versa. Example: 'q=Oakland thirty second' now matches to 'United States, CA, Oakland, 32nd St'. Autocomplete supports this in English only for cardinal and ordinal numbers. |
| OSQ-34009, OSQ-34011 | Geocode, Discover, Autosuggest: USA address search with alternative city names. These endpoints now support address search in USA with alternative city names as accepted by USPS. In the Geocoder, the result city name shows the default primary preferred city name, and there is a penalty of 5% in the fieldScore.city. In Discover and Autosuggest results, the alternative name is added to the result title in parenthesis. Example: The result title is '1910 Jelinda Dr, Santa Barbara (Montecito), CA 93108-2664, United States' for the query '1910 Jelinda Dr, Montecito'. |
| OSQ-31983 | Geocode: Improved address matching for addresses in small localities where street names are inherited from the city name or where people refer to streets by using the city name. |
Release 7.102
| Ticket Number | Description |
|---|---|
| OSQ-34798 | Geocode: Improved support for Saudi Arabia search with short addresses for qualified and hybrid queries. |
| OSQ-35317 | Autocomplete: Improved support for high lighting of street names for synonym matches. Synonym matches include abbreviations or different representations of numbers in street names. |
| OSQ-34765 | All endpoints: Added INWANI codes for Qatar to results. INWANI codes are added to the result title, the address label and to address building fields. Example: In the following address label, '90-699-2' is the INWANI code: '90-699-2, Al Nahda Street 2, Al Wakra, Qatar'. |
| OSQ-35288 | Autocomplete: New featured city lookup via postal code released in ALPHA status. For postal codes that are valid in multiple cities, with the parameter postalCodeMode=cityLookup, Autocomplete returns multiple results of type postalCode, one per city. Per default, Autocomplete returns a single postal code result with either an empty or default city name for the postal code. |
| OSQ-35286 | Geocode: The show=parsing parameter is out of BETA and is now fully supported. |
| OSQ-35287 | Autocomplete: The types filter for Autocomplete is out of BETA and now fully supported. Autocomplete supports the following values for the types filter: area, city, and postalCode. |
| OSQ-35285 | Autocomplete: Autocomplete now supports two new spatial filters: in=circle limits the results by a circular area, in=bbox limits the results by a bounding box. Now results outside of the areas will be returned. |
Release 7.101
| Ticket Number | Description |
|---|
Release 7.100
| Ticket Number | Description |
|---|---|
| OSQ-34847 | All endpoints: Added political view for the disputed areas of Paracel Islands and Spratly Islands.
|
| OSQ-34764 | All endpoints: Added Dubai MAKANI numbers to results. MAKANI number is added to result title, address label, and address building name. In the following example, the first two numbers from the label present the MAKANI number: '30005 95279, 19B Street, Al Rigga Dubai, United Arab Emirates'. Note: Search by MAKANI number is not supported yet by any endpoint. |
| OSQ-34433 | Geocode, Discover, Autosuggest: Australia: Improved matching of ranged house numbers. Example: '65-73 Nantilla Road, Clayton, Victoria 3168, Australia'. |
| OSQ-30732, OSQ-33523, OSQ-33735 | Geocode, Reverse Geocode: Filter by result type: The optional parameter types allows application to limit results to a specific type or to a list of types. For the Geocode endpoint, the types filter has BETA status. Autocomplete supports the types filter already with status BETA. There is no change for Autocomplete.
types filter are now supported by these three endpoints: |
| OSQ-32941 | Geocode: Saudi Arabia: Support search for new Saudi Arabia short addresses. Example query: 'q=RCTB4359' returns a precise house number result: 'RCTB4359, 4359 Abi Al Karam Street, Al Dhobbat, 12627 Riyadh, Saudi Arabia'. |
Release 7.99
| Ticket Number | Description |
|---|---|
| OSP-5263, OSQ-30207 | Discover, Autosuggest: Improved search results for addresses on United States highways where street name can be 'highway', 'hwy', 'route', or 'RT'. Example: Query for '807 highway 35, Ocean, NJ' now finds '807 RT-35, Ocean, NJ 07712-4546, United States' |
| OSP-6197, OSQ-33868 | Discover: Improved search results for United States interstate highway queries. Search by 'Interstate-' instead of 'I-' (Interstate-93) is now supported. |
| OSQ-20054 | Geocode: Hungary: Geocoder now supports different search strings for numbered district names in Budapest, Hungary. For example, the district name 'Budapest 21' can be found with queries 'Budapest, XXI. ker.', 'Budapest, XXI' or 'Bp XXI'. In address queries, a roman number is sufficient to match the district: 'Deák Ferenc utca 21, XXI'. |
| OSQ-34578 | Geocode: Hungary: Geocoder improvements for street type synonyms in Hungary. The Geocoder now accepts 'ut' as a street type synonym for 'utca'. 'u' is already accepted. In ambiguous cases, where streets with type 'utca' and 'ut' exist, the Geocoder prefers the exact street type match. |
| OSQ-21651 | Discover, Autosuggest: Japan: Improved support for sub-block queries. |
Release 7.98
| Ticket Number | Description |
|---|---|
| OSQ-34397 | Autocomplete: Removed the 'beta' tag from the autocomplete endpoint. Autocomplete is now generally available with full support. Autocomplete speeds up address entries from end users by providing better results with fewer keystrokes. |
| OSQ-33721 | Geocode, Reverse Geocode, Autocomplete: For addresses in the USA with multiple valid ZIP+4 add-on codes according to USPS, Geocoding and Search results now prefer to return add-on codes of type high-rise over other types street, firm, PO box. |
| OSQ-34231 | Geocode: Extended support for secondary unit designators detection in Australia. |
| OSP-6250, OSQ-34085 | Autosuggest: Japan: Extended support for abbreviated chain name queries. 13 abbreviated chain names added. |
| OSQ-34047 | Geocode: USA: Improved accuracy for address queries with at parameter. In cases where the Geocoder finds multiple good results for address queries, it prefers the result closer to the at position. This was the wrong decision in cases where it was between a Point Address and a postal code point result or between a Point Address and an interpolated address result. |
| OSQ-34407 | Discover, Autosuggest: Requests for 'walmart' also return Places belonging to the chain Walmart Neighborhood Market. |
| OSQ-34376 | Autosuggest: Vietnam: Improved search for POIs in or near another POI. Examples for EV charging station searches in (ở) or at (tại) grand park: trạm sạc tại vinhomes grand park, trạm sạc ở vinhomes grand park |
Release 7.97
| Ticket Number | Description |
|---|---|
| OSQ-32600 | Autosuggest, Discover: Requests for 'Mcd' return Places of the chain McDonald's. |
| OSQ-33957 | Geocode: In Brazil, the Geocoder now understands 'Centro' as central district of a city where the map data district name is the same as the city name. Example: Request for 'Rua Monsenhor Messias, S/N, Centro, 35700041, Sete Lagoas, MG' returns 'Rua Monsenhor Messias, Sete Lagoas - MG, 35700-041, Brazil' as the only result without any penalty on query or fields scores. |
| OSQ-31971 | Geocode, Discover, Autosuggest, Autocomplete: Improved address search in Australia. GS7 now supports addressing with nearby districts in Australia. In Australia, people commonly use the names of 'suburbs' to address locations, which are mapped to 'districts' in GS7. In border cases, it may happen that people use the name of a neighboring district instead of the district to which the address belongs in the map data. Geocoder, Autocomplete, Discover, and Autosuggest can now find addresses with the name of a nearby district. In the result, Geocoder, Discover, and Autosuggest show the actual district name based on the map data. Discover and Autosuggest also show the matched name of the district in brackets. Autocomplete shows the matched district name in the result. The customer application can obtain the actual district name by calling the Lookup endpoint with the ID returned by the Autocomplete endpoint. |
Release 7.96
| Ticket Number | Description |
|---|---|
| OSQ-33230, OSP-6033 | Autocomplete: Improved results for locality name queries. Autocomplete now ranks results with fully matching locality names higher. |
| OSQ-33633 | Geocode: Improved address search with partial city name for multi-term city names. Example: For query '51 Rue de la République Bohain', the Geocoder now returns the address result in the city 'Bohain en-Vermandois' instead of multiple results in cities without any matching city name. |
| OSQ-33439 | Autosuggest: Improved category search in or near a Place. Example: 'Charging Stations in Vinhomes Ocean Park' (same for 'near') where 'Vinhomes Ocean Park' is of category Residential Area/Building. |
| OSQ-33198, OSP-5485 | Autosuggest: Improved clarity of titles for matches with alternative names. Reducing matching names in parenthesis when the extra information does not increase the user's understanding of the result. |
| OSQ-33955 | Discover, Autosuggest: Support German requests 'tanken' to return gas stations. |
Release 7.95
| Ticket Number | Description |
|---|---|
| OSQ-33559 | Geocode: Improved matching in France when articles are combined with names in queries. Example: 'lafayette' instead of 'la fayette'. |
Release 7.90
| Ticket Number | Description |
|---|---|
| OSQ-28540 | Autocomplete: Similar to other endpoints, the Autocomplete endpoint now supports search by postal code only in Singapore and Ireland. The result for a postal code search in these countries is the complete address. |
| OSQ-23266 | Autocomplete: With return type filter types=postalCode, Autocomplete now returns results of type postalCodePoint (high precision postal codes) in addition to results of type postalCode (area type postal codes). Note: In Singapore and Ireland, postal codes are very precise and assigned to single addresses. For all endpoints, postal code searches in these countries return a complete address of result type houseNumber. Therefore, Autocomplete returns the address of result type houseNumber for postal code searches even if types=postalCode is provided. |
Release 7.89
| Ticket Number | Description |
|---|---|
| OSQ-31982 | Geocode: The Geocoder now detects and parses secondary unit designators in Austria. |
| OSQ-31383 | Geocode: Brazil: The Geocoder now supports spelled out house numbers. The Geocoder parses spelled out house numbers and matches them to the numeric form. The Geocoder also supports alternative forms of spelled out house numbers. Example: The queries "hélio pellegrino cento e quarenta e oito" and "hélio pellegrino um quatro oito" result in the same address "Avenida Hélio Pellegrino, 148, Moema, Sao Paulo - SP, 04513-100, Brazil". |
| OSQ-32052 | Autosuggest: Japan: Improved Autosuggest for abbreviated chain names. Examples: スタバ (Starbucks, full name: スターバックス), ケンタ (KFC, full name ケンタッキーフライドチキン). |
Release 7.88
| Ticket Number | Description |
|---|---|
| OSQ-31786 | All endpoints: Added political view for the disputed area of Cyprus.
|
| OSQ-20154 | Geocode: In the USA, city names in the map data may contain name supplements ", town of" or ", village of". For example, "Alabama, Town of". GS7 now removes these name supplements from city names and de-duplicates results. For example, the query "Superior, WI" provides a single result, "Superior, WI, United States", instead of three results "Superior, WI, United States", "Superior, Village of, WI, United States" and "Superior, Town of, WI, United States". |
| OSQ-31693, OSQ-31832 | Geocode, Autosuggest, Discover: Vietnam: Improved matching logic for alley/house number address format. A Vietnam address can contain an alley number in addition to the street name and house number. The alley number can be encoded either as part of the street name, in combination with the house number, or both. When encoded together with the house number, the alley number prefixes the house number, separated by a slash (/). GS7 now supports matching queries with just the house number to alley/house number combinations in the map content. Example: q="10 Ngõ 509 Phố Vũ Tông Phan, Phường Khương Đình". Previous result was a house number match "509" on the wrong street: "509 Phố Vũ Tông Phan, Phường Khương Đình". New result: "509/10 Ngõ 509 Phố Vũ Tông Phan, Phường Khương Đình". |
| OSQ-30642 | Geocode: USA: The Geocode endpoint supports spelled out house numbers in queries. For example, the address "10 Forbes Rd, Braintree, MA 02184-2602, United States" can also be found with the query "Ten Forbes Road, Braintree, MA" where the house number is spelled out as "ten". |
| OSQ-26573 | Geocode: Added search for address via building name. Building names are now indexed and may be used to find an address. When a building name is associated with an address, GS7 can now match the building name and respond with the precise address and location. Example: Search for "Fernville County Cork, Ireland" results in a precise Point Address "Fernville, 66 Sunday's Well Road, Cork, County Cork, T23 V8W6, Ireland". |
| OSQ-29638 | Discover: Japan: Improved train station search. Important train stations are now more likely to be ranked at the top. |
| OSQ-31817 | Autosuggest, Discover: Japan: Improved search for Costco chain in Japanese (コストコ). |
Release 7.85
| Ticket Number | Description |
|---|---|
| OSQ-30819 | Geocode: Denmark: Improved handling of abbreviations in street names. |
| OSQ-30032 | Geocode: Brasil: Support of Brasilia specific addressing schema. The city Brasilia organizes addresses in sectors, quadrants (quadras), and blocks (bloco), all referred to by shortened acronyms. |
| OSQ-29641 | All endpoints: Promoted results types intersection and postalCodePoint from BETA to stable. |
Release 7.84
| Ticket Number | Description |
|---|---|
| OSQ-30633 | Geocode: USA: Improved handling of directionals in street names in abbreviated and spelled out variants, positioned pre and post street base names. |
Release 7.83
| Ticket Number | Description |
|---|---|
| OSQ-23272 | Geocode: The Geocoder now supports the addressing schema "sokak/caddesi" in Turkey. Example: "İstiklal Caddesi, Yeşilçam Sokak, No:17, Beyoğlu, İstanbul". The optional "Caddesi" part of the query helps to disambiguate in cases where a city or locality has multiple "Sokak" streets with the same name. A "Sokak" is typically a small street on which houses can be located and part of the official addressing. The "Caddesi" is a larger street nearby that people add to find the "Sokak" location better. The Geocoder does not show the "Caddesi" name as part of the result address. But the Geocoder includes the "Caddesi" information in the parsing block (parameter show=parsing), and it considers the "Caddesi" part of the query in the overall query score. |
| OSQ-29181 | Geocode: Switzerland: Geocoder now parses and interprets prefixes of administrative areas in freeform queries. For example, the German query q="Kanton Zürich" or English query q="Canton of Zurich", the Geocoder recognizes "Kanton/Canton" as a state qualifier and tries to match "Zurich" to a state. The Geocoder matches Zurich to the city in the queries q="Zurich" or q="City Zurich". This feature is currently implemented for Switzerland addressing only. |
| OSQ-30346 | Geocode: United States: Allow search for United States highways as Highway or Hwy in addition to primary name Route and RT. Example: "807 Highway 35, Ocean, NJ" for "807 RT-35, Ocean, NJ". |
| OSQ-28270 | Autocomplete: Improved support for abbreviated names. Example: Matching of "Mount Brydges" to "Mt Brydges". |
| OSQ-30262 | Reverse Geocode: Reverse Geocoder crops results at a distance of 100 km from the reference point. The API accepts a larger radius. But a large radius only leads to unnecessary long-running queries without changing the results. The purpose of the Reverse Geocoder is to find relevant locations close to the user or asset. |
Release 7.82
| Ticket Number | Description |
|---|---|
| OSQ-27387 | Reverse Geocode: Improved accuracy of Reverse Geocoder results. The Reverse Geocoder is now more likely to respond with interpolated address results on a nearby street and not with Point Address results on streets further away. |
| OSQ-29680 | Geocode: The Geocoder now detects and parses secondary unit designators in Brazil. |
| OSQ-30034 | Geocode: The Geocoder now recognizes and parses "CEP" - the abbreviation for Brazilian postal code system - in front of postal codes. The existence of "CEP" in a query does not impact the query score anymore. |
| OSP-5144 | Autosuggest, Discover: Improved support for "ChargePoint". The query "ChargePoint" now returns EV charging stations belonging to the ChargePoint network of EV charging stations. Before, the result included EV charging stations of any network. |
| OSP-5164 | Autosuggest: Improved support for parking queries in Latvia. |
| OSQ-29730 | Autosuggest: Improved support for search in Serbian transliterated language. For best results, use lang=sr-Latn. |
| OSQ-29506 | Autosuggest, Discover: Improved support for category queries "Elementary School" and "Secondary School". Added translations for category name "Elementary School" and "Secondary School" for languages English, German, French, Spanish, Italian, Portuguese, Russian, Japanese, Vietnamese. |
| OSQ-29331 | Autosuggest, Discover: Vietnam: Improved support for EV charging stations and automotive dealerships. |
| OSQ-29506 | Autosuggest, Discover: Elementary and secondary schools can now be searched by category. |
| OSQ-28855 | Autosuggest, Discover, Browse: Improved cuisine type search for Armenian, Cambodian, Burmese, North African, South African, Seychellois, Sri Lankan, Tibetan cuisine places. |
| OSQ-30336 | Geocode: Mexico: The Geocoder now recognizes and parses "Colonia"/"Col" in front of district names in Mexico. The result is the same independent of whether or not "Colonia"/"Col" is part of the official district name in the HERE map data. The existence of "Colonia"/'"Col" in a query does not impact the query score anymore. |
| OSQ-30035 | All endpoints: Added political views for disputed areas Jammu and Kashmir, Gilgit-Baltistan and Junagadh Area.
|
Release 7.81
| Ticket Number | Description |
|---|---|
| OSQ-29549 | Geocode: In addition to Spanish address search, now also for Portuguese and Italian address search, the Geocoder endpoint recognizes and parses "s/n" (sin número, en: without number) as part of the address. The existence of "s/n" in a query does not impact the query score anymore. With the show=parsing parameter turned on, "s/n" will be included in the parsing block as houseNumber. |
| OSQ-28123 | Geocode: Added support for hyphenated house number format in Taiwan: In Taiwan, it is common to have house numbers consisting of two numbers, separated by a hyphen or the Chinese symbol 之. Example: "苗栗縣苗栗市中山路602之1號". The Geocode endpoint now recognizes this house number format and tries to match it to a corresponding Point Address in the HERE map content. If the Geocoder cannot match the complete input, the Geocoder attempts to fall back to a Point Address that consists only of the first part of the input (the part before the hyphen or 之 symbol. |
| OSQ-26550 | Geocode: Locality prefix terms added to parsing block of the result. The Geocoder endpoint recognizes prefixes to locality and administrative area names in some countries. Now, these prefixes are also added to the parsing block of the result when parameter show=parsing is turned on. Example for Indonesia: "DESA MULYOHARJO, JEPARA, CENTRAL JAVA 59431". "DESA" is now parsed as part of the sub-district name. |
| OSQ-29366 | Autocomplete: Improved support for multi-word street and administrative area names. Autocomplete now matches street and administrative area names where the end-user omitted a word that is not first or last in the complete name. Examples: "Via Tempini Brescia" instead of "Via Giovanni Tempini Brescia" (missing first name "Giovanni"), "Rue Puits de Janson Pignan" instead of "Rue du Puits de Janson Pignan" (missing article "du"). |
| OSQ-27164 | Autosuggest: Improved recognition of chain name "allego" (EV Charging Station). |
| OSQ-28691 | Reverse Geocode: Improved accuracy of Reverse Geocoder results where the input coordinate is close to multiple streets (e.g., at street intersections). The Reverse Geocoder now adds more weight to the distance between the input coordinate and the access (navigation) coordinate of a Point Address. Previously, the distance between the input coordinate and the display coordinate of the Point Address was considered more important. |
| OSQ-29031 | Autosuggest, Discover, Browse, Lookup, Reverse Geocode: School place category changes: New school place categories 800-8250-0000 (School), 800-8250-0287 (Primary School), 800-8250-0288 (Secondary School). Category 800-8200-0174 (School) has been removed. |
Release 7.80
| Ticket Number | Description |
|---|---|
| OSQ-26904 | Geocode: Support for United States highway name synonyms. The Geocoder endpoint now supports US highway name synonyms. For example, "US highway 101 Mountain View CA" or "US HWY 101, Mountain View, CA" are synonyms for "US-101, Mountain View, CA". The Geocoder now returns the same result ( "US-101, Mountain View, CA 94043, United States") for any three name variants in the input query. |
| OSP-4685 | Geocode: For Spanish address search, the Geocoder endpoint now recognizes and parses "s/n" (sin número, en: without number) as part of the address. The existence of "s/n" in a query does not impact the query score anymore. With the show=parsing parameter turned on, "s/n" will be included in the parsing block as houseNumber. |
| OSQ-29210 | Geocode: Japan: Improved fallback behavior fallback error where the Geocode cannot match the house and subblock information in the input query. Example query "神奈川県茅ヶ崎市今宿965-1", previous result showing wrong address: "〒253-0072 神奈川県茅ヶ崎市今宿小中島965-1", new result is a fallback to the district: "神奈川県茅ヶ崎市今宿". |
| OSQ-29478 | Autosuggest: Improved car workshop query support. |
Release 7.79
| Ticket Number | Description |
|---|---|
| OSP-4675 | Geocode: Change in postal code search response: In cases where a postal code area overlaps with multiple cities - partly or entirely - the Geocoder now supports queries for postal codes in combination with any of these city names. The result is a postal code with the matched city name and position within the overlapping postal code and city area. |
Release 7.78
| Ticket Number | Description |
|---|---|
| OSP-3366 | Lookup, Browse, Autosuggest, Discover: The National Stop Register (NSR) ID is now added to public transport stops in Norway. Where available, the ID is added to the references field with a supplier.id set to "nsr". |
| OSQ-27320 | Autosuggest: Improved category term matching for European countries and languages. |
| OSQ-28147 | Geocode: Geocoder improvements for English address queries in Taiwan. Geocoder improvements for English queries in Taiwan. The Geocoder is less strict to token order for street names. |
Release 7.77
| Ticket Number | Description |
|---|---|
| OSQ-24823 | Geocode: Geocoder now detects and parses secondary unit designators in Russia. |
| OSQ-28041 | Geocode: In Taiwan, it is common to prefix house numbers in English addresses with "No." The Geocoder now tolerates the prefix without penalties in queryScore or houseNumber fieldScore. |
| OSQ-28443 | All endpoints: Added political views for disputed areas Southern Patagonian Ice Field, Tierra Del Fuego, Falkland Islands, South Georgia and South Sandwich Islands. Show these areas in the Argentina view with politicalView=ARG. |
| OSQ-27850 | Browse, Autosuggest, Discover: Improvements in category search precision. |
Release 7.76
| Ticket Number | Description |
|---|---|
| OSQ-28058 | All endpoints: Added political views for disputed areas Bir Tawil, Halaib Triangle, Golan Heights.
|
| OSQ-23480 | Autocomplete: Added language code to results. Each Autocomplete result includes a language field with the preferred user language. The value is either the same as specified in the lang query parameter or if the client application did not provide the parameter, the language that Autocomplete identified from the input query. |
| OSQ-26199 | Geocode: Geocoder now supports secondary unit designator detection in France for commonly used designator "étage". |
| OSQ-28045 | Geocode: Geocoder now detects and parses secondary unit designators in Taiwan for Chinese and Latin (English) scripts. |
| OSQ-26887 | All endpoints: Point Addresses in the HERE map may include a building name. GS7 now exposes available building names for Point Address results within the address block and as part of result title and address label. Building names may also be included in the address block of Place results. |
| OSQ-28153 | Geocode: Improvements for the Galician language region in Spain. The Geocoder now tolerates common omissions in queries such as stop words, person first names, or person titles also for the Galician language. This feature was already supported for the Spanish and Catalan languages. |
| OSQ-11051 | Geocode: Improvements for the Galician language region in Spain. The Geocoder can now recognize and match street types in the Spanish language. |
Release 7.75
| Ticket Number | Description |
|---|---|
| OSQ-11049 | Geocode: Improvements for Catalan language region in Spain. In addition to Catalan, the Geocoder can now recognize and match street types in Spanish language. The second improvement is tolerating common ommissions in queries such as stop words, person first names, or person titles. This feature was already supported for the Spanish language and is now supported for Catalan as well. |
| OSQ-25758 | Geocode: Geocoder matching for postal codes in noisy queries is improved. In cases where the Geocoder can only recognize a postal code in the query text, it will now return a postal code result. The overall queryScore might drop below 0.5 because all other query tokens were not recognized. Previously, the Geocoder returned with an empty response. |
| OSQ-26409 | Geocode, Discover, Autosuggest: Japan: Improved matching of kana consonants in small and large forms: Katakan ka ヵ and カ, Katakana ke ヶ and ケ, Katakana 促音 "tsu" ッ and ツ, Hiragana 促音 "tsu" っ and つ. |
| OSQ-27727 | Geocode: Japan: Improved address search quality for queries with partially wrong (fuzzy) house number or subblock information. |
| OSQ-26080 | Autosuggest, Discover, Browse: Added description of response attribute excursionDistance to the Developer's Guide. excursionDistance is returned for search along the route requests. It is the distance from the route to the result. |
| OSQ-27375 | Autosuggest, Discover: Improved brewery category query support. |
| OSQ-26965 | Autosuggest, Discover: Enhanced chain search support for chains Ford, MAN, SEAT, Skoda, and Volkswagen. |
| OSQ-26720 | Autosuggest, Discover: Improved category search support for emergency room places ("ER", "A&E"). |
| OSQ-26697 | Autosuggest, Discover: Improved EV charging station category search in Serbian ("Stanica za punjenje"). |
| OSQ-25999 | Autosuggest, Discover: Improved Portuguese support for EV charging stations. |
| OSQ-22403 | Autosuggest, Discover: Improved Castles category search support. |
Release 7.74
| Ticket Number | Description |
|---|---|
| OSQ-27443 | All endpoints: Added political views for areas Ilemi Triangle, Lake Malawi, Courantyne Headwaters, Lawa Headwaters, Rincon de Artigas.
|
| OSQ-26551 | Geocode: Improved support for street name abbreviations in Indonesia. The Geocoder now recognizes all street name abbreviations that HERE defines in map content. |
Release 7.73
| Ticket Number | Description |
|---|---|
| OSQ-27193 | Geocode: Japan: Geocode alphabetic house number query. For example, match the input query 町田市山崎町1356-F to the address 〒195-0074 東京都町田市山崎町1356-F, where 'F' is the house number. |
| OSQ-25368 | Geocode: Japan: Address query fallback to wrong sub-block when fallback to sub-district is preferred. Example: q=滋賀県長浜市法楽寺町276-122, previous result: sub-block 滋賀県長浜市寺師町122, new result: sub-district 滋賀県長浜市法楽寺町 |
| OSQ-26531 | Geocode: Japan: Alphanumeric token at the end of address query should not impact the result. Example: q=神奈川県川崎市幸区下平間 153-1 When the Geocoder cannot match the last tokens -1 the fallback to be to sub-block. New result: sub-block 〒212-0053 神奈川県川崎市幸区下平間153 |
| OSQ-26735 | Autosuggest, Browse, Discover, Lookup: Vinfast supplier references added to references response elements. |
| OSQ-27054, OSQ-27228 | All endpoints: Improved quality of hotel, restaurant, grocery, pharmacy, theater, and police station places in Germany. |
| OSQ-24303 | Autosuggest, Browse, Discover: Additional excursionDistance response element for queries with a route parameter (BETA) |
| OSQ-26711, OSQ-26819, OSQ-27124 | Autosuggest, Discover: Improved category search in German, English, Spanish, Norwegian, Czech for categories such as airport terminal, boat sports, medical services, car dealerships and car repair places. |
Release 7.72
| Ticket Number | Description |
|---|---|
| OSQ-23411 | All endpoints: New response code 429 Too Many Requests: The user has sent too many requests in a given amount of time, or the user's request quota has been exceeded. |
| OSQ-25152 | Autosuggest, Discover: Added recognition of "Lojas de Departamento" as the Portuguese term for department store. Search for "Lojas de Departamento" can now result in a follow-up query suggestion for "ontologyId": "here:cm:ontology:department_store". |
| OSQ-25770 | Geocode: For address queries in Vietnam, the geocoder can recognize and match house number formats with a slash. Examples: "30/13 Hà thanh vạn thắng nha trang khánh hoà" results in house number match "30/13" on street "Hẻm 30 Hà Thanh". The previous wrong match was to house number "13" on the street "Đường Hà Thanh". |
| OSQ-26117 | Autosuggest: Better support for car brands one box search when combined with a service or sales category. |
| OSQ-24516 | Autosuggest, Discover: Added German "Rasthof" and "Rastanlage" queries support. |
| OSQ-21437 | Autosuggest, Discover: Added "Leela Palace" chain search support. |
Release 7.71
| Ticket Number | Description |
|---|---|
| OSQ-21343 | Autosuggest, Discover, Lookup, Browse: Chain name added to Place results in addition to chain IDs. Example: chains": [{ "id": "1173", "name": "Sparkasse" }]. Note: This feature is still in beta. We noticed that in rare cases the chain name is not correct. |
| OSQ-24267 | Autosuggest, Discover, Lookup, Browse: Support for 10k additional chains. |
| OSQ-25511 | Autosuggest, Discover: Japan: Improved chain recognition with additional chain names and abbreviations. |
| OSQ-26206 | Autosuggest, Discover: Japan: Katakana and Hiragana transliterations are no longer added to the search result title in parenthesis as alternative name. Japan users mostly find these additional names in the title unexpected or also disturbing. Example: Previous title: Starbucks Coffee 新田町ビル店 (スターバックスコーヒーシンデンチョウビルテン), new tile: 'Starbucks Coffee 新田町ビル店' |
| OSQ-26079 | Geocode: Improved support of street type abbreviation in English-speaking countries. |
Release 7.70
| Ticket Number | Description |
|---|---|
| OSQ-11412 | Geocode: Great Britain: Support directionals in street names. For example, the expected result for 'BS3 2EZ, Bristol, N ST BEDMINSTER 139' is '139 North Street, Bristol, BS3 1EZ, United Kingdom'. |
| OSQ-24236 | Geocode: Indonesia: In Indonesia, it is common to prefix a district or city name with an abbreviation or spelled out name that indicates the type of the entity. For example, in 'JL. MALIGI RAYA LOT P-4A, kab KARAWANG, WEST JAVA 41361 kel sukaluyu', 'kab' stands for 'kabupaten', which means city. 'kel' stands for 'kelurahan' and means a sub-district. The Geocoder supports the following prefixes: 'DS', 'Kel', 'Ds/Kel' and 'Desa', 'Kelurahan' before sub-district. 'Kec' and 'Kecamatan' before district. 'Kab' and 'Kabupaten' before city. 'Kota' before city. |
| OSQ-25368 | Geocode: Japan: Improved fallback behavior where the Geocoder cannot match the query house number. |
| OSQ-26198, OSQ-26274 | Geocode: Extended support for secondary unit designator detection in Great Britain and Indonesia. |
| OSQ-26220 | Geocode: Indonesia: Improved address matching by ranking candidates with matching street type higher than those where only the street base name matches. Important street types in Indonesia are 'Jalan' (abbr. 'Jl.'), 'Gang' (abbr. 'Gl.'), 'Lorong', 'Boulevard'. |
Release 7.69
| Ticket Number | Description |
|---|---|
| OSQ-22967 | Geocode: Extended support for secondary unit designator detection. Example: In query "200 Main St Ste 101A, 29926" the Geocoder now detects "Ste 101A" as suite information. In previous releases some unit numbers were falsely interpreted as house number or the existence of secondary unit information in the query let to empty responses. |
| OSQ-24372 | Geocode: Russia: Geocoder supports locality prefixes in Russia. Examples: "город"/"gorod", which mean "city". |
| OSQ-25548 | Geocode: Ireland and Great Britain: Increased coverage for Great Britain and Ireland (EIRCODEs) postal code search. Postal codes that are not associated to an address (house number) or building (building name) in the HERE map are now returned with resultType: postalCodePoint. |
| OSQ-25732 | Discover, Browse, Lookup: Endpoints return EV station attributes when the query "show" is set to the value "ev". This capability is restricted to customer applications for which the HERE EV-API has been licensed. |
| OSQ-25793 | Geocode: Japan: Geocoder returns precise house number results from address query with extended house number or room number. Before, the Geocoder returned subblock results. |
| OSQ-25794 | Geocode: Japan: Geocoder now tolerates white space symbols in queries. White spaces do not lead to reduced quality scores or empty responses anymore. |
| OSQ-25878 | Geocode: United Kingdom: Improved address matching. For address queries in United Kingdom, GS7 geocode recognizes and matches all the house number formats which are available in the HERE map. For example, matching of hyphenated house numbers as in 'PH7 4AU, Crieff, W HIGH ST 1 - 3'. |
| OSQ-25900 | Autosuggest: Improved house number result quality for very short numerical queries. |
| OSQ-25901 | Geocode, Discover, Autosuggest: Japan: Consistency between Hiragana and Katakana queries. A mapping exists between both Japanese scripts so that results should be the same independent of the chosen script. |
| OSQ-23344 | Reverse Geocode: Reverse Geocoder prefers street level results over interpolated address results in some cases. Example: /revgeocode?at=44.5560598,-79.1382582. Previous results, 2 street matches: "CR-47, Ramara, ON L0K, Canada", "Sideroad 5, Ramara, ON L0K, Canada", new results, 2 interpolated housenumber matches: "4024 CR-47, Ramara, ON L0K 1B0, Canada", "2799 Sideroad 5, Ramara, ON L0K, Canada" |
Release 7.68
| Ticket Number | Description |
|---|---|
| OSQ-24271 | Geocode: Vietnam: Improved address matching. Geocoder now tolerates omitted street types (queries with street base name only, no street type. |
| OSQ-24824 | Reverse Geocode: Singapore: Reverse Geocode now returns the high precision postal code with Singapore address results. Previously, the Reverse Geocoder responded with the 2-digit postal code instead of the precise 6-digit postal code. |
| OSQ-25649 | All endpoints: Added political view Morocco on Western Sahara (politicalView=MAR). Default = Country Western Sahara (ESH); MAR = As part of Morocco (MAR). |
Release 7.67
| Ticket Number | Description |
|---|---|
| OSQ-25314 | All endpoints: Added political view Serbia on Kosovo (politicalView=SRB). Default = Country Kosovo; SRB = As part of Serbia. |
| OSQ-24575, OSQ-24576 | Browse: Browse now supports a foodTypes and a chains filter accepting cuisine ids and chain ids, respectively. |
| OSQ-24837 | Autosuggest: Respond with address suggestions for queries containing only numbers. |
| OSQ-25293 | Geocode: Indonesia: For address queries in Indonesia, the Geocoder recognizes and tolerates house number prefix 'No.'. Before, the term 'No' was unmatched and could diminish Geocoder result quality. Example query with 'No' before house number 25: Jl. Jabaru II No 25, RT.03/RW.02, Pasirkuda, Kec. Bogor Bar., Kota Bogor, Jawa Barat 16119, Indonesia |
| OSQ-25292 | Geocode: Indonesia: For address queries in Indonesia, the Geocoder recognizes and matches all the house number formats as available in the HERE map. Example: C9/54, Jalan Kebon Jati, Bandung Kota 40181, Indonesia |
| OSQ-24767 | Geocode: Indonesia: Addresses can contain Rukun Tetangga (RT) and Rukun Warga (RW) numbers as the lowest administrative division of Indonesia. This information is currently not available in the HERE map data. The Geocoder now recognizes this pattern in queries and ignores the tokens instead of mistakingly interpreting the numbers as house numbers. |
| OSQ-24640 | Geocode, Discover, Autosuggest: Japan: Improved matching of sub-district names. |
| OSQ-24640 | Geocode, Discover, Autosuggest: Japan: Improved postal code matching for city postal codes (formats ###-##00). Examples: 759-2200, 680-0700. Before: empty responses. |
| OSQ-23835 | Geocode, Discover, Autosuggest: Japan: Improved handling of Hiragana/Katakana for Japan address search. |
| OSQ-25005 | Geocode, Discover, Autosuggest: Japan: Katakana spell correction based on phonetic similarity (consonant + vowel). |
| OSQ-24238 | Geocode, Discover, Autosuggest: Japan: Improved support for chain name and abbreviated chain name. |
Release 7.66
| Ticket Number | Description |
|---|---|
| OSQ-24887 | Discover, Browse, Lookup, Autosuggest: When a Place is included in the Venues dataset, the supplier ID is provided for supplier here:pds:placesupplier:venues. |
| OSQ-25021 | All endpoints: Japan: Treat small and large representations of five hiragana vowels and three additional kana as equivalent. Large (small): あ(ぁ), い(ぃ), う(ぅ), え(ぇ), お(ぉ), や(ゃ), ゆ(ゅ), よ(ょ) |
| OSQ-25020 | All endpoints: Japan: Treat small and large representations of five katakana vowels and three additional kana as equivalent. Large (small): ア(ァ), イ(ィ), ウ(ゥ), エ(ェ), オ(ォ), ヤ(ャ), ユ(ュ), ヨ(ョ) |
| OSQ-24809 | Autosuggest, Discover: Japan: Enhanced search quality for POI names with one or two tokens. |
| OSQ-24220 | Geocode: For Russia, the Geocoder supports abbreviated forms of specifiers in street names: "Бол" and "Б" for "Большой"/"Большая"/"Большое"/"Большие" ("Big"); "Мал" and "М" for "Малый"/"Малая"/"Малое"/"Малые" ("Small"); "Ср", "С" for "Средний"/"Средняя"/"Среднее"/"Средние" ("middle"). |
Release 7.65
| Ticket Number | Description |
|---|---|
| OSQ-23834 | All endpoints: Japan: Improved quality of administrative name search in Katakana and Hiragana. |
| OSQ-24643 | Autosuggest, Discover: Japan: Enhanced capability of returning POI names in Hiragana and Katakana. |
| OSQ-24169 | Discover, Browse, Lookup: Return EV stations static attributes. |
| OSQ-19967 | Reverse Geocode: Reverse Geocode returns high precision postal code points in countries where these are available. Example for the United Kingdom: at=51.2424992,-1.7955735, previous first result (place): "Red Devils Freefall Team, Pigott Close, Salisbury, SP4 9, United Kingdom", distance 54 m, new first result: "SP4 9QG, Salisbury, United Kingdom", distance 17 m |
| OSQ-24892 | All endpoints: Added support for political views. For this release, the only supported political view is the Russian view on Crimea. HERE Geocoding and Search represents it by default as part of Ukraine. For customer applications that target the Russian market, HERE Geocoding and Search allows setting Russian political with Crimea region shown as part of Russia (use parameter politicalView=RUS). |
Release 7.64
| Ticket Number | Description |
|---|---|
| OSQ-24155 | All endpoints: Increased coverage of GBR postal codes |
| OSQ-23491 | Geocode: Improved matching of Russia compound house number formats |
| OSQ-21301 | Geocode: Improved behavior for address queries that contain noise. The tolerance for the overall queryScore has been increased for cases with high enough individual fieldScores. Example: "SEEDRS LTD,CHURCHILL HOUSE,142-146 OLD STREET,london,EC1V 9BW" now returns "142 Old Street, London, EC1V 9BW, United Kingdom" |
| OSQ-23406 | Geocode: In Russia, the Geocoder now prefers Point Address fallbacks to alpha-numeric house numbers in situations where the query house number is numeric but does not exist in map content. Before, the Geocoder chose an interpolated location. This could lead to results up to a few hundred meters away from the destination. Example: q=121059, Россия, г Москва, г. Москва, наб Бережковская, 20, previous result (interpolated): "Бережковская набережная 20, Москва, Россия, 121059", new result (Point Address fallback to alpha-numeric house number): "Бережковская набережная 20А, Москва, Россия, 121059" |
| OSQ-23558 | Geocode: Tolerate common Russia prefix to the house number "dom"/"дом" (meaning "house"). The Geocoder now recognizes the prefix and tolerates it without any scoring penalty. |
New features added in previous releases:
| Ticket Number | Description |
|---|---|
| OSQ-18581 | Discover: Place search by telephone number including in Japan |
| OSQ-19595 | Geocode: For queries with at, Geocoder now ranks results in the proximity over those far away with a better score. This change in ranking includes house number fallbacks in proximity over exact house number matches far away. |
| OSQ-23507 | Geocode: For Russia addressing with numbers in street name, the position of the number before or after the base name is flexible and equally matched. |
| OSQ-23853 | Geocode: For Russia addressing, street names may contain words "Большой"/"Большая"/"Большое"/"Большие" ("Big"), "Малый"/"Малая"/"Малое"/"Малые" ("Small"), "Средний"/"Средняя"/"Среднее"/"Средние" ("middle"). Geocoder now supports the queries with flexible positioning of these specifiers in the street base name. |
| OSQ-22569 | Autocomplete: Autocomplete now also supports high precision postal code queries and returns results with result type postalCodePoint |
| OSQ-23942 | Geocode Geocoder supports common street type abbreviations in Indonesia: "JL"/"JLN" for " Jalan", "G" for "Gang" and "Lr"/"Lrg" for "Lorong" |
| OSQ-22573 | Geocode: Geocoder additionally supports Italian abbreviation "p.le" for "Piazzale" |
| OSQ-21419 | Discover, Browse, Lookup: Categories field added for contact information in place result items |
| OSQ-21421 | Discover, Browse, Lookup: Categories field added for opening hours in place result items |
| OSQ-18697 | Browse: Allow place categories negative filter. For example, to retrieve all restaurants except fast-food restaurants, an application would add to Browse queries categories=100-1000,!100-1000-0009. |
| OSQ-20855 | Autosuggest, Discover, Browse, Lookup: Phonetic translations added to result items |
| OSQ-18686 | Autosuggest, Discover, Browse, Lookup: Chain ids added to place result items |
| OSQ-18649 | Autosuggest, Discover, Browse, Lookup: Category translations added to place result items |
| OSQ-18090 | Autosuggest, Discover, Browse, Lookup: HERE core/yelp/Tripadvisor/Parkopedia ids added to place result items |
| OSQ-22875 | All endpoints: Added United Kingdom as entity on country level and moved England, Scotland, Wales, Ireland from country to state level. This change allows searching for addresses and places in UK and also to search for UK as country. |
Autosuggest, Discover, Geocode: Support of intersection search. Intersection queries can contain two street names, for example, "5th Ave @ E 82nd St New York". Results are of new resultType "intersection". Results provide the street names in the "streets" list. | |
Autosuggest, Discover: Search for 7-digit UK postal codes. For example, "EC2Y 5HN". These UK postal codes are high precision postal code points assigned to a single or small number of addresses. Results are of new resultType "postalCodePoint". | |
| Autosuggest, Discover: Support geo-coordinate queries in sexagesimal degrees (degrees, minutes, seconds, for example, "48°51'29.7"N 2°17'40.2"E") or decimal degrees ("48.8582,2.2945"). | |
| Autocomplete: Autocomplete is available as BETA. Autocomplete allows end-users to find better results with fewer keystrokes. |
Updated yesterday