BersandarPadaStandar7 : Let's Make Metadata

Main ideas, concepts, and lessons

• Metadata is essential for geospatial data

  • Metadata is “data about data” describing spatial resources so they can be found, used, analyzed, searched, and managed.
  • It improves data dissemination and reuse, helps users judge whether data matches their needs, and enables international sharing using standardized language/structure.

• Indonesia’s policy direction: “One Data Indonesia” / “One Map”

  • Standardized metadata supports the government’s principle of one data and helps build a quality geospatial information ecosystem.

• Indonesia mandates standardized geospatial metadata (BIG / Peraturan)

  • The webinar focuses on preparing metadata according to BIG Regulation No. 3 of 2023, including later development of the BIG Metadata Editor to implement those standards.
  • The metadata standard is built from a regulatory framework:
    • Law No. 4 (2011)
    • Presidential regulations
    • BIG regulations (including Perbig 3/2023 and related SNI-based standards)

• Metadata standards are based on the ISO 19115 family + encoded XML standards

  • Indonesia’s SNI profiles adapt ISO metadata structure, including:
    • SNI 8843 (Indonesia profile of ISO metadata framework; metadata structure)
    • Additional SNI/ISO parts for acquisition/process, quality, and encoding (XML)
  • Metadata must be encoded in a computer-readable format (XML) to be published and harvested by geoportals.

• A typical “metadata lifecycle” parallels the geospatial data lifecycle

  • Geospatial information (IG) production stages: planning → acquisition/collection → processing → storage/distribution → use
  • Metadata is prepared across these stages, with responsibility split among roles like:
    • Data producers (planning/production fields, quality-related inputs)
    • Data guardians (final quality/dissemination fields before public access)

• The Indonesian metadata profile organizes information into “13 packages/classes”

  • At a high level, the profile includes repeating core concepts such as:
    • Identifiers (with authority/codes and code space scope)
    • MD scope (what entity the metadata describes: dataset, feature type, etc.)
    • Spatial/temporal coverage and references
    • Citation and responsibility
    • Content information (abstract, status, resolution, topic categories, keywords)
    • Coverage / extent description
    • Data lineage
    • Data quality information (quality measure + evaluation method + results)

• Quality results must include both “how measured” and “what result”

  • Quality information should express:
    • Quantitative or qualitative results
    • Evaluation method and reference/criteria
    • Whether measured results conform to standards

• Why a metadata editor is needed

  • Many existing metadata implementations are incomplete or inconsistent when hand-coded (e.g., Notepad/Excel issues like wrong datatypes, wrong placements, wrong code list values).
  • The BIG Metadata Editor (BigM) is intended to:
    • Create metadata from scratch
    • Convert older XML formats to the newer standard
    • Validate structure and content before export

---

Methodology / workflow steps taught (detailed)

A) Create or convert metadata using Big Metadata Editor (BigM)

Access

• Web-based; no installation required
• No login required for the web editor (an account may be needed later for SSO integrations)

Choose mode

• Create new metadata
  • Start with an empty form
• Import XML
  • Import from a local XML file, or
  • Import via a repository catalog (explained as being handled in a later session)

Conversion

• If the XML uses an older metadata encoding format, BigM detects it and converts automatically.
  • Example: conversion from older ISO metadata XML versions to the newer SNI/ISO 19115 D3-based encoding

Validation during editing

BigM provides:

• Completeness/progress indicators for packages/classes
• Validation instructions for required fields
• Validation checking for:
  • Correct namespace
  • Correct package/element placement
  • Correct data types (e.g., character string vs integer)
  • Correct code list values (dropdown-constrained values must match ISO/SNI lists)

Editing approach

• Fill “blank/invalid” fields until packages show as complete
• Use in-editor search to jump to elements
• Use the XML panel to confirm the element uses the right code list/value type

Metadata identifier requirement

• The metadata identifier must be unique so it can link geospatial data with metadata in the geoportal
• Example naming pattern idea (conceptual):
  • [element] [scale] [region] [year] (to keep it comprehensive and unique)

Export

• After completing required elements (and as much optional/conditional content as possible), export/download XML
• The resulting XML is then used for publication

---

B) Publish and expose metadata through geoportals / national services (CSW harvesting model)

Publish concept

• Metadata is stored in a catalog server so geoportals can discover it
• Spatial services and metadata services are paired:
  • Metadata describes datasets and links to service endpoints

CSW (Catalog Service for the Web) requirements

• Geoportal publishing/discovery uses CSW endpoints
• Goal: interoperability, discoverability, and reuse for connected national nodes

Key CSW operations

• Configure and verify support for operations such as:
  • GetCapabilities
  • GetRecords / GetRecordById (as referenced in the session)

Harvesting & security considerations

• Harvesting must be carefully configured to avoid creating security loopholes
• Restrict access to allowed IPs/domains where relevant

Verification testing

• Test the CSW endpoint using browser/URL patterns (examples referenced such as /CSW, /catalog/csw, etc.)
• Confirm the CSW supports the required XML metadata profile/schema (e.g., MDB/ISO 19115 D3)
  • If the schema/profile is not supported, it may still be readable but may require conversion/compatibility handling
• Ensure the CSW endpoint is reachable
  • If geoportals are overly secure and block harvesting, discovery/publishing is ineffective

Publishing through Palapa (where applicable)

• After XML is produced/exported:
  • Upload or paste XML into Palapa’s publication interface
  • Ensure metadata links distribution services via the online resource URL
    • Example: WMS endpoint + workspace/layer name
  • Replace placeholders like localhost with the real domain and service path

Result

• Once published and harvested, metadata becomes discoverable via the geoportal ecosystem and can propagate to national-level portals

---

C) Guidance given during Q&A (practical constraints)

Do you need 100% completion?

• The session indicates:
  • Mandatory vs optional/conditional items are governed by the SNI profile
  • The editor enforces mandatory fields via validation (XML export may be blocked if mandatory items are missing)
  • The progress indicator is recommended to be filled as completely as possible, but publication may be staged if some elements are not yet available

If metadata already exists

• It may require reformatting/conversion
  • Example: conversion from older ISO 19139 to newer ISO 19115 D3 encoding/profile
• BigM can assist with converting older XML formats

Open-source metadata tools

• Tool choice is less important than standards compliance
• Tools must produce metadata conforming to the mandated SNI/ISO profiles

Non-spatial datasets

• Standards can technically apply beyond spatial data, but regulatory applicability may differ
  • There may be separate rules for statistical/non-geospatial domains

---

Speakers / sources featured (as named in the subtitles)

Speakers (identified by name/titles in the subtitles)

• Mr. Abdul Rasid — Director of Geospatial Information Technology and Standards (welcoming/opening)
• Mr. Abdul Rasyid / Abdur Rasyid — appears in the opening sequence (same context as the welcome; likely the same official)
• Ms. Ratih — moderator/host (named repeatedly)
• Mr. Ibnu Sofyan — Deputy for Geospatial Information Infrastructure (opening speech)
• Mr. Budi Herbroho / Budi Heri / Budi Herbroho — Young Expert Mapping Surveyor at BIG (metadata standards session)
• Mas Bagus Wiratmoko — introduces Big Metadata Editor practice session
• Mr. Muhammad Hasanudin Yusa — metadata publication and CSW session
• Mr. Geri / Mas Geri — quiz moderator/host
• Mr. Sisa (Mr. Sisa …) — answers a question about BigM accounts/no-login
• Mr. Muzakir Ahmadi — participant questioner (South Sumatra)
• Mr. Novi Adi — participant questioner (KKP/fisheries-related question)
• Mr. Ardiansah — participant questioner (Anambas Islands; governance/staging needs)
• Mr. Adiant / other Anambas respondent — appears in the Q&A flow
• Mr. Aldi / Andrian / Ardiansyah — quiz winners mentioned near the end
• Mr. Aldi — also appears in the winner confirmation segment

Institutional / regulatory sources referenced

• BIG (Badan Informasi Geospasial / Geospatial Information Agency)
• BIG Regulation No. 3 of 2023
• Perbig 3 of 2025 — referenced as timeline/updates about mandatory SNI metadata
• Law No. 4 of 2011 (especially Article 49 paragraph 2)
• Presidential Regulations referenced (including Perpres 27/2014 and Prespres 39/2019)
• SNI standards referenced
  • SNI 8843 and related parts
  • SNI ISO 19115 D2/D3 (acquisition/process and encoding)
  • ISO 19157 (data quality)
  • Additional ISO updates mentioned (e.g., consolidation updates related to 19157)
• ISO base concepts
  • Metadata as information about resources; ISO 19115 family

Platforms/services referenced

• BIG Metadata Editor (BigM)
• Palapa Geoportal
• INA Geoportal / TanahAir portal (tanahir.indonesia.go.id referenced)
• CSW (Catalog Service for Web)
• OGC services referenced: WMS, WFS, WCS, WMTS
• Geoserver / workspace layer naming referenced
• QGIS (referenced in Q&A)
• ArGIS / ArcGIS Pro (commercial metadata editor example)
• MD Editor / CATMD Edit (regional tool referenced in Q&A)
• Slido (used for questions)