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 location 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.
According to the International Aid Transparency Initiative (IATI) Standard, a project location is a set of geographical features (and additional attributes) 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 specific site 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 should 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.
In KfW’s data model, a location is always defined as the combination of a specific project activity with its respective geographic coordinates and additional project-specific, site-specific and activity-related attributes. Thus, additional attributes of a project location are project number, village name, location name, activity description, location type and geographical exactness, among others.
KfW’s 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 and additional attributes 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 project executing agency (PEA) or consultant to collect geo-coordinates and relevant attributes, .i.e. location data, 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 as part of the preparation of progress reports, i.e. usually on an annual basis, if not otherwise specified.
The International Aid Transparency Initiative (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 or indiviadual households
- 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.
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, other donors as well as for our internal and external stakeholders. The data is also used to appraise potential new project locations during project preparation and to assess portfolios for social, environmental or climate-related risks.
KfW strongly encourages project executing agencies (PEA) or consultant staff to collect project locations 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.
While most of the other attributes of the data model template closely follow International Aid Transparency Initiative IATI standards, the existing list of IATI location types, that was inadequate to international aid and development cooperation, has been amended to cover the full range of projects. A “location type” summarizes the output- or intervention-related type of a physical location or - in case there is no physical location related to a project activity (i.e. a so-called “immaterial location type”) - its target area.
Our updated list of 224 IATI location types cover all sectors of international aid and development: 32 location types were taken unchanged from the original IATI list (i.e. bridge), 14 location types were changed slightly (i.e. from “water pumping station” to “water pump” keeping its code) and 178 new project location types have been created. These include for example, immaterial location types “capacity development / training” or “voucher(s) (system) distributrion area”, which cannot be plotted based on any physical features on a map, but can be defined by their target area. Please refer to the list of location types in the Excel template or in the json model for more information.
For you to find your most suitable location type easily, we grouped them into “location type themes” that are most typical to a certain sector, i.e. you will find the location type “school” under the preselection field, i.e. location type theme “Education”. For location types that occur in many sectors, i.e. “building”, please choose the location type theme “_Generic / Cross_Sectoral”.
If a specific location type is not available, please use the most similar available type (e.g. “well” for “extraction well”) and mention “extraction well” in the activity description. If you cannot find any suitable similar location type, please choose “other physical” or “other immaterial”.
Approximate locations should be used if one 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).
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 the existing codelists of the International Aid Transparency Initiative IATI to collect project specific geo-information and other relevant location attributes, which are used by international aid and development organizations. It harmonizes and coordinates aid and development projects across multiple donor agencies. However, the IATI standard is not considered operational at subnational level - mainly, because its location types list is not (yet) suitable for international aid and development cooperation projects and other types of relevant attributes have not yet been selected and prioritized (for example, the most suitable administrative unit repositories) for a common minimum list of location attributes, i.e. a true common standard.
Therefore, the existing geolocation-related elements of the IATI standard were further developed and operationalized in our model. In particular, the existing IATI list of location types was modified to cover all physical and immaterial location types required by international aid and development cooperation standards. Also, the “exactness” categorization of geo-coordinates was expanded from the binary choice between “exact” and “approximate” to “exact” and three distinct categories of “approximate”:
- “exact location is yet unknown, or
- “exact location not to be published due to security concenrns” or
- location is a an “administrative 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 |
|---|
| - f_id | No | number | No | - | For new locations, this column will be empty. For updates, KfW will provide you with the list of f_id numbers of this file to ensure that the updated field ids match with the former ones. |
| + scheme_version | No | enum (of string) | No | - | - |
| + donor_project_no | No | number | No | - | Every project location must be assigned to its respective BMZ project number. |
| + project_acronym | No | string | No | - | Enter the acronym used for the name/title of the project (e.g. HREII) to be visible on your map. If the project has multiple phases, please add the number of the phase belonging to the before-stated KfW Project-No. |
| + data_provider | No | string | No | - | Legal Entity who owns the data provided here (= legal authorship). |
| + publishing_restrictions | No | enum (of string) | No | - | Indicates if the exact location is collected in fragile areas (e.g. of severe civil conflict or war) and should therefore be omitted from publicly available reports. |
| + date_of_data_collection | No | object | No | - | Date of data collection or latest update (if date of data collection is unknown). In case only the year is available please choose the 1st of january e.g. 2022-01-01. |
| + related_community | No | string | No | - | Enter a community, village, hamlet or neighbourhood name that relates to this location, this can serve for manually add smaller administrative unit names that are not in global databases. |
| + location_name | No | string | No | - | Unique name of the project site and its (main) activity incl local MIS-/GIS-ID, if availabe. This will be used as reference for line and polygon data. |
| + location_activity_status | No | enum (of string) | No | - | The location activity status according to the IATI standard. If you are unaware of the current status please choose ‘NA’. |
| + activity_start_date | No | object | No | - | Aprox. planned or actual start date of implementation of activities on the ground. This can be e.g. the date when construction work is planned to begin. For no information enter 2100-01-01. |
| + activity_end_date | No | object | No | - | Aprox. planned or actual end date of activities on the ground. This can be e.g. the date when the project is planned to cease implementation activities. For no information enter 2100-01-01. |
| + activity_description | No | string | No | - | A short description of the main project activity in this location, e.g., hydropower plant construction or construction of small irrigation systems. |
| + location_type_theme | No | enum (of string) | No | - | Sectoral_cross-sectoral location type preselection field, see table sheets ‘Location Types’ & KC Themes. If there is no fit, select ‘_Generic/Crosssect.’ here and then ‘other physical/immaterial’ in the next column. |
| + location_type_name | No | enum (of string) | No | - | After selecting the KC Theme, choose the most appropriate location type, see table sheet ‘Location Types’. If there is no fit please select ‘other phys./imm.’ |
| + geographic_exactness | No | enum (of string) | No | - | Use ‘exact’ if the exact coordinates are known + no security restrictions apply. Otherwise, use ‘approximate (security)’ or ‘approx. (yet unknown)’. If the target area is an admin unit, use ‘approx. (admin unit).’. |
1. Property Project Location Model > f_id
Description: For new locations, this column will be empty. For updates, KfW will provide you with the list of f_id numbers of this file to ensure that the updated field ids match with the former ones.
2. Property Project Location Model > scheme_version
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
3. Property Project Location Model > donor_project_no
Description: Every project location must be assigned to its respective BMZ project number.
4. Property Project Location Model > project_acronym
Description: Enter the acronym used for the name/title of the project (e.g. HREII) to be visible on your map. If the project has multiple phases, please add the number of the phase belonging to the before-stated KfW Project-No.
5. Property Project Location Model > data_provider
Description: Legal Entity who owns the data provided here (= legal authorship).
6. Property Project Location Model > publishing_restrictions
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Indicates if the exact location is collected in fragile areas (e.g. of severe civil conflict or war) and should therefore be omitted from publicly available reports.
Must be one of:
7. Property Project Location Model > date_of_data_collection
| |
|---|
| Type | object |
| Required | Yes |
| Additional properties | Any type allowed |
Description: Date of data collection or latest update (if date of data collection is unknown). In case only the year is available please choose the 1st of january e.g. 2022-01-01.
Description: Enter a community, village, hamlet or neighbourhood name that relates to this location, this can serve for manually add smaller administrative unit names that are not in global databases.
9. Property Project Location Model > location_name
Description: Unique name of the project site and its (main) activity incl local MIS-/GIS-ID, if availabe. This will be used as reference for line and polygon data.
10. Property Project Location Model > location_activity_status
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: The location activity status according to the IATI standard. If you are unaware of the current status please choose ‘NA’.
Must be one of:
- “NA”
- “Pipeline/identification”
- “Implementation”
- “Finalisation”
- “Closed”
- “Cancelled”
- “Suspended”
- “Other”
11. Property Project Location Model > activity_start_date
| |
|---|
| Type | object |
| Required | Yes |
| Additional properties | Any type allowed |
Description: Aprox. planned or actual start date of implementation of activities on the ground. This can be e.g. the date when construction work is planned to begin. For no information enter 2100-01-01.
12. Property Project Location Model > activity_end_date
| |
|---|
| Type | object |
| Required | Yes |
| Additional properties | Any type allowed |
Description: Aprox. planned or actual end date of activities on the ground. This can be e.g. the date when the project is planned to cease implementation activities. For no information enter 2100-01-01.
13. Property Project Location Model > activity_description
Description: A short description of the main project activity in this location, e.g., hydropower plant construction or construction of small irrigation systems.
14. Property Project Location Model > location_type_theme
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Sectoral_cross-sectoral location type preselection field, see table sheets ‘Location Types’ & KC Themes. If there is no fit, select ‘_Generic/Crosssect.’ here and then ‘other physical/immaterial’ in the next column.
Must be one of:
- “_Generic_Cross_Sectoral”
- “Agriculture_Rural_Development”
- “Aquaculture_Fishery”
- “Biodiversity_Conservation”
- “Education”
- “Energy”
- “Financial_Sector_Development”
- “Governance_Decentralization”
- “Health”
- “Mobility_Transport”
- “Protected_and_Conserved_Areas”
- “Peace_Displacement_Fragility”
- “Social_Protection”
- “Urban_Infrastructure”
- “Waste”
- “Water_Management”
15. Property Project Location Model > location_type_name
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: After selecting the KC Theme, choose the most appropriate location type, see table sheet ‘Location Types’. If there is no fit please select ‘other phys./imm.’
Must be one of:
- “building(s)”
- “common / public space(s)”
- “equipment / materials”
- “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)”
- “supply chains (support) area”
- “voucher(s) (system) distribution area”
- “slaughterhouse”
- “mine(s)”
- “workshop(s)”
- “sustainably farmed area(s)”
- “cultivated area”
- “garden(s)”
- “grazing / rangeland (management) area”
- “improved soil / erosion control area”
- “irrigated field(s)”
- “irrigation infrastructure”
- “nursery(-ies) / seed bank”
- “food processing & value addition”
- “weir(s)”
- “agricultural extension services”
- “contract farming / PPP”
- “farmers groups / cooperatives support”
- “agroforestry area”
- “aquaculture”
- “fisheries management area”
- “certified sustainable aquaculture or fisheries (MSC, ASC)”
- “coastguard station”
- “FAO catch-area”
- “feed-mill”
- “inland waters fishery”
- “pond”
- “small scale fisheries (SSF) zone”
- “school (primary, secondary, college)”
- “TVET school / infrastructure”
- “university”
- “scholarship program area”
- “area covered by off-grid renewable energy”
- “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”
- “wind power plant”
- “district heating area / distribution”
- “battery energy storage system (BESS)”
- “fuel station”
- “charging station”
- “power station (other)”
- “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”
- “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”
- “airplane(s)”
- “airport”
- “aviation safety system / flight control”
- “boat(s) / ship(s) / -yard”
- “bridge”
- “bus rapid transit (BRT) / bus system”
- “buses”
- “rolling stock”
- “ferry (line, system)”
- “intraurban rail infrastructure”
- “interurban rail infrastructure”
- “highway”
- “depot / marshalling yard”
- “other road-based vehicles”
- “pedestrian lane(s) / bike lane(s)”
- “port”
- “rail operation control system / intelligent transport system (ITS)”
- “railroad station”
- “railroad”
- “road”
- “traffic management center / IST”
- “(multimodal) logistic node / warehouse”
- “waterway(s) (system)”
- “bus station / terminal”
- “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”
- “child protection services”
- “women’s shelter / GBV support”
- “basic social services”
- “cash- / food-for-work”
- “cash transfers”
- “climate risk insurance”
- “social protection system”
- “employment subsidies”
- “strict nature reserve (IUCN Cat Ia)”
- “wilderness area (IUCN Cat Ib)”
- “national park (IUCN Cat II)”
- “natural monument or feature (IUCN Cat III)”
- “habitat or species management area (IUCN Cat IV)”
- “protected landscape or seascape (IUCN Cat V)”
- “protected area with sustainable use of natural resources (IUCN Cat VI)”
- “other effective area-based conservation measures (OECM)”
- “indigenous & community conservation area (ICCA)”
- “indigenous and traditional territories (ITT)”
- “wildlife management area / game reserve”
- “marine protected area (MPA)”
- “locally managed marine areas (LMMA)”
- “private protected area / conservation easement”
- “exclusive economic zone (EEZ)”
- “indigenous peoples & local communities (IP&LC)”
- “no-take zone”
- “visitor center / education facility”
- “regeneration / restoration / rehabilitation area”
- “watershed / catchment conservation area”
- “fire management area”
- “key biodiversity area (KBA) with financed management”
- “buffer zone around a protected or sensitive area”
- “invasive species management area”
- “ranger station / field base”
- “re- / afforestation area”
- “biodiversity offset / compensation area incl. PFES”
- “certified sustainable forest management (FSC, Rainforest Alliance, PEFC)”
- “ecological corridor / connectivity area”
- “monitoring and research sites”
- “harvesting sites for NTFPs and other biodiversity products”
- “(urban) street”
- “city district / urban development”
- “market (shopping area)”
- “parcs & other green areas”
- “shopping center or mall”
- “slum upgrading”
- “street lighting”
- “recycling facility”
- “improved waste collection”
- “landfill”
- “landfill gas capture and treatment”
- “mechanical-biological treatment plant”
- “other waste treatment plants”
- “transfer station”
- “waste-to-energy plant”
- “water pump”
- “desalination plant”
- “dezentralized sanitation (area)”
- “drinking water supply”
- “water pipeline”
- “drinking water treatment plant (without desalination)”
- “flood protection”
- “reservoir(s)”
- “sanitary facility”
- “sewage treatment plant”
- “sewer network”
- “sludge treatment & disposal”
- “stormwater network / system”
- “water intake”
- “water re-use”
- “water tank”
- “well”
- “hydro-meteorological measurement system”
- “water resources protection area”
- “watercourse”
16. Property Project Location Model > geographic_exactness
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Use ‘exact’ if the exact coordinates are known + no security restrictions apply. Otherwise, use ‘approximate (security)’ or ‘approx. (yet unknown)’. If the target area is an admin unit, use ‘approx. (admin unit).’.
Must be one of:
- “exact”
- “approximate (yet unknown)”
- “approximate (security)”
- “approximate (admin unit)”
Generated using json-schema-for-humans on 2026-03-31 at 08:55:08 +0000
This document describes the JSON schema for project_core_schema_fr.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 |
|---|
| - f_id | No | number | No | - | For new locations, this column will be empty. For updates, KfW will provide you with the list of f_id numbers of this file to ensure that the updated field ids match with the former ones. |
| + scheme_version | No | enum (of string) | No | - | - |
| + donor_project_no | No | number | No | - | Every project location must be assigned to its respective BMZ project number. |
| + project_acronym | No | string | No | - | Enter the acronym used for the name/title of the project (e.g. HREII) to be visible on your map. If the project has multiple phases, please add the number of the phase belonging to the before-stated KfW Project-No. |
| + data_provider | No | string | No | - | Legal Entity who owns the data provided here (= legal authorship). |
| + publishing_restrictions | No | enum (of string) | No | - | Indicates if the exact location is collected in fragile areas (e.g. of severe civil conflict or war) and should therefore be omitted from publicly available reports. |
| + date_of_data_collection | No | object | No | - | Date of data collection or latest update (if date of data collection is unknown). In case only the year is available please choose the 1st of january e.g. 2022-01-01. |
| + related_community | No | string | No | - | Enter a community, village, hamlet or neighbourhood name that relates to this location, this can serve for manually add smaller administrative unit names that are not in global databases. |
| + location_name | No | string | No | - | Unique name of the project site and its (main) activity incl local MIS-/GIS-ID, if availabe. This will be used as reference for line and polygon data. |
| + location_activity_status | No | enum (of string) | No | - | The location activity status according to the IATI standard. If you are unaware of the current status please choose ‘NA’. |
| + activity_start_date | No | object | No | - | Aprox. planned or actual start date of implementation of activities on the ground. This can be e.g. the date when construction work is planned to begin. For no information enter 2100-01-01. |
| + activity_end_date | No | object | No | - | Aprox. planned or actual end date of activities on the ground. This can be e.g. the date when the project is planned to cease implementation activities. For no information enter 2100-01-01. |
| + activity_description | No | string | No | - | A short description of the main project activity in this location, e.g., hydropower plant construction or construction of small irrigation systems. |
| + location_type_theme | No | enum (of string) | No | - | Sectoral_cross-sectoral location type preselection field, see table sheets ‘Location Types’ & KC Themes. If there is no fit, select ‘_Generic/Crosssect.’ here and then ‘other physical/immaterial’ in the next column. |
| + location_type_name | No | enum (of string) | No | - | After selecting the KC Theme, choose the most appropriate location type, see table sheet ‘Location Types’. If there is no fit please select ‘other phys./imm.’ |
| + geographic_exactness | No | enum (of string) | No | - | Use ‘exact’ if the exact coordinates are known + no security restrictions apply. Otherwise, use ‘approximate (security)’ or ‘approx. (yet unknown)’. If the target area is an admin unit, use ‘approx. (admin unit).’. |
1. Property Project Location Model > f_id
Description: For new locations, this column will be empty. For updates, KfW will provide you with the list of f_id numbers of this file to ensure that the updated field ids match with the former ones.
2. Property Project Location Model > scheme_version
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Must be one of:
3. Property Project Location Model > donor_project_no
Description: Every project location must be assigned to its respective BMZ project number.
4. Property Project Location Model > project_acronym
Description: Enter the acronym used for the name/title of the project (e.g. HREII) to be visible on your map. If the project has multiple phases, please add the number of the phase belonging to the before-stated KfW Project-No.
5. Property Project Location Model > data_provider
Description: Legal Entity who owns the data provided here (= legal authorship).
6. Property Project Location Model > publishing_restrictions
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Indicates if the exact location is collected in fragile areas (e.g. of severe civil conflict or war) and should therefore be omitted from publicly available reports.
Must be one of:
7. Property Project Location Model > date_of_data_collection
| |
|---|
| Type | object |
| Required | Yes |
| Additional properties | Any type allowed |
Description: Date of data collection or latest update (if date of data collection is unknown). In case only the year is available please choose the 1st of january e.g. 2022-01-01.
Description: Enter a community, village, hamlet or neighbourhood name that relates to this location, this can serve for manually add smaller administrative unit names that are not in global databases.
9. Property Project Location Model > location_name
Description: Unique name of the project site and its (main) activity incl local MIS-/GIS-ID, if availabe. This will be used as reference for line and polygon data.
10. Property Project Location Model > location_activity_status
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: The location activity status according to the IATI standard. If you are unaware of the current status please choose ‘NA’.
Must be one of:
- “NA”
- “Pipeline/identification”
- “Implementation”
- “Finalisation”
- “Closed”
- “Cancelled”
- “Suspended”
- “Other”
11. Property Project Location Model > activity_start_date
| |
|---|
| Type | object |
| Required | Yes |
| Additional properties | Any type allowed |
Description: Aprox. planned or actual start date of implementation of activities on the ground. This can be e.g. the date when construction work is planned to begin. For no information enter 2100-01-01.
12. Property Project Location Model > activity_end_date
| |
|---|
| Type | object |
| Required | Yes |
| Additional properties | Any type allowed |
Description: Aprox. planned or actual end date of activities on the ground. This can be e.g. the date when the project is planned to cease implementation activities. For no information enter 2100-01-01.
13. Property Project Location Model > activity_description
Description: A short description of the main project activity in this location, e.g., hydropower plant construction or construction of small irrigation systems.
14. Property Project Location Model > location_type_theme
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Sectoral_cross-sectoral location type preselection field, see table sheets ‘Location Types’ & KC Themes. If there is no fit, select ‘_Generic/Crosssect.’ here and then ‘other physical/immaterial’ in the next column.
Must be one of:
- “_Generic_Cross_Sectoral”
- “Agriculture_Rural_Development”
- “Aquaculture_Fishery”
- “Biodiversity_Conservation”
- “Education”
- “Energy”
- “Financial_Sector_Development”
- “Governance_Decentralization”
- “Health”
- “Mobility_Transport”
- “Protected_and_Conserved_Areas”
- “Peace_Displacement_Fragility”
- “Social_Protection”
- “Urban_Infrastructure”
- “Waste”
- “Water_Management”
15. Property Project Location Model > location_type_name
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: After selecting the KC Theme, choose the most appropriate location type, see table sheet ‘Location Types’. If there is no fit please select ‘other phys./imm.’
Must be one of:
- “building(s)”
- “common / public space(s)”
- “equipment / materials”
- “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)”
- “supply chains (support) area”
- “voucher(s) (system) distribution area”
- “slaughterhouse”
- “mine(s)”
- “workshop(s)”
- “sustainably farmed area(s)”
- “cultivated area”
- “garden(s)”
- “grazing / rangeland (management) area”
- “improved soil / erosion control area”
- “irrigated field(s)”
- “irrigation infrastructure”
- “nursery(-ies) / seed bank”
- “food processing & value addition”
- “weir(s)”
- “agricultural extension services”
- “contract farming / PPP”
- “farmers groups / cooperatives support”
- “agroforestry area”
- “aquaculture”
- “fisheries management area”
- “certified sustainable aquaculture or fisheries (MSC, ASC)”
- “coastguard station”
- “FAO catch-area”
- “feed-mill”
- “inland waters fishery”
- “pond”
- “small scale fisheries (SSF) zone”
- “school (primary, secondary, college)”
- “TVET school / infrastructure”
- “university”
- “scholarship program area”
- “area covered by off-grid renewable energy”
- “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”
- “wind power plant”
- “district heating area / distribution”
- “battery energy storage system (BESS)”
- “fuel station”
- “charging station”
- “power station (other)”
- “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”
- “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”
- “airplane(s)”
- “airport”
- “aviation safety system / flight control”
- “boat(s) / ship(s) / -yard”
- “bridge”
- “bus rapid transit (BRT) / bus system”
- “buses”
- “rolling stock”
- “ferry (line, system)”
- “intraurban rail infrastructure”
- “interurban rail infrastructure”
- “highway”
- “depot / marshalling yard”
- “other road-based vehicles”
- “pedestrian lane(s) / bike lane(s)”
- “port”
- “rail operation control system / intelligent transport system (ITS)”
- “railroad station”
- “railroad”
- “road”
- “traffic management center / IST”
- “(multimodal) logistic node / warehouse”
- “waterway(s) (system)”
- “bus station / terminal”
- “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”
- “child protection services”
- “women’s shelter / GBV support”
- “basic social services”
- “cash- / food-for-work”
- “cash transfers”
- “climate risk insurance”
- “social protection system”
- “employment subsidies”
- “strict nature reserve (IUCN Cat Ia)”
- “wilderness area (IUCN Cat Ib)”
- “national park (IUCN Cat II)”
- “natural monument or feature (IUCN Cat III)”
- “habitat or species management area (IUCN Cat IV)”
- “protected landscape or seascape (IUCN Cat V)”
- “protected area with sustainable use of natural resources (IUCN Cat VI)”
- “other effective area-based conservation measures (OECM)”
- “indigenous & community conservation area (ICCA)”
- “indigenous and traditional territories (ITT)”
- “wildlife management area / game reserve”
- “marine protected area (MPA)”
- “locally managed marine areas (LMMA)”
- “private protected area / conservation easement”
- “exclusive economic zone (EEZ)”
- “indigenous peoples & local communities (IP&LC)”
- “no-take zone”
- “visitor center / education facility”
- “regeneration / restoration / rehabilitation area”
- “watershed / catchment conservation area”
- “fire management area”
- “key biodiversity area (KBA) with financed management”
- “buffer zone around a protected or sensitive area”
- “invasive species management area”
- “ranger station / field base”
- “re- / afforestation area”
- “biodiversity offset / compensation area incl. PFES”
- “certified sustainable forest management (FSC, Rainforest Alliance, PEFC)”
- “ecological corridor / connectivity area”
- “monitoring and research sites”
- “harvesting sites for NTFPs and other biodiversity products”
- “(urban) street”
- “city district / urban development”
- “market (shopping area)”
- “parcs & other green areas”
- “shopping center or mall”
- “slum upgrading”
- “street lighting”
- “recycling facility”
- “improved waste collection”
- “landfill”
- “landfill gas capture and treatment”
- “mechanical-biological treatment plant”
- “other waste treatment plants”
- “transfer station”
- “waste-to-energy plant”
- “water pump”
- “desalination plant”
- “dezentralized sanitation (area)”
- “drinking water supply”
- “water pipeline”
- “drinking water treatment plant (without desalination)”
- “flood protection”
- “reservoir(s)”
- “sanitary facility”
- “sewage treatment plant”
- “sewer network”
- “sludge treatment & disposal”
- “stormwater network / system”
- “water intake”
- “water re-use”
- “water tank”
- “well”
- “hydro-meteorological measurement system”
- “water resources protection area”
- “watercourse”
16. Property Project Location Model > geographic_exactness
| |
|---|
| Type | enum (of string) |
| Required | Yes |
Description: Use ‘exact’ if the exact coordinates are known + no security restrictions apply. Otherwise, use ‘approximate (security)’ or ‘approx. (yet unknown)’. If the target area is an admin unit, use ‘approx. (admin unit).’.
Must be one of:
- “exact”
- “approximate (yet unknown)”
- “approximate (security)”
- “approximate (admin unit)”
Generated using json-schema-for-humans on 2026-03-31 at 08:55:08 +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-03-31 at 08:55:08 +0000