All data must meet certain formatting and metadata requirements to be successfully integrated into the FEWS NET Data Warehouse (FDW) upon upload. Standardized, domain-specific templates are used for recurring data uploads to maintain consistency and accuracy. Ad hoc data may require additional attention to ensure the data can be recognized.
This page outlines key considerations when preparing and uploading data, including defining and managing metadata, selecting an upload method, and troubleshooting common issues.
Preparing data
Data upload spreadsheets for most domains require a straight table with one data point per row.
For guidance about using specific data upload templates, see the Domain Specific Data Management pages.
The essential requirements for your file’s column headings, metadata, and data values are described below.
Column headings
Your file’s column headings must be recognized by FDW. When uploading ad hoc data, the column names may need to be adjusted.
If you regularly receive a document from a non-FEWS NET source that contains alternate column headings, do not edit the column headings every time. Instead, submit a help desk ticket so the Hub can add the headings as aliases to the system.
Make sure your column headings are properly defined by verifying the following:
-
Each column heading matches the expected naming conventions used by FDW, including spelling, capitalization, and formatting. Ensure no extra spaces are in the column headings.
-
Each column heading corresponds to the data contained in that column.
Additionally, ensure that all required columns are included in the file and are not hidden.
Metadata
Accurately preparing and managing metadata is critical to ensuring FDW can correctly interpret, categorize, and integrate uploaded data.
Make sure your file contains appropriate metadata information, including:
-
Values that match the metadata available in FDW.
-
Values that are accurate and appropriate for each record.
-
Values that are free of typos, extra characters or spaces, or values that cannot be recognized.
Certain types of metadata can automatically be added to FDW during data uploads. Others must be added through the relevant Data Series or metadata screen in FDW prior to upload in order to be recognized. These requirements are outlined in more detail below.
Metadata required in FDW prior to uploading
There are three primary elements of metadata that must be set up in FDW prior to uploading your data:
-
Source Document: The Source Document specifies the domain the data is in as well as additional attributes. For more information on setting up a Source Document, see https://fewsnet.atlassian.net/wiki/spaces/FDWKB/pages/edit-v2/2045870105
-
Geographic Unit: The Data Series under a given Source Document are tied to a Geographic Unit. For more information on working with Geographic Units in FDW, see Spatial Metadata.
-
Unit of Measure: The unit of measure must be available for a given product. The default units in FDW are primarily metric. Data can be stored in local or alternative units of measure and converted for data extractions.
Make sure the correct value for each element already exists or is added prior to uploading a spreadsheet of data referring to it.
Other metadata, such as new markets, products, currencies, or seasons, may need to be set up in FDW depending on the type of data being uploaded.
Metadata captured on upload
Some metadata can be automatically added to FDW while uploading data. For example, Data Series, Data Collections, and Collection Periods can all be created while uploading Data Points.
Data values
Ensure your file’s data values can be uploaded correctly by checking the following:
-
All data values align with the correct metadata field in the column headings.
-
All data values are within an expected range.
Choosing a data upload option
The Data Entry module in FDW includes the following options:
-
Add a Data collection: Recommended for uploading monthly data.
-
Import Data Points: Recommended for small bulk uploads of historical data or corrections.
-
Offline Data Uploads: Recommended for large bulk uploads of historical data or corrections. FDW will not immediate feedback for offline data uploads. Instead, you will receive an automated email from helpdesk@fews.net detailing the success or failure of the upload.
For additional instructions, see Uploading Monthly and Bulk Data.
Common errors
When uploading data using the Add a Data Collection screen, you’ll receive feedback on the success of your upload and any issues. If you use the Offline Data Uploads functionality, review the email sent by the system for information about any errors.
Common causes of data upload errors include:
Naming discrepancies: Misspellings, alternate spellings, or extra characters included in column headings and metadata will cause the upload to fail. For example, if the Data Source Document name used in the file does not match the Data Source Document name in FDW it will not be recognized.
Date issues: An upload may fail due to a missing or invalid period date. Or, the file may refer to metadata that has an End Date in FDW and therefore cannot accept data past that date. For example, if the Source Document specified by the upload file has an End Date of 2024-12-31 in FDW, data for 2025 cannot be added to it.
Missing metadata: If the file contains new metadata the FDW cannot recognize or interpret, you must first add this metadata to FDW. The file must also contain all required metadata to be successfully uploaded to FDW.
Incorrect metadata assignment: If the metadata in your file does not match the expected metadata in FDW, you will need to review the discrepancy and determine if your file or FDW needs to be updated. For example, if the product codes in the file are incorrect or out of date with FDW, they will need to be updated before upload. Ensure the metadata is captured under the correct column heading in the upload file.
For additional troubleshooting information with example error messages, see .