Updating static data

This page aims to explain how to update static data in IBF

Updating static data

Point data

• Static point data can be updated via an API-call
• Swagger endpoint
• See possible values for pointDataCategory here
• See examples of CSV's here -lat/lon are the required geo columns
• Notes
  • This API-call will first remove all existing entries for the same countryCodeISO3 and pointDataCategory
  • Static points might be related to pipelines, in case the pipeline uploads e.g. an exposure status of the point (MWI flash-floods) or forecast data about Glofas stations (floods). Make sure that in this case the identifiers of the updated data in IBF-Portal match with the data used in the pipelines.
  • When uploading new data, all existing data for the given countryCodeISO3 and pointDataCategory will be set to active:false but will stay in the database. This way also the dynamic data associated with these assets can stay in the database.

Lines/polygon data

• The current only examples of this are roads and buildings in Malawi Flash-floods
• Swagger endpoint > Also used for polygon data, even though it's called 'lines-data'
• Possible values for linesDataCategory are roads and buildings
• See examples of CSV's here
  • wkt is required geo column
• same Notes as above for Point data

Admin-area data

• Update static admin-area data, such as e.g. population per admin-area.
• Swagger endpoint
• TO BE COMPLETED

Updating configuration (admin-only)

TO BE COMPLETED

In addition to static data, configuration data can also be updated via API. This involves:

• admin areas
• event areas
• country settings
• notification info settings
• early actions
• indicator metadata
• layer metadata

In addition there are some settings, which can currently not be updated via API yet.

• disaster settings
• lead times
• areas of focus