Document

Transcription

Document

Geocoder API
Release Notes
Version 6.2.77
Geocoder API Release Notes
► Contents
2
Contents
Legal Notices..........................................................................................................................................................3
Document Information.................................................................................................................................... 4
Chapter 1: Overview................................................................................................................................. 5
D55 Highlights................................................................................................................................................. 6
Chapter 2: Release Major Changes............................................................................................ 7
API Changes......................................................................................................................................................8
Map Data Version........................................................................................................................................... 8
Chapter 3: D55 Issues............................................................................................................................ 9
Resolved Issues............................................................................................................................................ 10
Enhancements............................................................................................................................................... 11
Known Issues................................................................................................................................................. 16
► Legal Notices
3
Legal Notices
© 2015 HERE. All rights reserved.
This material, including documentation and any related computer programs, is protected by
copyright controlled by HERE. All rights are reserved. Copying, including reproducing, storing,
adapting or translating, any or all of this material requires the prior written consent of HERE. This
material also contains confidential information, which may not be disclosed to others without the
prior written consent of HERE.
Trademark Acknowledgements
HERE and Nokia are trademarks or registered trademarks of Nokia Corporation in the United States
and other countries.
Other trade names are trademarks or registered trademarks of their owners.
Disclaimer
This content is provided "as-is" and without warranties of any kind, either express or implied,
including, but not limited to, the implied warranties of merchantability, fitness for a particular
purpose, satisfactory quality and non-infringement. Nokia does not warrant that the content is error
free and Nokia does not warrant or make any representations regarding the quality, correctness,
accuracy, or reliability of the content. You should therefore verify any information contained in the
content before acting on it.
To the furthest extent permitted by law, under no circumstances, including without limitation Nokia's
negligence, shall Nokia be liable for any damages, including, without limitation, direct, special,
indirect, punitive, consequential, exemplary and/ or incidental damages that result from the use or
application of this content, even if Nokia or an authorized representative has been advised of the
possibility of such damages.
► Document Information
Document Information
Product
Name:
Geocoder API
Version:
Version 6.2.77
Document
Name:
Id:
129a5c1-1426788617
Status:
FINAL
Date:
2015-Mar-19, 18:12 (GMT)
4
► Overview
5
Chapter
1
Overview
Topics:
•
D55 Highlights
The scope of this document is to provide the release notes for the
Geocoder API for a particular release version. It also includes the
issues resolved and issues remaining in this release.
► Overview
6
D55 Highlights
•
•
•
•
Improved map view focus: We relaxed the map view focus so that the Geocoder takes more good
candidates from outside the set map view into consideration
Northern Cyprus: We updated the map content for Northern Cyprus in the Geocoder and Reverse
Geocoder to support street search and to return Turkish names instead of Greek names for
Turkish locales
Map update: The map update to 2015 Q1 is now complete with the exception of India and Taiwan
and the China maps
Other bug fixes
► Release Major Changes
Chapter
2
Release Major Changes
Topics:
•
API Changes
This section documents major changes to the release that may
require users to change their applications and/or associated map
•
Map Data Version
data.
7
► Release Major Changes
API Changes
There are no API changes in this release.
Map Data Version
Current map data version is 2015Q1 with the following exceptions:
•
Taiwan and India remain at 2014Q4
•
Russia and Ukraine remain at 2014Q3
•
Hong Kong remains at 2014Q2
•
China, Macau remain at 2014Q3
8
► D55 Issues
9
Chapter
3
D55 Issues
Topics:
•
Resolved Issues
•
Enhancements
•
Known Issues
This section lists resolved issues and enhancements in the current
release. It also lists known issues in the current release.
► D55 Issues
10
Resolved Issues
The following table contains resolved issues. The list summarizes major resolved issues relevant for a
broad audience.
#
Description
1
Precision for Distance Marker elements in response is too high
The DistanceMarker.offset and Related.RouteDistance values in responses show too many digits
after the decimal point. This level of precision is redundant.
•
DistanceMarker.Offset: 3 digits after the decimal (example: 0.998 instead of
0.9976342184930931)
•
Related.RouteDistance: 0 digit after the decimal (example: 1615.0 instead of
1615.0630197484381)
Note that RouteDistance is essentially an integer value. The XSD specifies it as double value only for
legacy reasons.
2
Missing link side and spot information for Taiwan addresses
The Geocoder does not add link side and spot information in results for some addresses in Taiwan and
other countries.
Example:
geocode.json
?searchtext=臺灣106臺北市臺北市大安區仁愛路三段123巷11弄8號
&locationattributes=mapReference
&gen=8
&language=en-US
Result:
...
address: {
label: "No. 8, Alley 11, Lane 123, Sec 3, Ren Ai Rd., Daan District,
Taipei City, Taipei City 106, Taiwan",
...
},
mapReference: {
referenceId: "788004296",
mapId: "VDAM14403",
mapVersion: "Q4/2014",
countryId: "23525046",
countyId: "23525031",
cityId: "23525031",
districtId: "23525082"
}
...
► D55 Issues
#
11
Description
Expected:
...
address: {
label: "No. 8, Alley 11, Lane 123, Sec 3, Ren Ai Rd., Daan District,
Taipei City, Taipei City 106, Taiwan",
...
},
mapReference: {
referenceId: "788004296",
mapId: "VDAM14403",
mapVersion: "Q4/2014",
spot: 0.61,
sideOfStreet: "right",
countryId: "23525046",
countyId: "23525031",
cityId: "23525031",
districtId: "23525082"
}
...
The issue is fixed. The problem was related to parsing and matching of special symbols as part of house
numbers.
Enhancements
The following table contains enhancements.
#
Description
1
Northern Cyprus: Greek names are returned for Turkish locale
The Geocoder returns Greek names for locations in Northern Cyprus even if the client application explicitly
requests the result in Turkish language.
For example, instead of the Greek name Skylloura the client application expects the Turkish name
Yılmazköy.
Below are examples comparing D54 with D55 results. The examples show the addressDetails section of the
responses where the language codes are included. These are Reverse Geocode examples. But the Forward
Geocoder follows the same language logic.
Requesting Turkish names:
reversegeocode.json
?mode=retrieveAddresses
&prox=35.231634,33.16595,200
&locationattributes=addressDetails
&gen=8
&languages=tr-tr
Result with transliterated Greek city name:
"addressDetails": {
"countryCode": "CYP",
"country":
{
► D55 Issues
#
Description
"value": "Kibris",
"language": "tr"
},
"county":
{
"value": "Lefkosa",
"language": "tr"
},
"city":
{
"value": "Skylloura",
"language": "el-Latn"
}
}
Expected are Turkish names:
"addressDetails": {
"countryCode": "NCY",
"country":
{
"value": "Kibris Türk Yönetimi",
"language": "tr"
},
"county":
{
"value": "Lefkosa",
"language": "tr"
},
"city":
{
"value": "Yilmazköy",
"language": "tr"
}
}
Example without language specifier (default language behavior):
reversegeocode.json
?mode=retrieveAddresses
&prox=35.231634,33.16595,200
&locationattributes=addressDetails
&gen=8
Result with Greek names:
"addressDetails": {
"countryCode": "CYP",
"country":
{
"value": "Κύπρος",
"language": "el"
},
"county":
{
"value": "Λευκωσια",
"language": "el"
},
"city":
12
► D55 Issues
#
13
Description
{
"value": "Σκυλλουρα",
"language": "el"
}
}
Expected are Turkish names (same as above when Turkish was explicitly requested):
"addressDetails": {
"countryCode": "NCY",
"country":
{
"value": "Kibris Türk Yönetimi",
"language": "tr"
},
"county":
{
"value": "Lefkosa",
"language": "tr"
},
"city":
{
"value": "Yilmazköy",
"language": "tr"
}
}
2
Support for street search in Northern Cyprus
We added the Turkish map data for Northern Cyprus to the Geocoder and Reverse Geocoder. With that
the Geocoder now supports street search in Northern Cyprus and street level results are also returned by
the Reverse Geocoder. Addresses (house number precision) are not supported yet because the data is not
available.
Example:
searchtext=Dr. Fazil Küçük Bulvarı, Ortaköy
Result:
empty
Expected:
label: Dr. Fazil Küçük Bulvarı, Ortaköy, Kıbrıs Türk Yönetimi
country: NCY
county: Lefkoşa
city: Ortaköy
street: Dr. Fazil Küçük Bulvarı
3
Israel: Admin level up-shift
The Geocoder admin leveling in Israel so far mapped administrative sub-districts (known as nafots) to city
level. In reality, these are regions above city level. This led to many ambiguous results for address searches
outside of the city where the user would only expect a single result within the city. The settlements were
mapped to districts (level below city).
We changed the mapping for Israel as follows:
► D55 Issues
#
Description
Table 1: Israel Admin Hierarchy in the Geocoder
RDF FeatureType
Feature Name
Geocoder Mapping pre
Geocoder Mapping
D55
starting with D55
1111
Country
country
country
1112
Mahoz
county
state
1119
Nafa
city
county
3110
Settlement
district
city
KD
KD-Zone
Not available
district
Example:
searchtext=Bilu 9, Tel Aviv&additionaldata=NormalizeNames,true
Result: More than 4 matches. Only the 4th result is expected.
label: Bilu 9, 51322 Tel-Aviv, Israel
country: ISR
county: Tel Aviv
city: Tel-Aviv
district: Bne Brak
street: Bilu
houseNumber: 9
postalCode: 51322
country: ISR
county: Tel Aviv
city: Tel-Aviv
district: Herzliya
street: Bilu
houseNumber: 9
postalCode: 46426
country: ISR
county: Tel Aviv
city: Tel-Aviv
district: Holon
street: Bilu
houseNumber: 9
postalCode: 58334
country: ISR
county: Tel Aviv
city: Tel-Aviv
district: Tel Aviv-Yafo
street: Bilu
houseNumber: 9
postalCode: 65222
...
Expected:
label: Bilu 9, 67132 Tel Aviv-Yafo, Israel
14
► D55 Issues
#
15
Description
country: ISR
state: Tel Aviv
county: Tel-Aviv
city: Tel Aviv-Yafo
district: Lev Tel-Aviv
street: Bilu
houseNumber: 9
postalCode: 67132
Note that we request normalized names from the Geoocder (additionaldata=NormalizeNames,true) in this
example. This is for illustration purposes only to get the normalized city name Tel Aviv-Yafo. Otherwise the
result would show the matched city name Tel Aviv.
4
Reverse Geocoder does not respond with any region or country information for the northern part
Arunashal Pradesh
This area of the India state is under dispute with China. China claims the northern part of this area as a part
of the Tibet Autonomous Region. The Reverse Geocoder response is now empty for the area above the
green line in the map shown below.
5
Improved handling of map view focus
We relaxed the map view focus in the Geocoder so that it takes better candidates, from outside the set
map view, into consideration.
In general, the Geocoder prefers result candidates that are within the set map view (map view focus). But
a user should still be able to find addresses in areas that are far away from the map view he is currently
looking at. E.g. looking at the map in Chicago but trying to find an address in Berlin. If the user provides a
fairly complete and un-ambiguous query then the expected far-away result should be returned. This has
not happened in some cases and this behavior has been improved now.
► D55 Issues
#
16
Description
Example: The user looks at the map close to Wuppertal (a city in Germany, mapview over Wuppertal or
close by) and queries for an address in Berlin:
searchtext=Hardenberg Str.10 Berlin
&mapview=51.34342,6.99945;51.30448,7.11317
Result:
...
distance: 8169.7
// distance in meters from map view center
label: Hardenbergstraße 10, 42109 Wuppertal, Germany
...
Expected:
...
distance: 449523.2
label: Hardenbergstraße 10, 10623 Berlin, Germany
...
Known Issues
The following table lists issues known to be present in the current release of the Geocoder API.
#
Description
1
Taiwan Geocoding - Island Names are not able to be geocoded - Q2 2013 TWN Map improvements
Islands to be considered as part of Taiwan.
2
Taiwan - Street Fallback - Returning the Best Candidate
If an address is not in the map, then either a house number fallback or up-hierarchy street level match is
expected. But in some cases, the Geocoder returns an address in the wrong street or lane.
Example:
彰化縣彰化市介壽北路1號
House number 1 is not in the map data. The result is therefore a fallback to house number 19:
No. 19, Jie Shou N. Rd., Changhua City, Changhua County 500, Taiwan
But if a house number fallback is not accepted (parameter:
additionaldata=HouseNumberMode,Streetlevel), then the result is expected to be a street level match:
Jie Shou N. Rd., Changhua City, Changhua County 500, Taiwan
The current response is an address match in a different – though close - street (South instead of North)
and in a lane while the request did not specify a lane:
No. 1, Lane 36, Jie Shou S. Rd., Changhua City, Changhua County 500, Taiwan
3
China: Reverse Geocoder retrieveAreas response not aligned with retrieveAddresses
► D55 Issues
#
17
Description
The Reverse Geocoder retrieveAreas response is not aligned with the response from retrieveAddresses
and Forward Geocoder. City and district names are only available in Chinese, the county information is
incorrect and state is empty (should be Chinese provinces).
4
Labels for highway exits do not include the exit number
The label only contains the highway name.
Workaround: Use highway name and exit number from the Name field.
5
The navigation coordinate in the response for Hong Kong building name matches is not always correct.
It is the same as the display coordinate. Only when the query matches a house number in addition to
the building name (MatchQuality element houseNumber exists in the result) the navigation coordinate is
correct.
Example:
The queries
Shek Wu Shui Baptist Chapel, Hong Kong
and
Shek Wu Shui Baptist Chapel, 33 Fu Hing St, Hong Kong
both match to the same address. But the navigation coordinate is correct for the latter query only.

Document

Transcription

Similar documents

Document

Gabe Westmaas Rackspace @westmaas

Sze Wong | CEO | Zerion Software, Inc.

Cyprexx Enhanced

presentation slides

Practical 5: OpenWeatherMap Objective Development of Web Applications Vincent Simonet, 2014-2015

2015 IEEE PES ASIA - PACIFIC POWER AND ENERGY

YPP CHRISTMAS EVENT

Whitepages Pro Caller Identification API

APIs as a Foundation for Systems of Engagement

The Tel Aviv Brand