File codes and minerals published in RUCOM in Cumbal
Count of 1 distinct file code associated with Cumbal in the ANM copy · does not locate mines or certify current operation.
1 layer · 1 published record · National Mining Agency · RUCOM; IGAC geometry; counted and adapted by GeoSAT
Open this query ↗File codes and minerals published in RUCOM
Count of 1 distinct file code associated with Cumbal in the ANM copy · does not locate mines or certify current operation
Open this query to inspect published records on the map, their attributes and each source’s dates. Empty, unavailable or partial results do not establish that no conditions apply.
Open this query in the viewer ↗What it includes
- Published mining-title file codes · RUCOM
1 record · date not declared · CC BY-SA 4.0 · IGAC geometry CC BY 4.0
National Mining Agency · RUCOM; IGAC geometry; counted and adapted by GeoSAT · Source checked: 2026-10-06
GeoSAT count of distinct file codes associated with the municipality in ANM’s RUCOM mining-title publication. Copy retrieved on 6 October 2026; catalog data load: 18 March 2026, with no record cutoff date. Rows can repeat file codes by mineral or other attributes: each code is counted once per municipality. Do not sum municipalities to obtain a national total. This is not the complete mining-title cadastre, an inventory of operating mines or a production measurement. Inclusion in this copy does not certify current legal status, environmental authorizations or activity: verify the official file and RUCOM. Original mineral labels, including spelling variants, are retained; they are not a standardized classification. Holder names, personal IDs and contact details are excluded. No mining geometries are provided: the IGAC polygon identifies the whole municipality, not a title, plant or extraction area; moving the map does not allocate the count. Reference generalized to approximately 0.000172 degrees and six decimals, mapping date undeclared; unsuitable for area measurements or densities. ANM data and GeoSAT adaptation CC BY-SA 4.0; IGAC geometry CC BY 4.0.
Official source ↗Diccionario ANM / ANM field definitions ↗
Preguntas oficiales RUCOM / Official RUCOM FAQ ↗
Consulta oficial RUCOM / Official RUCOM query ↗
How to use it
- Click “Open this query” to load Published mining-title file codes · RUCOM in the viewer.
- Select a feature on the map or in the Results list to read its record with attributes, source and date.
- Build a thematic map to compare, or open statistics to analyze the loaded data.
- Share the view link or export received results with attribution and dates.
Frequently asked questions
What does “File codes and minerals published in RUCOM” count?
Published mining-title file codes · RUCOM: distinct file codes associated with Cumbal in ANM publication 42ha-fhvj. Rows can repeat a code by mineral or other attributes; GeoSAT counts it once per municipality. This is not the complete mining-title cadastre or a count of operating mines. Do not sum municipalities to obtain a national total.
Does the map locate extraction and confirm it is active?
No. The table has no mining geometries. The IGAC polygon identifies the municipality, not a title, plant or mine. The RUCOM publication does not measure production; this copy does not certify current legal or environmental status either. Verify the file code in official ANM services. Plant entries marked “POR CONFIRMAR” are not converted into availability claims.
How old is the information, and how do I read the minerals?
The catalog data load is dated 18 March 2026 and the copy was retrieved on 6 October 2026. No record cutoff date is published. Select the municipality to read file codes and mineral labels. Source spelling variants are retained, without standardizing them or counting them as unique minerals.
What can I export, and under which license?
Export the received municipal aggregate with source, method and retrieval date. ANM data and the GeoSAT adaptation are CC BY-SA 4.0; IGAC reference geometry is CC BY 4.0, generalized and without a declared mapping date. Holder names, personal IDs and contacts are excluded. The geometry is unsuitable for area measurements or densities.