GeocodingStatus class

Inheritance

• Object
• EnumClass
• GeocodingStatus

Properties

hashCode → int

The hash code for this object.

no setter, inherited

name → String

final, inherited

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited

Static Properties

serializer → Serializer<GeocodingStatus>

no setter

values → BuiltSet<GeocodingStatus>

no setter

Static Methods

valueOf(String name) → GeocodingStatus

Constants

INVALID_REQUEST → const GeocodingStatus

The status field within the Geocoding response object contains the status of the request, and may contain debugging information to help you track down why geocoding is not working. The "status" field may contain the following values: - OK indicates that no errors occurred; the address was successfully parsed and at least one geocode was returned. - ZERO_RESULTS indicates that the geocode was successful but returned no results. This may occur if the geocoder was passed a non-existent address or a latlng in a remote location. - OVER_DAILY_LIMIT indicates any of the following: - The API key is missing or invalid. - Billing has not been enabled on your account. - A self-imposed usage cap has been exceeded. - The provided method of payment is no longer valid (for example, a credit card has expired). - OVER_QUERY_LIMIT indicates that you are over your quota. - REQUEST_DENIED indicates that your request was denied. - INVALID_REQUEST generally indicates that the query (address, components, or latlng) is missing. - UNKNOWN_ERROR indicates that the request could not be processed due to a server error. The request may succeed if you try again.

OK → const GeocodingStatus

The status field within the Geocoding response object contains the status of the request, and may contain debugging information to help you track down why geocoding is not working. The "status" field may contain the following values: - OK indicates that no errors occurred; the address was successfully parsed and at least one geocode was returned. - ZERO_RESULTS indicates that the geocode was successful but returned no results. This may occur if the geocoder was passed a non-existent address or a latlng in a remote location. - OVER_DAILY_LIMIT indicates any of the following: - The API key is missing or invalid. - Billing has not been enabled on your account. - A self-imposed usage cap has been exceeded. - The provided method of payment is no longer valid (for example, a credit card has expired). - OVER_QUERY_LIMIT indicates that you are over your quota. - REQUEST_DENIED indicates that your request was denied. - INVALID_REQUEST generally indicates that the query (address, components, or latlng) is missing. - UNKNOWN_ERROR indicates that the request could not be processed due to a server error. The request may succeed if you try again.

OVER_DAILY_LIMIT → const GeocodingStatus

The status field within the Geocoding response object contains the status of the request, and may contain debugging information to help you track down why geocoding is not working. The "status" field may contain the following values: - OK indicates that no errors occurred; the address was successfully parsed and at least one geocode was returned. - ZERO_RESULTS indicates that the geocode was successful but returned no results. This may occur if the geocoder was passed a non-existent address or a latlng in a remote location. - OVER_DAILY_LIMIT indicates any of the following: - The API key is missing or invalid. - Billing has not been enabled on your account. - A self-imposed usage cap has been exceeded. - The provided method of payment is no longer valid (for example, a credit card has expired). - OVER_QUERY_LIMIT indicates that you are over your quota. - REQUEST_DENIED indicates that your request was denied. - INVALID_REQUEST generally indicates that the query (address, components, or latlng) is missing. - UNKNOWN_ERROR indicates that the request could not be processed due to a server error. The request may succeed if you try again.

OVER_QUERY_LIMIT → const GeocodingStatus

The status field within the Geocoding response object contains the status of the request, and may contain debugging information to help you track down why geocoding is not working. The "status" field may contain the following values: - OK indicates that no errors occurred; the address was successfully parsed and at least one geocode was returned. - ZERO_RESULTS indicates that the geocode was successful but returned no results. This may occur if the geocoder was passed a non-existent address or a latlng in a remote location. - OVER_DAILY_LIMIT indicates any of the following: - The API key is missing or invalid. - Billing has not been enabled on your account. - A self-imposed usage cap has been exceeded. - The provided method of payment is no longer valid (for example, a credit card has expired). - OVER_QUERY_LIMIT indicates that you are over your quota. - REQUEST_DENIED indicates that your request was denied. - INVALID_REQUEST generally indicates that the query (address, components, or latlng) is missing. - UNKNOWN_ERROR indicates that the request could not be processed due to a server error. The request may succeed if you try again.

REQUEST_DENIED → const GeocodingStatus

The status field within the Geocoding response object contains the status of the request, and may contain debugging information to help you track down why geocoding is not working. The "status" field may contain the following values: - OK indicates that no errors occurred; the address was successfully parsed and at least one geocode was returned. - ZERO_RESULTS indicates that the geocode was successful but returned no results. This may occur if the geocoder was passed a non-existent address or a latlng in a remote location. - OVER_DAILY_LIMIT indicates any of the following: - The API key is missing or invalid. - Billing has not been enabled on your account. - A self-imposed usage cap has been exceeded. - The provided method of payment is no longer valid (for example, a credit card has expired). - OVER_QUERY_LIMIT indicates that you are over your quota. - REQUEST_DENIED indicates that your request was denied. - INVALID_REQUEST generally indicates that the query (address, components, or latlng) is missing. - UNKNOWN_ERROR indicates that the request could not be processed due to a server error. The request may succeed if you try again.

UNKNOWN_ERROR → const GeocodingStatus

The status field within the Geocoding response object contains the status of the request, and may contain debugging information to help you track down why geocoding is not working. The "status" field may contain the following values: - OK indicates that no errors occurred; the address was successfully parsed and at least one geocode was returned. - ZERO_RESULTS indicates that the geocode was successful but returned no results. This may occur if the geocoder was passed a non-existent address or a latlng in a remote location. - OVER_DAILY_LIMIT indicates any of the following: - The API key is missing or invalid. - Billing has not been enabled on your account. - A self-imposed usage cap has been exceeded. - The provided method of payment is no longer valid (for example, a credit card has expired). - OVER_QUERY_LIMIT indicates that you are over your quota. - REQUEST_DENIED indicates that your request was denied. - INVALID_REQUEST generally indicates that the query (address, components, or latlng) is missing. - UNKNOWN_ERROR indicates that the request could not be processed due to a server error. The request may succeed if you try again.

ZERO_RESULTS → const GeocodingStatus

The status field within the Geocoding response object contains the status of the request, and may contain debugging information to help you track down why geocoding is not working. The "status" field may contain the following values: - OK indicates that no errors occurred; the address was successfully parsed and at least one geocode was returned. - ZERO_RESULTS indicates that the geocode was successful but returned no results. This may occur if the geocoder was passed a non-existent address or a latlng in a remote location. - OVER_DAILY_LIMIT indicates any of the following: - The API key is missing or invalid. - Billing has not been enabled on your account. - A self-imposed usage cap has been exceeded. - The provided method of payment is no longer valid (for example, a credit card has expired). - OVER_QUERY_LIMIT indicates that you are over your quota. - REQUEST_DENIED indicates that your request was denied. - INVALID_REQUEST generally indicates that the query (address, components, or latlng) is missing. - UNKNOWN_ERROR indicates that the request could not be processed due to a server error. The request may succeed if you try again.