Resolved Issues
The following table contains resolved issues in the current release of the HERE Geocoding and Search API v7.
Release 7.152
| Issue ID | Description |
|---|---|
| GSQ-10191 | Autocomplete: The /autocomplete endpoint now tolerates two-letter postal code prefixes in countries where Geocoding and Search API includes them in result titles, such as Denmark, Finland, or Sweden. Previously, unmatched postal code prefixes could prevent autocomplete from returning follow‑up suggestions based on a previously returned result title - for example, for “Karlshamnsvägen, SE‑294 93 Pukavik, Sweden”. |
| GSQ-10150 | Geocode: Alignment of query parts to result fields has been improved to prefer exact and complete matches, even when they apply to less prominent address components. This fixes issues such as in Denmark, where “Sj” in the query “GRANVÆNGET 2, 4500, Nyköping Själland” was previously matched to the city “Nykøbing Sj” instead of the state “Sjælland”. Similar changes apply to Hong Kong, where the two lowest administrative levels may share the same name. For example, in the query “Flat H, 38/F, Tower 8, Cullinan West, 28 Sham Mong Road, Sham Shui Po, Kowloon, Hong Kong”, “Sham Shui Po” is now matched to the subdistrict instead of the district “Sham Shui Po District” with no penalties on the field and query scores. |
Release 7.151
| Issue ID | Description |
|---|---|
| GSQ-10154 | Geocode: The /geocode endpoint now tolerates ’ (U+2019 - right single quotation mark) used instead of ' (U+0027 - ASCII apostrophe). |
| GSQ-9895 | Geocode: Fixed an issue where district names were misaligned when a district name was contained within a city name. For example, the query “Boryspil” now correctly returns the district “Boryspil” within the city “Boryspilskyi raion.” |
| GSQ-9646 | Geocode: Improved matching of numbered routes composed of combined numeric and non‑numeric parts when no dividing space is present. |
Release 7.150
| Issue ID | Description |
|---|---|
| GSQ-9831 | All endpoints: Administative area codes (stateCode or countyCode) in Israel, Vietnam, and Thailand are correctly returned in the address section of response. This also improves the rendering of the related administrative names in the response. |
| GSQ-7489 | Geocode: Fixed inconsistencies in postal code scoring for cases of partial matches. |
| GSQ-10667, GSQ-10841 | Geocode: In Australia, when the requested address is missing from the map data, the /geocode endpoint now more consistently prefers falling back to a neighboring house number on the same street rather than falling back up the hierarchy to the suburb (district). |
Release 7.149
| Issue ID | Description |
|---|---|
| GSQ-10280 | Geocode: Further enhanced logic for resolving ambiguity in house numbers, prioritizing the number adjacent to the street name - even when one of the numbers includes leading zeros. This improvement applies to all countries. |
| GSQ-9057 | Geocode: In the USA, the /geocode endpoint now correctly recognizes the five digits format of secondary unit designators. |
| GSQ-10621 | Geocode: The /geocode endpoint now detects secondary unit designators and matches them to micro point addresses (MPAs) for hyphenated house numbers in Austria. This capability was already supported for other house number formats. |
Release 7.148
| Issue ID | Description |
|---|---|
| GSQ-9996 | Geocode: The pattern “Flat” followed by a character, for example "Flat A", was added to the default secondary unit designator set for all countries which use default patterns, including the UK. |
| GSQ-9832 | Geocode: Enhanced logic for resolving ambiguity in house numbers, prioritizing the number adjacent to the street name - even when one of the numbers includes leading zeros. This improvement addresses problem in Armenia where postal codes with leading zeros were previously misinterpreted as house numbers. |
| GSQ-9582 | Geocode: Enhanced parsing of secondary unit designators in Brazil for queries where spaces between secondary units and other tokens were omitted. |
| GSQ-10327 | Geocode: The /geocode endpoint already treats Brazilian postal codes (CEP) as high-precision, prioritizing the 5-digit base over the 3-digit extension. With this release, the /geocode endpoint improves handling of cases where the exact extension is missing in map data: for postal code queries, it now falls back to the default code with extension “000.” This applies to both input formats - with or without a hyphen separating the extension. For example, queries like 38690024 or 38690-024 will return the postal code 38690-000. |
| GSQ-10146 | Reverse Geocode, Multi-Reverse Geocode: Fixed some edge cases where nearby streets are not returned. |
| GSQ-10219 | Autocomplete: Increased success rate for the searches of prominent cities when the query is ambiguous. |
Release 7.147
| Issue ID | Description |
|---|---|
| GSQ-9466 | Geocode, Autocomplete, Discover, Autosuggest: Fixed some edge cases where GS7 was returning zip-codes in the USA with empty city and county fields. |
| GSQ-10091 | Reverse Geocode, Multi-Reverse Geocode: Improved the navigation attributes coverage for streets without names in some countries, and continuous global impovement is planned for a future release. |
| GSQ-9619 | Geocode: Previously, the /geocode endpoint did not handle the flexible word order in Romanian street names, which could result in incorrect matches. This capability has now been extended, allowing the /geocode endpoint to tolerate variations in the word order for street names in Romania. |
| GSQ-8308 | Geocode: Previously, business postal code searches in Japan could fail when a search center was defined. Searches now work as expected regardless of the search center configuration. |
| GSQ-9805 | Geocode: In Greece, postal codes are often written with a space dividing two digit groups. The /geocode endpoint now correctly interprets this format as a valid postal code and no longer mistakenly matches the second group to a house number, even when the postal code does not exactly match map data. |
| GSQ-10218 | Autocomplete: Increased success rate for city searches where the city name is commonly used in local POIs and street entities. |
Release 7.146
| Issue ID | Description |
|---|---|
| GSQ-9391 | Geocode: Fixed an issue in Brazil where the geocode endpoint could misinterpret a number in a street name as a house number. |
| GSQ-9668 | Geocode: In the United Kingdom, the /geocode endpoint now recognizes detailed postal codes in queries even when the space between the street name and postal code is omitted. |
| GSQ-9748 | Geocode: The /geocode endpoint now supports alphanumeric house numbers in Slovenia with a space between numeric and alphabetic parts, and can match them to the Point Addresses which do not include a dividing space. |
Release 7.144
| Issue ID | Description |
|---|---|
| GSQ-9161 | Geocode, Discover, Autosuggest: fixed a problem with limited set of "short addresses" in Saudi Arabia not returned by GS7. |
| GSQ-9094 | Geocode: Fixed an issue in London where, if the postal code in a query didn’t match map data, HERE Geocoding and Search API v7 incorrectly parsed the first part as a postal district. This behavior has now been corrected. |
| GSQ-9014 | Geocode: Improved HERE Geocoding and Search API v7 logic for U.S. area postal codes (zip codes) to better associate them with overlapping cities in map data. This enhances geocoder results for queries combining postal code, city name, and unmatched address details. |
| GSQ-8631, GSQ-1229 | Geocode: In countries with detailed postal codes (for example, United Kingdom, Ireland), the /geocode endpoint now more reliably falls back to the postal code point when house number data is missing. This behavior existed before, but the success rate has been improved with this update. |
| GSQ-8452 | Autocomplete: The /autocomplete endpoint now prioritizes results with matching postal codes when identical street names appear across multiple postal codes within the same city. |
| GSQ-8526 | Browse*: The /browse endpoint now supports the combination of both a name filter and evStation filters. |
| GSQ-9342 | Autosuggest: href now contains valid in=circle values. |
Release 7.143
| Issue ID | Description |
|---|---|
| GSQ-8299 | All endpoints: Changed result title and address label for the city of Warsaw, Poland to include the city name instead of Warsaw district names. |
| GSQ-9059 | Geocode: The /geocode endpoint logic is improved to reflect high reliability of postal codes (also known as Eircodes) in Ireland. The /geocode endpoint now prioritizes results with an exact match on detailed postal codes - with resultType either houseNumber or postalCodePoint or place - over results with missing or approximate postal code matches. |
| GSQ-8864, GSQ-8800 | Geocode: The /geocode endpoint logic is improved to reflect higher reliability of postal codes in Great Britain in comparison with postal or administrative city names. Now it prefers results with exactly matching at least base part of the postal code to results with matching city names. |
| GSQ-8730 | Geocode: Resolved the problem with the /geocode endpoint misinterpreting numeric part of numbered districts in Turkey as house numbers. |
| GSQ-8523 | Geocode: The /geocode endpoint now recognizes zip+4 codes in queries in the USA even if the postal code in the query is missing hyphen between zip code and the "+4" extension part and there is no exactly matching zip+4 postal code in the map data. For example, for the query 'PO BOX 1472 LANCASTER PA 176081472" the /geocode endpoint now successfully returns a PO BOX zip code "17608". |
Release 7.142
| Issue ID | Description |
|---|---|
| GSQ-7991, GSQ-8630 | Geocode: First set of improvements of the /geocode endpoint logic to prioritize exact postal code point results over lower-precision matches, such as streets or areas, even when those have higher query scores. |
| GSQ-8312 | Geocode: In Sweden, the /geocode endpoint now tolerates the common substitutes of special Swedish letters, such as "Aa" or "A" for "Å", "Ae" or "A" for "Ä" and "Oe" or "O" for "Ö". |
Release 7.141
| Issue ID | Description |
|---|---|
| GSQ-8366 | Geocode: Street names tokenization improvements for Turkey: the /geocode endpoint now supports cases when in a query, a word in the street name is entered as a single word, while in the map data it is split into two tokens. For example, a street name "Çöreotu sokak" in the query is now matched to the street name "Çöre Otu Sokak" in the map data. |
| GSQ-8332 | Geocode: Solved the problem with the /geocode endpoint not recognizing street names format used in city Mannheim in Germany, like "C3". |
Release 7.140
| Issue ID | Description |
|---|---|
| GSQ-8080 | all endpoints: timeZone data are updated to the latest version which has fixed incorrect time zone info in Chile. |
| GSQ-7913, GSQ-7324 | Geocode: Fixed a few edge cases where the /geocode endpoint was not able to return small towns for queries which do not provide additional information, such as upper administrative areas or spatial reference. |
| GSQ-7774 | Geocode: Street names tokenization improvements for Turkey: the /geocode endpoint now supports cases when in the query, a word in the street name is split into two tokens, while in the map data it is coded as a single token. For example, a street name "Orhan Gazi sokak" in the query is now matched to the street name "Orhangazi Sokak" in the map data. |
| GSQ-7819 | Geocode: Improved up-hierarchy fallback logic for queries which contain details that do not exist in the map content. In case of ambiguity, a district result is now consistently preferred to an area postal code result as more precise. |
| GSQ-7681, GSQ-8182 | Geocode: For the cases where postal code covers multiple cities, for queries combining the postal code and a smaller city/town within this postal code, the /geocode endpoint now consistently returns the city result with the matching postal code. |
| GSQ-7680 | Geocode: For queries with at position, the candidates within a proximity of 100 km, with otherwise similar quality, are more strictly ranked by distance. |
Release 7.139
| Issue ID | Description |
|---|---|
| GSQ-4471, GSQ-1360 | Geocode, Discover, Autosuggest, Autocomplete: Improved the addressing feature in neighboring districts in Australia. In Australia, people commonly use the names of 'suburbs' to address locations, which are mapped to 'districts' in HERE Geocoding and Search API v7. 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. The district is now assigned as a "neighboring" one to all street-sections/addresses/places in adjacent districts within a configurable buffer of 1250m. |
| GSQ-7805 | Geocode, Discover, Autosuggest, Autocomplete: In Canada, the /geocode endpoint now correctly recognizes house numbers preceded with "#" with or without dividing space in the queries. |
| GSQ-7630 | Geocode: In Colombia, the /geocode endpoint now accepts "Distrito Capital de Bogotá" as a valid synonym for "Bogota, D.C." without any additional penalties on the field or query scores. |
| GSQ-1650, GSQ-7594 | Geocode, Autocomplete: Improved query parsing in the areas where in the map data, a district has the same name as a city. Now, the /geocode and /autocomplete endpoints consistently prefer the match on the city name for address queries. |
Release 7.138
| Issue ID | Description |
|---|---|
| GSQ-7179 | Geocode: Improved support of different representations of the most commonly used numerals in street names in Italy. For example, for query "Via Primo Maggio 10, Costermano sul Garda, Verona 37010, ITA", the /geocode endpoint now returns the address on street "Via 1 Maggio" without any penalty on street field score. |
| GSQ-6815 | Geocode: Improved parsing of the queries where street name includes a district name, such as, for example, "12A Lieu-dit Le Pave, Le Pavé, Billy, 03260", where second "Le Pave" is district name. |
| GSQ-1655 | Geocode: Fixed the issue in Chile when "Y" in street name was misinterpreted as an indicator of street intersection, which was leading to unexpected results. |
Release 7.137
| Issue ID | Description |
|---|---|
| GSQ-6768 | Geocode: Implemented smarter way to identify not valid queries with too many numeric tokens. For queries in Hong Kong that have phone numbers and valid address, the /geocode endpoint now returns the result for the address part of the query. |
| GSQ-6850 | Geocode: For the house number results in Taiwan, the /geocode endpoint now consistently returns detailed 6-digit postal codes independent on which postal code format, 3- or 6-digit, was in the query. |
Release 7.136
| Issue ID | Description |
|---|---|
| GSQ-6218, GSQ-6287 | Geocode: The /geocode endpoint now recognizes hyphenated house numbers in Germany. |
| GSQ-6277 | Geocode: The /geocode endpoint now treats Arabic commas the same way as Latin commas, which are not expected to be matched, and do not cause penalties on any scores. |
| GSQ-5712 | Geocode: Qualified city query 'Tokyo' and also its Chinese and Korean variants now return the Tokyo Prefecture, the capital state in Japan. |
Release 7.135
| Issue ID | Description |
|---|---|
| GSQ-5239 | all endpoints: HERE Geocoding and Search API v7 now consistently returns city results in the Netherlands with non-empty area postal codes. |
Release 7.134
| Issue ID | Description |
|---|---|
| GSQ-5499 | Autosuggest, Discover: Improved category search support in the Polish language. |
Release 7.133
| Issue ID | Description |
|---|---|
| GSQ-6011 | all endpoints: Hong Kong: Fixed the missing space between street base name and street type in the Chinese transliterated language variant. |
| GSQ-5251 | Geocode: Improved results ranking in Canada, when the result on the correct street is missing a detailed postal codes, and, therefore, a result with fuzzy matching street name, but detailed postal code, was preferred. |
| GSQ-6029 | Geocode: Romania: the /geocode endpoint now correctly parses numbered districts in Bucharest. For example, in the query "Bulevardul Ghencea nr. 126-132, Bucureşti 6, 61699", "Bucureşti 6" is now correctly parsed as district and not anymore split into "Bucureşti" as city and "6" as potential house number. |
| GSQ-4261 | Autocomplete: Hong Kong: fixed the Chinese result title format to follow the rules of Chinese language. |
| GSQ-4898 | Discover: "hanoi" requests now return the city of Hanoi ranked over the county. |
Release 7.132
| Issue ID | Description |
|---|---|
| GSQ-5204 | Autosuggest: Improved the ranking of house numbers over related streets. |
| GSQ-4173 | Autosuggest: "taco" queries now return both, the taquiera category, and the Taco Bell chain, while "tacos" queries return only places related to taquiera. |
| GSQ-4304 | Autosuggest, Discover: German "essen" queries are now only associated with eat & drink category, and not with groceries. |
| GSQ-5409 | Geocode: In Taiwan, the /geocode endpoint now correctly handles special characters (for example: 廿 and 卅) and hyphens (之 or "-") in Chinese house numbers. |
| GSQ-5269 | Geocode: In Turkey, the /geocode endpoint now recognizes and treats alpha-numeric house numbers with and without a dividing space and delivers the same result. |
| GSQ-5070 | Reverse Geocode, Multi-Reverse Geocode: The administrative area names and street names are returned in the consistent language for the countries which official languages are in the Latin script. |
| GSQ-4185 | all endpoints: For the results in Hong Kong, HERE Geocoding and Search API v7 now renders address label / result title in the transliterated form of Chinese (zh-Latn), according to Latin scripts label format - with the dividing spaces, and without the Chinese house number symbol. |
Release 7.131
| Issue ID | Description |
|---|---|
| GSQ-4845 | Reverse Geocode, Multi-Reverse Geocode: When the requested language is English, but there isn’t English name available in the data, the name in the default or a regional language of the country is returned as a fallback. |
| GSQ-5198 | Autocomplete: The result title of postal code result in Australia was missing locality name when the postal code did not have a district name assigned. Now it is fixed and the /autocomplete endpoint includes into the result title for postal codes in Australia either the district name or, if there is no district name, the city name. |
| GSQ-4263 | Autocomplete: Corrected format of result title for the /autocomplete endpoint results in Taiwan in the Chinese language. |
| GSQ-4268 | Geocode: Improved few special cases when the /geocode endpoint did not always return house number results in Taiwan when, in an otherwise English language query, the end user put the Chinese symbol "號" (Number) after the house number, additionally to English "No.", in front of the house numbers. For example: "No. 65號, Anxiang Rd, Xindian District, New Taipei City, Taiwan 231". |
| GSQ-5109 | Geocode: Improved parsing of the secondary unit designators in USA - the /geocode endpoint now recognizes and correctly parses dash separated secondary unit patterns such as, for example, "Ste C-50". |
| GSQ-4934 | Geocode: Improved parsing of the secondary unit designators in USA - fixed the edge case when the /geocode endpoint did not correctly parse suite number, for example "Ste 5", and instead used "ste" as an abbreviated form of otherwise missing street type "street". |
Release 7.130
| Issue ID | Description |
|---|---|
| GSQ-2915 | Reverse Geocode, Multi-Reverse Geocode: State name in Spain is returned in full spelling. |
Release 7.129
| Issue ID | Description |
|---|---|
| GSQ-4251 | Autosuggest, Browse, Discover: evStation[*] filters are applied to light weight vehicle EV stations (category ID 700-7600-0322), trucks (category ID 700-7600-0323) and 2-wheelers (category ID 700-7600-0324). |
| GSQ-4563 | Geocode: The /geocode endpoint now correctly recognizes secondary units with special symbol “º“ (number) for relevant countries and languages. |
| GSQ-4114 | Geocode: When there are different views on one of administrative levels for a place result, such as, for example, postal versus administrative city, the /geocode endpoint sometimes returned the name from an unexpected view because the expected one was not available in the requested language. Now the /geocode endpoint correctly returns the expected view on the administrative level, either in the requested language or in the default language of the country, if the requested one is not available in the map content. |
| GSQ-1656 | Geocode: In the United Kingdom, the /geocode endpoint now more consistently ranks higher result with postal code matching on at least the base part. |
| GSQ-4701 | Autosuggest: Improved the category suggestion titles casing for the following languages: Danish, Dutch, Finnish, French, German, Italian, Norwegian, Polish, Portuguese, Romanian, Serbian, Spanish, Suomi, Swedish, and Turkish. |
Release 7.128
| Issue ID | Description |
|---|---|
| GSQ-1132 | Geocode: Solved the problem when the /geocode endpoint did not return address results in South Africa for building name query in qualified house number field. |
| GSQ-4067 | Geocode: Fixed the problem with ranking postal code candidates located in different countries. |
| GSQ-3594 | Reverse Geocode: Fixed a rare issue where the /revgeocode endpoint returned a distant city result with a high rank when "types=city" is requested. |
Release 7.127
| Issue ID | Description |
|---|---|
| GSQ-1089 | Geocode: Improved geocoding for "address line" + "postal code" queries where "postal code" is incomplete or partly incorrect. |
| GSQ-3188 | Geocode: The list of name variants for numbered routes in the USA is extended. Now the /geocode endpoint also can, for example, relate ‘FL-54’ to ‘State Road 54’. |
Release 7.126
| Issue ID | Description |
|---|---|
| GSQ-3318 | Autosuggest, Discover: Spanish phrase "como llegar a..." is now supported. |
| GSQ-2207 | Autosuggest, Discover: German queries "freibad", "naturbad", and "waldbad" are now supported. |
| GSQ-1594 | Reverse Geocode: Relevant street result to the input location is returned, instead of an irrelevant house number result from a different street. |
| GSQ-3189 | Geocode: USA: The /geocode endpoint now parses "PMB" (Private Mail Box) number, such as "#PMB344", as a secondary unit designator. |
| GSQ-2734 | Geocode: Fixed the issue when in some cases, HERE Geocoding and Search API v7 /geocode endpoint was returning unintentional results not limited by the 'types' filter. |
| GSQ-1659 | Geocode: Improved tolerance to additional leading zeros in the house number in the query. |
| GSQ-1653 | Geocode: For city queries, the /geocode endpoint now lists all the cities with names matching the query, including cases where the city name has an additional specifier. For example, "Münster (Hessen)" is now included into the list of the results for the query "Münster". |
| GSQ-1642 | Geocode: Improved matching of an address with shortened variant of city name. |
| GSQ-948 | Geocode: Improved tolerance to single letter typo in short query tokens. |
| GSQ-1030 | Geocode: Improved tolerance of misspells in street names in the HERE Geocoding and Search API v7 /geocode endpoint. |
Release 7.125
| Issue ID | Description |
|---|---|
| OSQ-33690, OSQ-41863, OSQ-39419, OSQ-39415, OSQ-39416 | all endpoints: Improved assignment of city and district names to area postal codes. |
| OSQ-40922 | all endpoints: "twp" and "township" are now considered synonyms. |
| OSQ-41740 | Autosuggest, Discover: Improved Hyatt chains search in New Zealand. |
| OSQ-41449 | Discover: Tokyo requests now return Tokyo state at the top. |
| OSQ-36839 | Discover, Geocode: Czech Republic: Improved recognition of house numbers in Czechia with omitted prefix "ev. č.". |
| OSQ-41333 | Geocode: Improved geocoding of query pattern street address + postal code without name of city or any other administrative places. |
| OSQ-40708 | Geocode: The /geocode endpoint now correctly matches street names with initialisms, for example "Impasse des E.M.O.". |
| OSQ-40695 | Geocode: Improved ranking rules for ambiguous street name matches. |
| OSQ-40468 | Geocode: Improved geocoding of addresses on numbered streets in Malaysia and Indonesia. |
Release 7.124
| Issue ID | Description |
|---|---|
| OSQ-40857 | all endpoints: Increase arabic street names coverage in Dubai/United Arab Emirates (UAE). |
| OSQ-41155 | Browse, Discover, Lookup: EV station results for queries with show=ev following elements now indlude: fixedCable, numberOfOutOfService, numberOfReserved. |
| OSQ-41184 | Autosuggest, Discover: mta requests in New York City , mbta requests in Boston, and bart in San Franciscp requests only return public transport places in these cities. |
| OSQ-34158 | Autosuggest, Discover: SA requests in Japan return large highways rest areas. PA requests in Japan return smaller parking areas with restrooms. |
| OSQ-40858 | Autosuggest, Discover: Indonesian queries SPKL return EV charging station results. |
| OSQ-40422 | Geocode: Spain: Added missing common street type abbreviations, for example "Avda" for Avenida. |
| OSQ-38935 | Geocode: Fixed the /geocode endpoint behavior for city + postal code queries. When a city has multiple postal codes, the /geocode endpoint now correctly returns postalCode result also for central postal code of the city. For city (town or village) + postal code queries, when the complete locality has one postal code, geocode continues returning city results. |
| OSQ-38935 | Geocode: Fixed incorrect scoring of administrative places when single character replacement was scored too high. |
| OSQ-40682 | Geocode: Improved matching of house numbers with prefix "N" with or without dividing space for countries and languages where it is relevant. |
| OSQ-40585 | Geocode: Aruba: Added missing common street type abbreviations. |
| OSQ-40703 | Geocode: France: Added missing common street type abbreviations. |
| OSQ-40551 | Geocode: Peru: Added missing common street type abbreviations. |
| OSQ-40573 | Reverse Geocode: Fixed the problem when looking up an ID in Japan that was retrieved from the /autocomplete endpoint, a HTTP 404 error was returned from the /lookup endpoint. |
Release 7.123
| Issue ID | Description |
|---|---|
| OSQ-35970 | Geocode, Autosuggest, Discover: USA: Fixed the problem with queries where the numbered route name is followed by PO BOX. For example, for a query "106477 hwy 89 po box 5236 etna , wy 83118", HERE Geocoding and Search API v7 now returns "106477 US Highway 89, Etna, WY 83118-9726, United States". |
| OSQ-40578 | Autosuggest, Discover: Bopomofo terms (Chinese character shorthand language input) are returned by default in the titles of results in Taiwan. |
| OSQ-40653 | Autosuggest, Discover: Improved EV station category search in Danish. |
| OSQ-27641 | Autosuggest, Discover: Enhanced cuisine search support for doner, kebab and shawarma. |
| OSQ-39861 | Autosuggest, Discover: Improved category search support in Vietnamese. |
| OSQ-40205 | Autosuggest, Discover: Improved the category search support for restaurants serving cuisine from the middle east. |
| OSQ-40766 | Autosuggest, Discover: Primary city names are now preferred over alternate city names in the results titles and address labels, even if end users are using alternate city names in their queries. Note: this behavior does not apply to the /geocode and /revgeocode endpoints. |
| OSQ-37400, 40399 | Autocomplete: Improved completion for queries consisting of house number and street name prefix, starting from 4 characters. For example query "17500 Trans" is now autocompleted to "Canada, QC, H9J 2X8, Kirkland, 17500 Trans Canada Hwy". |
| OSQ-39284, 40818 | Geocode: The /geocode endpoint now can find district or city result for qualified queries with long multiword county names. |
| OSQ-40435 | Geocode: Improved support of misspelled street names containing "l'" in long address queries in France. |
| OSQ-35968 | Geocode: Improved matching of street names when a single token in the street name as of the map data, in the query is divided into two words. |
| OSQ-40626 | Geocode: The /geocode endpoint now supports common English street type abbreviations for street names with language code "en-Latn" in Thailand. |
| OSQ-40574 | Geocode: Improved tolerance of omitted directionals, for example "Sur" or "Norte", in Spanish street names. |
| OSQ-40684 | Geocode: Improved the /geocode endpoint logic to correctly recognize in the query secondary unit with leading zero or a preceding special character. |
| OSQ-40572 | Geocode: Improved matching of house numbers in Chile which in the map data are coded with leading zeros. |
| OSQ-40662 | Discover: Some queries for "Walmart Supercenter" now do not return places belonging to the Walmart Neighborhood Market chain, but only to Walmart Supercenter chain. |
| OSQ-40897 | Discover: Queries for "uc san diego", "ucsd" and "university of california san diego" now return the expected UCSD place. |
| OSQ-40898 | Discover: Queries for "University of Michigan" now return the expected place. |
| OSQ-39589 | Discover: Queries for "DT2 7SA" and "DORCHESTER DT2 7SA" now return the result "DT2 7SA, Dorchester, United Kingdom" with a high precision postal code. |
| OSQ-41072 | Discover: Improved searchability of Pondok Indah Mall 1/2/3 in Jakarta through "pim" queries. |
Release 7.122
| Issue ID | Description |
|---|---|
| OSQ-38451 | Geocode: When the same detailed postal code is associated to multiple streets, the /geocode endpoint returns it with the street name matching to the query. For example in case of "SP1 3WE" it may be either "Archers Court" or "Castle Street" depending on the query. |
| OSQ-40462 | Geocode: HERE Geocoding and Search API v7 /geocode endpoint in United Kingdom now prefers more accurate exactly matching detailed postal code result to far away house number fallback result with different postal code. |
| OSQ-40432 | Geocode: Improved detection of secondary unit designators in the USA. |
| OSQ-40510 | Geocode: Improved matching of number routes, for example "D52" in France. |
| OSQ-39845 | Geocode: US: In ambiguous cases, the /geocode endpoint now prefers as a house number the number in the query preceding the street name to the one after the street name, since this is more common address format. |
| OSQ-40886 | Geocode: Australia: the /geocode endpoint now consistently prefers exactly matching Point Address over ranged Point Address. |
| OSQ-40430, OSQ-35967 | Geocode, Search, Autosuggest: HERE Geocoding and Search API v7 is now more resistant to typos in lettered suffix at the end of numerals in cardinal numbers in street names. |
| OSQ-38458 | Autosuggest, Discover: Germany: Improved "Globus" and "Globus Baumarkt" chain support. |
| OSQ-33095 | Autosuggest, Discover: Enhanced support for shopping mall category search in Turkish. |
| OSQ-40337 | Autosuggest, Discover: Improved the chain search support for Ritz-Carlton hotels. |
| OSQ-40705 | Autosuggest, Discover: Added support for Vietnamese People's Court place category search. |
| OSQ-40543 | Autosuggest, Discover: Added support for "aus32" queries to receive gas stations serving Diesel with AUS32 additives in the response. |
| OSQ-40668 | Autosuggest, Discover: Improved support of Kroger Marketplace chain search. |
| OSQ-40639 | Autosuggest, Discover: Added support for the Turkish near-like conjunction "en yakın". |
| OSQ-40638 | Autosuggest, Discover: Requests with the Turkish term "otagarı" are now interpreted as a category search for bus stations. |
| OSQ-36422 | Autosuggest, Discover: German queries about place categories of a certain chain are now supported in both <category>; <chain> and <>chain> <category> forms. For example: "tankstelle Aral". |
| OSQ-40095 | Autosuggest, Discover: Requests for "wallmart supercenter" now return places from that specific chain (with the chain ID 35812)." |
| OSQ-40112 | Discover: Requests for "Wisma Mulia" in Jakarta now return the expected skyscraper. |
| OSQ-39774 | Discover: Requests such as "korean food near korea town" from Barrie/Canada now return korean food restaurants in Korea town district from Los Angeles instead of the nearby Korea town from Toronto. |
| OSQ-38543 | Discover: Requests for "courtyard marriotte near san diego airport" now return the expected hotel nearest the San Diego airport. |
| OSQ-39810 | Discover: Chinese queries centered in Hong-Kong return places with category ID translations in Cyrillic. |
| OSQ-38199 | Discover: Coordinate search responses contain the requested coordinate as display position. |
| OSQ-37704 | Autosuggest: Requests for "mission & 1st aly" in San-Francisco now return the expected intersection. |
| OSQ-40039 | Autosuggest: Short numerical queries return far away results in Singapore (postal codes) or Japan (block/sublocks). |
| OSQ-40726 | Reverse Geocode: If there are multiple house numbers with the same value located on the same street but at different locations, the reverse geocoding will now return the nearby house number instead of a house number that is further away, or a street result. |
| OSQ-37073 | Reverse Geocode: The /revgeocode endpoint consistently returns the house number that comes first in lexicographical order when multiple house numbers are located at the same geographic coordinates. |
Release 7.121
| Issue ID | Description |
|---|---|
| OSQ-39606 | Geocode, Search, Autosuggest: Improved matching of street names for special case when street name contains a word recognized as a secondary unit designator. For example, "4 Roome Rd, Towaco, NJ". |
| OSQ-40377 | Geocode, Search, Autosuggest: HERE Geocoding and Search API v7 now can match and return special (PO BOX) zip codes in Guam with result type "postalCodePoint". |
| OSQ-39155 | Autosuggest, Discover: Added support for "hauptbahnhof" and "hbf" place category use case. |
| OSQ-36458 | Autosuggest, Discover: Indonesia: Improved address search result relevance when the query contains indonesian address parts qualifiers. |
| OSQ-40293 | Geocode : Fixed the problem of returning empty responses for alpha-numeric hosue number queries, when showMapReferences=pointAddress is requested. |
| OSQ-39968 | Geocoder: Indonesia: Improved parsing on street names with numeric suffix. Before, Geocode sometimes matched the number in the street name to a house number. |
| OSQ-40434 | Geocode: Spain: Improved matching of house numbers with prefix "N" with or without a dividing space. |
| OSQ-40579 | Geocode: The /geocode endpoint now supports common English street type abbreviations for street names with language code "UKE" - Arabic names translated into Latin-1 characters for all countries with this type of language coding. |
| OSQ-40587 | Geocode: Saudi Arabia: The /geocode endpoint now supports common English street type abbreviations for street names with language code "UKE" - Arabic names translated into Latin-1 characters. |
| OSQ-40584 | Geocode: Kuwait: The /geocode endpoint now supports common English street type abbreviations for street names with language code "UKE" - Arabic names translated into Latin-1 characters. |
| OSQ-40586 | Geocode: Qatar: The /geocode endpoint now supports common English street type abbreviations for street names with language code "UKE" - Arabic names translated into Latin-1 characters. |
| OSQ-40580 | Geocode: Egypt: The /geocode endpoint now supports common English street type abbreviations for street names with language code "UKE" - Arabic names translated into Latin-1 characters. |
| OSQ-40583 | Geocode: United Arab Emirates: The /geocode endpoint now supports common English street type abbreviations for street names with language code "UKE" - Arabic names translated into Latin-1 characters. |
| OSQ-39840 | Geocode: Brazil: Improved the /geocode endpoint logic to prefer the result closest to "at" position from multiple fuzzy matching house number candidates on the same street but with different districts and postal codes. |
| OSQ-40214 | Geocode: Jordan: The /geocode endpoint now supports common English street type abbreviations for street names with language code "UKE" - Arabic names translated into Latin-1 characters. |
| OSQ-40176 | Geocode: The /geocode endpoint parses out "Lot" followed by a number as a secondary unit designator only if the query has other good house number match. Otherwise it accepts the number after "Lot" as a house number. |
| OSQ-39732 | Autocomplete: If the query matches to a county and to a city which does not belong to this county, the /autocomplete endpoint now returns both of them. If city belongs to the county with the same name, the /autocomplete continues de-duplicating the results by keeping only the city. |
| OSQ-38638 | Discover: Improved Main Beach Park searchability for "laguna beach" queries. |
| OSQ-40479 | Discover: Hong Kong: Improved stability of the results for primary school search qieries. |
Release 7.120
| Issue ID | Description |
|---|---|
| OSQ-39069 | Autosuggest, Discover : Australia: improved the support of common abbreviations in the address queries, for example: "Tce" for "Terrace". |
| OSQ-40201 | Autosuggest, Discover : Improved support for place categories in the Thai language. |
| OSQ-40396 | Geocode: Improved /geocode endpoint logic to disambiguate the cases when a query has more than one token which may potentially be parsed as house number. Now geocode more consistently prefers the one which is closer to the street name in the query. |
| OSQ-39438 | Geocode: United States: the /geocode endpoint now successfully returns Postal Code 01201. |
| OSQ-40109 | Geocode: For a qualified query "Pont de Gaye," in "13270, Fos-sur-Mer, FR", which does not exist in the map data, the /geocode endpoint now prefers fuzzy match in the correct city and postal code. |
| OSQ-39047 | Geocode: Fixed the problem with house number fallback logic in small towns where the street name is the same as the name of the town. |
| OSQ-39282 | Geocode: Argentina: Improved cases where house number result on a street with a matching name in the wrong locality was preferred to a street result in the correct locality. |
| OSQ-35262, OSQ-39068 | Geocode: United States: the /geocode endpoint now correctly recognizes multiword spelled out numbers in street names. For example, for a query "Oakland, thirty second st" the /geocode endpoint now returns street result "32nd St, Oakland, CA, United States" instead of "2nd St, Oakland, CA 94607, United States". |
| OSQ-38345 | Autosuggest : Improved /autosuggest endpoint results for "Starbucks Coffee" requests to suggest nearest Starbucks places |
| OSQ-38888 | Autosuggest : Fixed issue when some highlights were off by a character when using alternate names with diacritics. |
| OSQ-38933 | Autocomplete: For query "forbes" in , the /autocomplete endpoint now returns as first suggestion the best matching city "Australia, NSW, 2871, Forbes", instead of less relevant suggestion "Australia, VIC, 3990, Glen Forbes". |
| OSQ-39956 | Browse : Improved /browse endpoint results to include the high precision postal code for place results in Canada. |
| OSQ-39874 | Discover : Fixed the issue when "india gate" requests did not return the famous square in New Delhi when the search center was far away. |
Release 7.119
| Issue ID | Description |
|---|---|
| OSQ-35503 | Discover: India Gate is now correctly returned for "india gate" queries. |
| OSQ-39801 | Geocode: "New York, NY" queries now return expected results. |
| OSQ-39768 | Geocode: The /geocode now parses hash (#) symbol as valid house number prefix in Australia also in special cases where a single numeric house number is matched to a "ranged" Point Address. |
| OSQ-39281 | Geocode: Improved house number fallback logic in small towns where people use the name of the town as a street name. Previously, the /geocode was falling back to the town as an area result instead of returning the closest available house number. |
| OSQ-21626 | Autocomplete: Improved prefix support that prevents the /autocomplete from loosing postal code suggestions in Great Britain after entering third character from the end. |
| OSQ-39101 | Autosuggest : Improved Hot Dog places searchability for "hot dogs" plural requests. |
Release 7.118
| Issue ID | Description |
|---|---|
| OSQ-39046 | Geocode, Autocomplete, Discover, Autosuggest: Improved tolerance for omitted hyphens in the query. For example, for a query "q=Wilhelmleonhardstraße 10, 77694 Kehl" endpoints now return the result: "Wilhelm-Leonhard-Straße 10, 77694 Kehl, Germany". |
| OSQ-38223 | Discover: Request query "CoCo壱番屋 東急白楽駅前通店" now returns correct results with "CoCo壱番屋 東急白楽駅前通店" displayed as the first result. |
| OSQ-37695 | Discover: Allianz Arena place in Munich, Germany is now correctly returned. |
| OSQ-38255 | Geocode: Geocode endpoint now supports hash (#) symbol as valid house number designator in Australia. |
| OSQ-38346 | Geocode: Malaysia: improved house number fallback logic for numbered streets. |
| OSQ-39504 | Geocode: Improved tolerance for omitted space between numeric and non-numeric tokens in the query, for example, between postal code and city name. |
| OSQ-39365 | Geocode: The Netherlands: Geocode now supports directional abbreviations in street names - it can match spelled out directionals in the query to the standard directional abbreviations in the map data. For , it can match street name "Waalhaven Oostzijde" in the query to "Waalhaven O.Z." in the map data. |
| OSQ-37113 | Autosuggest: Ionity chain suggestion is now correctly returned for queries in the United States. |
Release 7.117
| Issue ID | Description |
|---|---|
| OSQ-35961 | Geocode, Autocomplete, Discover, Autosuggest: Improved query matching where a space or a divider is missing between two tokens in the query. For example, for query q=5995 Gulfwinds Drive 33706, St Pete Beach, FL GS7 now returns "5995 Gulf Winds Dr, St Pete Beach, FL 33706-3719". |
| OSQ-39096 | Geocode, Autocomplete, Discover, Autosuggest: Now the endpoints correctly return the city results in France with names starting with "La". |
| OSQ-38905 | Geocode, Autocomplete, Discover, Autosuggest: Now the endpoints more consistently match queries where a space or a divider is missing before or after a numeric token in the query. |
| OSQ-36518 | Discover, Autosuggest, Lookup: Parking availability information is now rendered by providing 'customerParking: true (or false)'. The feature is only available for select customers using a parameter: 'showParkingAmenities=customerParking' |
| OSQ-38106 | Autosuggest, Discover: Improved search quality for a chain Toom Baumarkt. |
| OSQ-39307, OSQ-38795 | Reverse Geocode, Lookup: Tunisia, Macau: POI names are now returned in latin script if language code "en-GB" is requested. |
| OSQ-38936 | Autosuggest, Discover: "Bay Thai" requests now correctly return nearby "Bay Thai Cuisine" place. |
| OSQ-38266 | Geocode: Improved street scoring in Poland by adding support of common street type abbreviations, for example "pl", "al", "os". |
| OSQ-38260 | Geocode: Geocode endpoint now correctly recognizes one of "E", "W", "N", "S" directionals plus number, like "E414", as secondary unit designator instead of street in queries like "950 Maine Ave SW E414". |
| OSQ-38259 | Geocode: Improved support of ordinal number variants for street names in German. For example, "Erste Suedwieke" in the query is now matched to street name "1. Suedwieke" in the map data as an exact match. |
| OSQ-38249 | Geocode: Improved street scoring in Bulgaria by adding support of common street type abbreviations. |
| OSQ-38442 | Geocode: Improved street scoring in Romania by adding support of common street type abbreviations. |
| OSQ-38476 | Geocode: Improved parsing of queries like "Gewerbepark 3, 7423 Grafenschachen", where locality name can also be matched to a street name. Now Geocode endpoint returns house number "3" on street "Gewerbepark" in city "Grafenschachen" instead of house number "3" on street "Grafenschachen" close to an intersection with street "Gewerbepark". |
| OSQ-38311 | Geocode: United States: for queries with omitted directional in the street name, Geocode endpoint now consistently returns the same result for spelled out or abbreviated street type. |
| OSQ-39229,OSQ-39227 | Geocode: Improved support of non-numeric postal codes in geocode qualified queries in Bermuda, Anguilla, Brunei Darussalam, Eswatini. |
| OSQ-30530 | Geocode: Geocode endpoint now supports matching between Arabic and Roman numerals up to 31 in admin names in Philippines. For example, for a query "noveleta santa rosa 2", it now returns district "Santa Rosa II, Noveleta" as an exact match. |
| OSQ-38263 | Geocode: The Geocode logic to recognize and parse "wrong" street type as part of street name, which was available only to the USA, is extended to Great Britain, Canada, and Australia. With this feature, Geocode now applies penalties of 0.1 to street field score and 0.03 to query score to street type not matching to the map data. |
| OSQ-39061 | Autosuggest: "Autosuggest now correctly returns the same result for queries: "10023" and "10023, New York, NY, United States". |
| OSQ-38477, OSQ-39244 | Geocode: Malaysia: Geocode endpoint now parses and scores "No." as valid prefix of house number and returns results also for otherwise fuzzy queries with low query score. |
| OSQ-38468 | Discover: Scivias St. Valentinus-Krankenhaus is now returned for "scivias" queries. |
| OSQ-38857 | Discover: “Casa Loma” queries now correctly return the intended museum. |
| OSQ-38907 | Discover: "Mainkai" queries now correctly return a well known place Mainkai Café. |
Release 7.116
| Issue ID | Description |
|---|---|
| OSQ-38510 | all endpoints: Improved response of district name for postal code queries - when a postal code crosses multiple districts, it is more probable that postal code result has non-empty district name. |
| OSQ-38936 | Autosuggest, Discover : "Bay Thai" requests now return the nearby "Bay Thai Cuisine" place. |
| OSQ-36686 | Discover: Requests for "museum of science and industry" now correctly return the place named "Mosi Museum of Science and Industry" in Tampa, FL. |
| OSQ-38370 | Discover: Requests for "Schottenhof" in Mainz/Germany now correctly return the place "Hotel Schottenhof". |
| OSQ-38315 | Discover: Requests in Mainz/Germany for "Gangel" now correctly return the nearby Hotel Gangel. |
| OSQ-38508 | Discover: Japan: "sushir" and "sushiro" queries now return Sushiro results with consistent casing. |
| OSQ-38930 | Discover: Requests containing following spelling errors now correctly return the expected results: "McKellen" (in place of "McClellan"), "Food Line" (in place of "Food Lion"). |
| OSQ-36253 | Discover: Request query "an arbor" now correctly returns Ann Arbor, Michigan, USA. |
| OSQ-37626 | Discover: The city Seattle is returned for "seattle" requests in London. |
| OSQ-36253 | Discover : "an arbor" requests return Ann Arbor, Michigan, USA. |
| OSQ-36686 | Discover : Requests for "museum of science and industry" now return the place named "Mosi Museum of Science and Industry". |
| OSQ-38509 | Geocode: If a query contains multiple numbers which may be matched as house numbers, Geocode endpoint now prefers the one which is not separated from the street name by some other address fields. |
| OSQ-38362 | Geocode: Geocoder now correctly returns postal code results in Argentine for qualified queries. |
| OSQ-38508 | Autocomplete: Improved autocomplete queries for cities in West Bank, Palestine. |
| OSQ-37975 | Autocomplete: Autocomplete now correctly returns cities in West Bank, Palestine, for example Ramallah or Nablus. |
| OSQ-39061 | Autosuggest : "10023" and "10023, New York, NY, United States" queries now return the same result. |
Release 7.115
| Issue ID | Description |
|---|---|
| OSQ-38767, OSQ-37526 | Geocode, Autocomplete, Search, Autosuggest: Previously, using abbreviation "str" for German 'Strasse'/'Straße' sometimes gave wrong results. |
| OSQ-38274 | Geocode, Autocomplete, Search, Autosuggest: In the United States Virgin Islands endpoints return special zip codes (PO BOX or "Unique" zip codes). |
| OSQ-37619 | Autosuggest, Discover: Improved "société générale" response quality with diacritic symbols in France. |
| OSQ-34946 | Autosuggest, Discover: Improved support of search queries with typos, for example: "310 boardway san Francisco". |
| OSQ-24725 | Autosuggest, Discover: Improved spell correction, for example for a query spelled "14527 Jupiter Street Hesperia California" the 14527 Juniper Street Hesperia California address is now returned, and for a query "McKellen and Eastern Schenectady New York" the McClellen and Eastern Schenectady New York address is correctly returned. |
| OSQ-34497 | Autosuggest, Discover: Improved support of phonetic input search queries with typos, for example: Incorrectly spelled request "932 Sigel Ave. Charlotte" does not return 932 Seigle Ave. Charlotte. |
| OSQ-38482 | Autosuggest, Discover: Improved Marks & Spencer chain search support. |
| OSQ-38474 | Discover: The results for "eni" requests now return Agip gas stations following the company name change in some countries, for example Italy. |
| OSQ-38421 | Discover: St Josefs Hospital place in Mayence/Germany is returned for a "St Josefs" request. |
| OSQ-38248 | Geocode: Improved recognition of abbreviated street types that leads to higher street and query scores in Lithuania. |
| OSQ-37408 | Geocode: Geocode returns correct results for street name in Singaporean addresses abbreviated in the map data and spelled out in the query, for example "Kampong"/"Kg" and "Industrial"/"Ind". |
| OSQ-38861 | Geocode: Street score is 1.0 in German speaking countries 'fieldScore.streets' when 'strasse'/'straße' is abbreviated in the query to 'str'. |
| OSQ-36177 | Geocode: Improved recognition and tolerance of omitted or abbreviated first names or person titles in street names in Argentina, that may lead to no result, wrong result or lower query and street scores for otherwise correct result, for example Boulevard Illia, Córdoba. |
| OSQ-37525 | Geocode: Improved result for city/postal code fallback when the postal code is specified as qualified query field. The problem of getting a far away result instead of a result based on postal code was originally observed for queries in Sweden but the fix applies to queries with qualified postal code field world wide. |
| OSQ-38466 | Autosuggest: Fixed duplicated query terms. |
| OSQ-38549 | Autosuggest: Improved search result for a specific query: "seattle starbucks pike" request returns correct address of Starbucks, 1912 Pike Pl, Seattle, WA 98101. |
| OSQ-38105 | Autosuggest: Improved search threshold, "106 W 12th St, Kansas City, MO 64105" request returns relevant second result (rank 2). |
Release 7.114
| Issue ID | Description |
|---|---|
| OSQ-36981, OSP-7089 | Geocode, Discover: Geocoder and Search now return results for street names that contain the word "stop". For example: "E Stop 18 Rd". |
| OSQ-24455, OSP-4076 | Geocode, Discover: Improved consistency of Geocoder and Search results for addressline-only queries like "123 main street". Instead of far away Point Address results, now nearby interpolated results are returned. |
| OSQ-38544, OSP-7521 | Discover: Single case where Search returns duplicate results for the query "Tuchinger Strasse" in city Freising, Germany is resolved. |
| OSQ-36171, OSP-6860 | Discover: Single case where Search does not return "ABC Store" in Greensboro even though the at position is near-by is resolved. |
| OSQ-37859, OSP-7296 | Discover: Single case where Search does not return "Mezita Coffeehouse" in Ontario/CA for the query "Mezita Coffee" is resolved. |
| OSQ-37270, OSP-7110 | Discover: Single case where Search does not return "H-57 Spur 3311" in Moran/MI for the query "H-57 Spur 3311" is resolved. |
| OSQ-37858, OSP-7295 | Discover: Frankfurt airport is now returned at top position for the query "Flughafen Frankfurt am Main". |
| OSQ-33550, OSP-6096 | Geocode: Single case where Geocoder does not recognize "SW LEJUNE RD" as relevant match for "S Le Jeune Rd" is resolved. |
| OSQ-29066, OSP-4803 | Geocode: Single case where Geocoder does not return the correct address for "Via Giuseppe Verdi 23, Pavia, IT" is resolved. Previously the Geocoder returned a Point Address house number in the county Pavia instead of an interpolated house number in the city Pavia. |
| OSQ-36905, OSP-7057 | Autocomplete: Autocomplete now consistently provides state type suggestions for queries with spelled out USA state names. |
| OSQ-38190, OSP-7376 | Autosuggest: Wrong casing for German "Ec-Automat" in categoryQuery suggestion title is resolved. The corrected title is "EC-Automat". |
| OSQ-38545, OSP-7186 | Autosuggest: Single case where Autosuggest does not find "1127-1133 Kearny Apartments" in San Francisco for the query "1127-11" is resolved. |
Release 7.113
| Issue ID | Description |
|---|---|
| OSQ-38160 | all endpoints: Indonesia: The result title and address label of address and place results in Indonesia are complete and have correct position of RT/RW address field. |
| OSQ-38195 | Discover, Geocode: USA: Fixed application of alpha-numeric interpolation. Incorrect suffix is not added for house number when it is mistakenly included into the query. |
| OSQ-36118 | Discover, Geocode, Autosuggest: USA: GS7 now correctly returns city with its official state code and name. Previously, if a city had some streets extending into neighboring state, when neighboring state name or code is included into request, GS7 might return this city with mismatching state name and code: its "official" state code and neighboring state name. |
| OSQ-37849 | Geocode: New Zealand: Geocode recognizes secondary unit in format preceding house number without "/" separator and without secondary unit designator. |
| OSQ-38282, 38195 | Geocode: In some countries with non-Latin script, in particular in Serbia, Geocode endpoint now can match and return alpha-numeric Point Addresses with non-Latin alpha part. |
Release 7.112
| Issue ID | Description |
|---|---|
| OSQ-36118 | Discover, Geocode, Autosuggest: USA: GS7 now correctly returns city with its official state code and name. Previously, if a city had some streets extending into neighboring state, when neighboring state name or code is included into request, GS7 might return this city with mismatching state name and code: its "official" state code and neighboring state name. |
| OSQ-37843 | Geocode: Puerto Rico: now correctly returns postal codes in Puerto Rico with two leading zeros, for examples for queries like: "00923 PRI". |
| OSQ-37295 | Geocode: USA: now correctly returns hierarchy fallback in correct state instead of address result in wrong state. |
| OSQ-37850 | Geocode: Australia: Geocode recognizes all secondary unit designator patterns in Australia. |
| OSQ-37527 | Discover, Geocode: USA: Fixed application of alpha-numeric interpolation. Incorrect suffix is not added for house number when it is mistakenly included into the query. |
Release 7.111
| Issue ID | Description |
|---|---|
| OSQ-37719 | Discover, Geocode, Autosuggest: Indonesia: the endpoint now does not expose names of "greater cities" such as Jabodetabek, Pengembangan Ibu Kota Nusantara, Pusat Ibu Kota Nusantara, Bandung Raya, in the response as state and as part of address label and result title. |
| OSQ-37282 | Geocode: Supports inrerpolation for special house numbers formats in USA, for example: "W168N11415". |
| OSQ-37388 | Geocode: Geocode now detects all the secondary unit designators defined by the USPS. |
| OSP-7115, OSQ-37155 | Geocode: Geocode endpoints now correcly returns "Logan Hyperdome Shopping Complex" in Brisbane, Australia without matching "06" from "Tenancy MM06A" as house number. |
| OSQ-36203 | Geocode: Geocode endpoints now correcly returns "Logan Hyperdome Shopping Complex" in Brisbane, Australia without matching "06" from "Tenancy MM06A" as house number. |
Release 7.110
| Issue ID | Description |
|---|---|
| OSQ-37118 | Autosuggest: Improved ranking for house number vs street results. Autosuggest now ranks more distant exact house number matches higher than nearby street matches. |
| OSP-6437, OSQ-35153 | Autosuggest: Japan: Improved ranking of prominent places that are nearby the driver location ('at' parameter). |
| OSP-7115, OSQ-37155 | Autosuggest: Improved follow-up category query suggestion responses for 'car service' in Czech search ('auto servis'). |
Release 7.109
| Issue ID | Description |
|---|---|
| OSQ-37114, OSQ-36884, OSP-7096, OSP-7052 | Geocode: Geocoder returns the "Airport Police" instead of "Washington Dulles Int'l Airport" for the query "Dulles International Airport". This has been fixed by adding support for abbreviation from "International" to "Int'l". |
| OSP-7003, OSQ-36725 | Autosuggest: 'Aldi' is not recognized as ontology in Australia even though 'Aldi' grocery stores exist in Australia. This has been fixed. Autosuggest now provides the chain query follow-up suggestion for 'Aldi'. |
| OSP-6802, OSP-7005, OSQ-35905 | Discover, Autosuggest: Japan: Japanese chain names are missing in results. This has been fixed. Japanese chain names where available in the source data are now returned. |
| OSQ-36763 | Discover, Autosuggest: Japan: The Japanese chain name for 'Family Mart' (ファミリーマート) is not shown in results. This has been fixed. |
Release 7.108
| Issue ID | Description |
|---|---|
| OSQ-36408 | Autosuggest, Discover: Improved search for chain Electrify Canada. Autosuggest provides chain follow-up query suggestion when relevant for user query. |
| OSP-6868, OSQ-36365 | Autocomplete: Improved Autocomplete in Mexico by supporting street type abbreviation 'BLVD'. |
| OSP-5522, OSQ-31687 | Geocode: The Geocoder now offers improved fallback behavior for address queries in the USA, particularly those containing state codes and postal codes. Previously, the Geocoder favored results based on matching street and house numbers, potentially leading to results in distant or incorrect states. The improved behavior prioritizes returning results within the correct state, focusing on city or postal code results. |
| OSP-7071, OSQ-36946 | Autosuggest: Improved follow-up category query suggestion responses for 'zoo' in Serbian search ('zooloski vrt'). |
| OSP-7072, OSQ-37036 | Autosuggest: Improved follow-up category query suggestion responses for 'charging station' in Serbian search ('stanica za punjenje'). |
| Autosuggest: Improved follow-up category query suggestion responses for 'parking' or 'parking garage' Estonian, Danish, Spanish, Czech, Serbian, Lituanian, Italian, Portuguese, Polish, Greek, Turkish searches. |
Release 7.107
| Issue ID | Description |
|---|---|
| OSP-6261, OSP-6810, OSQ-35921 | Geocode: Geocoder did not apply spell correction to street names in rare cases for qualified queries in Spain. The implementation has been adapted to work with long and detailed qualified query input. |
| OSQ-36558 | Geocode: Improved matching of United States ZIP codes with leading 0. Example: 01263 USA |
| OSQ-36638 | Geocode: Improved address search for French addresses. In some cases, the Geocoder misinterpreted 'r' (abbreviation for street type 'Rue') as part of a house number. |
Release 7.106
| Issue ID | Description |
|---|---|
| OSP-6600, OSQ-35242 | Geocode: Improved street matching in Serbia. Example: For query "UGRINOVAČKI PUT 8 DEO" the Geocoder used to match to a street with the wrong street number: "Ugrinovacki put 38. deo". The improved result is "Ulica Ugrinovacki put 8. deo". |
| OSP-6862, OSQ-36178 | Geocode: Improved address matching in Argentina. Previously, the Geocoder had a tendency to prioritize address results from the wrong city over street results within the specified city. The Geocoder now gives higher priority to street results specifically within the specified city, ensuring more accurate and relevant search results. |
| OSP-6646, OSQ-35573 | Geocode: Previously, the Geocoder did not recognize the '+' sign as a valid separator between two parts of a postal code. For example, 'HP8+4SQ' was not correctly interpreted. The Geocoder now interprets the '+' sign as space character. |
| OSP-6801, OSQ-35903 | Geocode: Previously, the Geocoder did not return correct results for abbreviated street names in Singapore. |
| OSP-6862, OSQ-36175 | Geocode: Previously, the Geocoder did not support flexible word in street names in Argentina. The Geocoder now accommodates different variations of word order commonly found in street names across the country. |
Release 7.105
| Issue ID | Description |
|---|---|
| OSP-6206, OSQ-33889 | Discover: Fixed issue where the expected result - query 'Stanley Park' - was not returned when the language parameter was not set. |
| OSP-6770, OSQ-35839 | Geocode: Fixed issue where the Geocode endpoint with qualified input incorrectly aligns district field input to the city when city and district of the result item are the same. The fieldScore,city showed the district score. |
| OSP-6227, OSQ-33958 | Autocomplete: Fixed issue where Autocomplete incorrectly matched alias languages. Specifically, in the query '1 Sansome St Sa,' the 'Sa' part was erroneously matching to the exonym country name 'Saharat' instead of the intended city name 'San Francisco.' |
| OSP-6476, OSQ-37871 | Geocode: Fixed issue where in the query 'C/ Pasteur, 43 1o 1a Barcelona Barcelona ES 08024' the Geocoder was incorrectly matching the house number '1a' instead of the expected '43.' This issue has been fixed, and the geocoder now accurately identifies and returns the correct house number '43' for the given address. |
| OSP-6477, OSQ-34874 | Geocode: Fixed issue related to Vienna addresses. The issue was that in the query 'Breitenseer Straße 76/1/4/32 Wien AT 1140', the Geocoder was incorrectly matching the house number '32' instead of the expected '76'. This discrepancy occurred when there were multiple house number components separated by slashes ('/'). The Geocoder was prioritizing the last component instead of correctly identifying the main house number. |
| OSQ-35784 | Geocode: Improved consistency for returning street names in results of type postalCodePoint. |
| OSQ-34605 | Geocode: Improved behavior related to handling multiple numbers in a query that are not parsed as postal code, part of the street or administrative name, or secondary unit designators. Previously, the geocoder considered any of these numbers as potential house numbers without a specific preference. The Geocoder endpoint now applies a preference rule to prioritize the number that is closer to the street name in the query. As a result of this improvement, in the query 'Olga Cossettini 730, 1106, Puerto Madero, Ciudad Autónoma de Buenos Aires, Argentina', the number '730' is now correctly matched as the house number instead of '1106'. This ensures that the geocoder provides more accurate and contextually relevant results for queries with multiple numbers. |
| OSQ-35178 | Goocode, Discover, Autocomplete: Fixed issue where country name was not provided for the result 'Güney Kıbrıs Rum Yönetimi' with politicalView=TUR. "Güney Kıbrıs Rum Yönetimi" refers to the "Greek Cypriot Administration" in English. It is a term used to denote the Turkey government view of the southern part of the island of Cyprus. |
Release 7.104
| Issue ID | Description |
|---|---|
| OSP-6386,OSQ-34454 | Geocode: Geocoder does not find a Place result when the term "International" is omitted from the query input. This is improved. The Geocoder now more likely returns results where the term 'International' is part of the Place name but omitted from the query input. |
| OSP-6783, OSQ-35884 | Discover: Improved search for university in Thai "มหาวิทยาลัย". |
| OSP-6739, OSQ-35610 | Autosuggest: Improved search category name for bakery in Turkish language. |
| OSP-6534, OSQ-34973 | Autosuggest: Improved search for Place Tempe Marketplace. It was not showing in response before. |
| OSP-6576, OSQ-35140 | Discover: Improved search for "Electric vehicle charging station". |
| OSQ-34929 | Autosuggest: Japan: Improved search for EV charging stations when searching with common EV search terms in Japanse. |
| OLPSUP-15400, OSQ-28392 | Discover: Japan: Discover endpoint fails to return expected result for subblock address search in cases where the query does not contaion the block suffix "丁目". |
| OSP-6180, OSQ-33793 | Discover: Dealership search requires exact name input but should return with request for "Toyota of <city>". |
Release 7.103
| Issue ID | Description |
|---|---|
| OSQ-32614 | Geocode: Qualified country field qq=country (e.g. qq=country=USA) mistakenly behaves as hard country filter where the country code or country name has to be correctly spelled. This is fixed. The filter now accepts variances and misspells of the country code or country name in the same way as all other qualified field parameters. |
| OSP-6479, OSQ-34870 | Geocode: The Geocoder does not recognize French ordinal numbers as secondary unit designators. Example: In query '28, Allée du Docteur Robert Lafon 2eme étage Cabinet Ophtalmea Bayonne FR 64100', '2eme étage' describes a unit. The Geocoder should detect and ignore these terms so that they do not negatively impact the match quality. |
| OSP-6236, OSP-6359, OSQ-34088 | Discover: Search for 'MAX' does not return relevant results. |
| OSQ-34695 | All endpoints: All endpoints return duplicated address or street results in countries where Arabic is the primary official language and English or French is the second official language. This is fixed for address (result type houseNumber) results. Street-type results may still be returned as duplicates. |
Release 7.102
| Issue ID | Description |
|---|---|
| OSQ-35323 | Geocode: Geocoder does not recognize "1/2" as secondary unit designator. Example: 'q=1451 1/2 Missouri Ave , East Saint Louis, IL 62201-3207' |
Release 7.101
| Issue ID | Description |
|---|---|
| OSQ-35030 | Geocode: Search for city "Faro" (Portugal) with county name variant "Distrito de Faro" returns street results in Mexico. |
| OSQ-33630 | Geocode: Postal code queries in the Netherlands without country filter does not return postal code result. |
| OSQ-33530 | Geocode: Geocoder does find United States ZIP codes that start with '0' for queries with postal code and country code. Example: 'q=04005 US'. |
| OSP-6261, OSQ-34125 | Geocode: Geocoder does not always apply spell correction for qualified queries in Spain. |
| OSP-6350, OSQ-34413 | Autosuggest: Japan: Search for KFC provides three follow-up chain suggestions for Kentucky Fried Chicken that are difficult to distinguish for the end user. |
| OSP-5861, OSQ-34673 | Autosuggest: Japan: Improved search for 'Narita airport terminal 2'. |
Release 7.100
| Issue ID | Description |
|---|---|
| OSQ-33788 | All endpoints: Japan: Format of English label and title changed for rural areas where Chome (丁目) is not used. |
| OSP-6360, OSQ-34466 | Autocomplete: Autocomplete does not return results for query string ending with slash in house number. Example: '37 Jalan 1/'. |
| OSP-6332, OSQ-34414 | Geocode: Geocoder returns a wrong address for queries containing 'New York' twice. Example: '665 W 252nd St New York, New York'. |
Release 7.99
| Issue ID | Description |
|---|---|
| OSP-6352, OSQ-34489 | Discover: Singapore: Full Postal code is not shown in the result for Places. Only the 2 digit postal code is shown. |
| OSP-6014, OSP-6473, OSP-6396, OSQ-33100, OSQ-34804 | Browse: EV charging stations results from the /browse endpoint can be a long distance from the point of search, even located in neighboring countries, despite the availability of more local stations. |
| OSQ-33956 | Geocode: Geocoder endpoint incorrectly includes attached house number prefix from the query to the house number in the response. Example: The query 'n3816 Dodson Chapel Rd, Hermitage, TN 37076, United States' should not include the 'n' prefix in the response. |
| OSQ-33622 | Discover: Requests for 'University of Sidney' do not return the expected place. |
| OSQ-33564 | Discover: Requests for 'innout chino' return a city result instead of the expected In-N-Out Burger place in Chino, United States. |
| OSQ-30207 | Discover: Requests for '807 highway 35, Ocean, NJ' do not return the expected address: '807 RT-35, Ocean, NJ 07712-4546, United States'. |
Release 7.98
| Issue ID | Description |
|---|---|
| OSP-6088, OSP-6242, OSQ-33415 | Geocode, Discover, Autosuggest, Lookup: The position of postal codes from New York is wrong in rare cases. For example, a search for New York postal 10019 returns a position in New Jersey. |
| OSQ-34264 | Geocode, Discover, Autosuggest, Autocomplete, Lookup: For streets crossing multiple postal code areas, GS7 street-level results show the wrong postal code for the location. This is fixed. GS7 street results no longer show a postal code if the street crosses multiple postal code areas. |
| OSQ-34314 | Geocode: Hungary: Small misspells lead to the wrong match. For example, the query '2112, Veresegyház, Hétvezér út HU' results in 'Tas vezér utca, Veresegyház 2112' instead of in 'Hét vezér utca, Veresegyház 2112'. |
| OSQ-31850 | Geocode: In Spain, the number after keyword 'código' was mistakenly recognized as a house number. |
Release 7.97
| Issue ID | Description |
|---|---|
| OSQ-25699 | Autosuggest: Requests for 'Cathedral of cordoba' return nearby Old St Mary's Cathedral instead of the expected place in Argentina. |
| OSQ-24144 | Discover: Requests for German 'kreisfreie' cities (ex Regensburg) return both the expected city and the German Landkreis results, instead of only the city. |
| OSQ-33842 | Discover, Autosuggest: Requests for 'banking' return ATM places instead of regular bank places. |
| OSQ-33838 | Discover: Requests for 'residence inn ontario airport' return the hotel named 'Residence Inn Phoenix Airport' instead of the expected hotel named 'Residence Inn-Ontario Airport'. |
| OSQ-33857 | Discover, Autosuggest: Requests for 'hyundai services' do not return repair services places belonging to the chain Hyundai. |
| OSQ-33650 | Discover: Requests for the hotel named 'Fairfield Inn by Marriott-Anaheim Resort' do not return the hotel. |
| OSQ-33648 | Discover: Requests for the hotel named 'Fairfield Anaheim Resort' does not return this place ranked at the top. |
| OSQ-33646 | Discover: Requests for 'fairfield inn & suites by marriott los angeles west covina' do not return the expected hotel named 'Fairfield Inn & Suites Los Angeles West Covina'. |
| OSQ-34147 | Discover: Requests for 'Las Vegas Country Club' do not rank the expected place as the top result. |
| OSQ-34144 | Autosuggest, Discover: German requests 'Hauptbahnhof' return nearby places of category railway station instead of railway stations named likewise. |
| OSQ-33038 | Discover: Requests for 'London Zoo' do not rank the expected place as the top result. |
| OSQ-33080 | Autocomplete: Autocomplete does not return addresses whose number starts with zero. |
| OSQ-34167 | Geocode: Geocoder decreases street field score for queries in Malaysia that abbreviate the street type 'Jalan' with 'Jln'. |
| OSQ-33612 | Geocode: For 5-digit postal code query, the Geocoder prefers a postalCodePoint result in Malaysia instead of the same ZIP code (area postalCode) result in the USA. |
Release 7.96
| Issue ID | Description |
|---|---|
| OSQ-32764, OSP-5938 | All endpoints: Chinese address label and title format shown for English Taiwan address results. |
Release 7.95
| Issue ID | Description |
|---|---|
| OSQ-30839, CS0066286, OSP-5440, OSP-6047 | All endpoints: All endpoints do not return 4-digit postal codes in the Netherlands. |
| OSQ-33356, CS0079404, OSP-6064 | All endpoints: Repeated administrative names in address label and title. Most prominent examples with city and state names in Switzerland. Example: Previous title: Rue des Charmilles 11, 1203 Genève Genève, Suisse, new title: Rue des Charmilles 11, 1203 Genève, Suisse. |
| OSQ-29784, OSP-5899 | All endpoints: Japan: Unexpected format of English label and title where Chome (丁目) is shown as block. Example: Previous title and address label: 5-11 Shin-yokohama 2-chome, Kohoku-ku, Yokohama-shi, Kanagawa 222-0033, Japan, new title and address label: 2-5-11 Shin-yokohama, Kohoku-ku, Yokohama-shi, Kanagawa 222-0033, Japan. The block has moved to the beginning: From Subblock-HouseNumber Subdistrict+block, District, City, County, State PostalCode, Country to Block-Subblock-HouseNumber Subdistrict, District, City, County, State PostalCode, Country. |
| OSQ-33462 | Autocomplete: Autocomplete with item type filter types=postalCode returns unexpected results of type houseNumber in rare cases. |
| OSQ-33360, OSP-6074 | Autosuggest: 'EV station' not recognized as query term for EV charging stations. |
| OSQ-31792, OSP-5681 | Discover: 'Mountain Warehouse' results close to search center are not returned in England. Behavior improved. 'Mountain Warehouse' has been added as chain. |
Release 7.90
| Issue ID | Description |
|---|
Release 7.89
| Issue ID | Description |
|---|---|
| OSQ-29067 | Geocode: Improved city search, especially in Sweden and the Netherlands, where the Geocoder previously responded with multiple results for the same city at different positions and with different postal codes. |
| OSQ-29124 | Geocode: Improved address and area search for Dublin, Ireland, where the Geocoder previously interpreted the one or two digits long district number falsely as house number. |
| OSQ-31845, OSP-5635 | Geocode: Improved address search for ambiguous queries where the Geocoder previously responded with lower accuracy interpolated address result instead of a more accurate Point Address on the same street. |
| OSQ-32028, OSP-5758 | Geocode: Geocoding "Santa Barbara California" provides a result in Mexico in the first position. This is fixed. The Geocoder now provides "Santa Barbara, CA, United States" in the first position. |
| OSQ-31979 | Geocode: In Austria, the Geocoder matches digit "1" as county code for Innsbruck "I" instead of matching as house number. This is fixed. The Geocoder now provides the expected address result. |
| OSQ-32061, OSP-5761 | Discover: Discover Search does not recognize "Espl" as abbreviation for "Esplanade". This is fixed. |
| OSQ-23621 | Discover: Improved search for queries "Vattenfall in Charge Laddstation" (search for EV stations with Swedish term "Laddstation"). |
| OSQ-30534 | Discover: Japan: Search with keywords "SA" or "PA" does not return the expected service or parking area even though the abbreviations "SA" or "PA" are part of the Place name. This is fixed. Search now returns the expected areas. |
| OSQ-31110 | All endpoints: Japan: The administrative name suffixes are often missing from the results. These are suffixes that indicate the administrative type for city, village etc. (市, 町, 村, 郡). These suffixes are added now. |
Release 7.88
| Issue ID | Description |
|---|---|
| OSQ-31756 | Geocode: GS7 returns multiple city results where the city extends to multiple counties or states. GS7 now de-duplicates the results. It keeps the most relevant entity, the entity for which the HERE map locates the city POI. |
| OSQ-29067 | Geocode: In multiple countries, the administrative map encoding falsely causes duplicate city search results. Example countries are Sweden, Netherlands, and Germany. The Geocoder returns duplicated city results with the same name but at slightly different positions and sometimes with different postal code assignments. One example is the Germany city "Augsburg". The first result is in "county: Augsburg (City)" and the second in "county: Augsburg (Landkreis)". GS7 now removes the second result from the response. |
| OSQ-28221, OSP-4834 | Geocode: Geocoder does not match the complete country name "United States of America" when provided in a query and returns unexpected results. This is fixed. Queries with "United States of America" now return the same results as queries with "United States". Example: "375 Park Avenue S, New York, NY, United States of America" |
| OSQ-31930, OSP-5732 | Geocode: Wrong Geocoding for Ancizes-Comps 63770 - for freeform and hybrid queries, GS7 geocode prefers city matches in wrong postal codes. The result is in another zipcode Comps, Nouvelle-Aquitaine, France 33710. |
| OSQ-31791, OSP-5662 | Geocode: USA: The Geocode endpoint prefers an exact street match in the wrong state even if state code was specified in the qualified "state" field. |
Release 7.85
| Issue ID | Description |
|---|---|
| OSQ-30131, OLPSUP-17987 | Browse: Japan: Browse with chain id 76 (/browse?chains=76) returns results of chain 653. Chain Id 653 belongs to the gas station brand with the name "76". |
| OSQ-23798, OLPSUP-12700 | Geocode: Japan: Failed to geocode block or address query when block name in query is provided in Katakana. |
| OSQ-27621, OLPSUP-15995 | Discover: Japan: Discover endpoint fails to return the expected result for block address search when the query does not contain the block suffix "丁目". |
| OSP-5284 | Autosuggest: Street name and house number queries that fail to find the house number return street-level matches instead of house number fallbacks (the requested house number was corrected to match the nearest known house number). |
| OSP-5383 | Discover: Search for "Clinic" sometimes returns places that do not meet the definition of "Clinic". |
Release 7.84
| Issue ID | Description |
|---|---|
| OSQ-30712 | Autocomplete: Improved highlighting. Autocomplete highlights the complete name even if query text only contains a prefix. Example: City name "Neuenhagen bei Berlin" is completely highlighted in the city attribute and title even though the query only contains the prefix "Neuenhagen". |
| OSQ-30639 | Geocode: USA: Fixed house number recognition for numbered streets. Example: 210 174 ST, Sunny Isles Beach, FL |
| OSP-5247 | Autosuggest: Query "Thannhausen Bahnhofstraße" does not return "Bahnhofstraße, 86470 Thannhausen, Germany" |
| OSP-5039 | Autosuggest: Query "Berlin, Bahnhofstr" does not return Bahnhofstrasse in Berlin and instead prefers results of lower relevance based on proximity ranking. |
Release 7.83
| Issue ID | Description |
|---|---|
| OSP-4281 | Discover: Discover Search responds with the state New South Wales of Australia for query "Wales" instead of the expected more prominent country Wales (modeled as a state in GS7 results, same as all constituent countries of the United Kingdom) that is part of the United Kingdom. |
| OSP-5227 | Reverse Geocode: For German highways, the Reverse Geocode responds with the European name of the road (example: E45) instead of the more common and, therefore, more recognizable name for the German part of the highway (example: A9). |
| OLPSUP-17536 | Discover: Japan: 市役所駅 (Shiyakusho Station) cannot be found with the query "市役所駅". |
| OLPSUP-14479 | All endpoints: Japan: Wrong subblock/house number split for Japanese results in English language: Example: Address in Japanese: 新潟県長岡市与板町与板乙1644-10, result in English: subblock: "Otsu1", house number: "644 10", expected result: subblock: "Otsu1644", house number: "10". |
| OSP-4340 | Discover: Query for "Marienplatz" returns unexpected results such as taxi stands at Marienplatz instead of just the prominent place Marienplatz in Munich. |
| OSP-4510 | Autosuggest, Discover: Added support for "Philly" as short name for Philadelphia, PA in queries. |
| OSP-3971 | Geocode: Japan: Some queries for subblocks are failing. GS7 falsy interprets the subblock number as a house number or block number. |
| OSP-5288 | Autosuggest: Japan: Search for "gas station" at provides two category suggestions: "gas station" and "gas stations", only one of these is expected. |
| OSP-5229 | Discover: Search for "Pharmacy" in does not return expected results. |
| OSP-5335 | Autosuggest: Autosuggest provides multiple query suggestion results that are difficult for the end user to distinguish. Example: Query for "Raststaette" returns the query suggestions complete_rest_area and rest_area. |
| OSQ-29612 | Autosuggest, Discover, Browse, Lookup: In private data results (BYOD), country and state codes are returned instead of the respective names in attributes countryName and state. The codes are only expected in attributes countryCode and stateCode. |
| OSQ-29613 | Autosuggest, Discover, Browse, Lookup: In private data results (BYOD), administrative areas names and category names are not returned in the default language in cases where the request does not provide the preferred result language. |
| OSP-5192 | Geocode: Geocoder falsely parses sequences of house number, hyphen (-), and postal code as hyphenated house number. Example: In query "President Kennedylaan 59 - 6883 AC Velp" the Geocoder tries to match "59 - 6883" as house number where the house number in the query is only the "59" part. |
| OSP-4410 | Autosuggest, Discover, Browse, Lookup: Hours of operation format for Places is wrong in cases where the query does not provide a language parameter for the preferred result language. For example, for a Place in Germany, the week days are expected to be in German when the lang parameter is not set: "Mo-Sa: 07:30 - 20:00" |
Release 7.82
| Issue ID | Description |
|---|---|
| OSP-4762 | Geocode: Result for postal code search is far away from current position. Example: "q=4234&at=46.62427%2C8.03583", expected first result: "4234 Zullwil Solothurn, Switzerland", actual first result: "4234 Suldal, Norway". |
| OSQ-30257 | Autosuggest, Discover: Unexpected intersection results when query without any intersection indicator. Example: The query "Via 4 Novembre Traversetolo" returns the intersection "Via 4 Novembre & Viale Arturo Toscanini & Largo Fanfulla, 43029 Traversetolo PR, Italia" at second position. |
| OSQ-24560 | Autosuggest, Discover: Famous POI Taj Mahal isn't returned when querying with a combination of Hindi and German. |
| OSQ-30164 | Autosuggest: Upper-cased chain names in chainQuery result titles are camel-cased. Example: Autosuggest query "q=Kfc", title in chainQuery result: "title: Kfc". |
| OSP-5118 | Discover: POI "Texas Roadhouse" not found when searching by its exact name. |
| OSQ-28164 | Discover: A leading query article "the" prevents specific chain searches to succeed. |
| OSQ-25361 | Discover: The query "boa" does not return a specific Bank of America as top result. |
| OSQ-24957 | Autosuggest, Discover: The intersection query “cass ave@ stinson st, Detroit” does not return the expected intersection. |
| OSQ-22370 | Geocode, Autosuggest, Discover: "Mexico City" cannot be found. |
Release 7.81
| Issue ID | Description |
|---|---|
| OSQ-24128 | Autocomplete: Results for high precision postal code queries in the Netherlands, Canada, UK are not matching to all query tokens. |
| OSQ-29343 | All endpoints: Vietnam address label corrected. The district and county names are now added where available in the HERE map content. Example, previous result address label: "12 Đường Phạm Hữu Lầu, Quận 7, Vietnam", new result address label: "12 Đường Phạm Hữu Lầu, Phường Phú Mỹ, Quận 7, Hồ Chí Minh 72906". |
| OSQ-29094 | Discover, Autosuggest: Japan: Search for Tokyo Station (東京駅) does not return the expected train station. For Japan, prominent train stations are now ranked higher. |
| OSP-5116 | Autosuggest, Discover, Browse, Lookup: Japan label format: There is no space in the address label between the house number and place name, which make the label difficult to read. Example: "〒212-0055 神奈川県川崎市幸区南加瀬5丁目6-18Family Mart". |
Release 7.80
| Issue ID | Description |
|---|---|
| OSP-5084 | Geocode: There are unexpected results in the Netherlands for queries containing street names and postal codes. The Geocoder weighs fuzzy postal code matches too high, compared to fuzzy street name matches. |
| OSP-5056 | Geocode: In Russia, in some cases, an abbreviated street type in the query prevents house number match. |
| OSP-4960 | Geocode: The Geocoder falsely prefers street-level results over more precise and accurate Place results on the same street. |
Release 7.79
| Issue ID | Description |
|---|---|
| OSP-4806 | Autocomplete: No results for autocomplete query q=Ban and CountryCode=THA. Autocomplete now returns prominent city results starting from first letter. |
| OSQ-23918 | Autocomplete: The language field in the result for Chinese language now differentiates between simplified Chinese "zh-Hans" and traditional Chinese "zh-Hant". |
Release 7.78
| Issue ID | Description |
|---|---|
| OSP-4956 | Geocode: The Geocoder does not correctly handle the abbreviation "St" for "Saint" in district and city names. |
| OSP-4789 | All endpoints except Autocomplete: The Geocoder does not return the correct city name for postal code 2150 in Denmark. The city name Nordhavn is expected. This issue is resolved in release 7.78 for all endpoints but not yet for Autocomplete. |
| OSQ-28752 | Discover, Autosuggest: Place results return synonyms in parenthesis in Japanese, Chinese, English, and Japanese transliterations that are not meaningful to the end-user. |
| OSP-5043 | Geocode: The query for Netherlands "2283GL 485AF172" (house number, postal code) does not return the expected address "Generaal Spoorlaan 485A-F172, 2283 GL Rijswijk, Netherlands". |
| OSP-4914 | Geocode: The query "2 grand canal dublin" does not return the expected address "2 Grand Canal Quay, Dublin, County Dublin, 2, Ireland". |
| OSQ-23925 | Reverse Geocode: The Reverse Geocoder does not return a highway road result in cases where the request position is on or close to the highway. Instead, a further away address from a street unrelated to the highway is returned. |
Release 7.77
| Issue ID | Description |
|---|---|
| OSP-4869 | Geocode: For qualified queries the relevant results are sometimes returned with queryScore 0. |
| OSP-4875 | Geocode: Geocoder returns a single arbitrary result for street search where multiple relevant results exist. Example: "q=Berlin, Bahnhofstrasse" |
| OSP-4937 | Geocode: Geocoder returns a single arbitrary result for city search where multiple relevant results exist. Example: "q=Frankfort" |
| OSQ-28451 | Geocode: Japan: Missing block number in map content leads to match in wrong sub-district. Example: "q=神奈川県横浜市港北区篠原町1046-1" matches to "〒222-0021 神奈川県横浜市港北区篠原北1丁目" instead of falling back to "神奈川県横浜市港北区篠原町". Sub-district 篠原北 (Engl. Shinoharakita) instead of 篠原町 (Engl. Shinohara-cho). |
| OSQ-28452 | Geocode: Japan: Missing house number in map content leads to address match in wrong sub-district. Example: "q=京都府京都市中京区壬生花井町22ー39" matches to "〒604-8871 京都府京都市中京区壬生朱雀町22-39" instead of falling back to "〒604-8873 京都府京都市中京区壬生花井町22". Sub-district 壬生朱雀町 (Engl. Mibu Suzaku-cho) instead of 壬生花井町 (Engl. Mibu Hanai-cho). |
| OSQ-28753 | Discover, Autosuggest: Vietnam: The query "Tram sac" does not return EV charging stations. |
Release 7.76
| Issue ID | Description |
|---|---|
| OSP-4209 | Geocode: Netherland house number with <number>+<number> format affects search results negatively. Example: Query "Narcislaan 4+11, 8441 GW" is expected to match "Narcislaan 4-11, 8441 GW Heerenveen, Netherlands". |
| OSP-3604 | All endpoints: Result label format does not follow Greek conventions. In an address label, the house number must follow the street name. Example: "Παναιτωλίου 10, 121 32 Περιστέρι, Ελλάδα" |
| OSP-3670 | All endpoints: Result label format does not follow Vietnam conventions. In an address label, the house number must precede the street name. Example: "2 Đường Ngô Đức Kế" |
| OSQ-27779 | Reverse Geocode: The Reverse Geocoder now returns the name on the road sign for a street in cases where multiple names are available for the street. Example: For a street close to coordinate 32.8059,-117.2191, the result is now "2799 Garnet Ave, San Diego". Previously two results were returned: "2799 Garnet Ave, San Diego", and "2799 Garnet St, San Diego". |
| OSP-3592, OSP-4179 | Discover: Improved "Hauptbahnhof" search (main train station) in Germany. |
Release 7.75
| Issue ID | Description |
|---|---|
| OSP-2967 | Discover: Television Azteca vs. TV Azteca in Search returns different results in Mexico. |
| OSQ-26856 | All endpoints: Saudi Arabia localized address label is not correct. For Arabic language, the format needs to be: <country>, <city name> <add-on code>-<postal code>, <district>, <street name> <house number> |
| OSP-4691 | Geocode: Street without apostrophe does not match for address in Belarus. Query "vul. Kulman 9, Minsk" is expected to match "vulitsa Kul'man 9, 220000 Minsk, Belarus". |
| OSP-4715 | Geocode: Geocoder does not support English street type abbreviations in Thailand. The most common street type abbreviation is "Rd." for "Road". |
| OSP-4728 | Geocode: Geocoder does not return addresses in Moscow despite them being in the HERE map. Example: Query "Moscow, Vol'naya 28/4 k3" is expected to match "Vol'naya ulitsa 28/4 korp 3, Moscow, Russia, 105187". |
| OSP-4741 | Geocode: Geocoder does not return the biggest Moscow airport Domodedovo. Request in Russian: аэропорт Домодедово |
| OSP-4732 | Autosuggest: Search for "Home d" returns chain suggestion named "home depo". "Home depo" is not expected to be returned as a chain suggestion for the query "home d". |
Release 7.74
| Issue ID | Description |
|---|---|
| OSP-4355 | Autocomplete: Autocomplete unexpected response language. For example, Chinese transliterated name variants are returned for county names in Spain, Italian name variants are returned for city names in France. |
| OSP-4356 | Autocomplete: Autocomplete returns only two of the three expected relevant street results. |
Release 7.73
| Issue ID | Description |
|---|---|
| OSP-4493 | All endpoints: Results in India are returned in the Hindi language when the user application requests a response in Latin script language. If the requested language is not available, a fallback to hi-Latn or to English is expected. |
| OSP-2791 | Autocomplete: Unexpected result language in some cases. The response language is specified as lang=de but Autocomplete results language is not German. For example, for 'Fráncfort del Meno', the result is a mixture of French and Italian. |
| OSP-4536 | Geocode: Thailand: Searching for province return with empty response. Example with qualified geocoding: county=พิจิตร, previous result: empty response, new result: พิจิตร, ประเทศไทย (Phichit, Thailand) |
| OSQ-27009 | Geocode: Geocoder does not understand Danish character ø. Leading to low confidence results. |
| OSP-4688 | Geocode: Geocoder does not show parsed city when provided in Cyrillic in parsing (turn on with parameter show=parsing) response element. |
| OSQ-26694 | Autosuggest: Improved quality of queries for food types in districts. |
Release 7.72
| Issue ID | Description |
|---|---|
| OSP-4289 | Discover: Search for "Lowe's" only provides results when the search term includes the apostrophe. The expectation is that a search for "Lowes" without apostrophe also provides results. |
| OSP-4392 | Autocomplete: Autocomplete does not return city match for Brasilia if the complete city name is provided in the query. |
| OSQ-26829 | Autosuggest: Bad results for autosuggest queries in Norwegian with search center outside of Norway and language request parameter lang=no-NO. Fix: Autosuggest now considers the Norwegian language 'no-NO' and the Norwegian written standard Bokmål (nb-NO) as language indicator. |
Release 7.71
| Issue ID | Description |
|---|---|
| OSQ-26438 | Reverse Geocode: Reverse Geocode returns interpolated address results from outside of the specified radius (parameter in=circle:<latitude>,<longitude>;r=<radius>). |
| OSQ-26469 | Reverse Geocode: Reverse Geocode in the USA returns ZIP+4 results (resultType: postalCodePoint) instead of addresses or streets. In situations with a few postal code points nearby, these results hide address or street results. End-users will therefore not get information about which street they are on or what the closest address is. |
| OSQ-26668 | Geocode: USA: The Geocoder does not match addresses where the house number in reality and the map data includes a hyphen - common for New York addresses - but the house number in the query does not. Example: 'q=8943 Elmhurst Avenue, Flushing, NY, 11373' returns a street match 'Elmhurst Avenue, Flushing, NY, 11373', expected correct result is: '89-43 Elmhurst Ave, Elmhurst, NY 11373, United States' |
Release 7.70
| Issue ID | Description |
|---|---|
| OSQ-26379 | Discover, Autosuggest, Lookup: Opening hours with 0 minutes opening hours for a day are falsely shown as open for 24 hours from T000000 to PT24H00M. |
| OSP-4448 | Geocode: USA: The Geocoder misinterprets the postal code as house number in rare cases in the USA. Example: ' 487 Washington St Braintree, Town of, Massachusetts 02184' |
| OSP-4387 | Geocode: USA: Wrong results from Geocoder in rare cases in for queries with 'New York, New York' (example: 199 Centre St New York, New York 11231), and intersection search (example: 400 south and main street Springville, Utah). |
| OSQ-26653 | Discover, Autosuggest: Autosuggest does not recognize 'WC' as an ontology in Autosuggest and Search for queries with language setting German. |
Release 7.69
| Issue ID | Description |
|---|---|
| OSQ-22683 | Autocomplete: Some GS7 Autocomplete results are violating the rule that it shall prefer results in local language or the customer application language. |
Release 7.68
| Issue ID | Description |
|---|---|
| OSQ-24766 | Geocode: Indonesia address matching: In Indonesia, parallel streets often share the same base name and can only be differentiated by an additional number. The Geocoder falsely interpreted this number as a house number. |
| OSQ-25211 | Geocode: In countries Poland, Brazil, Italy, Mexico, the Geocoder sometimes falsely interprets postal codes in queries as house numbers. |
| OSQ-25295 | Lookup: Lookup with valid ID for postal code point returns an error message. |
| OSQ-25510 | Reverse Geocode: API Reference Guide: "scoring" and "parsing" attributes are not relevant to Reverse Geocoder responses, these are removed from the API reference. |
Release 7.67
| Issue ID | Description |
|---|---|
| OSP-4247 | Geocode: Indeterminism in rare cases in Geocoder results occurs when the service is called multiple times with the same parameter. |
| OSQ-25360 | Autosuggest: Query 'Hospital near Berlin' returns central railway station on top instead of hospitals. |
| OSP-4153 | Geocode: Ireland: District digit causing conflict with house number in Dublin. Example query: 84 LARKHILL ROAD WHITEHALL Dublin 9, previous result: 9 Larkhill Road, Dublin, County Dublin, D09 AE78, Ireland (district number 9 misinterpreted as house number, new result: 84 Larkhill Road, Dublin, County Dublin, D09 N520, Ireland |
| OSQ-24842 | Reverse Geocode: Reduce the number of Places returned by the Reverse Geocoder at the same location, providing more valuable responses for end-user orientation. |
| OSQ-25107 | Reverse Geocode: limit parameter impacts result ranking of Reverse Geocoder. Reverse Geocoder does not always return closest result when limit parameter is set to 0 or limit parameter is not specified. Fix: Reverse Geocoder always returns the closest result independent of limit parameter. |
Release 7.66
| Issue ID | Description |
|---|---|
| OSQ-23076 | Autosuggest: Suggestions are not relevant when the query contains city and street prefix (e.g.: "Paris rue de ma", depending on user's position, expected results are "Rue de Maubeuge", "Rue de Marignan"). |
| OSQ-24009 | Discover: Unexpected results for query "Berlin city centre". |
| OSQ-23188 | Discover: Query for "Oslo Stasjon" does not return the expected "Oslo S" main railway station in Oslo in the top 3 results. |
| OSQ-24779 | Geocode: Geocode does not support diacritic symbols (a glyph added to a letter, examples: à, á, ả, ã, ạ, ă, â, ê, ô, ơ, ư) in Vietnamese. |
| OSQ-24895 | Geocode: Geocode query for postal code does not return results based on user-defined lat/lon. Example: Query for postal code 80019 with at position in Chicago (42.0311877,-85.520835) returns postal code in Italy first. Expected is a result in the United States. |
| OSQ-24822 | Geocode: Potentially wrong postal code returned for interpolated addresses in the Netherlands. |
| OSQ-24840 | Geocode: Geocode fails with HTTP 500 Internal Server Error in rare cases for qualified intersection queries. |
| OSQ-24406 | All endpoints: Results for locations on Jersey and Guernsey show Jersey/Guernsey as city. Change: Show Jersey/Guernsey as country and parishes as a city instead of a district. |
Release 7.65
| Issue ID | Description |
|---|---|
| OSQ-23469 | Geocode: Geocoder in Greece returns inconsistent results when changing the case of the query or removing the diacritics. |
Release 7.64
| Issue ID | Description |
|---|---|
| OSQ-21801 | Geocode: The Geocoder returns results in Greek when the application requests English language, but English is not available in map data. Greek might not be readable for this user. Therefore the fallback is expected to be in Latin script. |
| OSQ-24179 | All endpoints: In rare cases, different endpoints return different "Ids" for the address result |
Resolved issues from previous releases:
| Issue ID | Description |
|---|---|
| OSQ-23422 | Geocode: Geocoder does not score Cyrillic ё correctly |
| OSQ-21133 | Geocode: Geocoder misinterprets not matching parts of high precision postal codes as house numbers |
| OSQ-23218 | Geocode: In Japan, Geocoder responds with place intersection result where the user expects a subdistrict result. Example query: 北海道小樽市住吉町, previous result: 北海道小樽市住吉町 (resultType: place), new result: 北海道小樽市住吉町 (resultType: subdistrict) |
| OSQ-23130 | Discover, Reverse Geocode: In Japan, redundant place intersection results for the same location. Example: discover?q=内幸町&at=35.6707286,139.7560705, previous result: 4 place intersection results "内幸町", new result: one place intersection result "内幸町" |
Updated yesterday