Street Names - BlagnacNom voies Blagnac

Nom voies BlagnacStreet Names - Blagnac

APIExecutable4/7Query nowOpen workbench Subscribe🇫🇷France

Website Docs

⬇ Export CSV List records Select & filter Run verified request Read the docs

Trust score

How is this computed?

fair

Weighted across five axes. Tap a ring for what it measures.

Data schema (3 fields)

Filterable via the API (1)

Click a field to see example values.

Field	Type	Description
geo_point_2dGeo Point	geo_point_2d	Latitude and longitude coordinates of the street location.Latitude and longitude coordinates of the street location.
geo_shapeShape	geo_shape	Geographic geometry representing the street's spatial feature.Geographic geometry representing the street's spatial feature.
id	int	Internal record identifier for the street name entry.Internal record identifier for the street name entry.

Schema captured from opendatasoft 3 days ago.

Query the data

Pick columns and a sort, then fetch a live preview straight from the source. Choose an API-filterable column (marked ▾) under “Where” to pick from its list of values.

Where=

Sort by

Sample data (5 records)

These rows are ODbL-1.0: share-alike. Reusing them obliges you to license any derived database on the same terms.

Record 1id: 0 · geo_shape: {"type":"Feature","geometry":{"type":"Po

{
  "id": 0,
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        1.398355560863141,
        43.64036099891527
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 43.64036099891527,
    "lon": 1.398355560863141
  }
}

Record 2id: 0 · geo_shape: {"type":"Feature","geometry":{"type":"Po

{
  "id": 0,
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        1.383735504126879,
        43.62525646397207
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 43.62525646397207,
    "lon": 1.383735504126879
  }
}

Record 3id: 0 · geo_shape: {"type":"Feature","geometry":{"type":"Po

{
  "id": 0,
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        1.378345453012108,
        43.64264493574045
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 43.64264493574045,
    "lon": 1.378345453012108
  }
}

Record 4id: 0 · geo_shape: {"type":"Feature","geometry":{"type":"Po

{
  "id": 0,
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        1.369011640162127,
        43.63900072086666
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 43.63900072086666,
    "lon": 1.369011640162127
  }
}

Record 5id: 0 · geo_shape: {"type":"Feature","geometry":{"type":"Po

{
  "id": 0,
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        1.399386706473837,
        43.64289246283088
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 43.64289246283088,
    "lon": 1.399386706473837
  }
}

Live sample captured at profiling time — values may have changed upstream.

Verification Status

Using the API

Configuration

Base URL: https://data.toulouse-metropole.fr/api/explore/v2.1/catalog/datasets/nom-voies-blagnac

License

Open Data Commons Open Database License 1.0Open

✓ Redistributable
✓ Attribution required

Query examples

curl -s 'https://data.toulouse-metropole.fr/api/explore/v2.1/catalog/datasets/nom-voies-blagnac/records?limit=20' -H 'Accept: application/json'

First 20 records of the dataset as JSON.

Uses the Opendatasoft Explore v2.1 syntax — supports select, where, group_by and order_by.

Full API documentation ↗

Rate limits

20 000 req/day

per ipmeasured

observed 3 days ago

Dataset

Volume & freshness

Records

1.0k

1038

Update cadence

Annual

declared upstream

Last upstream update

8 years ago

2019-06-17

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: opendatasoft

Machine-readable & source

JSON

Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.