MRH Accessibility Analysis on Spatial Planning

Open data API in a single place

Provided by Bundesamt für Kartographie und Geodäsie

Get early access to MRH Accessibility Analysis on Spatial Planning API!

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

Dataset information

Catalog
Country of origin
Updated
2019.10.21 22:00
Created
Available languages
German
Keywords
Auswertungen, GDIMRH, Geodaten, Oberzentrum, Mittelzentrum, Reisezeit, MRH, Erreichbarkeit, Analysen, Metropolregion, TRAN
Quality scoring
155

Dataset description

The maps show the fastest accessible middle and upper center with different means of transport. The accessibility is mapped on an inhabited 100-metre grid and a comprehensive 500-metre grid in minutes. All 132 central and 27 upper centres in the catchment area of the Hamburg Metropolitan Region (MRH) are taken into account. In the calculation of the nearest centre, the upper centres are also taken into account. The indication of walking times was waived, as no precise location of the center is possible. Other central locations are located in Hamburg according to the Hamburg Center Concept. Thus, the B1 centres are defined as upper centres and the B2 centres are defined as middle centres. Calculation of travel times: Travel times and distances in passenger, foot and cycling traffic are based on a detailed route network based on OpenStreetMap (OSM). Travel times in passenger cars are based on road loads typical of professional traffic. In passenger cars, surcharges depending on the area type are also calculated for parking search traffic, access and set-off times as well as connections. These are based on the RIN R1 Integrated Network Design Guidelines (FGSV 2010, p. 47) and are between two and nine minutes. The data in public transport are based on the real timetable data on a normal Tuesday of the timetable period 18/19. Only the timetables and between 9 a.m. and 12 o'clock are taken into account. The travel time also includes walking times to and from the stop as well as a waiting time at the starting stop. The interchange frequency corresponds to the necessary changes on the fastest connection. The number of connections indicates the frequency of journeys between 9 a.m. and 12 o'clock. In long-distance transport, only the journeys on the railway lines from Hamburg to Berlin and Rostock are taken into account in order to meet the high importance of the stops in Schwerin and Ludwigslust. Flexible offers (AST, call buses, etc.) are only considered if they are included in the electronic timetable information. In individual traffic by car, bike or on foot, a maximum travel time of 60 minutes is assumed. This travel time in public transport is a maximum of 120 minutes. In these two hours, the walking times to stops and all waiting times are already included. Sources: Timetable data: (Yearly timetable 2019): Prepared by TUHH; Deutsche Bahn AG, Verkehrsgesellschaft Ludwigslust-Parchim mbH, Nahbus GmbH (Nordwestmecklenburg), Stadtverkehr Schwerin GmbH Network of foot and bike paths: Processed by TUHH (gradients, speeds); based on OpenStreetMap (OSM 2019) and SRTM height data (SRTM 2000) Road network: Processed by TUHH; based on Openstreetmap (OSM 2019) Central and Upper Centres: TUHH (2019), LGV (2019), Center Concept Hamburg (2014)
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
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.

Didn't find the API you need?

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

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks