Moabi is built as a platform to allow multiple groups to collaborate on vector geodata, all within one database with common, agreed-upon data definitions. In order for the data to remain structured and usuable, it’s important to keep some things in mind:
All data imported must adhere to Moabi’s attribute schema (found in the map features documentation). The schema is built to be flexible and is able to grow as new features require additional data definitions.
All large-scale imports must take place with an awareness of what already exists within the database. Otherwise, duplicate and outdated features will decrease the quality of the dataset.
All imports must clearly document dataset metadata, including source, date, a short dataset description, and if necessary, dataset precision.
If you have a dataset and would like to upload it to Moabi, there are a few things you should do in order to prepare your data for import. As an example, this guide provides a step-by-step explanation of how to upload new information on agriculture concessions. The results, when rendered on the database, will look something like this:
If you have data you would like to upload, get in touch with us. We are building Data Working Groups around the different datasets we manage. If others are already working on data that relates to yours, come join the conversation.
Convert your dataset’s attributes to match Moabi’s attribute schema. This will entail adding some new attributes to each proposed feature, changing the name of some existing attributes, and possibly removing some existing attributes that don’t apply.
Moabi creates it’s own unique feature id, so no need to keep the
id column. If, however, this were a unique key assigned to each concession by the ministry of agriculture, this would be something we would want to keep track of. In this case, though, it’s clearly relevant only to this specific dataset.
There is no need to keep track of geographic data like province or district – Moabi keeps track of this for us automatically. So, we can also ignore
Localisati. Similarly, Moabi can keep track of area and perimeter on its own, so no need to keep the
Now, to match our attributes to Moabi’s agricultural concession attribute schema, we go to the Map Features page.
Primary Attributes define the feature type, such as hydroelectric dam or logging concession. Usually, one attribute is sufficient to define the feature type, and that attribute should be the same across all features of that feature type. In this case, we add
concession = agriculture to all features in our dataset.
Optional Attributes, different for each feature type, represent additional information about each feature. In this case, it looks like the
operator attribute matches our dataset’s
Acquereur attribute, and the
resource attribute matches our dataset’s
It looks like a few of our optional attributes have missing
NULL values. That is OK. In fact, Moabi is a great tool for collaborating on incomplete data, for crowdsourcing verification, and for groundtruthing datasets.
When we are done transforming our dataset, the attribute table should look something like this:
Congratulations! Your dataset should now be ready to upload. Simply add it to our public Google Drive folder and it will be added to the upload queue. If you are having trouble with Google Drive, you can also email it to us.
In summary, some good things to keep in mind:
Attribute keys of imported datasets must match exactly with the keys documented in the Map Features page. Attribute values should reflect the values that already exist in the database.
All attribute keys should be lower case.
All spaces in attribute keys should be replaced by an underscore:
Attribute values that contain multiple values should be separated by a comma and space (
, ). For instance, if a mining concession extracts multiple minerals, the feature would be tagged with the attribute
resource=Au, Diamant, Fe.
True/false (aka boolean) attributes should only be present for features where the attribute is true. For instance, while an artisanal mine needs to be tagged with an
artisanal=yes attribute, there is no need for an industrial concession to be tagged with
This upload process only applies to Vector Data. If you have Raster Data you would like to upload, contact us.
if you are unsure about any of these guidlines, or are having trouble preparing your dataset, get in touch with us. We are always willing to help out with the process.