Metadata Matters: Making Spatial Data Trustworthy
In July 2025, I carried out the process of updating the administrative village boundary dataset. This dataset is crucial because it serves as the foundation for development planning, resource management, and even resolving boundary disputes. The update process refers to Minister of Home Affairs Regulation No. 45 of 2016 on Guidelines for the Establishment and Affirmation of Village Boundaries.
This experience reminded me that working with spatial data is not only about drawing boundaries on a map. It’s equally about documenting every step of the update process to ensure accountability. Metadata plays a key role in making spatial data trustworthy, reusable, and accessible for different stakeholders.
So, talking with process, I documented the workflow directly in QGIS. Here are the steps you could follow:
1. Importing the Shapefile
I opened QGIS and added the latest shapefile named IGT_BatasDesa_Juli2025 (make sure the file you want to create the meta data). Once the layer was successfully added, the village boundary polygons appeared on the map canvas, representing administrative areas in Indonesia. A notification at the top confirmed that the layer was successfully exported and saved into my project folder.
2. Opening the Metadata Menu
After loading the layer, the next step was to add metadata. To do this, I right-clicked the layer and selected Properties > Metadata.
Once completed, I saved the metadata file using the Save Metadata to File option. The metadata was stored in .qmd format under the name Metadata_Juli2025.qmd. This file can be reloaded later if needed, or shared along with the main shapefile to maintain complete documentation.
With the metadata saved, the July 2025 village boundary dataset is now ready for use in spatial analysis, thematic mapping, or integration with other datasets such as population, infrastructure, and development planning. Thanks to its metadata, the dataset is more reliable and transparent, as it clearly states its source, update process, and legal foundation.
However, since the file is stored in .qmd format, the information is somewhat limited. If your goal is simply to manage Quarto documents locally, this format is sufficient. But if you need metadata for broader purposes (such as external data management, compliance, or digital archiving) you’ll require a more comprehensive metadata standard (e.g., ISO 19115, Dublin Core, or FGDC).
And here’s the catch: for formal administrative use, compliance with ISO metadata standards is required. That’s why, in the end, I had to switch to ArcGIS, which provides more robust tools for creating ISO-compliant metadata. HAHAHAHA But Thankyou for reading. Now, You know, right?
Comments
Post a Comment