This data set is a logistics model that quantifies the shipment volumes of almost 6,000 recipients in the rural towns of Mittenaar, Hohenahr, Bischoffen and Siegbach in the Lahn-Dill district, based on logistical KEP broadcast data from Q4 2019 and Q1 2020, and establishes a source-target relationship with the three largest resident CEP service providers. Information on the expected shipment quantities per target coordinate is aggregated on a daily basis and is target address specific. The dataset contains the following fields:
_tourID [Integer]: Individual identification number of a delivery
_DCDistrictC1 [String]: District of the KEP company’s distribution centre with the largest distribution volume in charge of supply
_DCDistrictC2 [String]: Locality of the distribution centre of the CEP company responsible for supplying the second largest distribution volume
_DCDistrictC3 [String]: Locality of the distribution centre of the CEP company responsible for supplying the third largest distribution volume
_DCZipC1 [Integer]: Postal code of the distribution centre of the CEP company with the largest distribution volume in charge of supply
_DCZipC2 [Integer]: Postal code of the distribution centre of the CEP company responsible for supply with the second largest distribution volume
_DCZipC3 [Integer]: Postal code of the distribution centre responsible for supplying the CEP company with the third largest distribution volume
_DCLatC1 [decimal degree]: Latitude of the KEP company’s distribution centre with the largest distribution volume in charge of supply
_DCLatC2 [decimal degree]: Latitude of the distribution centre of the CEP company responsible for supplying the second largest distribution volume
_DCLatC3 [decimal degree]: Latitude of the distribution centre of the CEP company responsible for supplying the third largest distribution volume
_DCLongC1 [decimal degree]: Longitude of the KEP company’s distribution centre with the largest distribution volume in charge of supply
_DCLongC2 [decimal degree]: Longitude of the distribution centre of the CEP company responsible for supplying the second largest distribution volume
_DCLongC3 [decimal degree]: Longitude of the distribution centre of the CEP company responsible for supplying the third largest distribution volume
_shareC1 [Double]: Percentage share of C1 distribution infrastructure in total distribution volume
_shareC2 [Double]: Percentage share of C2 distribution infrastructure in total distribution volume
_shareC3 [Double]:Percentage of C3 distribution infrastructure in total distribution volume
_recipientDistrict [String]: Locality of the delivery recipient
_recipientType [String]: Classification of the delivery recipient by building category
_recipientZip [Integer]: Postal code of the consignee
_recipientLat [decimal degree]: Latitude of the consignee
_recipientLong [decimal degree]: Longitude of the consignee
_deliveryRate [Double]: Daily delivery frequency per target coordinate and day in parcel quantities
The data comes from the mFUND project “Data Modeling for the Use of Autonomous Minibuses in Rural Areas for Combined Transport of Persons and Goods” (Combinom), which deals with data availability for simulation-based mapping and analysis of combined transports in rural areas.
Kombinom is funded by the Federal Ministry of Transport and Digital Infrastructure as part of the innovation initiative mFUND. As part of mFUND, the BMVI has been supporting research and development projects on data-based digital applications for mobility 4.0 since 2016. In addition to the financial support, the mFUND supports the networking between actors from politics, business and research as well as access to the data portal mCLOUD with various event formats. More information can be found at www.mfund.de.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.