The present dataset is part of the report titled Gradinaru S.R., Hersperger A.M., Schmid F. (2021). Deriving Planning Intentions from written planning documents. Report on CONCUR Project- From plans to land change: how strategic spatial planning contributes to the development of urban regions.
The data corresponds to the data collected as part of the DPI Method for deriving all PIs contained in a plan (open coding) as detailed in section 4 of the report. The method involved reading the plans to break down of information in meaningful discrete “incidents” or planning intentions. To identify the planning intentions, the starting points were represented by a) the structuring of the plans in chapters and sub chapters and b) the themes that the plans addressed. Thus, the collected information was not grouped according to pre-defined categories of planning intentions, but rather put together as a list of intentions as revealed by each plan. As a result, we provide, for each case study, a document (named [Urban region name] PI as defined in the plan) which contains:
Date when the information was filled in.
Name of the urban region and analysed strategic spatial plan .
A list of all planning intentions contained in a plan, with each PI being addresses as follows:
Name of PI as it appears in the plan
Translated name of the PI (i.e. short name for easy understanding of the meaning)
Explanation regarding the meaning of the PI
Why the PI is considered a priority for the urban region
Spatial information on the PI (text and cartographic representations).
In total, 14 documents are available, one for each case study. Documents contain up to 20 pages of information extracted from the plans together with explanations and notes taken during plan reading.
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.