Skip to content
Plaza Plaza Docs
GuidesBlogPlaygroundDashboard
API Reference
Datasets

Query features in a dataset

FeatureCollection datasets().features(DatasetFeaturesParamsparams = DatasetFeaturesParams.none(), RequestOptionsrequestOptions = RequestOptions.none())
GET/api/v1/datasets/{id}/features

Query features in a dataset

ParametersExpand Collapse
DatasetFeaturesParams params
Optional<String> id
Optional<String> cursor

Cursor for pagination

Optional<String> format

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

Optional<Long> limit

Maximum results

Optional<Double> outputBuffer

Buffer geometry by meters

Optional<Boolean> outputCentroid

Replace geometry with centroid

Optional<String> outputFields

Comma-separated property fields to include

Optional<Boolean> outputGeometry

Include geometry (default true)

Optional<String> outputInclude

Extra computed fields: bbox, distance, center

Optional<Long> outputPrecision

Coordinate decimal precision (1-15, default 7)

Optional<Double> outputSimplify

Simplify geometry tolerance in meters

Optional<String> outputSort

Sort by: distance, name, osm_id

ReturnsExpand Collapse
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.

List<GeoJsonFeature> features

Array of GeoJSON Feature objects

GeoJsonGeometry geometry

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.

One of the following:
List<double>
List<List<double>>
List<List<List<double>>>
List<List<List<List<double>>>>
Type type

Geometry type

One of the following:
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

Optional<String> id

Compound identifier in type/osm_id format

Type type

Always FeatureCollection

Query features in a dataset

package com.plazafyi.example;

import com.plazafyi.client.PlazaClient;
import com.plazafyi.client.okhttp.PlazaOkHttpClient;
import com.plazafyi.models.FeatureCollection;
import com.plazafyi.models.datasets.DatasetFeaturesParams;

public final class Main {
    private Main() {}

    public static void main(String[] args) {
        PlazaClient client = PlazaOkHttpClient.fromEnv();

        FeatureCollection featureCollection = client.datasets().features("id");
    }
}
{
  "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"
}
Returns Examples
{
  "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"
}