Data upload walkthrough
Below you will find a short walkthrough of how to upload data onto the Verify portal. Below that there is also a step-by-step written guide.
Dataset Screen Overview
The first screen you see when you log in is the 'Datasets' page. It lists all the datasets you’ve created or have access to as a user.
You can filter these datasets by commodity, origin, or date, and archive any datasets that are no longer relevant. Archiving helps keep the screen uncluttered and focused on active datasets.
Creating a New Dataset
Let’s go ahead and create a brand-new dataset:
Step 1: Commodity and Origin Selection
First, choose a commodity. For example, coffee.
Next, select an origin. For example, Indonesia.
Finally, the system will suggest a name based on unit-commodity-origin but you are free to edit this
Step 2: Test Profile and Methodology Version selection
You’ll then have the option to select a test profile and methodology version. Currently, we have one profile for EUDR compliance.
You can review the tests included in the profile. At the moment these include older versions of our methodology. We recommend to select the most recent methodology version which will be the first one. Once satisfied, continue by selecting the profile and clicking 'Save and Continue'
Step 3: Select the Data you want to upload
Next, upload the actual data. This typically includes:
Geospatial Data: This could be a geopoint of a farm or, more commonly, a polygon outlining the farm.
Metadata: This includes essential details like farmer ID, farm plot ID, commodity type, and other relevant information.
Here’s how it works:
The system accepts xlsx, geojson, csv, kml and shape files
Select a file and upload it into the database.
After uploading, the screen will display options to delete the file or upload additional files.
Since geospatial data and metadata may be in separate files, users can upload as many files as needed.
Step 4: Map the Attributes of your data
The fourth step involves mapping the data, which tells the system where to find specific fields in the uploaded files. It is important to complete this step correctly to ensure the system can read your data properly and maximise the number of applicable tests. This step provides the system with the data it needs to run tests.
The farm plot ID is a mandatory field and must be selected.
You can also map other fields, such as the farmer ID, mapping date, aggregator etc. and continue mapping as required.
The more fields you map out the better as this will allow the system to run as many tests as are applicable for your dataset
GIS-Specific Details
In the final section, you can add an additional level of GIS-specific details if you are using an excel or csv file, for example. Once everything is confirmed, the system will run the tests, and you’ll see the results.
Tip: To simplify this step, use clear and descriptive header names that directly correspond to the fields in the Verify Portal, making it easier to match them accurately at this stage.
Step 5: Create filters
Next we can create some filters that can help us to splice the data later.
To create a filter simply select what data you would like to filter by here are the options for this dataset and then give your filter a name.
You can create additional filters by clicking ‘Create Filter’ and repeating the same process.
In the example below, we've selected the value Mapping_date and then given that filter the same name.
Step 6: Understanding the final Test Results page
Here you can see that the unit that is going to be analysed for this test profile is the farm plot. It also reminds you which test profile you are using (in this case EUDR).
In this example, the total tests that the verified portal can run is 38. But, this specific dataset below we see that only 33 tests will be applicable for this dataset.
If we click the 'view all tests' button, we can get a better understanding of which tests won't be applicable and why that is.
If we click the 'View all Tests' button then this will give us additional information on why the total test number may be different then the applicable test number.
Some tests may show as No. This could be due to:
A test being skipped (e.g., because of geometric issues). In this example below, the dataset we uploaded only had polygons, no geopoints, so the system will automatically skip the geopoint test, ATT04 - Farm plot is recorded as a geopoint but estimated size is >4Ha, for this specific dataset.
Missing data fields in the uploaded files.
Attributes either not being mapped out or being mapped out incorrectly at step 4.
Conclusion
In conclusion, this guide walks you through the essential steps to upload datasets effectively, from creating and uploading data to mapping fields, applying filters, etc.. By following these steps, you can ensure data accuracy, streamline analysis, and identify key risks or insights with ease.