CONDUCTOR UC3 simulation data

Open data API in a single place

Provided by Zenodo

Get early access to CONDUCTOR UC3 simulation data API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.11.19 00:00
Created
2025.01.01
Available languages
English
Keywords
Quality scoring

Dataset description

The CONDUCTOR-UC3data.zip file contains the demand data used to perform the validation exercises for the CONDUCTOR UC3 Madrid Pilot. Specifically, the following files are included: - parcel_demand_scenario_1.csv: CSV file separated with "," containing the daily last-mile parcel demand estimation in the UC3 study zone for the current demand scenario (year 2024) of the CONDUCTOR UC3 Madrid Pilot. The size of the file is 1.36MB and has the following columns:    - Latitute_pick_up: latitude of the parcel pick-up location (EPSG:4326)    - Longitude_pick_up: longitude of the parcel pick-up location (EPSG:4326)    - Latitude_delivery: latitude of the parcel delivery location (EPSG:4326)    - Longitude_delivery: longitude of the parcel delivery location (EPSG:4326)    - pickup_Start: init time of the parcel pick-up time window (format HH:MM:SS)    - pickup_End: end time of the parcel pick-up time window (format HH:MM:SS)    - delivery_Start: init time of the parcel delivery time window (format HH:MM:SS)    - delivery_End: end time of the parcel delivery time window (format HH:MM:SS)    - Weight: weight of the parcel (in kg)    - Volume: volume of the parcel (in m3) - parcel_demand_scenario_2.csv: CSV file separated with "," containing the daily last-mile parcel demand estimation in the UC3 study zone for the intermediate demand scenario (year 2027) of the CONDUCTOR UC3 Madrid Pilot. The size of the file is 1.64MB and has the following columns:    - Latitute_pick_up: latitude of the parcel pick-up location (EPSG:4326)    - Longitude_pick_up: longitude of the parcel pick-up location (EPSG:4326)    - Latitude_delivery: latitude of the parcel delivery location (EPSG:4326)    - Longitude_delivery: longitude of the parcel delivery location (EPSG:4326)    - pickup_Start: init time of the parcel pick-up time window (format HH:MM:SS)    - pickup_End: end time of the parcel pick-up time window (format HH:MM:SS)    - delivery_Start: init time of the parcel delivery time window (format HH:MM:SS)    - delivery_End: end time of the parcel delivery time window (format HH:MM:SS)    - Weight: weight of the parcel (in kg)    - Volume: volume of the parcel (in m3) - drt-ccam_demand_scenario_1.csv: CSV file separated with "," containing the daily DRT-CCAM service demand estimation in the UC3 study zone for the current demand scenario (year 2024) of the CONDUCTOR UC3 Madrid Pilot. The size of the file is 3.75MB and has the following columns:    - lon_start: longitude of the trip start location (EPSG:4326)    - lat_start: latitude of the trip start location (EPSG:4326)    - lon_end: longitude of the trip end location (EPSG:4326)    - lat_end: latitude of the trip end location (EPSG:4326)    - pickup_start: init time of the trip pick-up time window (format HH:MM:SS)    - pickup_end: end time of the trip pick-up time window (format HH:MM:SS)    - dropoff_End: end time of the trip drop-off time window (format HH:MM:SS)    - dropoff_start: init time of the trip drop-off time window (format HH:MM:SS) - drt-ccam_demand_scenario_2.csv: CSV file separated with "," containing the daily DRT-CCAM service demand estimation in the UC3 study zone for the intermediate demand scenario (year 2027) of the CONDUCTOR UC3 Madrid Pilot. The size of the file is 17.4MB and has the following columns:    - lon_start: longitude of the trip start location (EPSG:4326)    - lat_start: latitude of the trip start location (EPSG:4326)    - lon_end: longitude of the trip end location (EPSG:4326)    - lat_end: latitude of the trip end location (EPSG:4326)    - pickup_start: init time of the trip pick-up time window (format HH:MM:SS)    - pickup_end: end time of the trip pick-up time window (format HH:MM:SS)    - dropoff_End: end time of the trip drop-off time window (format HH:MM:SS)    - dropoff_start: init time of the trip drop-off time window (format HH:MM:SS) - UC3_study_zone.shp: Shape file and all the auxiliary files (.cpg, .dbf, .prj, .qpj, .shx) containing the geometry of the study zone used for the analysis of the CONDUCTOR UC3 Madrid Pilot. The size of the files is 2.32KB. The shape file has the following fields:    - id: id of the sudy zone (id=10)    - geometry: geometry of the zone (polygon) (EPSG:3857) - pick_up_locations.shp: Shape file and all the auxiliary files (.cpg, .dbf, .prj, .qpj, .shx) containing the location of the three consolidation centres used in the CONDUCTOR UC3 Madrid Pilot to transport the parcels from their respective logistic centres for the combined service. The size of the files is 1KB. The shape file has the following fields:    - Latitute_p: latitude of the consolidation centre (EPSG:4326)    - Longitude_: latitude of the consolidation centre (EPSG:4326)    - geometry: coordinates of the consolidation centre (point) (EPSG:4326) - logistic_points.csv: CSV file separated with "," containing the location of logistic and delivery hubs in the Madrid Región used for the CONDUCTOR UC3 Madrid Pilot. The size of the file is 2KB and has the following columns:    - name: name of the logistic hub    - latitude: latitude of the logistic hub location (EPSG:4326)    - longitude: longitude of the logistic hub location (EPSG:4326)
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks