We define humanitarian data as:

1. data about the context in which a humanitarian crisis is occurring (e.g., baseline/development data, damage assessments, geospatial data)
2. data about the people affected by the crisis and their needs
3. data about the response by organisations and people seeking to help those who need assistance.

HDX includes two categories of data - curated indicators and user-contributed datasets. We curate about 130 indicators from multiple sources, ensuring they are comparable across countries and have gone through a quality-control process. We also have datasets that organisations have shared.

Yes. HDX uses an open-source software called CKAN for our technical back-end. We partner with ScraperWiki for data transformation and operations support. You can find all of our code on GitHub.

We build and test HDX using the latest versions of Chrome and Firefox. We also test on Internet Explorer 10 and later, but do not formally support it.

You can register by clicking on 'Sign Up' on the upper-right corner of any HDX page.

Anyone can view and download the data from the site, but registered users can access more features. After signing up you can:

1. follow the latest changes to data, locations, organisations, topics and crises;
2. share datasets publicly or privately, and join organisations to get access to private datasets*;
3. add data visualizations as gallery items alongside datasets*;
4. contact data contributors.

*You need to be affiliated with an organisation to access these features.

HDX allows registered users to follow the data they are interested in. Updates to the datasets that you follow will appear as a running list in your user dashboard(accessible from your user name in the top right of every page when you are logged in). You can follow data, organisations, locations, topics and crises.

You'll find a 'contact the contributor' link below the title of every dataset. Please find more details here.

Use our password recovery form to reset your account details. Enter your username or e-mail and we will send you an e-mail with a link to create a new password.

Organisations in HDX can be legal entities, such as WFP, or informal groups, such as the Shelter Cluster or Information Management Working Group for a specific country. Data can only be shared on HDX through an organisation. The HDX team verifies all organisations to ensure they are trusted and have relevant data to share with the HDX user community.

On an organization's page, click on the "Stats" tab to see how many visitors an organization has received and which datasets are most popular in terms of downloads. Here's an example. The number of unique visitors is approximate and is based on the browser someone uses when visiting HDX. A user visiting from different browsers or from different devices will be counted separately.

You can also see a timeline of how often an individual dataset has been downloaded on each dataset page. The download timeline is located on the left side of a dataset page, just beside the dataset description. Downloads for a dataset are counted as the total of downloads of any resource in a dataset, with repeated downloads of the same resource by the same user being counted a maximum of once per day.

There is a delay, usually less than one day, between when a user views a page or downloads a resource on HDX and when the activity is visible in these graphs and figures.

You can request an organisation through the 'Add Data' button. We ask you to submit the following information: an organisation name, description and link to an organisation-related website (optional). We review this information and then either accept the request or ask for more information, such as a sample dataset.

Registered users can request membership through the organisation's profile page. Click on the 'Request Membership' button and a request will be sent to the organisation's administrator(s). The requestor can not specify the role (i.e., admin, editor or member). Instead, the person receiving the request assigns the role.

Organisation membership includes three roles:

• Administrators can add, edit and delete datasets belonging to the organisation and accept or refuse new member requests.
• Editors can add, edit and delete datasets belonging to the organisation but cannot manage membership.
• Members can view the organisation's private datasets, but cannot add new datasets or manage membership.

The user who requests the creation of an organisation is assigned an administrator role. That person can invite other HDX users into their organisation and assign them one of the three roles above, or registered users on HDX can request membership from the organisation's administrator(s).

For full details on managing members, please read this document.

Yes. Registered users can be part of several organisations. Only users belonging to an organisation can add data to HDX.

If your organisation is not listed, you can request to create one (click the 'Add Data' button) or you may want to join an existing organisation. For instance, there may be a WFP organisation that was created by its staff at headquarters in Rome. You may prefer to join that one rather than creating a separate organisation for a specific location, e.g., WFP Liberia. You can see the full list of organisations by clicking the 'Organisations' link at the top of any page.

Yes. Each administrator is able to manage datasets and membership. If a user requests membership, the request will be sent to all organisation administrators. The decision to accept or deny a membership request will be taken by whichever administrator acts first. The other administrators are not alerted to this action. We are planning to make this process more clear in future versions of the platform, so please bear with us!

HDX offers custom organisation pages to all organisations on the site. The page includes the organisation's logo and colour palette, topline figures, space for a data visualization and the list of datasets. We created our first custom organisation pages for WFP and the Somalia NGO Consortium. If you would like a custom page, send a request to hdx.feedback@gmail.com.

Please find more details here.

You can keep your account. On the organisation page that you're a part of, click the link to 'Leave this organisation'. If you want to change the email address associated with your account, click on your username on the upper-right corner of any HDX page and then select 'User Settings'. From there, you can update your profile.

Data on HDX is shared through organisations. You need to be a member of an organisation (with appropriate privileges) before you can contribute data. If you have data to share, you can either request to create a new organisation or ask to join an existing one. (See more under Organisations above.)

Yes. For each dataset that you create, you have a choice of sharing publicly or restricting access to other members of the same organisation. The default visibility is set to private when you upload a new dataset. We encourage the open sharing of data, but we recognize that some data may not be suitable for public release.

A dataset is a collection of related data resources. A resource is an individual file within a dataset. When sharing data, you first create a dataset and then you can add one or more resources to it. A resource can either be a file uploaded to HDX (such as a CSV or XLS file) or a link to another website with a downloadable file. A resource, such as a readme file, could also contain documentation that helps users to understand the dataset, such as a readme file.

Click on the 'Add Data' button from any page on HDX. You will be required to login and associate yourself with an organisation. These slides provide a walk-through of how to add a dataset. Here are more details on the 'update frequency' field.

You can only edit a dataset if you are an administrator or editor of your organisation. If you have the appropriate role, you will find an 'Edit' button just below the dataset description. This will allow you to edit the dataset metadata and the resources. These slides provide a walk-through of how to edit a dataset.

If your data uses the HXL standard, then HDX can automatically create customizable graphs and key figures to help you highlight the most important aspects of your dataset. We call these "Quick Charts". For a Quick Chart to be generated, your dataset needs to be public and contain a CSV or XLSX resource with HXL tags. HXL is easy! Check out the 30-second tutorial.

The resource can be stored on HDX or as a remote resource at another URL. Quick Charts will be generated from the first resource with HXL tags in the list of a dataset's resources. The system will try to generate up to three charts based on the HXL tags, and these can be changed to best tell the story in your data. You can edit each Quick Chart's title, axis labels, and description. Don't forget to save the changes so they become the default view that users see when viewing your dataset. Here's a good example to get you started.

Quick Charts doesn't work with all HXL tags, but we're working to expand its capabilities and your feedback is welcome at hdx.feedback@gmail.com.

We define data as information that software can read and analyse. We encourage contributions in any common data format. HDX has built-in preview support for tabular data in CSV and Microsoft Excel (xls only) formats, and for geographic data in zipped shapefile, kml and geojson formats.

A PDF file is not data. If you have a data visualization in PDF format, you can add it as a gallery item on the dataset page. If you wish to share documents, graphics, or other types of humanitarian information that are not related to the data you are sharing, please visit our companion sites ReliefWeb and HumanitarianResponse. A resource, such as a readme file, could also contain documentation that helps users to understand the dataset.

For datasets: the keywords in your dataset title are matched to the search terms users enter when looking for data in HDX. Avoid using abbreviations in the title that users may not be familiar with. Also avoid using words such as current, latest or previous when referring to the time period (e.g., latest 3W), as these terms become misleading as the dataset ages. The following is a good example of a dataset title: 'Who is Doing What Where in Afghanistan, Dec 2016'.

For resources: by default, the resource name is the name of the uploaded file. However, you can change this if needed to make it more clear to users.

For zipped shapefiles: we recommend the filename be name_of_the_file.shp.zip. However, the system does not require this construction.

If your resource is simply a link to a file hosted elsewhere, there is no size limit. If you are uploading a file onto HDX, the file size is limited to 300MB. If you have larger files that you want to share, e-mail us at hdx.feedback@gmail.com.

Yes. HDX can host the data for you, but it works equally well with a link to data hosted somewhere else on the web. For example, if your organisation already has a system or API that produces data for download, you can simply include a link to that data as a resource in your dataset, and the version on HDX will automatically stay up to date.

Yes. HDX allows you to drag and drop files from your computer. First, you need to click on the 'Add Data' link and then select files from your computer. Drop the files in the designated area. A new dataset form will appear with some fields already pre-filled.

First you need to be sure that the Google Drive file or files are publicly visible or accessible to anyone who has the link. For instructions on how to change, follow this walkthrough. You can click on 'Add Data' and choose the option to import files from 'Google Drive'. A 'Google Drive' pop-up will show and help you choose the file/files from your account. The files will not be copied into HDX. Instead, the HDX 'Download' button will always direct users to the live version of the Google document.

The HDX Resource Picker for Google Drive will only have access to your list of Google Drive files when you are logged into Google Drive. You can revoke this permission at any time in Google Drive's App Manager. However, this will not change the visibility of the Google Drive resources already created on HDX.

HDX can live-link to and preview files stored in any Dropbox folder and even preview them if they are in CSV or XLS format. You can click on 'Add Data' and choose the option to import files from 'Dropbox'. A 'Dropbox' popup will show and help you choose the file/files from your account.

To include a link to a Google Sheet, you must first set the sheet's sharing permissions so that it is either publicly visible or at least accessible to anyone who has the link. We recommend creating at least two separate resources for each Google Sheet: 1) a link to the sheet itself in the regular Google Drive interface; and 2) a direct-download link to an Excel or CSV version of the sheet, so that users can preview it in HDX. The version in HDX will update automatically as you make changes to the original Google Sheet.

To obtain the direct download link, download the sheet to your own computer in Excel or CSV format, then open your web browser's 'Downloads' screen and copy the link from there.

HDX can live-link to and preview files stored in any Dropbox folder and even preview them if they are in CSV or XLS format. You must login to Dropbox via the web application and navigate to the folder containing the spreadsheet (or other file) that you want to share. Select the file and choose 'Share link', following the instructions in the Dropbox help centre. You will then receive a special link that allows anyone to download the file.

Add that link as a resource to your HDX dataset. When you receive a Dropbox link, it normally looks something like this:
https://www.dropbox.com/etc/etc/your_file_name.csv?dl=0

For HDX to be able to process and preview your file, you'll need to change the last '0' to a '1' so that it looks like this:
https://www.dropbox.com/etc/etc/your_file_name.csv?dl=0

The HDX resource will automatically track any changes you save to the Dropbox file on your own computer. Be careful not to move or rename the file after you share it.

The data on HDX will always reflect updates made to the remote resource (such as a file on Dropbox or on a GeoNode). However, the metadata and activity stream will not automatically indicate the date of the update. Basically, at the moment HDX has no way of knowing that the remote resource has changed (we're working on a solution to this). Triggering an update to the date on HDX can be done manually by the dataset maintainer by making a small change to some part of the metadata of the dataset and saving it. If the resource is not remote (i.e. it is uploaded to HDX), the "updated" date will change each time a resource is uploaded.

The library is open source software and available here: hdx-python-api. Learn more about the library in this blog post.

The HDX system will attempt to create a map, or geographic preview, from geodata formats that it recognizes. For a geographic preview to be generated, your data needs to be in either a zipped shapefile, kml or geojson format. Ensure that the 'File type' field for the resource also has one of the above formats. Pro tip: HDX will automatically add the correct format if the extenion is '.shp.zip', '.kml', or '.geojson'. Here are examples of geodata points, lines, and polygons showing the preview feature.

The preview feature will continue to work when there are multiple geodata resources in a single dataset (i.e., one HDX dataset with many resources attached). The layers icon in the top-right corner of the map enables users to switch between geodata layers. Here is an example.

To generate a map preview, a dataset can have multiple resources but each resource can only include one layer within it. Resources with multiple layers (e.g., multiple shapefiles in a single zip file) are not supported. In this case, the system will only create a preview of the first layer in the resource, however all the layers will still be available in the downloaded file. If you would like all of the layers to display, you need to create a separate resource for each layer.

HDX has some datasets that are links to data stored on GeoNodes, such as the Ebola GeoNode, the Sala Humanitaria GeoNode, and the U.S. Department of State GeoNode. These links are currently maintained manually. Updates to downloadable resources on a GeoNode will be reflected in the download from HDX. Updates to metadata or descriptions are only captured if the dataset owner updates them manually on HDX.

Searching for datasets on HDX is done in two ways: by searching for terms that you type into the search bar found at the top of almost every page on HDX, and by filtering a list of search results.

Entering a search term causes HDX to look for matching terms in the titles, descriptions, locations and tags of a dataset. The resulting list of items can be further filtered by clicking on the blue filter icon at the top of the page (in the search bar). You can filter by location, tag, organisation, license and format.

In 2015, HDX migrated the Common Operational Datasets (CODs) from the COD Registry on HumanitarianResponse.info to HDX. Each of these datasets has a 'cod' tag. To limit search results to only CODs, open the filter panel (click the blue filter icon) and check the 'Only show CODs' option.

All data on HDX must include a minimum set of metadata fields. You can read our Guide to Metadata to learn more. We encourage data contributors to include as much metadata as possible to make their data easier to understand and use for analysis.

Data quality is important to us, so we manually review every new dataset for relevance, accuracy, timeliness, interpretability and comparability. We contact data contributors if we have any concerns or suggestions for improvement. You can learn more about our definition of the dimensions of data quality and our quality-assurance processes here.

HDX will never make changes to the data that has been shared. We do add tags, or make changes to dataset titles to help make your data more discoverable by HDX users. We may also add a data visualization for the data in the dataset gallery. These changes will appear in the activity stream on the left-hand column of the dataset page.

There are two APIs for accessing HDX. The best choice for most tasks is the HDX Python Library. The library is open source software available here: hdx-python-api. Learn more about the library in this blog post.

The HDX Python Library is essentially a wrapper around the most common functions of the base CKAN API, on which HDX is built. HDX supports both the core CKAN 2.3 API and, for some datasets, the CKAN Datastore API. For more information, please e-mail hdx.feedback@gmail.com. We will be happy to assist you.

The Humanitarian Exchange Language (HXL) is a simple standard for messy data. It is based on spreadsheet formats such as CSV or Excel, but it adds hashtags with semantic information to allow software to validate, clean, merge and analyse data more easily.

HDX is currently adding features to visualise HXL-tagged data. To learn more about HXL and who's currently using it, visit the HXL standard site.

Yes and no. HDX does not allow personally identifiable information (PII) to be shared in public datasets. All data shared publicly through the platform must be sufficiently aggregated or anonymized so as to prevent identification of people or harm to affected people and the humanitarian community. We do allow private datasets to include PII, such as contact information for humanitarian responders. Read more about our Terms of Service.

HDX promotes the use of licenses developed by the Creative Commons Foundation and the Open Data Foundation. The main difference between the two classes of licences is that the Creative Commons licences were developed for sharing creative works in general, while the Open Data Commons licences were developed more specifically for sharing databases. See the full list of licences here.

For general enquiries, e-mail hdx@un.org. If you see an issue with the site, e-mail hdx.feedback@gmail.com. You can also reach us on Twitter at @humdata. Sign up to receive our blog posts here.