Item talk:Q3646: Difference between revisions
(Created page with "We're still working through exactly what the classification should be here, and this may shift as we get clarity. The concept of "mine" might be a type of mining feature (sometimes synonymous with adit), but it is a word we use in referring generally to a mine by name that is in a location operating over some time period. We're using it that way now, and this page provides a way to discuss what we're trying to do with this concept in the GeoKB. = Questions we have about...") |
|||
(One intermediate revision by the same user not shown) | |||
Line 19: | Line 19: | ||
* product or material produced | * product or material produced | ||
* rock names (ore, gangue) | * rock names (ore, gangue) | ||
= Other queries = | |||
== Handling competing location claims == | |||
One core issue we deal with is rectifying cases where we have multiple sources of mine information asserting different geographic locations (generally point coordinates). We've teed up a few examples to work through, both in terms of how we model the information and in how we reason on what we encode. | |||
<sparql tryit="1"> | |||
PREFIX wd: <https://geokb.wikibase.cloud/entity/> | |||
PREFIX wdt: <https://geokb.wikibase.cloud/prop/direct/> | |||
SELECT ?mine ?mineLabel (COUNT(?location) AS ?numLocations) | |||
WHERE { | |||
?mine wdt:P1 wd:Q3646 ; # Instance of mine | |||
wdt:P6 ?location . # coordinate location property | |||
SERVICE wikibase:label { bd:serviceParam wikibase:language "en" . } | |||
} | |||
GROUP BY ?mine ?mineLabel | |||
HAVING (COUNT(?location) > 1) | |||
</sparql> |
Latest revision as of 17:29, 20 July 2023
We're still working through exactly what the classification should be here, and this may shift as we get clarity. The concept of "mine" might be a type of mining feature (sometimes synonymous with adit), but it is a word we use in referring generally to a mine by name that is in a location operating over some time period. We're using it that way now, and this page provides a way to discuss what we're trying to do with this concept in the GeoKB.
Questions we have about mines
These questions help define what properties/predicates we need to have about mines. From that, we can look at how we need to further flesh out the knowledge model to accommodate all the things that need to be linked for answers to these questions to become possible.
- What mining operations are going on now and back through time for a given set of minerals?
- Where are the mines?
- What's their geoscientific context in terms of mineral deposit types and other aspects of their geologic setting?
- What's been extracted from the mining sites in ore, and what do we know about the grade or mineral content of those ores?
Related entities/properties
- Mineral commodities
- Location - both specific geometry and place names at different levels
- Mineral deposit types
- Geologic formations
- Lithostratigraphic entities
- Chronostratigraphic entities
- product or material produced
- rock names (ore, gangue)
Other queries
Handling competing location claims
One core issue we deal with is rectifying cases where we have multiple sources of mine information asserting different geographic locations (generally point coordinates). We've teed up a few examples to work through, both in terms of how we model the information and in how we reason on what we encode.
PREFIX wd: <https://geokb.wikibase.cloud/entity/>
PREFIX wdt: <https://geokb.wikibase.cloud/prop/direct/>
SELECT ?mine ?mineLabel (COUNT(?location) AS ?numLocations)
WHERE {
?mine wdt:P1 wd:Q3646 ; # Instance of mine
wdt:P6 ?location . # coordinate location property
SERVICE wikibase:label { bd:serviceParam wikibase:language "en" . }
}
GROUP BY ?mine ?mineLabel
HAVING (COUNT(?location) > 1)