Welcome to KfW’s guide for collecting project location data in development cooperation. This website will describe how to collect and validate project locations according to the specifications of our data-model. If you have any questions, comments or suggestions for improvements, please open a ticket in our Github repository.
This guide:
- Describes the data model and its development (version control) and serves as an open-source reference for other institutions in the development cooperation sector
- Shows KfW project partners how to submit geospatial information on project locations, based on the requirements of our data model
- Enables KfW project partners and KfW staff to validate submitted geo-information against the requirements of our data model
This guide is prepared for:
- KfW project partners i.e. the project-executing agency (PEA) or a consulting entity assisting the PEA alongside project development and implementation phases. We recommend our partners to identify staff with knowledge of Geographic Information Systems (GIS) to assist with the data collection process.
- KfW staff: Responsible for the data collection, verification, and submission within KfW.
This guide is structured in the following way:
General Content
Gives you an overview of processes, formats and general information to collect and validate project location data.
Annex 1
Contains Excel Templates to collect (attribute) data according to our model
Annex 2
Contains detailled descriptions of all fields from the datamodel automatically extracted from our json schema.
This section describes how Project Locations data should be collected, including information on technical requirements and expected formats; this guidance is intended for KfW staff, Project Executing Agencies (PEAs), consultants, and other external stakeholders responsible for data collection.
A Project Location is a set of one or more features that are part of a financially supported activity, where it is not feasible to make any further geographical distinctions with regards to funding. For instance, a financially supported hospital at a specific location is an example of a single-feature Project Location. Another example of a multi-feature Project Location is a group of adjacent agricultural plots that are being financed under an irrigation plan that benefits all producers in that area. A set of protected areas that are jointly financed from a single source of funding is another example of a multi-feature Project Location. However, if funding allocation can be further distinguished by smaller geographic areas, data across multiple Project Locations and the respective financial allocations must be collected. KfW strongly encourages capturing the geographical discrimination of financial flows to specific project locations where possible, which contributes to transparency and financial accountability.
The Project Location Model is a structured data model, developed by the KfW Development Bank, to collect location-specific information about projects supported by international development cooperation. The model is in use and continues to be developed by KfW, together with their peers and partners.
The model, in Excel format, is currently available for download in English and French, see also Excel Templates. The model can be used in combination with a Geojson file.
Data related to specific project locations should be collected with respect to the outlined requirements. Please see FAQ for more information about the International Aid Transparency Initiative (IATI) standards and enhancements particular to KfW’s operational needs.
A Project location is defined as a set of one or more spatial features that are part of a financially supported activity, where it is not feasible to make any further geographical distinctions regarding funding.
The responsible party gathers all project locations and associated information, which has received financial support, within the context of a specific cooperation project. Project locations are generally collected on the output level. Additionally, if geospatial data contributes to the measurement of project outcomes and impacts, then location data for potential outcome sites should also be collected.
Examples:
-
A project financially supports the construction of a hospital. The hospital is built at a specific location. It is represented as a single feature (point), which indicates the spatial location of the hospital (=output). Project outcomes are measured using non-geospatial data (e.g. patient statistics), hence no additional project locations information needs to be collected.
-
A project financially supports the construction of irrigation infrastructure that benefits a group of small-scale farmers. The irrigation infrastructure (=output) is composed of multiple features (e.g. weirs and watercourses) that are mapped as a collection of features (i.e. multiple points). Furthermore, remote sensing data is consulted to measure project outcomes (e.g. by quantifying changes in agricultural productivity). In this case, geospatial information on outcome areas (i.e. the irrigated fields that make use of and benefit from the irrigation infrastructure) should also be submitted.
KfW strongly encourages the PEA or consultant to collect geo-coordinates as early as possible to increase the utilization potential of such data throughout the entire project cycle. If possible, data should be collected already during the project preparation phase, e.g. as part of a feasibility study. Data can be updated later if a project location site changes. Data updates should be ideally performed on an annual basis with the preparation of progress reports, if not otherwise specified.
The IATI standard describes a project location as exact or approximate. Exact locations refer to the geographical endpoints of financial flows and are reported with precise coordinates. All exact coordinates in Excel must be collected using WGS 84 (EPSG 4326) as the coordinate reference system, which is the standard for web mapping applications. Coordinates (“Latitude” and “Longitude” columns) have to be provided in decimal format with an accuracy of at least 5 digits after the separator (i.e. 00.00000).
It is advised to report an approximate project location, if the location of project implementation is a target area defined by an administrative unit, or if the exact location of the project implementation site is (yet) unknown or if it should be anonymized (e.g. for security reasons). Also in these two latter cases, the respective administrative unit (at an appropriate level) where the project is implemented should be used instead. More explanations on when to use approximate locations are given in the FAQs.
Project locations can be represented by three types of geometry:
- points, e.g. a well or a hospital
- lines, e.g. a road or transmission line
- polygons, e.g. a protected area, agricultural plot, or administrative unit
Additionally, different levels of detail may be used to represent this information. A road can be further segmented, where each sub-section represents different measures that have been financed, respectively. Furthermore, locations may be aggregated in a polygon that represents an intervention area or administrative unit. This might be useful for cases where there are a large number of sites that are part of the same project, and also if precise locations are unknown or if they should not be revealed due to privacy or security reasons.
While there are no strict rules governing the choice of geometry type and aggregation level for data collection, the following principles should be applied by the responsible party:
- Maximize transparency and precision of financial flows
- Allow for precise and unambigous spatial identification and delination of project locations and different supported activities
- Preserve data privacy: data should not be collected on an aggregation level where it contains personal information or could lead to the identification of individuals
- Avoid security risks: data should not be collected on an aggregation level that might expose or endanger vulnerable groups, such as refugees or minorities that might face discrimination
- Follow a reasonable cost-benefit ratio for collecting and producing the required information
In case you are unsure, please get in touch with your project partner to discuss the necessary details.
For the collection of point-loctions, we currently accept submissions in .XLSX and .GeoJSON formats.
The .XLSX format is best suited, if your institution does not know how to handle geospatial data and has no former experience with Geographic Information System (GIS) software. In this case you can use the most recent version of our Excel templates to collect all relevant information.
For the collection of point-locations, the use of .GeoJSON is optional but recommended for its reliability and flexibility. For the collection of line- or polygon-locations, only .GeoJSON format is accepted.
We highlight two common cases for generating the required data:
-
Desktop-production: For manual data collection, we recommend using the Excel templates to store all attributes and merging this information with spatial information (feature geometries) in a GIS software. Since the Excel templates are pre-configured, it is easier to provide data that is compliant with our data-model and pass the validation check as a way to ensure data quality. A short video tutorial (to be released soon) will demonstrate how to use the Excel template with QGIS software.
-
Database-extraction: If location information is available in a geospatial database, it is possible to extract and transform the data into field-mappings that also match our requirements. In these cases, the data-model can be provided as a JSON schema. This supports batch conversions as a starting point; any missing information can then be manually added.
If GeoJSON format is used, multi-point, -line or -polygon features can also be submitted to reduce data redundancies. This can be useful if the same project activity benefits multiple sites (e.g. all irrigated fields that benefit from an irrigation infrastructure). You can also use multi geometry feature collections if your submitted data contains different geometry formats.
You are required to validate your data before submission to KfW. This increases data quality at entry and reduces the need to go back and forth betweeen you and your project partners. You can do this manually by comparing your data to our requirements described in Annex 2.
As an alternative you can also use our online Location Validator in browser, which accepts both GeoJSON and Excel files and also allows you to visualize submitted information on a map. It gives you visual feedback if your data is compliant and automatically creates an email draft for you in case you pass the test.
While the Data Model template closely follows IATI standards, additional location types have been created to cover the full range of financial cooperation projects. Location types provide a brief description about the function of the Project Location.
Our extended list includes IATI location types that are useful for international development, as well as additional types relevant to all sectors. 197 new project location types have been created. These include for example, Capacity Development/Training or Voucher Schemes, which cannot be plotted based on any physical features on a map, but can be defined by underlying areas in which these types of projects operate. By extension, location types can be defined as project output- or intervention-related types of physical locations or areas. Please refer to the list of location types in the Excel template or in the json model for more information.
If a specific location type has not yet been added, please use the most similar available type (e.g. “well” for “extraction well”). Additional information can then be added if necessary.
The German Financial Cooperation uses Project Locations to report on the relevance, progress, and impacts of our project portfolios. We create maps of the portfolios of Project Locations for the German Federal Ministry for Economic Cooperation and Development BMZ and for our internal and external stakeholders. The data is used to assess portfolios for social, environmental or climate-related risks.
KfW strongly encourages PEA or consultant staff to collect geo-coordinates as early as possible, to optimize the potential utility of such data throughout the entire project cycle. Ideally, data should already be collected during the project preparation phase, e.g. as part of a feasibility study.
If exact locations cannot be determined at this stage, approximate location should be used (see below) and rechecked later during project appraisal and inception stages, where it may be possible to update approximate to exact locations. During project implementation, data should be updated at least once annually in project progress reviews. This ensures that any potential changes are reflected in the geographical allocation of funds, which are common in Financial Cooperation projects.
The Excel template must be submitted without containing any personal data or any data that could be linked to individual persons, such as houses of private households. Exact coordinates of Project Locations remain confidential and are not published publicly by KfW.
Location data in fragile and conflict contexts are treated with extra diligence. If an exact Project Location is not to be collected or communicated due to security reasons, select the option “approximate (security)” in the “Geographic Exactness” column. Furthermore, by indicating “yes” in the column “Publishing restrictions due to security reasons” associated to a Project Location, it will be omitted from publicly available reports.
The Project Locations Model is mostly based on a proposal by the International Aid Transparency Initiative (IATI) to collect project specific geo-information, which is used by international development organizations. It harmonizes and coordinates development projects across multiple donor agencies.
This standard was further developed in this context to address our operational needs. In particular, the Project Location Model mostly uses predefined categories under the International Aid Transparency Initiative (IATI) standard. Furthermore, built-in selection methods support clean data entry in Excel. The existing IATI list of location types has been expanded to cover all physical and immaterial location types required by international development cooperation standards.
Approximate locations should be used if onf of the following circumstances apply:
1. An exact project location has not (yet) been specified or is not yet known (e.g., the exact project locations have not yet been determined) -> then choose the option: approximate (yet unknown).
2. An exact project location is not to be collected or communicated due to security reasons (e.g., in a conflict zone) -> then choose the option: approximate (security).
3. The target location(s) is/are one or more administrative units, such as a district, a province, or the entire country or group of countries (e.g., an entire country for a Policy-Based-Lending project or a number of districts in a country for a decentralization project) -> then choose the option: approximate (admin unit).
These Fact Sheets were developed for all practitioners in preparing and implementing Financial Cooperation (FC) projects and provides them with assistance and examples of how to manage, monitor, and verify FC projects remotely.
These Fact Sheets were carefully drafted by KfW, its advisers, and experts on the topics covered reflecting the extensive experience gained in KfW’s own FC projects. The material and information provided in them Fact Sheet are however general in nature. It can only provide an initial general overview and some broad practitioner guidelines over relevant aspects, risks, and issues that typically occur in this context and that KfW deems to be generally of interest and importance when dealing with such types of projects and questions. It does not constitute any form of legal, technical, or other advice and therefore does not purport to replace such legal, technical, or other advice for a specific project or question by a user.
Before entering into any of the activities contemplated in these Fact Sheets, any Fact Sheet user should first seek advice for themselves as they deem necessary and should not solely rely upon the material and information given herein as a basis for making any business, legal, or other decision. Any use of the material or information provided in this Fact Sheet for specific projects is at the user’s own risk.
Due to the general nature of the Fact Sheets, conclusions drawn from them always need to be adjusted to the specific needs and design of the respective project context. KfW can therefore not be held liable for any use and any conclusions drawn from these Fact Sheets.
KfW makes no representation and excludes to the fullest extent permitted by applicable law any responsibility or liability for these Fact Sheets, their content, or any errors or omissions made in the content of these Fact Sheets. The information contained in these Fact Sheets is provided for information purposes only and on an “as is” basis with no guarantees of completeness, accuracy, usefulness, or timeliness.
2022 KfW Development Bank
Palmengartenstrasse 5 – 9
60325 Frankfurt am Main, Germany
Phone: +49 69 7431 0
Fax: +49 69 7431 2944
This work is a product of the staff of KfW Development Bank with external contributions. The findings, interpretations, and conclusions expressed in this work do not necessarily reflect the views of KfW Development Bank, its Board of Executive Directors, or the governments they represent. KfW Development Bank does not guarantee the accuracy of the data included in this work. The boundaries, colors, denominations, and other information shown on any map in this work do not imply any judgment on the part of KfW Development Bank concerning the legal status of any territory or the endorsement or acceptance of such boundaries.
Further contributors can be found here.
Development Monitors LLC, Mainlevel Consulting AG, crisscrossed GmbH, Dentons, CUBE Agentur für Kommunikation.
United Nations University - Institute for Environment and Human Security (UNU-EHS), Urban Futures and Sustainability Transformation Division (climate resilience tools)
English version
French version
This document describes the JSON schema for project_core_schema_en.json.
Title: Project Location Model
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
Description: This schema defines the structure of the project location model. It is used to validate the project location data provided by the KfW counterpart.
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + schemeVersion | No | enum (of string) | No | - | - |
| + activityDescriptionGeneral | No | string | No | - | A short description of the main project activity in this location. |
| - additionalActivityDescription | No | string | No | - | Free text for additional location–specific information. |
| - alternativeLocationTypeName | No | string | No | - | If you selected ‘other physical’ or ‘other immaterial’ in the column ‘Location Type Name’, please propose your own location type name. |
| - budgetShare | No | number | No | - | The budget share allocated to this location in Euros. The sum of all locations in a project should add up to the budget sum in INPRO/PMT, including overheads. Please do not enter data from private entities/PEAs here |
| + dac5PurposeCode | No | enum (of integer) | No | - | The DAC 5 Purpose Codes (1 to 4) for the entire project. This is provided by KfW in the Project Location data collection ToR of by the KfW counterpart. |
| + dataOwner | No | string | No | - | Legal entity that owns the data provided here (= legal authorship). |
| - dateOfDataCollection | No | string | No | - | Date of data collection or latest update. In case only the year is available please choose the 1st of January i.e. YYYY-01-01 |
| - filenameOfAdditionalGeoData | No | string | No | - | Filename of the KML file where the associated geometry information is found. |
| + geographicExactness | No | enum (of string) | No | - | Please use ‘exact’ if the end destination of a financial flow is geographically known, and it is not an administrative unit, and if you do not face security restrictions to do so. Otherwise, please choose ‘approximate (yet unknown)’, ‘approximate (security)’, or ‘approximate (admin unit)’ |
| + sector | No | enum (of string) | No | - | lore ipsum |
| + location_type | No | enum (of string) | No | - | Sectoral / cross-sectoral location type preselection field. / most appropriate location type |
| + kfwProjectNoINPRO | No | string | No | - | Every project location in the FC Geodata Model must be assigned to its respective KfW project number, which is provided by KfW. |
| - locationActivityStatus | No | enum (of string) | No | - | The location activity status according to the IATI standard. |
| + locationName | No | string | No | - | Short name of the project site ideally containing a summary of the main project activity and the location name. |
| + plannedOrActualEndDate | No | string | No | - | Approximate planned or actual end date of activities on the ground. |
| + plannedOrActualStartDate | No | string | No | - | Approximate planned or actual start date of implementation of activities on the ground. |
| - primaryKey | No | string | No | - | This is only required if you provide additional geolocation information in another KML file. |
| - projectAcronym | No | string | No | - | Please enter the acronym used for the name/title of the project to be visible on your map. |
| - projectSpecificLocationIdentifier | No | string | No | - | If the location or activity has a project-specific identifier, it can be entered here. |
| + publishingRestrictions | No | enum (of string) | No | - | Indicates if this information is collected in fragile regions and should therefore be omitted from publicly available reports. |
| - relatedCommunityVillageNeighborhood | No | string | No | - | You may enter a village, hamlet, or neighborhood name that relates to this location. This can serve to manually add smaller community or administrative unit names not identified in existing global databases. |
| - uniqueId | No | string | No | - | For new locations, this column is empty. For updates, your KfW counterpart will provide you with a list of unique_id numbers in this file to ensure that updated location IDs match with the former ones. |
1. Property Project Location Model > schemeVersion
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
2. Property Project Location Model > activityDescriptionGeneral
Description: A short description of the main project activity in this location.
3. Property Project Location Model > additionalActivityDescription
Description: Free text for additional location–specific information.
4. Property Project Location Model > alternativeLocationTypeName
Description: If you selected ‘other physical’ or ‘other immaterial’ in the column ‘Location Type Name’, please propose your own location type name.
5. Property Project Location Model > budgetShare
Description: The budget share allocated to this location in Euros. The sum of all locations in a project should add up to the budget sum in INPRO/PMT, including overheads. Please do not enter data from private entities/PEAs here
6. Property Project Location Model > dac5PurposeCode
| |
|---|
| Type | enum (of integer) |
| Required | Yes |
Description: The DAC 5 Purpose Codes (1 to 4) for the entire project. This is provided by KfW in the Project Location data collection ToR of by the KfW counterpart.
Must be one of:
- 11110
- 11120
- 11130
- 11182
- 11220
- 11230
- 11231
- 11232
- 11240
- 11250
- 11260
- 11320
- 11330
- 11420
- 11430
- 12110
- 12181
- 12182
- 12191
- 12220
- 12230
- 12240
- 12250
- 12261
- 12262
- 12263
- 12264
- 12281
- 12310
- 12320
- 12330
- 12340
- 12350
- 12382
- 13010
- 13020
- 13030
- 13040
- 13081
- 14010
- 14015
- 14020
- 14021
- 14022
- 14030
- 14031
- 14032
- 14040
- 14050
- 14081
- 15110
- 15111
- 15112
- 15113
- 15114
- 15125
- 15130
- 15142
- 15150
- 15151
- 15152
- 15153
- 15160
- 15170
- 15180
- 15190
- 15210
- 15220
- 15230
- 15240
- 15250
- 15261
- 16010
- 16020
- 16030
- 16040
- 16050
- 16061
- 16062
- 16063
- 16064
- 16070
- 16080
- 21010
- 21020
- 21030
- 21040
- 21050
- 21061
- 21081
- 22010
- 22020
- 22030
- 22040
- 23110
- 23181
- 23182
- 23183
- 23210
- 23220
- 23230
- 23231
- 23232
- 23240
- 23250
- 23260
- 23270
- 23310
- 23320
- 23330
- 23340
- 23350
- 23360
- 23410
- 23510
- 23610
- 23620
- 23630
- 23631
- 23640
- 23641
- 23642
- 24010
- 24020
- 24030
- 24040
- 24050
- 24081
- 25010
- 25020
- 25030
- 25040
- 31110
- 31120
- 31130
- 31140
- 31150
- 31161
- 31162
- 31163
- 31164
- 31165
- 31166
- 31181
- 31182
- 31191
- 31192
- 31193
- 31194
- 31195
- 31210
- 31220
- 31261
- 31281
- 31282
- 31291
- 31310
- 31320
- 31381
- 31382
- 31391
- 32110
- 32120
- 32130
- 32140
- 32161
- 32162
- 32163
- 32164
- 32165
- 32166
- 32167
- 32168
- 32169
- 32170
- 32171
- 32172
- 32173
- 32174
- 32182
- 32210
- 32220
- 32261
- 32262
- 32263
- 32264
- 32265
- 32266
- 32267
- 32268
- 32310
- 33110
- 33120
- 33130
- 33140
- 33150
- 33181
- 33210
- 41010
- 41020
- 41030
- 41040
- 41081
- 41082
- 43010
- 43030
- 43040
- 43050
- 43060
- 43071
- 43072
- 43073
- 43081
- 43082
- 51010
- 52010
- 53030
- 53040
- 60010
- 60020
- 60030
- 60040
- 60061
- 60062
- 60063
- 72010
- 72040
- 72050
- 73010
- 74020
- 91010
- 93010
- 99810
- 99820
7. Property Project Location Model > dataOwner
Description: Legal entity that owns the data provided here (= legal authorship).
8. Property Project Location Model > dateOfDataCollection
| |
|---|
| Type | string |
| Required | No |
| Format | date |
Description: Date of data collection or latest update. In case only the year is available please choose the 1st of January i.e. YYYY-01-01
9. Property Project Location Model > filenameOfAdditionalGeoData
Description: Filename of the KML file where the associated geometry information is found.
10. Property Project Location Model > geographicExactness
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Please use ‘exact’ if the end destination of a financial flow is geographically known, and it is not an administrative unit, and if you do not face security restrictions to do so. Otherwise, please choose ‘approximate (yet unknown)’, ‘approximate (security)’, or ‘approximate (admin unit)’
Must be one of:
- “exact”
- “approximate (yet unknown)”
- “approximate (security)”
- “approximate (admin unit)”
11. Property Project Location Model > sector
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: lore ipsum
Must be one of:
- “_Generic / Cross_Sectoral”
- “Agriculture / Rural_Development”
- “Aquaculture / Fishery”
- “Education”
- “Energy”
- “Financial_Sector_Development”
- “Governance / Decentralization”
- “Health”
- “Marine_Natural_Resources_Protection”
- “Mobility / Transport”
- “Peace / Displacement / Fragility”
- “Social_Protection”
- “Terrestrial_Natural_Resources_Protection”
- “Urban_Infrastructure”
- “Waster”
- “Water_Management”
12. Property Project Location Model > location_type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Sectoral / cross-sectoral location type preselection field. / most appropriate location type
Must be one of:
- “building(s)”
- “common / public community area”
- “equipment / materials distribution area”
- “facility”
- “factory”
- “housing (development)”
- “hub /cluster / incubator”
- “ICT-infrastructure / ICT-equipment”
- “micro, small & medium enterprises (MSME)”
- “ministry”
- “museum”
- “office building”
- “other physical”
- “other immaterial”
- “rehabilitation / reconstruction”
- “research institute / facility”
- “advisory facility support”
- “capacity development / training”
- “civil society support”
- “digital services usage area”
- “early warning system”
- “environmental & social mgt system”
- “income generating activities (IGA)”
- “insurance (other)”
- “matching grants distribution area”
- “political / institutional reforms (PBF / PBL)”
- “public / social dialogue”
- “saving groups / VSLA / SACCOs support”
- “sensitization / awareness raising (campaign)”
- “socio-economic rehabilitation / recovery”
- “supply chains (support) area”
- “voucher(s) (system) distributrion area”
- “(smallholder) farm area(s)”
- “(tree) plantation area”
- “agricultural facility”
- “certified agriculture area”
- “cultivated area”
- “garden(s)”
- “grazing area”
- “improved soil / erosion control area”
- “irrigated field(s)”
- “irrigation infrastructure”
- “nursery(-ies)”
- “post harvest processing & value addition”
- “restored / rehabilitated land area”
- “weir(s)”
- “agricultural extension services”
- “contract farming / PPP”
- “farmers groups / cooperatives support”
- “aquaculture area”
- “certified sustainable aquaculture or fisheries (MSC, ASC)”
- “coastguard station”
- “FAO catch-area”
- “feed-mill”
- “inland waters fishery”
- “pond “
- “school (primary, secondary, college)”
- “TVET school / infrastructure”
- “university”
- “scholarship program area”
- “area covered by off-grid renewable energy (ex. photovoltaic grid)”
- “area covered by on-grid renewable energy “
- “biogas plant”
- “electric power transmission & distribution (T&D)”
- “electric substation”
- “energy efficiency measure(s)”
- “geothermal power plant”
- “hydrogen plant”
- “hydropower plant / dam”
- “solar power plant”
- “solar water pump”
- “wind power plant”
- “district heating area / distribution”
- “battery energy storage system (BESS)”
- “bank”
- “banking branch / outlet”
- “company”
- “credit guarantee fund”
- “financial institution”
- “fonds manager headquarter”
- “free trade zone “
- “industrial area / zone”
- “microfinance institution (MFI)”
- “bonds”
- “guarantees”
- “loans”
- “subordinated loans”
- “ ICT infrastructure (broadband / connectivity)“
- “ ICT infrastructure (data center)“
- “(communal) public infrastructure”
- “(communal) public office”
- “citizen service center”
- “customs office”
- “fire station”
- “media support”
- “public (admin) training institute”
- “violence prevention”
- “cadastre / land management / tenure system / area”
- “citizen participation / feedback (system)”
- “decentralisation support & communal development”
- “democratization support”
- “digital transformation of public services”
- “domestic revenue mobilization”
- “intergovernmental fiscal transfer mechanism”
- “public financial management (PFM)”
- “clinic”
- “dispensary”
- “health post”
- “hospital”
- “laboratory”
- “medical isolation station”
- “medical products development”
- “distribution of medical products / contraceptives”
- “social franchising / NGO clinics”
- “social marketing”
- “coast”
- “coral reef”
- “exclusive economic zone (EEZ)”
- “kelp-forest”
- “mangroves”
- “marine protected area (MPA)”
- “no-take-zone”
- “seagrass-meadow”
- “small scale fisheries (SSF) zone”
- “airplane(s)”
- “airport”
- “aviation safety system / flight control”
- “boats / boat yard”
- “bridge “
- “bus rapid transit (BRT) / bus system”
- “buses”
- “electric / diesel multiple unit (DMU/EMU)”
- “ferry (line, system)”
- “freight waggons”
- “heavy rail system”
- “highway”
- “intermodal passenger hub”
- “light rail transit system”
- “locomotives / trains”
- “marshelling yard”
- “multimodal terminal / logistic node”
- “other road based-vehicles”
- “passenger coaches”
- “pedestrian lane(s) / bike lane(s)”
- “port”
- “rail infrastructure interurban”
- “rail infrastructure intraurban”
- “rail operation control system / intelligent transport system (ITS)”
- “rail station”
- “railroad”
- “road”
- “rural road(s)”
- “subway (system)”
- “terminal (within port)”
- “traffic management center / ITS”
- “tramway (system)”
- “warehouse / logistics center”
- “waterway(s) (system)”
- “bus station”
- “camp(s)”
- “emergency supplies distribution area”
- “food access point”
- “internally displaced persons (IDP) camp”
- “refugee camp “
- “community policing”
- “disarmament, demobilisation, reintegration of combatants (DDR)”
- “election support”
- “reparation payments”
- “women’s shelter / GBV support”
- “basic social services”
- “cash- / food-for-work”
- “cash transfers”
- “climate risk insurance”
- “social protection system”
- “employment subsidies”
- “agrobiodiversity area”
- “agroecology area”
- “agroforestry area”
- “certified sustainable forest management (FSC, Rainforest Alliance, PEFC)”
- “coastal protection area”
- “corridor / ecosystem connectivity”
- “deforestation (area)”
- “forest station”
- “forest(s)”
- “glacier(s)”
- “grassland”
- “habitat or species management area (IUCN Cat IV)”
- “indigenous & community conservation area (ICCA)”
- “indigenous peoples & local communities (IP&LC)”
- “lake”
- “national park (IUCN Cat II)”
- “natural monument or feature (IUCN Cat III)”
- “ocean”
- “protected area with sustainable use of natural resources (IUCN Cat VI)”
- “protected farmland area”
- “protected landscape or seascape (IUCN Cat V)”
- “ranger station”
- “re- / afforestation area”
- “regeneration / restoration / rehabilition area”
- “renaturation of water bodies”
- “scrubland”
- “sea”
- “seed bank”
- “strict nature reserve (IUCN Cat Ia)”
- “swamp”
- “tribal area”
- “watercourse”
- “watershed”
- “wilderness area (IUCN Cat Ib)”
- “area under payment for environmental services / incentive system”
- “other effective area-based conservation measures (OECM)”
- “(urban) street”
- “city district / urban development”
- “market (shopping area)”
- “parcs & other green areas”
- “public space(s)”
- “shopping center or mall”
- “slum upgrading”
- “street lightning”
- “composting plant”
- “fermentation plant”
- “improved waste collection”
- “landfill”
- “landfill gas capture and treatment”
- “mechanical-biological treatment plant”
- “other waste treatment plants”
- “transfer station”
- “waste sorting plant”
- “waste-to-energy plant”
- “decentralized water supply”
- “desalination plant”
- “dezentralized sanitation (area)”
- “drinking water network”
- “drinking water pump station”
- “drinking water transport pipeline”
- “drinking water treatment plant (without desalination)”
- “flood protection”
- “reservoir(s) “
- “sanitary facility”
- “sewage treatment plant”
- “sewer network”
- “sewer pump station”
- “sludge treatment & disposal”
- “stormwater network / system”
- “wastewater pipeline”
- “water intake”
- “water re-use”
- “water storage infrastructure”
- “water tank”
- “well”
- “hydro-meteorological measurement system”
- “water resources protection area”
13. Property Project Location Model > kfwProjectNoINPRO
Description: Every project location in the FC Geodata Model must be assigned to its respective KfW project number, which is provided by KfW.
14. Property Project Location Model > locationActivityStatus
| |
|---|
| Type | enum (of string) |
| Required | No |
Description: The location activity status according to the IATI standard.
Must be one of:
- “NA”
- “Pipeline/identification”
- “Implementation”
- “Finalisation”
- “Closed”
- “Cancelled”
- “Suspended”
- “Other”
15. Property Project Location Model > locationName
Description: Short name of the project site ideally containing a summary of the main project activity and the location name.
16. Property Project Location Model > plannedOrActualEndDate
| |
|---|
| Type | string |
| Required | Yes |
| Format | date |
Description: Approximate planned or actual end date of activities on the ground.
17. Property Project Location Model > plannedOrActualStartDate
| |
|---|
| Type | string |
| Required | Yes |
| Format | date |
Description: Approximate planned or actual start date of implementation of activities on the ground.
18. Property Project Location Model > primaryKey
Description: This is only required if you provide additional geolocation information in another KML file.
19. Property Project Location Model > projectAcronym
Description: Please enter the acronym used for the name/title of the project to be visible on your map.
20. Property Project Location Model > projectSpecificLocationIdentifier
Description: If the location or activity has a project-specific identifier, it can be entered here.
21. Property Project Location Model > publishingRestrictions
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Indicates if this information is collected in fragile regions and should therefore be omitted from publicly available reports.
Must be one of:
Description: You may enter a village, hamlet, or neighborhood name that relates to this location. This can serve to manually add smaller community or administrative unit names not identified in existing global databases.
23. Property Project Location Model > uniqueId
Description: For new locations, this column is empty. For updates, your KfW counterpart will provide you with a list of unique_id numbers in this file to ensure that updated location IDs match with the former ones.
Generated using json-schema-for-humans on 2026-01-13 at 12:37:05 +0000
This document describes the JSON schema for project_core_schema_fr.json.
Title: Modèle de Localisation des Projets
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
Description: Ce schéma définit la structure du modèle de sites des projet. Il sert à valider les données de sites du projet fournies par le partenaire KfW.
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + schemeVersion | No | enum (of string) | No | - | - |
| + activityDescriptionGeneral | No | string | No | - | Une brève description de l’activité principale du projet sur ce site. |
| - additionalActivityDescription | No | string | No | - | Texte libre pour des informations supplémentaires spécifiques au site. |
| - alternativeLocationTypeName | No | string | No | - | Si vous avez sélectionné ‘autre physique’ ou ‘autre immatériel’ dans la colonne ‘Nom du type de site’, veuillez proposer votre propre nom de type de site. |
| - budgetShare | No | number | No | - | La part du budget allouée à ce site en €. |
| + dac5PurposeCode | No | enum (of integer) | No | - | Les codes CAD 5 assignés à l’ensemble du projet. |
| + dataOwner | No | string | No | - | Entité juridique qui possède les données fournies ici (= droit d’auteur légal). |
| - dateOfDataCollection | No | string | No | - | Date de collecte des données ou de la dernière mise à jour. |
| - filenameOfAdditionalGeoData | No | string | No | - | Nom du fichier KML contenant les informations géométriques associées. |
| + geographicExactness | No | enum (of string) | No | - | Veuillez utiliser ‘exacte’ si vous connaissez la destination finale géographique exacte d’un flux financier. |
| + sector | No | enum (of string) | No | - | lore ipsum |
| - location_type | No | enum (of string) | No | - | Champ de présélection du type de localisation Secteurs / Sous-secteurs. / type de localisation le plus approprié. |
| + kfwProjectNoINPRO | No | string | No | - | Chaque site du projet dans le modèle de géodonnées FC doit être attribué à son numéro de projet KfW respectif, qui est fourni par la KfW. |
| - locationActivityStatus | No | enum (of string) | No | - | La phase de réalisation de l’activité selon la norme IATI. |
| + locationName | No | string | No | - | Nom court du site, incluant idéalement un résumé de l’activité principale et le nom du lieu. |
| + plannedOrActualEndDate | No | string | No | - | Date de fin approximative prévue ou réelle des activités sur le site. |
| + plannedOrActualStartDate | No | string | No | - | Date de début approximative prévue ou réelle de la mise en œuvre des activités sur le site. |
| - primaryKey | No | string | No | - | Ceci n’est requis que si vous fournissez des informations de géolocalisation supplémentaires dans un autre fichier KML. |
| - projectAcronym | No | string | No | - | Veuillez entrer l’acronyme utilisé pour le nom/titre du projet afin qu’il soit visible sur votre carte. |
| - projectSpecificLocationIdentifier | No | object | No | - | Si le site ou l’activité a un identifiant spécifique au projet, il peut être saisi ici. |
| + publishingRestrictions | No | enum (of string) | No | - | Indique si ces informations sont collectées dans des régions fragiles et doivent donc être omises des rapports accessibles au public. |
| - relatedCommunityVillageNeighborhood | No | string | No | - | Vous pouvez saisir le nom d’un village, d’un hameau ou d’un quartier lié à ce site. |
| - uniqueId | No | string | No | - | Pour les nouveaux sites, cette colonne reste vide. Pour les mises à jour, votre partenaire KfW fournira une liste de numéros unique_id afin d’assurer la correspondance avec les identifiants précédents. |
1. The following properties are required
2. Property Modèle de Localisation des Projets > schemeVersion
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
3. Property Modèle de Localisation des Projets > activityDescriptionGeneral
Description: Une brève description de l’activité principale du projet sur ce site.
4. Property Modèle de Localisation des Projets > additionalActivityDescription
Description: Texte libre pour des informations supplémentaires spécifiques au site.
5. Property Modèle de Localisation des Projets > alternativeLocationTypeName
Description: Si vous avez sélectionné ‘autre physique’ ou ‘autre immatériel’ dans la colonne ‘Nom du type de site’, veuillez proposer votre propre nom de type de site.
6. Property Modèle de Localisation des Projets > budgetShare
Description: La part du budget allouée à ce site en €.
7. Property Modèle de Localisation des Projets > dac5PurposeCode
| |
|---|
| Type | enum (of integer) |
| Required | Yes |
Description: Les codes CAD 5 assignés à l’ensemble du projet.
Must be one of:
- 11110
- 11120
- 11130
- 11182
- 11220
- 11230
- 11231
- 11232
- 11240
- 11250
- 11260
- 11320
- 11330
- 11420
- 11430
- 12110
- 12181
- 12182
- 12191
- 12220
- 12230
- 12240
- 12250
- 12261
- 12262
- 12263
- 12264
- 12281
- 12310
- 12320
- 12330
- 12340
- 12350
- 12382
- 13010
- 13020
- 13030
- 13040
- 13081
- 14010
- 14015
- 14020
- 14021
- 14022
- 14030
- 14031
- 14032
- 14040
- 14050
- 14081
- 15110
- 15111
- 15112
- 15113
- 15114
- 15125
- 15130
- 15142
- 15150
- 15151
- 15152
- 15153
- 15160
- 15170
- 15180
- 15190
- 15210
- 15220
- 15230
- 15240
- 15250
- 15261
- 16010
- 16020
- 16030
- 16040
- 16050
- 16061
- 16062
- 16063
- 16064
- 16070
- 16080
- 21010
- 21020
- 21030
- 21040
- 21050
- 21061
- 21081
- 22010
- 22020
- 22030
- 22040
- 23110
- 23181
- 23182
- 23183
- 23210
- 23220
- 23230
- 23231
- 23232
- 23240
- 23250
- 23260
- 23270
- 23310
- 23320
- 23330
- 23340
- 23350
- 23360
- 23410
- 23510
- 23610
- 23620
- 23630
- 23631
- 23640
- 23641
- 23642
- 24010
- 24020
- 24030
- 24040
- 24050
- 24081
- 25010
- 25020
- 25030
- 25040
- 31110
- 31120
- 31130
- 31140
- 31150
- 31161
- 31162
- 31163
- 31164
- 31165
- 31166
- 31181
- 31182
- 31191
- 31192
- 31193
- 31194
- 31195
- 31210
- 31220
- 31261
- 31281
- 31282
- 31291
- 31310
- 31320
- 31381
- 31382
- 31391
- 32110
- 32120
- 32130
- 32140
- 32161
- 32162
- 32163
- 32164
- 32165
- 32166
- 32167
- 32168
- 32169
- 32170
- 32171
- 32172
- 32173
- 32174
- 32182
- 32210
- 32220
- 32261
- 32262
- 32263
- 32264
- 32265
- 32266
- 32267
- 32268
- 32310
- 33110
- 33120
- 33130
- 33140
- 33150
- 33181
- 33210
- 41010
- 41020
- 41030
- 41040
- 41081
- 41082
- 43010
- 43030
- 43040
- 43050
- 43060
- 43071
- 43072
- 43073
- 43081
- 43082
- 51010
- 52010
- 53030
- 53040
- 60010
- 60020
- 60030
- 60040
- 60061
- 60062
- 60063
- 72010
- 72040
- 72050
- 73010
- 74020
- 91010
- 93010
- 99810
- 99820
8. Property Modèle de Localisation des Projets > dataOwner
Description: Entité juridique qui possède les données fournies ici (= droit d’auteur légal).
9. Property Modèle de Localisation des Projets > dateOfDataCollection
| |
|---|
| Type | string |
| Required | No |
| Format | date |
Description: Date de collecte des données ou de la dernière mise à jour.
10. Property Modèle de Localisation des Projets > filenameOfAdditionalGeoData
Description: Nom du fichier KML contenant les informations géométriques associées.
11. Property Modèle de Localisation des Projets > geographicExactness
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Veuillez utiliser ‘exacte’ si vous connaissez la destination finale géographique exacte d’un flux financier.
Must be one of:
- “exacte”
- “approximative (encore inconnue)”
- “approximative (sécurité)”
- “approximative (unité d’administration)”
12. Property Modèle de Localisation des Projets > sector
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: lore ipsum
Must be one of:
- “_Générique_Intersectoriel”
- “Agriculture_Développement_rural”
- “Aquaculture_Pêche”
- “Éducation”
- “Énergie”
- “Développement_secteur_financier”
- “Gouvernance_Décentralisation”
- “Santé”
- “Protection_des_ressources_naturelles_marines”
- “Mobilité_Transport”
- “Paix_Déplacement_Fragilité”
- “Protection_sociale”
- “Protection_des_ressources_naturelles_terrestres”
- “Infrastructure_urbaine”
- “Déchets”
- “Gestion_de_l’eau”
13. Property Modèle de Localisation des Projets > location_type
| |
|---|
| Type | enum (of string) |
| Required | No |
Description: Champ de présélection du type de localisation Secteurs / Sous-secteurs. / type de localisation le plus approprié.
Must be one of:
- “bâtiment(s)”
- “zone commune / espace public”
- “zone de distribution des équipements / matériels”
- “installation”
- “usine”
- “(développement du) logement”
- “hub / cluster / incubateur”
- “infrastructure TIC / équipement TIC”
- “micro, petites et moyennes entreprises (MPME)”
- “ministère”
- “musée”
- “bureau”
- “autre physique”
- “autre immatériel”
- “réhabilitation / reconstruction”
- “institut de recherche”
- “(soutien par) cabinet de conseil”
- “développement des capacités / formation”
- “soutien à la société civile”
- “zone d’utilisation des services numériques”
- “système d’alerte précoce”
- “système de gestion environnementale et sociale”
- “activités génératrices de revenus (AGR)”
- “assurance (autre)”
- “zone de distribution des subventions de contrepartie”
- “réformes politiques / institutionnelles (PBF / PBL)”
- “dialogue public / social”
- “soutien aux groupes d’épargne / VSLA / SACCO”
- “sensibilisation / prise de conscience (campagne)”
- “réhabilitation / reprise socio-économique”
- “zone des chaînes d’approvisionnement (soutien)”
- “zone de distribution du (des) bon(s) (système)”
- “petite exploitation agricole”
- “zone de plantation (arbre)”
- “installation agricole”
- “zone agricole certifiée”
- “surface cultivée”
- “jardin(s)”
- “zone de pâturage”
- “zone de contrôle du sol / de l’érosion améliorée”
- “champ(s) irrigué(s)”
- “infrastructure d’irrigation”
- “pépinière(s)”
- “traitement post-récolte et valeur ajoutée”
- “zone de terre restaurée / réhabilitée”
- “barrage(s)”
- “services de vulgarisation agricole”
- “agriculture contractuelle / PPP”
- “soutien aux groupes / coopératives d’agriculteurs”
- “zone d’aquaculture”
- “aquaculture ou pêche durable certifiée (MSC, ASC)”
- “poste de garde-côtes”
- “zone de capture FAO”
- “usine de production d’aliments”
- “pêche en eaux intérieures”
- “étang”
- “école (primaire, secondaire, collège)”
- “école / infrastructure EFTP”
- “université”
- “zone du programme de bourses”
- “zone couverte par une énergie renouvelable hors réseau (ex. réseau photovoltaïque)”
- “zone couverte par une énergie renouvelable sur réseau”
- “usine de biogaz”
- “transport et distribution d’électricité (T&D)”
- “sous-station électrique”
- “mesure(s) d’efficacité énergétique”
- “centrale géothermique”
- “usine d’hydrogène”
- “centrale hydroélectrique / barrage”
- “centrale solaire”
- “pompe à eau solaire”
- “parc éolien”
- “zone / distribution de chauffage urbain”
- “système de stockage d’énergie par batterie (BESS)”
- “banque”
- “succursale / agence bancaire”
- “entreprise”
- “fonds de garantie de crédit”
- “institution financière”
- “siège du gestionnaire de fonds”
- “zone franche”
- “zone / zone industrielle”
- “institution de microfinance (IMF)”
- “obligations”
- “garanties”
- “prêts”
- “prêts subordonnés”
- “infrastructure TIC (haut débit / connectivité)”
- “infrastructure TIC (centre de données)”
- “infrastructure publique (communale)”
- “bureau public (communal)”
- “centre de service aux citoyens”
- “bureau de douane”
- “caserne de pompiers”
- “soutien aux médias”
- “institut de formation publique (admin)”
- “prévention de la violence”
- “cadastre / gestion foncière / système de tenure / zone”
- “participation / retour d’information citoyenne (système)”
- “soutien à la décentralisation et développement communal”
- “soutien à la démocratisation”
- “transformation numérique des services publics”
- “mobilisation des revenus intérieurs”
- “mécanisme de transfert fiscal intergouvernemental”
- “gestion des finances publiques (GFP)”
- “clinique”
- “dispensaire”
- “poste de santé”
- “hôpital”
- “laboratoire”
- “station d’isolement médical”
- “développement de produits médicaux”
- “distribution de produits médicaux / contraceptifs”
- “franchise sociale / cliniques ONG”
- “marketing social”
- “côte”
- “récif corallien”
- “zone économique exclusive (ZEE)”
- “forêt de varech”
- “mangroves”
- “zone marine protégée (ZMP)”
- “zone interdite à la pêche”
- “herbier marin”
- “zone de pêche artisanale (SSF)”
- “avion(s)”
- “aéroport”
- “système de sécurité aérienne / contrôle de vol”
- “bateaux / chantier naval”
- “pont”
- “transport en commun rapide par bus (BRT) / système de bus”
- “bus”
- “rame électrique / diesel (DMU/EMU)”
- “ferry (ligne, système)”
- “wagons de fret”
- “système ferroviaire lourd”
- “autoroute”
- “hub intermodal pour passagers”
- “système de métro léger”
- “locomotives / trains”
- “gare de triage”
- “terminal multimodal / nœud logistique”
- “autres véhicules routiers”
- “voitures de passagers”
- “voie(s) piétonne(s) / piste(s) cyclable(s)”
- “port”
- “infrastructure ferroviaire interurbaine”
- “infrastructure ferroviaire intra-urbaine”
- “système de contrôle des opérations ferroviaires / système de transport intelligent (ITS)”
- “gare ferroviaire”
- “chemin de fer”
- “route”
- “route(s) rurale(s)”
- “métro (système)”
- “terminal (dans le port)”
- “centre de gestion du trafic / ITS”
- “tramway (système)”
- “entrepôt / centre logistique”
- “voie(s) navigable(s) (système)”
- “gare routière”
- “camp(s)”
- “zone de distribution des fournitures d’urgence”
- “point d’accès alimentaire”
- “camp de personnes déplacées internes (PDI)”
- “camp de réfugiés”
- “police communautaire”
- “désarmement, démobilisation, réintégration des combattants (DDR)”
- “soutien électoral”
- “paiements de réparation”
- “refuge pour femmes / soutien VBG”
- “services sociaux de base”
- “argent / nourriture contre travail”
- “transferts en espèces”
- “assurance contre les risques climatiques”
- “système de protection sociale”
- “subventions à l’emploi”
- “zone d’agrobiodiversité”
- “zone d’agroécologie”
- “zone d’agroforesterie”
- “gestion durable certifiée des forêts (FSC, Rainforest Alliance, PEFC)”
- “zone de protection côtière”
- “corridor / connectivité des écosystèmes”
- “déforestation (zone)”
- “station forestière”
- “forêt(s)”
- “glacier(s)”
- “prairie”
- “zone de gestion d’habitat ou d’espèces (UICN Cat IV)”
- “zone de conservation autochtone et communautaire (ICCA)”
- “peuples autochtones et communautés locales (IP&LC)”
- “lac”
- “parc national (UICN Cat II)”
- “monument ou élément naturel (UICN Cat III)”
- “océan”
- “zone protégée avec utilisation durable des ressources naturelles (UICN Cat VI)”
- “zone agricole protégée”
- “paysage ou paysage marin protégé (UICN Cat V)”
- “poste de garde forestier”
- “zone de re- / afforestation”
- “zone de régénération / restauration / réhabilitation”
- “renaturation des plans d’eau”
- “broussailles”
- “mer”
- “banque de semences”
- “réserve naturelle intégrale (UICN Cat Ia)”
- “marais”
- “zone tribale”
- “cours d’eau”
- “bassin versant”
- “zone de nature sauvage (UICN Cat Ib)”
- “zone sous paiement pour services environnementaux / système d’incitation”
- “autres mesures de conservation efficaces par zone (OECM)”
- “rue (urbaine)”
- “quartier urbain / développement urbain”
- “marché (zone commerciale)”
- “parcs et autres espaces verts”
- “espace(s) public(s)”
- “centre commercial ou galerie marchande”
- “amélioration des bidonvilles”
- “éclairage public”
- “usine de compostage”
- “usine de fermentation”
- “collecte améliorée des déchets”
- “décharge”
- “capture et traitement des gaz de décharge”
- “usine de traitement mécano-biologique”
- “autres usines de traitement des déchets”
- “station de transfert”
- “usine de tri des déchets”
- “usine de valorisation énergétique des déchets”
- “approvisionnement en eau décentralisé”
- “usine de dessalement”
- “assainissement décentralisé (zone)”
- “réseau d’eau potable”
- “station de pompage d’eau potable”
- “pipeline de transport d’eau potable”
- “usine de traitement d’eau potable (sans dessalement)”
- “protection contre les inondations”
- “réservoir(s)”
- “installation sanitaire”
- “station d’épuration des eaux usées”
- “réseau d’égouts”
- “station de pompage des égouts”
- “traitement et élimination des boues”
- “réseau / système d’eaux pluviales”
- “pipeline d’eaux usées”
- “prise d’eau”
- “réutilisation de l’eau”
- “infrastructure de stockage d’eau”
- “réservoir d’eau”
- “puits”
- “système de mesure hydrométéorologique”
- “zone de protection des ressources en eau”
14. Property Modèle de Localisation des Projets > kfwProjectNoINPRO
Description: Chaque site du projet dans le modèle de géodonnées FC doit être attribué à son numéro de projet KfW respectif, qui est fourni par la KfW.
15. Property Modèle de Localisation des Projets > locationActivityStatus
| |
|---|
| Type | enum (of string) |
| Required | No |
Description: La phase de réalisation de l’activité selon la norme IATI.
Must be one of:
- “Ne s’applique pas (NA)”
- “Identification”
- “Exécution”
- “Finalisation”
- “Terminé”
- “Annulé”
- “Suspendu”
- “Divers”
16. Property Modèle de Localisation des Projets > locationName
Description: Nom court du site, incluant idéalement un résumé de l’activité principale et le nom du lieu.
17. Property Modèle de Localisation des Projets > plannedOrActualEndDate
| |
|---|
| Type | string |
| Required | Yes |
| Format | date |
Description: Date de fin approximative prévue ou réelle des activités sur le site.
18. Property Modèle de Localisation des Projets > plannedOrActualStartDate
| |
|---|
| Type | string |
| Required | Yes |
| Format | date |
Description: Date de début approximative prévue ou réelle de la mise en œuvre des activités sur le site.
19. Property Modèle de Localisation des Projets > primaryKey
Description: Ceci n’est requis que si vous fournissez des informations de géolocalisation supplémentaires dans un autre fichier KML.
20. Property Modèle de Localisation des Projets > projectAcronym
Description: Veuillez entrer l’acronyme utilisé pour le nom/titre du projet afin qu’il soit visible sur votre carte.
21. Property Modèle de Localisation des Projets > projectSpecificLocationIdentifier
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
Description: Si le site ou l’activité a un identifiant spécifique au projet, il peut être saisi ici.
22. Property Modèle de Localisation des Projets > publishingRestrictions
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Indique si ces informations sont collectées dans des régions fragiles et doivent donc être omises des rapports accessibles au public.
Must be one of:
Description: Vous pouvez saisir le nom d’un village, d’un hameau ou d’un quartier lié à ce site.
24. Property Modèle de Localisation des Projets > uniqueId
Description: Pour les nouveaux sites, cette colonne reste vide. Pour les mises à jour, votre partenaire KfW fournira une liste de numéros unique_id afin d’assurer la correspondance avec les identifiants précédents.
Generated using json-schema-for-humans on 2026-01-13 at 12:37:05 +0000
This document describes the JSON schema for feature_project_schema.json.
Title: GeoJSON Feature
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
Description: Main Schema with geometries and project_core_schema_en.md or project_core_schema_fr.md properties. It is built hierarchially and is represented as Feature - a known Geojson Format.
In the properties are all the project information which is separated from the geometry.
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| - id | No | Combination | No | - | - |
| + properties | No | object | No | In project_core_schema.json | 😅 ERROR in schema generation, a referenced schema could not be loaded, no documentation here unfortunately 🏜️ |
| + geometry | No | Combination | No | - | - |
| - bbox | No | array of number | No | - | - |
1. Property GeoJSON Feature > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
2. Property GeoJSON Feature > id
| |
|---|
| Type | combining |
| Required | No |
| Additional properties | Any type allowed |
2.1. Property GeoJSON Feature > id > oneOf > item 0
2.2. Property GeoJSON Feature > id > oneOf > item 1
3. Property GeoJSON Feature > properties
| |
|---|
| Type | object |
| Required | Yes |
| Additional properties | Any type allowed |
| Defined in | project_core_schema.json |
Description: 😅 ERROR in schema generation, a referenced schema could not be loaded, no documentation here unfortunately 🏜️
4. Property GeoJSON Feature > geometry
| |
|---|
| Type | combining |
| Required | Yes |
| Additional properties | Any type allowed |
4.1. Property GeoJSON Feature > geometry > oneOf > item 0
4.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON Point
Title: GeoJSON Point
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.2.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON Point > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.2.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON Point > coordinates
| Array restrictions |
|---|
| Min items | 2 |
| Max items | 2 |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.2.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON Point > coordinates > coordinates item 0
| Restrictions | |
|---|
| Minimum | ≥ -180 |
| Maximum | ≤ 180 |
4.2.2.2. GeoJSON Feature > geometry > oneOf > GeoJSON Point > coordinates > coordinates item 1
| Restrictions | |
|---|
| Minimum | ≥ -90 |
| Maximum | ≤ 90 |
4.2.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON Point > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.2.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON Point > bbox > bbox items
4.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON LineString
Title: GeoJSON LineString
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.3.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON LineString > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.3.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON LineString > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.3.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON LineString > coordinates > coordinates items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.3.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON LineString > coordinates > coordinates items > coordinates items items
4.3.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON LineString > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.3.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON LineString > bbox > bbox items
4.4. Property GeoJSON Feature > geometry > oneOf > GeoJSON Polygon
Title: GeoJSON Polygon
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.4.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON Polygon > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.4.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON Polygon > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.4.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON Polygon > coordinates > coordinates items
| |
|---|
| Type | array of array |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.4.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON Polygon > coordinates > coordinates items > coordinates items items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.4.2.1.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON Polygon > coordinates > coordinates items > coordinates items items > coordinates items items items
4.4.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON Polygon > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.4.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON Polygon > bbox > bbox items
4.5. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiPoint
Title: GeoJSON MultiPoint
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.5.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiPoint > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.5.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiPoint > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.5.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiPoint > coordinates > coordinates items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.5.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiPoint > coordinates > coordinates items > coordinates items items
4.5.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiPoint > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.5.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiPoint > bbox > bbox items
4.6. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiLineString
Title: GeoJSON MultiLineString
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.6.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiLineString > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.6.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiLineString > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.6.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiLineString > coordinates > coordinates items
| |
|---|
| Type | array of array |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.6.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiLineString > coordinates > coordinates items > coordinates items items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.6.2.1.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiLineString > coordinates > coordinates items > coordinates items items > coordinates items items items
4.6.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiLineString > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.6.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiLineString > bbox > bbox items
4.7. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon
Title: GeoJSON MultiPolygon
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.7.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.7.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.7.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon > coordinates > coordinates items
| |
|---|
| Type | array of array |
| Required | No |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.7.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon > coordinates > coordinates items > coordinates items items
| |
|---|
| Type | array of array |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.7.2.1.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon > coordinates > coordinates items > coordinates items items > coordinates items items items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.7.2.1.1.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon > coordinates > coordinates items > coordinates items items > coordinates items items items > coordinates items items items items
4.7.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.7.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON MultiPolygon > bbox > bbox items
4.8. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection
Title: GeoJSON GeometryCollection
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + geometries | No | array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.8.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.8.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items
| |
|---|
| Type | combining |
| Required | No |
| Additional properties | Any type allowed |
4.8.2.1.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Point
Title: GeoJSON Point
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of number | No | - | - |
| - bbox | No | array of number | No | - | - |
4.8.2.1.1.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Point > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.8.2.1.1.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Point > coordinates
| |
|---|
| Type | array of number |
| Required | Yes |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.1.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Point > coordinates > coordinates items
4.8.2.1.1.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Point > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.8.2.1.1.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Point > bbox > bbox items
4.8.2.1.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON LineString
Title: GeoJSON LineString
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.8.2.1.2.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON LineString > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.8.2.1.2.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON LineString > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.2.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON LineString > coordinates > coordinates items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.2.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON LineString > coordinates > coordinates items > coordinates items items
4.8.2.1.2.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON LineString > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.8.2.1.2.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON LineString > bbox > bbox items
4.8.2.1.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Polygon
Title: GeoJSON Polygon
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.8.2.1.3.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Polygon > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.8.2.1.3.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Polygon > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.3.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Polygon > coordinates > coordinates items
| |
|---|
| Type | array of array |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.3.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Polygon > coordinates > coordinates items > coordinates items items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.3.2.1.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Polygon > coordinates > coordinates items > coordinates items items > coordinates items items items
4.8.2.1.3.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Polygon > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.8.2.1.3.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON Polygon > bbox > bbox items
4.8.2.1.4. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPoint
Title: GeoJSON MultiPoint
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.8.2.1.4.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPoint > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.8.2.1.4.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPoint > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.4.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPoint > coordinates > coordinates items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.4.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPoint > coordinates > coordinates items > coordinates items items
4.8.2.1.4.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPoint > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.8.2.1.4.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPoint > bbox > bbox items
4.8.2.1.5. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiLineString
Title: GeoJSON MultiLineString
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.8.2.1.5.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiLineString > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.8.2.1.5.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiLineString > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.5.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiLineString > coordinates > coordinates items
| |
|---|
| Type | array of array |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.5.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiLineString > coordinates > coordinates items > coordinates items items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.5.2.1.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiLineString > coordinates > coordinates items > coordinates items items > coordinates items items items
4.8.2.1.5.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiLineString > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.8.2.1.5.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiLineString > bbox > bbox items
4.8.2.1.6. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon
Title: GeoJSON MultiPolygon
| |
|---|
| Type | object |
| Required | No |
| Additional properties | Any type allowed |
| Property | Pattern | Type | Deprecated | Definition | Title/Description |
|---|
| + type | No | enum (of string) | No | - | - |
| + coordinates | No | array of array | No | - | - |
| - bbox | No | array of number | No | - | - |
4.8.2.1.6.1. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon > type
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
4.8.2.1.6.2. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon > coordinates
| |
|---|
| Type | array of array |
| Required | Yes |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.6.2.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon > coordinates > coordinates items
| |
|---|
| Type | array of array |
| Required | No |
| Array restrictions |
|---|
| Min items | N/A |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.6.2.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon > coordinates > coordinates items > coordinates items items
| |
|---|
| Type | array of array |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.6.2.1.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon > coordinates > coordinates items > coordinates items items > coordinates items items items
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 2 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
4.8.2.1.6.2.1.1.1.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon > coordinates > coordinates items > coordinates items items > coordinates items items items > coordinates items items items items
4.8.2.1.6.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.8.2.1.6.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > geometries > geometries items > oneOf > GeoJSON MultiPolygon > bbox > bbox items
4.8.3. Property GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
4.8.3.1. GeoJSON Feature > geometry > oneOf > GeoJSON GeometryCollection > bbox > bbox items
5. Property GeoJSON Feature > bbox
| |
|---|
| Type | array of number |
| Required | No |
| Array restrictions |
|---|
| Min items | 4 |
| Max items | N/A |
| Items unicity | False |
| Additional items | False |
| Tuple validation | See below |
| Each item of this array must be | Description |
|---|
| bbox items | - |
5.1. GeoJSON Feature > bbox > bbox items
Generated using json-schema-for-humans on 2026-01-13 at 12:37:05 +0000