Baselight

Transport Performance Statistics By 200 Metre Grids For Subset Of Urban Centres In France

Office for National Statistics

@ukgov.transport_performance_statistics_by_200_metre_grids_fo_2597837a

Loading...
Loading...

About this Dataset

Transport Performance Statistics By 200 Metre Grids For Subset Of Urban Centres In France

Experimental public transit transport performance statistics by 200 metre grids for a subset of urban centres in France, with the following fields (Note: These data are experimental, please see the Methods and Known Limitations/Caveats Sections for more details).

Attribute Description
id Unique Identifier
population Global Human Settlement Layer population estimate downsampled to 200 metre (represents the total population across adjacent 100 metre cells)
access_pop The total population that can reach the destination cell within 45 minutes using the public transit network (origins within 11.25 kilometres of the destination cell)
proxim_pop The total population within an 11.25 kilometre radius of the destination cell
trans_perf The transport performance of the 200 metre cell. The percentage ratio of accessible to proximal population
city_nm Name of the urban centre
country_nm Name of the country that the urban centre belongs to

_
_

Methods:

For more information please visit:

· Python Package: https://github.com/datasciencecampus/transport-network-performance

· Docker Image: https://github.com/datasciencecampus/transport-performance-docker

Known Limitations/Caveats:

These data are experimental – see the ONS guidance on experimental statistics for more details. They are being published at this early stage to involve potential users and stakeholders in assessing their quality and suitability. The known caveats and limitations of these experimental statistics are summarised below.

Urban Centre and Population Estimates:

· Population estimates are derived from data using a hybrid method of satellite imagery and national censuses. The alignment of national census boundaries to gridded estimates introduce measurement errors, particularly in newer housing and built-up developments. See section 2.5 of the GHSL technical report release 2023A for more details.

Public Transit Schedule Data (GTFS):

· Does not include effects due to delays (such as congestion and diversions).

· Common GTFS issues are resolved during preprocessing where possible, including removing trips with unrealistic fast travel between stops, cleaning IDs, cleaning arrival/departure times, route name deduplication, dropping stops with no stop times, removing undefined parent stations, and dropping trips, shapes, and routes with no stops. Certain GTFS cleaning steps were not possible in all instances, and in those cases the impacted steps were skipped. Additional work is required to further support GTFS validation and cleaning.

Transport Network Routing:

· “Trapped” centroids: the centroid of destination cells on very rare occasions falls on a private road/pathway. Routing to these cells cannot be performed. This greatly decreases the transport performance in comparison with the neighbouring cells. Potential solutions include interpolation based on neighbouring cells or snapping to the nearest public OSM node (and adjusting the travel time accordingly). Further development to adapt the method for this consideration is necessary.

Please also visit the Python package and Docker Image GitHub issues pages for more details.

How to Contribute:

We hope that the public, other public sector organisations, and National Statistics Institutions can collaborate and build on these data, to help improve the international comparability of statistics and enable higher frequency and more timely comparisons. We welcome feedback and contribution either through GitHub or by contacting datacampus@ons.gov.uk.
Publisher name: Office for National Statistics
Last updated: 2024-12-10T01:53:28Z

Tables

Table 1

@ukgov.transport_performance_statistics_by_200_metre_grids_fo_2597837a.table_1
  • 4.27 MB
  • 68130 rows
  • 10 columns
Loading...

CREATE TABLE table_1 (
  "fid" BIGINT,
  "id" VARCHAR,
  "population" DOUBLE,
  "access_pop" DOUBLE,
  "proxim_pop" DOUBLE,
  "trans_perf" DOUBLE,
  "city_nm" VARCHAR,
  "country_nm" VARCHAR,
  "shape_area" DOUBLE,
  "shape_length" DOUBLE
);

Share link

Anyone who has the link will be able to view this.