Red Hat Summitこのコンテンツは選択した言語では利用できません。
Chapter 107. Geocoder Component
Available as of Camel version 2.12
The geocoder: component is used for looking up geocodes (latitude and longitude) for a given address, or reverse lookup. The component uses the Java API for Google Geocoder library.
Maven users will need to add the following dependency to their pom.xml for this component:
107.1. URI format
geocoder:address:name[?options] geocoder:latlng:latitude,longitude[?options]
geocoder:address:name[?options]
geocoder:latlng:latitude,longitude[?options]107.2. Options
The Geocoder component has no options.
The Geocoder endpoint is configured using URI syntax:
geocoder:address:latlng
geocoder:address:latlngwith the following path and query parameters:
107.2.1. Path Parameters (2 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
| address | The geo address which should be prefixed with address: | String | |
| latlng | The geo latitude and longitude which should be prefixed with latlng: | String |
107.2.2. Query Parameters (14 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
| clientId (producer) | To use google premium with this client id | String | |
| clientKey (producer) | To use google premium with this client key | String | |
| headersOnly (producer) | Whether to only enrich the Exchange with headers, and leave the body as-is. | false | boolean |
| language (producer) | The language to use. | en | String |
| httpClientConfigurer (advanced) | Register a custom configuration strategy for new HttpClient instances created by producers or consumers such as to configure authentication mechanisms etc | HttpClientConfigurer | |
| httpConnectionManager (advanced) | To use a custom HttpConnectionManager to manage connections | HttpConnectionManager | |
| synchronous (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean |
| proxyAuthDomain (proxy) | Domain for proxy NTML authentication | String | |
| proxyAuthHost (proxy) | Optional host for proxy NTML authentication | String | |
| proxyAuthMethod (proxy) | Authentication method for proxy, either as Basic, Digest or NTLM. | String | |
| proxyAuthPassword (proxy) | Password for proxy authentication | String | |
| proxyAuthUsername (proxy) | Username for proxy authentication | String | |
| proxyHost (proxy) | The proxy host name | String | |
| proxyPort (proxy) | The proxy port number | Integer |
107.3. Exchange data format
Camel will deliver the body as a com.google.code.geocoder.model.GeocodeResponse type.
And if the address is "current" then the response is a String type with a JSON representation of the current location.
If the option headersOnly is set to true then the message body is left as-is, and only headers will be added to the Exchange.
107.4. Message Headers
| Header | Description |
|---|---|
|
|
Mandatory. Status code from the geocoder library. If status is |
|
| The formatted address |
|
| The latitude of the location. |
|
| The longitude of the location. |
|
| The latitude and longitude of the location. Separated by comma. |
|
| The city long name. |
|
| The region code. |
|
| The region name. |
|
| The country long name. |
|
| The country short name. |
Notice not all headers may be provided depending on available data and mode in use (address vs latlng).
107.5. Samples
In the example below we get the latitude and longitude for Paris, France
from("direct:start")
.to("geocoder:address:Paris, France")
from("direct:start")
.to("geocoder:address:Paris, France")
If you provide a header with the CamelGeoCoderAddress then that overrides the endpoint configuration, so to get the location of Copenhagen, Denmark we can send a message with a headers as shown:
template.sendBodyAndHeader("direct:start", "Hello", GeoCoderConstants.ADDRESS, "Copenhagen, Denmark");
template.sendBodyAndHeader("direct:start", "Hello", GeoCoderConstants.ADDRESS, "Copenhagen, Denmark");To get the address for a latitude and longitude we can do:
from("direct:start")
.to("geocoder:latlng:40.714224,-73.961452")
.log("Location ${header.CamelGeocoderAddress} is at lat/lng: ${header.CamelGeocoderLatlng} and in country ${header.CamelGeoCoderCountryShort}")
from("direct:start")
.to("geocoder:latlng:40.714224,-73.961452")
.log("Location ${header.CamelGeocoderAddress} is at lat/lng: ${header.CamelGeocoderLatlng} and in country ${header.CamelGeoCoderCountryShort}")Which will log
Location 285 Bedford Avenue, Brooklyn, NY 11211, USA is at lat/lng: 40.71412890,-73.96140740 and in country US
Location 285 Bedford Avenue, Brooklyn, NY 11211, USA is at lat/lng: 40.71412890,-73.96140740 and in country USTo get the current location you can use "current" as the address as shown:
from("direct:start")
.to("geocoder:address:current")
from("direct:start")
.to("geocoder:address:current")
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}