## Find features near a geographic point `elements().nearbyPost(ElementNearbyPostParamsparams = ElementNearbyPostParams.none(), RequestOptionsrequestOptions = RequestOptions.none()) : FeatureCollection` **post** `/api/v1/features/nearby` Find features near a geographic point ### Parameters - `params: ElementNearbyPostParams` - `lat: Optional` Legacy shorthand. Latitude (-90 to 90). Use near param instead. - `limit: Optional` Maximum results (default 20, max 100) - `lng: Optional` Legacy shorthand. Longitude (-180 to 180). Use near param instead. - `near: Optional` Point geometry for proximity search (lat,lng or GeoJSON). Alternative to lat/lng params. - `outputBuffer: Optional` Buffer geometry by meters - `outputCentroid: Optional` Replace geometry with centroid - `outputFields: Optional` Comma-separated property fields to include - `outputGeometry: Optional` Include geometry (default true) - `outputInclude: Optional` Extra computed fields: bbox, distance, center - `outputPrecision: Optional` Coordinate decimal precision (1-15, default 7) - `outputSimplify: Optional` Simplify geometry tolerance in meters - `outputSort: Optional` Sort by: distance, name, osm_id - `radius: Optional` Search radius in meters (default 500, max 10000) ### Returns - `class FeatureCollection:` GeoJSON FeatureCollection (RFC 7946). For paginated endpoints, metadata is returned in HTTP response headers rather than the body: | Header | Description | | --------------- | ------------------------------------------------ | | `X-Limit` | Requested result limit | | `X-Has-More` | `true` if more results exist | | `X-Next-Cursor` | Opaque cursor for next page (cursor pagination) | | `X-Next-Offset` | Numeric offset for next page (offset pagination) | | `Link` | RFC 8288 `rel="next"` link to the next page | Content-Type is `application/geo+json`. - `features: List` Array of GeoJSON Feature objects - `geometry: GeoJsonGeometry` GeoJSON Geometry object per RFC 7946. Coordinates use [longitude, latitude] order. 3D coordinates [lng, lat, elevation] are used for elevation endpoints. - `coordinates: Coordinates` Coordinates array. Nesting depth varies by geometry type: Point = [lng, lat], LineString = [[lng, lat], ...], Polygon = [[[lng, lat], ...], ...], etc. - `List` - `List>` - `List>>` - `List>>>` - `type: Type` Geometry type - `POINT("Point")` - `LINE_STRING("LineString")` - `POLYGON("Polygon")` - `MULTI_POINT("MultiPoint")` - `MULTI_LINE_STRING("MultiLineString")` - `MULTI_POLYGON("MultiPolygon")` - `properties: Properties` OSM tags flattened as key-value pairs, plus `@type` (node/way/relation) and `@id` (OSM ID) metadata fields. May include `distance_m` for proximity queries. - `type: Type` Always `Feature` - `FEATURE("Feature")` - `id: Optional` Compound identifier in `type/osm_id` format - `type: Type` Always `FeatureCollection` - `FEATURE_COLLECTION("FeatureCollection")` ### Example ```kotlin package com.plazafyi.example import com.plazafyi.client.PlazaClient import com.plazafyi.client.okhttp.PlazaOkHttpClient import com.plazafyi.models.FeatureCollection import com.plazafyi.models.elements.ElementNearbyPostParams fun main() { val client: PlazaClient = PlazaOkHttpClient.fromEnv() val featureCollection: FeatureCollection = client.elements().nearbyPost() } ``` #### Response ```json { "features": [ { "geometry": { "coordinates": [ 2.3522, 48.8566 ], "type": "Point" }, "properties": { "@id": "bar", "@type": "bar", "amenity": "bar", "cuisine": "bar", "name": "bar" }, "type": "Feature", "id": "node/21154906" } ], "type": "FeatureCollection" } ```