## Execute a PlazaQL query

`FeatureCollection Query.Execute(QueryExecuteParamsparameters, CancellationTokencancellationToken = default)`

**post** `/api/v1/query`

Execute a PlazaQL query

### Parameters

- `QueryExecuteParams parameters`

  - `required string data`

    Body param: PlazaQL query string

  - `string format`

    Query param: Response format: json (default), geojson, csv, ndjson

### 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`.

  - `required IReadOnlyList<GeoJsonFeature> Features`

    Array of GeoJSON Feature objects

    - `required GeoJsonGeometry Geometry`

      GeoJSON Geometry object per RFC 7946. Coordinates use [longitude, latitude] order. 3D coordinates [lng, lat, elevation] are used for elevation endpoints.

      - `required Coordinates Coordinates`

        Coordinates array. Nesting depth varies by geometry type: Point = [lng, lat], LineString = [[lng, lat], ...], Polygon = [[[lng, lat], ...], ...], etc.

        - `IReadOnlyList<Double>`

        - `IReadOnlyList<IReadOnlyList<Double>>`

        - `IReadOnlyList<IReadOnlyList<IReadOnlyList<Double>>>`

        - `IReadOnlyList<IReadOnlyList<IReadOnlyList<IReadOnlyList<Double>>>>`

      - `required Type Type`

        Geometry type

        - `"Point"Point`

        - `"LineString"LineString`

        - `"Polygon"Polygon`

        - `"MultiPoint"MultiPoint`

        - `"MultiLineString"MultiLineString`

        - `"MultiPolygon"MultiPolygon`

    - `required IReadOnlyDictionary<string, JsonElement> 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.

    - `required Type Type`

      Always `Feature`

      - `"Feature"Feature`

    - `string ID`

      Compound identifier in `type/osm_id` format

  - `required Type Type`

    Always `FeatureCollection`

    - `"FeatureCollection"FeatureCollection`

### Example

```csharp
QueryExecuteParams parameters = new()
{
    Data = "$$ = search(node, amenity: \"cafe\").around(distance: 500, geometry: point(48.8566, 2.3522));",
};

var featureCollection = await client.Query.Execute(parameters);

Console.WriteLine(featureCollection);
```

#### 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"
}
```