@azure-rest/maps-search 2.0.0-beta.2 → 2.0.0-beta.3

package/types/maps-search-rest.d.ts

@@ -1,1066 +0,0 @@
-import type { AzureKeyCredential } from '@azure/core-auth';
-import type { AzureSASCredential } from '@azure/core-auth';
-import { Client } from '@azure-rest/core-client';
-import { ClientOptions } from '@azure-rest/core-client';
-import { HttpResponse } from '@azure-rest/core-client';
-import { RawHttpHeaders } from '@azure/core-rest-pipeline';
-import { RequestParameters } from '@azure-rest/core-client';
-import { StreamableMethod } from '@azure-rest/core-client';
-import type { TokenCredential } from '@azure/core-auth';
-
-export declare interface AddressAdminDistrictsItemOutput {
-    /**
-     * The name for the corresponding adminDistrict field,
-     * For adminDistrict[0], this could be full name of state such as Washington,
-     * For adminDistrict[1], this could be the full name of the county
-     */
-    name?: string;
-    /**
-     * The short name for the corresponding adminDistrict field,
-     * For adminDistrict[0], this could be short name of state such as WA,
-     * For adminDistrict[1], this could be the short name of the county
-     */
-    shortName?: string;
-}
-
-export declare interface AddressCountryRegionOutput {
-    /** ISO of country/region */
-    ISO?: string;
-    /** name of country/region */
-    name?: string;
-}
-
-/** The address of the result */
-export declare interface AddressOutput {
-    /** AddressLine that includes Street Name and Number */
-    addressLine?: string;
-    /** locality property */
-    locality?: string;
-    /** neighborhood property */
-    neighborhood?: string;
-    /** The subdivision name in the country or region for an address. This element is typically treated as the first order administrative subdivision, but in some cases it also contains the second, third, or fourth order subdivision in a country, dependency, or region. */
-    adminDistricts?: Array<AddressAdminDistrictsItemOutput>;
-    /** Postal Code property */
-    postalCode?: string;
-    countryRegion?: AddressCountryRegionOutput;
-    /** Formatted Address property */
-    formattedAddress?: string;
-    /** The address of the result. */
-    intersection?: IntersectionOutput;
-}
-
-/**
- * `GeoJSON GeocodingFeature` object that describe the boundaries of a geographical area. Geometry of the feature is described with `GeoJSON GeometryCollection`.
- *
- * Please note, the service typically returns a GeometryCollection with Polygon or MultiPolygon sub-types.
- */
-export declare interface BoundaryOutput extends GeoJsonFeatureOutputParent, BoundaryPropertiesOutput {
-    type: "Boundary";
-}
-
-/** Properties of a Boundary object. */
-export declare interface BoundaryPropertiesOutput {
-    /** The name associated with the geographical area. */
-    name?: string;
-    /** The copyright string. */
-    copyright?: string;
-    /** A URL that lists many of the data providers for Azure Maps and their related copyright information. */
-    copyrightURL?: string;
-    /** A collection of copyright information for each geometry of the Boundary object in the same order they appear. */
-    geometriesCopyright?: Array<GeometryCopyrightOutput>;
-}
-
-/** The resource management error additional info. */
-export declare interface ErrorAdditionalInfoOutput {
-    /** The additional info type. */
-    readonly type?: string;
-    /** The additional info. */
-    readonly info?: Record<string, unknown>;
-}
-
-/** The error detail. */
-export declare interface ErrorDetailOutput {
-    /** The error code. */
-    readonly code?: string;
-    /** The error message. */
-    readonly message?: string;
-    /** The error target. */
-    readonly target?: string;
-    /** The error details. */
-    readonly details?: Array<ErrorDetailOutput>;
-    /** The error additional info. */
-    readonly additionalInfo?: Array<ErrorAdditionalInfoOutput>;
-}
-
-/** Common error response for all Azure Resource Manager APIs to return error details for failed operations. (This also follows the OData error response format.). */
-export declare interface ErrorResponseOutput {
-    /** The error object. */
-    error?: ErrorDetailOutput;
-}
-
-export declare interface FeaturesItemOutput {
-    /** The type of a feature must be Feature. */
-    type?: "Feature";
-    /** ID for feature returned */
-    id?: string;
-    properties?: FeaturesItemPropertiesOutput;
-    /** A valid `GeoJSON Point` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.2) for details. */
-    geometry: GeoJsonPointOutput;
-    /** Bounding box. Projection used - EPSG:3857. Please refer to [RFC 7946](https://datatracker.ietf.org/doc/html/rfc7946#section-5) for details. */
-    bbox?: Array<number>;
-}
-
-export declare interface FeaturesItemPropertiesOutput {
-    /**
-     * One of:
-     * * Address
-     * * RoadBlock
-     * * RoadIntersection
-     * * Neighborhood
-     * * PopulatedPlace
-     * * Postcode1
-     * * AdminDivision1
-     * * AdminDivision2
-     * * CountryRegion
-     */
-    type?: string;
-    /**
-     * The level of confidence that the geocoded location result is a match. Use this value with the match code to determine for more complete information about the match.
-     *
-     * The confidence of a geocoded location is based on many factors including the relative importance of the geocoded location and the user’s location, if specified.
-     */
-    confidence?: "High" | "Medium" | "Low";
-    /**
-     * One or more match code values that represent the geocoding level for each location in the response.
-     *
-     * For example, a geocoded location with match codes of `Good` and `Ambiguous` means that more than one geocode location was found for the location information and that the geocode service did not have search up-hierarchy to find a match.
-     *
-     * Similarly, a geocoded location with match codes of `Ambiguous` and `UpHierarchy` implies that a geocode location could not be found that matched all the provided location information, so the geocode service had to search up-hierarchy and found multiple matches at that level. An example of up an `Ambiguous` and `UpHierarchy` result is when you provide complete address information, but the geocode service cannot locate a match for the street address and instead returns information for more than one RoadBlock value.
-     *
-     * The possible values are:
-     *
-     * `Good`: The location has only one match or all returned matches are considered strong matches. For example, a query for New York returns several Good matches.
-     *
-     * `Ambiguous`: The location is one of a set of possible matches. For example, when you query for the street address 128 Main St., the response may return two locations for 128 North Main St. and 128 South Main St. because there is not enough information to determine which option to choose.
-     *
-     * `UpHierarchy`: The location represents a move up the geographic hierarchy. This occurs when a match for the location request was not found, so a less precise result is returned. For example, if a match for the requested address cannot be found, then a match code of `UpHierarchy` with a RoadBlock entity type may be returned.
-     */
-    matchCodes?: Array<"Good" | "Ambiguous" | "UpHierarchy">;
-    /** The address of the result */
-    address?: AddressOutput;
-    /** A collection of geocode points that differ in how they were calculated and their suggested use. */
-    geocodePoints?: Array<GeocodePointsItemOutput>;
-}
-
-export declare interface GeocodePointsItemOutput {
-    /** A valid `GeoJSON Point` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.2) for details. */
-    geometry?: GeoJsonPointOutput;
-    /** The method that was used to compute the geocode point. */
-    calculationMethod?: "Interpolation" | "InterpolationOffset" | "Parcel" | "Rooftop";
-    /**
-     * The best use for the geocode point.
-     * Each geocode point is defined as a `Route` point, a `Display` point or both.
-     * Use `Route` points if you are creating a route to the location. Use `Display` points if you are showing the location on a map. For example, if the location is a park, a `Route` point may specify an entrance to the park where you can enter with a car, and a `Display` point may be a point that specifies the center of the park.
-     */
-    usageTypes?: Array<"Display" | "Route">;
-}
-
-/** The list of address geocoding queries/requests to process. The list can contain a max of 100 queries and must contain at least 1 query. */
-export declare interface GeocodingBatchRequestBody {
-    /** The list of queries to process. */
-    batchItems?: Array<GeocodingBatchRequestItem>;
-}
-
-/** Batch Query object */
-export declare interface GeocodingBatchRequestItem {
-    /** id of the request which would show in corresponding batchItem */
-    optionalId?: string;
-    /** Maximum number of responses that will be returned. Default: 5, minimum: 1 and maximum: 20. */
-    top?: number;
-    /** A string that contains information about a location, such as an address or landmark name. */
-    query?: string;
-    /**
-     * The official street line of an address relative to the area, as specified by the locality, or postalCode, properties. Typical use of this element would be to provide a street address or any official address.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    addressLine?: string;
-    /**
-     * Signal for the geocoding result to an [ISO 3166-1 Alpha-2 region/country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) that is specified e.g. FR./
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    countryRegion?: string;
-    /**
-     * A rectangular area on the earth defined as a bounding box object. The sides of the rectangles are defined by longitude and latitude values. For more information, see Location and Area Types. When you specify this parameter, the geographical area is taken into account when computing the results of a location query.
-     *
-     * Example: [lon1, lat1, lon2, lat2]
-     */
-    bbox?: Array<number>;
-    /** A string that specifies an [ISO 3166-1 Alpha-2 region/country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2). This will alter Geopolitical disputed borders and labels to align with the specified user region. */
-    view?: string;
-    /** A point on the earth specified as a longitude and latitude. When you specify this parameter, the user’s location is taken into account and the results returned may be more relevant to the user. Example: [lon, lat] */
-    coordinates?: Array<number>;
-    /**
-     * The country subdivision portion of an address, such as WA.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    adminDistrict?: string;
-    /**
-     * The county for the structured address, such as King.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    adminDistrict2?: string;
-    /**
-     * The named area for the structured address.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    adminDistrict3?: string;
-    /**
-     * The locality portion of an address, such as Seattle.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    locality?: string;
-    /**
-     * The postal code portion of an address.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    postalCode?: string;
-}
-
-export declare interface GeocodingBatchResponseItemOutput {
-    /** id of the batchItem which would be the same as the id in the request */
-    optionalId?: string;
-    /** The type of a FeatureCollection object must be FeatureCollection. */
-    type?: "FeatureCollection";
-    features?: Array<FeaturesItemOutput>;
-    /** The is the link to the next page of the features returned. If it's the last page, no this field. */
-    nextLink?: string;
-    /** The error detail. */
-    error?: ErrorDetailOutput;
-}
-
-/** This object is returned from a successful Geocoding Batch service call. */
-export declare interface GeocodingBatchResponseOutput {
-    /** Summary for the batch request */
-    summary?: GeocodingBatchResponseSummaryOutput;
-    /** Array containing the batch results. */
-    batchItems?: Array<GeocodingBatchResponseItemOutput>;
-    /** The is the link to the next page of the features returned. If it's the last page, no this field. */
-    nextLink?: string;
-}
-
-/** Summary for the batch request */
-export declare interface GeocodingBatchResponseSummaryOutput {
-    /** Number of successful requests in the batch */
-    successfulRequests?: number;
-    /** Total number of requests in the batch */
-    totalRequests?: number;
-}
-
-/** This object is returned from a successful Geocoding call */
-export declare interface GeocodingResponseOutput {
-    /** The type of a FeatureCollection object must be FeatureCollection. */
-    type?: "FeatureCollection";
-    features?: Array<FeaturesItemOutput>;
-    /** The is the link to the next page of the features returned. If it's the last page, no this field. */
-    nextLink?: string;
-}
-
-export declare interface GeoJsonFeatureCollectionDataOutput {
-    /** Contains a list of valid `GeoJSON Feature` objects. */
-    features: Array<GeoJsonFeatureOutput>;
-}
-
-/** A valid `GeoJSON FeatureCollection` object type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.3) for details. */
-export declare interface GeoJsonFeatureCollectionOutput extends GeoJsonObjectOutputParent, GeoJsonFeatureCollectionDataOutput {
-    type: "FeatureCollection";
-}
-
-export declare interface GeoJsonFeatureDataOutput {
-    /** A valid `GeoJSON` geometry object. The type must be one of the seven valid GeoJSON geometry types - Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon and GeometryCollection. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1) for details. */
-    geometry: GeoJsonGeometryOutput;
-    /** Properties can contain any additional metadata about the `Feature`. Value can be any JSON object or a JSON null value */
-    properties?: Record<string, unknown>;
-    /** Identifier for the feature. */
-    id?: string;
-    /** The type of the feature. The value depends on the data model the current feature is part of. Some data models may have an empty value. */
-    featureType?: string;
-}
-
-/** A valid `GeoJSON Feature` object type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.2) for details. */
-export declare type GeoJsonFeatureOutput = GeoJsonFeatureOutputParent | BoundaryOutput;
-
-/** A valid `GeoJSON Feature` object type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.2) for details. */
-export declare interface GeoJsonFeatureOutputParent extends GeoJsonObjectOutputParent, GeoJsonFeatureDataOutput {
-    type: "Feature" | "Boundary";
-}
-
-export declare interface GeoJsonGeometryCollectionDataOutput {
-    /** Contains a list of valid `GeoJSON` geometry objects. **Note** that coordinates in GeoJSON are in x, y order (longitude, latitude). */
-    geometries: Array<GeoJsonGeometryOutput>;
-}
-
-/** A valid `GeoJSON GeometryCollection` object type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.8) for details. */
-export declare interface GeoJsonGeometryCollectionOutput extends GeoJsonGeometryOutputParent, GeoJsonGeometryCollectionDataOutput {
-    type: "GeometryCollection";
-}
-
-/** A valid `GeoJSON` geometry object. The type must be one of the seven valid GeoJSON geometry types - Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon and GeometryCollection. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1) for details. */
-export declare type GeoJsonGeometryOutput = GeoJsonGeometryOutputParent | GeoJsonPointOutput | GeoJsonMultiPointOutput | GeoJsonLineStringOutput | GeoJsonMultiLineStringOutput | GeoJsonPolygonOutput | GeoJsonMultiPolygonOutput | GeoJsonGeometryCollectionOutput;
-
-/** A valid `GeoJSON` geometry object. The type must be one of the seven valid GeoJSON geometry types - Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon and GeometryCollection. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1) for details. */
-export declare interface GeoJsonGeometryOutputParent extends GeoJsonObjectOutputParent {
-    type: "GeoJsonGeometry" | "Point" | "MultiPoint" | "LineString" | "MultiLineString" | "Polygon" | "MultiPolygon" | "GeometryCollection";
-}
-
-export declare interface GeoJsonLineStringDataOutput {
-    /** Coordinates for the `GeoJson LineString` geometry. */
-    coordinates: Array<Array<number>>;
-}
-
-/** A valid `GeoJSON LineString` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.4) for details. */
-export declare interface GeoJsonLineStringOutput extends GeoJsonGeometryOutputParent, GeoJsonLineStringDataOutput {
-    type: "LineString";
-}
-
-export declare interface GeoJsonMultiLineStringDataOutput {
-    /** Coordinates for the `GeoJson MultiLineString` geometry. */
-    coordinates: Array<Array<Array<number>>>;
-}
-
-/** A valid `GeoJSON MultiLineString` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.5) for details. */
-export declare interface GeoJsonMultiLineStringOutput extends GeoJsonGeometryOutputParent, GeoJsonMultiLineStringDataOutput {
-    type: "MultiLineString";
-}
-
-/** Data contained by a `GeoJson MultiPoint`. */
-export declare interface GeoJsonMultiPointDataOutput {
-    /** Coordinates for the `GeoJson MultiPoint` geometry. */
-    coordinates: Array<Array<number>>;
-}
-
-/** A valid `GeoJSON MultiPoint` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.3) for details. */
-export declare interface GeoJsonMultiPointOutput extends GeoJsonGeometryOutputParent, GeoJsonMultiPointDataOutput {
-    type: "MultiPoint";
-}
-
-export declare interface GeoJsonMultiPolygonDataOutput {
-    /** Contains a list of valid `GeoJSON Polygon` objects. **Note** that coordinates in GeoJSON are in x, y order (longitude, latitude). */
-    coordinates: Array<Array<Array<Array<number>>>>;
-}
-
-/** A valid `GeoJSON MultiPolygon` object type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.7) for details. */
-export declare interface GeoJsonMultiPolygonOutput extends GeoJsonGeometryOutputParent, GeoJsonMultiPolygonDataOutput {
-    type: "MultiPolygon";
-}
-
-/** A valid `GeoJSON` object. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3) for details. */
-export declare type GeoJsonObjectOutput = GeoJsonGeometryOutput | GeoJsonPointOutput | GeoJsonFeatureOutput | BoundaryOutput | GeoJsonMultiPointOutput | GeoJsonLineStringOutput | GeoJsonMultiLineStringOutput | GeoJsonPolygonOutput | GeoJsonMultiPolygonOutput | GeoJsonGeometryCollectionOutput | GeoJsonFeatureCollectionOutput;
-
-/** A valid `GeoJSON` object. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3) for details. */
-export declare interface GeoJsonObjectOutputParent {
-    /** Bounding box. Projection used - EPSG:3857. Please refer to [RFC 7946](https://datatracker.ietf.org/doc/html/rfc7946#section-5) for details. */
-    bbox?: Array<number>;
-    type: "GeoJsonObject" | "GeoJsonGeometry" | "Point" | "Feature" | "Boundary" | "MultiPoint" | "LineString" | "MultiLineString" | "Polygon" | "MultiPolygon" | "GeometryCollection" | "FeatureCollection";
-}
-
-/** Data contained by a `GeoJson Point`. */
-export declare interface GeoJsonPointDataOutput {
-    /** A `Position` is an array of numbers with two or more elements. The first two elements are _longitude_ and _latitude_, precisely in that order. _Altitude/Elevation_ is an optional third element. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.1) for details. */
-    coordinates: Array<number>;
-}
-
-/** A valid `GeoJSON Point` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.2) for details. */
-export declare interface GeoJsonPointOutput extends GeoJsonGeometryOutputParent, GeoJsonPointDataOutput {
-    type: "Point";
-}
-
-export declare interface GeoJsonPolygonDataOutput {
-    /** Coordinates for the `GeoJson Polygon` geometry type. */
-    coordinates: Array<Array<Array<number>>>;
-}
-
-/** A valid `GeoJSON Polygon` geometry type. Please refer to [RFC 7946](https://tools.ietf.org/html/rfc7946#section-3.1.6) for details. */
-export declare interface GeoJsonPolygonOutput extends GeoJsonGeometryOutputParent, GeoJsonPolygonDataOutput {
-    type: "Polygon";
-}
-
-/** Copyright information of a geometry of a Boundary object. */
-export declare interface GeometryCopyrightOutput {
-    /** The name of the data provider */
-    sourceName?: string;
-    /** The copyright string for the data provider */
-    copyright?: string;
-}
-
-export declare interface GetGeocoding {
-    /**
-     *
-     * The `Get Geocoding` API is an HTTP `GET` request that returns the longitude and latitude coordinates of the location being searched.
-     *
-     * In many cases, the complete search service might be too much, for instance if you are only interested in traditional geocoding. Search can also be accessed for address look up exclusively. The geocoding is performed by hitting the geocoding endpoint with just the address or partial address in question. The geocoding search index will be queried for everything above the street level data. No Point of Interest (POIs) will be returned. Note that the geocoder is very tolerant of typos and incomplete addresses. It will also handle everything from exact street addresses or street or intersections as well as higher level geographies such as city centers, counties and states. The response also returns detailed address properties such as street, postal code, municipality, and country/region information.
-     */
-    get(options?: SearchGetGeocodingParameters): StreamableMethod<SearchGetGeocoding200Response | SearchGetGeocodingDefaultResponse>;
-}
-
-export declare interface GetGeocodingBatch {
-    /**
-     *
-     * The `Get Geocoding Batch` API is an HTTP `POST` request that sends batches of up to **100** queries to the [Geocoding](/rest/api/maps/search/get-geocoding) API in a single request.
-     *
-     * ### Submit Synchronous Batch Request
-     * The Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API.
-     * ```
-     * POST https://atlas.microsoft.com/geocode:batch?api-version=2023-06-01
-     * ```
-     * ### POST Body for Batch Request
-     * To send the _geocoding_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 2 _geocoding_ queries:
-     *
-     *
-     * ```
-     * {
-     *   "batchItems": [
-     *     {
-     *       "addressLine": "One, Microsoft Way, Redmond, WA 98052",
-     *       "top": 2
-     *     },
-     *     {
-     *       "addressLine": "Pike Pl",
-     *       "adminDistrict": "WA",
-     *       "locality": "Seattle",
-     *       "top": 3
-     *     }
-     *   ]
-     * }
-     * ```
-     *
-     * A _geocoding_ batchItem object can accept any of the supported _geocoding_ [URI parameters](/rest/api/maps/search/get-geocoding#uri-parameters).
-     *
-     *
-     * The batch should contain at least **1** query.
-     *
-     *
-     * ### Batch Response Model
-     * The batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests` i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item is of one of the following types:
-     *
-     *   - [`GeocodingResponse`](/rest/api/maps/search/get-geocoding#geocodingresponse) - If the query completed successfully.
-     *
-     *   - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.
-     *
-     *
-     *
-     */
-    post(options: SearchGetGeocodingBatchParameters): StreamableMethod<SearchGetGeocodingBatch200Response | SearchGetGeocodingBatchDefaultResponse>;
-}
-
-export declare interface GetPolygon {
-    /**
-     *
-     * The `Get Polygon` API is an HTTP `GET` request that supplies polygon data of a geographical area outline such as a city or a country region.
-     */
-    get(options: SearchGetPolygonParameters): StreamableMethod<SearchGetPolygon200Response | SearchGetPolygonDefaultResponse>;
-}
-
-export declare interface GetReverseGeocoding {
-    /**
-     *
-     * The `Get Reverse Geocoding` API is an HTTP `GET` request used to translate a coordinate (example: 37.786505, -122.3862) into a human understandable street address. Useful in tracking applications where you receive a GPS feed from the device or asset and wish to know the address associated with the coordinates. This endpoint will return address information for a given coordinate.
-     */
-    get(options: SearchGetReverseGeocodingParameters): StreamableMethod<SearchGetReverseGeocoding200Response | SearchGetReverseGeocodingDefaultResponse>;
-}
-
-export declare interface GetReverseGeocodingBatch {
-    /**
-     *
-     * The `Get Reverse Geocoding Batch` API is an HTTP `POST` request that sends batches of up to **100** queries to [Reverse Geocoding](/rest/api/maps/search/get-reverse-geocoding) API using a single request.
-     *
-     * ### Submit Synchronous Batch Request
-     * The Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API.
-     * ```
-     * POST https://atlas.microsoft.com/reverseGeocode:batch?api-version=2023-06-01
-     * ```
-     * ### POST Body for Batch Request
-     * To send the _reverse geocoding_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 2 _reverse geocoding_ queries:
-     *
-     *
-     * ```
-     * {
-     *   "batchItems": [
-     *     {
-     *       "coordinates": [-122.128275, 47.639429],
-     *       "resultTypes": ["Address", "PopulatedPlace"]
-     *     },
-     *     {
-     *       "coordinates": [-122.341979399674, 47.6095253501216]
-     *     }
-     *   ]
-     * }
-     * ```
-     *
-     * A _reverse geocoding_ batchItem object can accept any of the supported _reverse geocoding_ [URI parameters](/rest/api/maps/search/get-reverse-geocoding#uri-parameters).
-     *
-     *
-     * The batch should contain at least **1** query.
-     *
-     *
-     * ### Batch Response Model
-     * The batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests` i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item is of one of the following types:
-     *
-     *   - [`GeocodingResponse`](/rest/api/maps/search/get-reverse-geocoding#geocodingresponse) - If the query completed successfully.
-     *
-     *   - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.
-     *
-     *
-     *
-     */
-    post(options: SearchGetReverseGeocodingBatchParameters): StreamableMethod<SearchGetReverseGeocodingBatch200Response | SearchGetReverseGeocodingBatchDefaultResponse>;
-}
-
-/** The address of the result. */
-export declare interface IntersectionOutput {
-    /** Primary street for the location. */
-    baseStreet?: string;
-    /** The first intersecting street. */
-    secondaryStreet1?: string;
-    /** If any, the second intersecting street. */
-    secondaryStreet2?: string;
-    /** Type of intersection. */
-    intersectionType?: string;
-    /** Complete name of the intersection. */
-    displayName?: string;
-}
-
-export declare function isUnexpected(response: SearchGetGeocoding200Response | SearchGetGeocodingDefaultResponse): response is SearchGetGeocodingDefaultResponse;
-
-export declare function isUnexpected(response: SearchGetGeocodingBatch200Response | SearchGetGeocodingBatchDefaultResponse): response is SearchGetGeocodingBatchDefaultResponse;
-
-export declare function isUnexpected(response: SearchGetPolygon200Response | SearchGetPolygonDefaultResponse): response is SearchGetPolygonDefaultResponse;
-
-export declare function isUnexpected(response: SearchGetReverseGeocoding200Response | SearchGetReverseGeocodingDefaultResponse): response is SearchGetReverseGeocodingDefaultResponse;
-
-export declare function isUnexpected(response: SearchGetReverseGeocodingBatch200Response | SearchGetReverseGeocodingBatchDefaultResponse): response is SearchGetReverseGeocodingBatchDefaultResponse;
-
-/**
- * Creates an instance of MapsSearchClient from a subscription key.
- *
- * @example
- * ```ts
- * import MapsSearch from "@azure-rest/maps-search";
- * import { AzureKeyCredential } from "@azure/core-auth";
- *
- * const credential = new AzureKeyCredential("<subscription-key>");
- * const client = MapsSearch(credential);
- *```
- *
- * @param credential - An AzureKeyCredential instance used to authenticate requests to the service
- * @param options - Options used to configure the Search Client
- */
-declare function MapsSearch(credential: AzureKeyCredential, options?: ClientOptions): MapsSearchClient;
-
-/**
- * Creates an instance of MapsSearch from an Azure Identity `TokenCredential`.
- *
- * @example
- * ```ts
- * import MapsSearch from "@azure-rest/maps-search";
- * import { DefaultAzureCredential } from "@azure/identity";
- *
- * const credential = new DefaultAzureCredential();
- * const client = MapsSearch(credential, "<maps-account-client-id>");
- *```
- *
- * @param credential - An TokenCredential instance used to authenticate requests to the service
- * @param mapsAccountClientId - The Azure Maps client id of a specific map resource
- * @param options - Options used to configure the Search Client
- */
-declare function MapsSearch(credential: TokenCredential, mapsAccountClientId: string, options?: ClientOptions): MapsSearchClient;
-
-/**
- * Creates an instance of MapsSearch from an Azure Identity `AzureSASCredential`.
- *
- * @example
- * ```ts
- * import MapsSearch from "@azure-rest/maps-search";
- * import { AzureSASCredential } from "@azure/core-auth";
- *
- * const credential = new AzureSASCredential("<SAS Token>");
- * const client = MapsSearch(credential);
- * ```
- *
- * @param credential - An AzureSASCredential instance used to authenticate requests to the service
- * @param options - Options used to configure the Search Client
- */
-declare function MapsSearch(credential: AzureSASCredential, options?: ClientOptions): MapsSearchClient;
-export default MapsSearch;
-
-export declare type MapsSearchClient = Client & {
-    path: Routes;
-};
-
-/** The optional parameters for the client */
-export declare interface MapsSearchClientOptions extends ClientOptions {
-    /** The api version option of the client */
-    apiVersion?: string;
-}
-
-/** The list of reverse geocoding queries/requests to process. The list can contain a max of 100 queries and must contain at least 1 query. */
-export declare interface ReverseGeocodingBatchRequestBody {
-    /** The list of queries to process. */
-    batchItems?: Array<ReverseGeocodingBatchRequestItem>;
-}
-
-/** Batch Query object */
-export declare interface ReverseGeocodingBatchRequestItem {
-    /** id of the request which would show in corresponding batchItem */
-    optionalId?: string;
-    /** The coordinates of the location that you want to reverse geocode. Example: [lon,lat] */
-    coordinates?: Array<number>;
-    /**
-     * Specify entity types that you want in the response. Only the types you specify will be returned. If the point cannot be mapped to the entity types you specify, no location information is returned in the response.
-     * Default value is all possible entities.
-     * A comma separated list of entity types selected from the following options.
-     *
-     * - Address
-     * - Neighborhood
-     * - PopulatedPlace
-     * - Postcode1
-     * - AdminDivision1
-     * - AdminDivision2
-     * - CountryRegion
-     *
-     * These entity types are ordered from the most specific entity to the least specific entity. When entities of more than one entity type are found, only the most specific entity is returned. For example, if you specify Address and AdminDistrict1 as entity types and entities were found for both types, only the Address entity information is returned in the response.
-     */
-    resultTypes?: Array<"Address" | "Neighborhood" | "PopulatedPlace" | "Postcode1" | "AdminDivision1" | "AdminDivision2" | "CountryRegion">;
-    /** A string that specifies an [ISO 3166-1 Alpha-2 region/country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2). This will alter Geopolitical disputed borders and labels to align with the specified user region. */
-    view?: string;
-}
-
-export declare interface Routes {
-    /** Resource for '/geocode' has methods for the following verbs: get */
-    (path: "/geocode"): GetGeocoding;
-    /** Resource for '/geocode:batch' has methods for the following verbs: post */
-    (path: "/geocode:batch"): GetGeocodingBatch;
-    /** Resource for '/search/polygon' has methods for the following verbs: get */
-    (path: "/search/polygon"): GetPolygon;
-    /** Resource for '/reverseGeocode' has methods for the following verbs: get */
-    (path: "/reverseGeocode"): GetReverseGeocoding;
-    /** Resource for '/reverseGeocode:batch' has methods for the following verbs: post */
-    (path: "/reverseGeocode:batch"): GetReverseGeocodingBatch;
-}
-
-export declare interface SearchGetGeocoding200Headers {
-    /** request id. */
-    "x-ms-request-id"?: string;
-}
-
-/**
- *
- * The `Get Geocoding` API is an HTTP `GET` request that returns the longitude and latitude coordinates of the location being searched.
- *
- * In many cases, the complete search service might be too much, for instance if you are only interested in traditional geocoding. Search can also be accessed for address look up exclusively. The geocoding is performed by hitting the geocoding endpoint with just the address or partial address in question. The geocoding search index will be queried for everything above the street level data. No Point of Interest (POIs) will be returned. Note that the geocoder is very tolerant of typos and incomplete addresses. It will also handle everything from exact street addresses or street or intersections as well as higher level geographies such as city centers, counties and states. The response also returns detailed address properties such as street, postal code, municipality, and country/region information.
- */
-export declare interface SearchGetGeocoding200Response extends HttpResponse {
-    status: "200";
-    body: GeocodingResponseOutput;
-    headers: RawHttpHeaders & SearchGetGeocoding200Headers;
-}
-
-/**
- *
- * The `Get Geocoding Batch` API is an HTTP `POST` request that sends batches of up to **100** queries to the [Geocoding](/rest/api/maps/search/get-geocoding) API in a single request.
- *
- * ### Submit Synchronous Batch Request
- * The Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API.
- * ```
- * POST https://atlas.microsoft.com/geocode:batch?api-version=2023-06-01
- * ```
- * ### POST Body for Batch Request
- * To send the _geocoding_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 2 _geocoding_ queries:
- *
- *
- * ```
- * {
- *   "batchItems": [
- *     {
- *       "addressLine": "One, Microsoft Way, Redmond, WA 98052",
- *       "top": 2
- *     },
- *     {
- *       "addressLine": "Pike Pl",
- *       "adminDistrict": "WA",
- *       "locality": "Seattle",
- *       "top": 3
- *     }
- *   ]
- * }
- * ```
- *
- * A _geocoding_ batchItem object can accept any of the supported _geocoding_ [URI parameters](/rest/api/maps/search/get-geocoding#uri-parameters).
- *
- *
- * The batch should contain at least **1** query.
- *
- *
- * ### Batch Response Model
- * The batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests` i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item is of one of the following types:
- *
- *   - [`GeocodingResponse`](/rest/api/maps/search/get-geocoding#geocodingresponse) - If the query completed successfully.
- *
- *   - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.
- *
- *
- *
- */
-export declare interface SearchGetGeocodingBatch200Response extends HttpResponse {
-    status: "200";
-    body: GeocodingBatchResponseOutput;
-}
-
-export declare interface SearchGetGeocodingBatchBodyParam {
-    /** The list of address geocoding queries/requests to process. The list can contain a max of 100 queries and must contain at least 1 query. */
-    body: GeocodingBatchRequestBody;
-}
-
-/**
- *
- * The `Get Geocoding Batch` API is an HTTP `POST` request that sends batches of up to **100** queries to the [Geocoding](/rest/api/maps/search/get-geocoding) API in a single request.
- *
- * ### Submit Synchronous Batch Request
- * The Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API.
- * ```
- * POST https://atlas.microsoft.com/geocode:batch?api-version=2023-06-01
- * ```
- * ### POST Body for Batch Request
- * To send the _geocoding_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 2 _geocoding_ queries:
- *
- *
- * ```
- * {
- *   "batchItems": [
- *     {
- *       "addressLine": "One, Microsoft Way, Redmond, WA 98052",
- *       "top": 2
- *     },
- *     {
- *       "addressLine": "Pike Pl",
- *       "adminDistrict": "WA",
- *       "locality": "Seattle",
- *       "top": 3
- *     }
- *   ]
- * }
- * ```
- *
- * A _geocoding_ batchItem object can accept any of the supported _geocoding_ [URI parameters](/rest/api/maps/search/get-geocoding#uri-parameters).
- *
- *
- * The batch should contain at least **1** query.
- *
- *
- * ### Batch Response Model
- * The batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests` i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item is of one of the following types:
- *
- *   - [`GeocodingResponse`](/rest/api/maps/search/get-geocoding#geocodingresponse) - If the query completed successfully.
- *
- *   - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.
- *
- *
- *
- */
-export declare interface SearchGetGeocodingBatchDefaultResponse extends HttpResponse {
-    status: string;
-    body: ErrorResponseOutput;
-}
-
-export declare interface SearchGetGeocodingBatchMediaTypesParam {
-    /** Request content type */
-    contentType?: "application/json";
-}
-
-export declare type SearchGetGeocodingBatchParameters = SearchGetGeocodingBatchMediaTypesParam & SearchGetGeocodingBatchBodyParam & RequestParameters;
-
-/**
- *
- * The `Get Geocoding` API is an HTTP `GET` request that returns the longitude and latitude coordinates of the location being searched.
- *
- * In many cases, the complete search service might be too much, for instance if you are only interested in traditional geocoding. Search can also be accessed for address look up exclusively. The geocoding is performed by hitting the geocoding endpoint with just the address or partial address in question. The geocoding search index will be queried for everything above the street level data. No Point of Interest (POIs) will be returned. Note that the geocoder is very tolerant of typos and incomplete addresses. It will also handle everything from exact street addresses or street or intersections as well as higher level geographies such as city centers, counties and states. The response also returns detailed address properties such as street, postal code, municipality, and country/region information.
- */
-export declare interface SearchGetGeocodingDefaultResponse extends HttpResponse {
-    status: string;
-    body: ErrorResponseOutput;
-}
-
-export declare type SearchGetGeocodingParameters = SearchGetGeocodingQueryParam & RequestParameters;
-
-export declare interface SearchGetGeocodingQueryParam {
-    queryParameters?: SearchGetGeocodingQueryParamProperties;
-}
-
-export declare interface SearchGetGeocodingQueryParamProperties {
-    /** Maximum number of responses that will be returned. Default: 5, minimum: 1 and maximum: 20. */
-    top?: number;
-    /** A string that contains information about a location, such as an address or landmark name. */
-    query?: string;
-    /**
-     * The official street line of an address relative to the area, as specified by the locality, or postalCode, properties. Typical use of this element would be to provide a street address or any official address.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    addressLine?: string;
-    /**
-     * Signal for the geocoding result to an [ISO 3166-1 Alpha-2 region/country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) that is specified e.g. FR./
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    countryRegion?: string;
-    /**
-     * A rectangular area on the earth defined as a bounding box object. The sides of the rectangles are defined by longitude and latitude values. When you specify this parameter, the geographical area is taken into account when computing the results of a location query.
-     *
-     * Example: lon1,lat1,lon2,lat2
-     */
-    bbox?: Array<number>;
-    /**
-     * A string that represents an [ISO 3166-1 Alpha-2 region/country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2). This will alter Geopolitical disputed borders and labels to align with the specified user region. By default, the View parameter is set to “Auto” even if you haven’t defined it in the request.
-     *
-     * Please refer to [Supported Views](https://aka.ms/AzureMapsLocalizationViews) for details and to see the available Views.
-     */
-    view?: string;
-    /** A point on the earth specified as a longitude and latitude. When you specify this parameter, the user’s location is taken into account and the results returned may be more relevant to the user. Example: &coordinates=lon,lat */
-    coordinates?: Array<number>;
-    /**
-     * The country subdivision portion of an address, such as WA.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    adminDistrict?: string;
-    /**
-     * The county for the structured address, such as King.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    adminDistrict2?: string;
-    /**
-     * The named area for the structured address.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    adminDistrict3?: string;
-    /**
-     * The locality portion of an address, such as Seattle.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    locality?: string;
-    /**
-     * The postal code portion of an address.
-     *
-     * **If query is given, should not use this parameter.**
-     */
-    postalCode?: string;
-}
-
-/**
- *
- * The `Get Polygon` API is an HTTP `GET` request that supplies polygon data of a geographical area outline such as a city or a country region.
- */
-export declare interface SearchGetPolygon200Response extends HttpResponse {
-    status: "200";
-    body: BoundaryOutput;
-}
-
-/**
- *
- * The `Get Polygon` API is an HTTP `GET` request that supplies polygon data of a geographical area outline such as a city or a country region.
- */
-export declare interface SearchGetPolygonDefaultResponse extends HttpResponse {
-    status: string;
-    body: ErrorResponseOutput;
-}
-
-export declare type SearchGetPolygonParameters = SearchGetPolygonQueryParam & RequestParameters;
-
-export declare interface SearchGetPolygonQueryParam {
-    queryParameters: SearchGetPolygonQueryParamProperties;
-}
-
-export declare interface SearchGetPolygonQueryParamProperties {
-    /** A point on the earth specified as a longitude and latitude. Example: &coordinates=lon,lat */
-    coordinates: Array<number>;
-    /**
-     * A string that represents an [ISO 3166-1 Alpha-2 region/country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2). This will alter Geopolitical disputed borders and labels to align with the specified user region. By default, the View parameter is set to “Auto” even if you haven’t defined it in the request.
-     *
-     * Please refer to [Supported Views](https://aka.ms/AzureMapsLocalizationViews) for details and to see the available Views.
-     */
-    view?: string;
-    /** The geopolitical concept to return a boundary for. If not specified, the default is `countryRegion` result type. */
-    resultType?: "countryRegion" | "adminDistrict" | "adminDistrict2" | "postalCode" | "postalCode2" | "postalCode3" | "postalCode4" | "neighborhood" | "locality";
-    /** Resolution determines the amount of points to send back. If not specified, the default is medium resolution. */
-    resolution?: "small" | "medium" | "large" | "huge";
-}
-
-/**
- *
- * The `Get Reverse Geocoding` API is an HTTP `GET` request used to translate a coordinate (example: 37.786505, -122.3862) into a human understandable street address. Useful in tracking applications where you receive a GPS feed from the device or asset and wish to know the address associated with the coordinates. This endpoint will return address information for a given coordinate.
- */
-export declare interface SearchGetReverseGeocoding200Response extends HttpResponse {
-    status: "200";
-    body: GeocodingResponseOutput;
-}
-
-/**
- *
- * The `Get Reverse Geocoding Batch` API is an HTTP `POST` request that sends batches of up to **100** queries to [Reverse Geocoding](/rest/api/maps/search/get-reverse-geocoding) API using a single request.
- *
- * ### Submit Synchronous Batch Request
- * The Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API.
- * ```
- * POST https://atlas.microsoft.com/reverseGeocode:batch?api-version=2023-06-01
- * ```
- * ### POST Body for Batch Request
- * To send the _reverse geocoding_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 2 _reverse geocoding_ queries:
- *
- *
- * ```
- * {
- *   "batchItems": [
- *     {
- *       "coordinates": [-122.128275, 47.639429],
- *       "resultTypes": ["Address", "PopulatedPlace"]
- *     },
- *     {
- *       "coordinates": [-122.341979399674, 47.6095253501216]
- *     }
- *   ]
- * }
- * ```
- *
- * A _reverse geocoding_ batchItem object can accept any of the supported _reverse geocoding_ [URI parameters](/rest/api/maps/search/get-reverse-geocoding#uri-parameters).
- *
- *
- * The batch should contain at least **1** query.
- *
- *
- * ### Batch Response Model
- * The batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests` i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item is of one of the following types:
- *
- *   - [`GeocodingResponse`](/rest/api/maps/search/get-reverse-geocoding#geocodingresponse) - If the query completed successfully.
- *
- *   - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.
- *
- *
- *
- */
-export declare interface SearchGetReverseGeocodingBatch200Response extends HttpResponse {
-    status: "200";
-    body: GeocodingBatchResponseOutput;
-}
-
-export declare interface SearchGetReverseGeocodingBatchBodyParam {
-    /** The list of reverse geocoding queries/requests to process. The list can contain a max of 100 queries and must contain at least 1 query. */
-    body: ReverseGeocodingBatchRequestBody;
-}
-
-/**
- *
- * The `Get Reverse Geocoding Batch` API is an HTTP `POST` request that sends batches of up to **100** queries to [Reverse Geocoding](/rest/api/maps/search/get-reverse-geocoding) API using a single request.
- *
- * ### Submit Synchronous Batch Request
- * The Synchronous API is recommended for lightweight batch requests. When the service receives a request, it will respond as soon as the batch items are calculated and there will be no possibility to retrieve the results later. The Synchronous API will return a timeout error (a 408 response) if the request takes longer than 60 seconds. The number of batch items is limited to **100** for this API.
- * ```
- * POST https://atlas.microsoft.com/reverseGeocode:batch?api-version=2023-06-01
- * ```
- * ### POST Body for Batch Request
- * To send the _reverse geocoding_ queries you will use a `POST` request where the request body will contain the `batchItems` array in `json` format and the `Content-Type` header will be set to `application/json`. Here's a sample request body containing 2 _reverse geocoding_ queries:
- *
- *
- * ```
- * {
- *   "batchItems": [
- *     {
- *       "coordinates": [-122.128275, 47.639429],
- *       "resultTypes": ["Address", "PopulatedPlace"]
- *     },
- *     {
- *       "coordinates": [-122.341979399674, 47.6095253501216]
- *     }
- *   ]
- * }
- * ```
- *
- * A _reverse geocoding_ batchItem object can accept any of the supported _reverse geocoding_ [URI parameters](/rest/api/maps/search/get-reverse-geocoding#uri-parameters).
- *
- *
- * The batch should contain at least **1** query.
- *
- *
- * ### Batch Response Model
- * The batch response contains a `summary` component that indicates the `totalRequests` that were part of the original batch request and `successfulRequests` i.e. queries which were executed successfully. The batch response also includes a `batchItems` array which contains a response for each and every query in the batch request. The `batchItems` will contain the results in the exact same order the original queries were sent in the batch request. Each item is of one of the following types:
- *
- *   - [`GeocodingResponse`](/rest/api/maps/search/get-reverse-geocoding#geocodingresponse) - If the query completed successfully.
- *
- *   - `Error` - If the query failed. The response will contain a `code` and a `message` in this case.
- *
- *
- *
- */
-export declare interface SearchGetReverseGeocodingBatchDefaultResponse extends HttpResponse {
-    status: string;
-    body: ErrorResponseOutput;
-}
-
-export declare interface SearchGetReverseGeocodingBatchMediaTypesParam {
-    /** Request content type */
-    contentType?: "application/json";
-}
-
-export declare type SearchGetReverseGeocodingBatchParameters = SearchGetReverseGeocodingBatchMediaTypesParam & SearchGetReverseGeocodingBatchBodyParam & RequestParameters;
-
-/**
- *
- * The `Get Reverse Geocoding` API is an HTTP `GET` request used to translate a coordinate (example: 37.786505, -122.3862) into a human understandable street address. Useful in tracking applications where you receive a GPS feed from the device or asset and wish to know the address associated with the coordinates. This endpoint will return address information for a given coordinate.
- */
-export declare interface SearchGetReverseGeocodingDefaultResponse extends HttpResponse {
-    status: string;
-    body: ErrorResponseOutput;
-}
-
-export declare type SearchGetReverseGeocodingParameters = SearchGetReverseGeocodingQueryParam & RequestParameters;
-
-export declare interface SearchGetReverseGeocodingQueryParam {
-    queryParameters: SearchGetReverseGeocodingQueryParamProperties;
-}
-
-export declare interface SearchGetReverseGeocodingQueryParamProperties {
-    /** The coordinates of the location that you want to reverse geocode. Example: &coordinates=lon,lat */
-    coordinates: Array<number>;
-    /**
-     * Specify entity types that you want in the response. Only the types you specify will be returned. If the point cannot be mapped to the entity types you specify, no location information is returned in the response.
-     * Default value is all possible entities.
-     * A comma separated list of entity types selected from the following options.
-     *
-     * - Address
-     * - Neighborhood
-     * - PopulatedPlace
-     * - Postcode1
-     * - AdminDivision1
-     * - AdminDivision2
-     * - CountryRegion
-     *
-     * These entity types are ordered from the most specific entity to the least specific entity. When entities of more than one entity type are found, only the most specific entity is returned. For example, if you specify Address and AdminDistrict1 as entity types and entities were found for both types, only the Address entity information is returned in the response.
-     */
-    resultTypes?: Array<"Address" | "Neighborhood" | "PopulatedPlace" | "Postcode1" | "AdminDivision1" | "AdminDivision2" | "CountryRegion">;
-    /**
-     * A string that represents an [ISO 3166-1 Alpha-2 region/country code](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2). This will alter Geopolitical disputed borders and labels to align with the specified user region. By default, the View parameter is set to “Auto” even if you haven’t defined it in the request.
-     *
-     * Please refer to [Supported Views](https://aka.ms/AzureMapsLocalizationViews) for details and to see the available Views.
-     */
-    view?: string;
-}
-
-export { }