action neutrinoapi_geocode_reverse {
label: "Geocode Reverse"
description: "Convert a geographic coordinate (latitude and longitude) into a real world address"
provider: neutrinoapi
method: GET
path: "/geocode-reverse"
encoding: json
input: {
type: "object"
properties: {
"language-code": {
type: "string"
}
latitude: {
type: "string"
}
longitude: {
type: "string"
}
zoom: {
type: "string"
}
}
required: ["latitude", "longitude"]
additionalProperties: false
}
output: {
type: "object"
required: ["address", "address-components", "city", "country", "country-code", "country-code3", "currency-code", "found", "latitude", "location-tags", "location-type", "longitude", "postal-address", "postal-code", "region-code", "state", "timezone"]
properties: {
address: {
type: "string"
description: "The complete address using comma-separated values"
}
"address-components": {
type: "object"
description: "The components which make up the address such as road, city, state, etc"
}
city: {
type: "string"
description: "The city of the location"
}
country: {
type: "string"
description: "The country of the location"
}
"country-code": {
type: "string"
description: "The ISO 2-letter country code of the location"
}
"country-code3": {
type: "string"
description: "The ISO 3-letter country code of the location"
}
"currency-code": {
type: "string"
description: "ISO 4217 currency code associated with the country"
}
found: {
type: "boolean"
description: "True if these coordinates map to a real location"
}
latitude: {
type: "number"
format: "double"
description: "The location latitude"
}
"location-tags": {
type: "array"
description: "Array of strings containing any location tags associated with the address. Tags are additional pieces of metadata about a specific location, there are thousands of different tags. Some examples of tags: shop, office, cafe, bank, pub"
items: {
type: "string"
}
}
"location-type": {
type: "string"
description: "The detected location type ordered roughly from most to least precise, possible values are: