Predicates and classes used in the faceted-search

[seilagonzalez]

Issue created to include all classes and predicates use by the queries. Version 1

[seilagonzalez]

Predicates: rdf:type rdfs:label rdfs:subClassOf kwg-ont:hasZipCode kwg-ont:hasExpertise kwg-ont:locatedIn geo:hasGeometry geo:sfWithin geo:asWKT sosa:phenomenonTime time:hasBeginning time:inXSDDateTime time:inXSDDate kwg-ont:hasImpact sosa:isFeatureOfInterestOf sosa:hasMember sosa:observedProperty sosa:hasSimpleResult iospress:contributorAffiliation

[seilagonzalez]

Classes: kwg-ont:AdministrativeRegion kwg-ont:ZipCodeArea kwg-ont:USClimateDivision kwg-ont:NWZone kwg-ont:Hazard kwg-ont:EarthquakeEvent kwg-ont:Fire kwg-ont:Wildfire kwg-ont:WildlandFireUse kwg-ont:PrescribedFire kwg-ont:UnknownFire kwg-ont:Hurricane iospress:Contributor kwg-ont:AdministrativeRegion_3 kwg-ont:AdministrativeRegion_2 kwg-ont:ExpertiseTopic

[cogan-shimizu]

Instances: kwgr:Earth.North_America.United_States.USA kwgr:earthquakeObservableProperty.mag kwgr:earthquakeObservableProperty.depth kwgr:deathDirect kwgr:injuryDirect kwgr:hazardtopic.storm.aspecttopic.injury

[zhurui0509]

Thanks @seilagonzalez. I will take a look and provide mapping, where necessary, to you by tomorrow (March 8th).

[zhurui0509]

@seilagonzalez

Predicate: kwg-ont:locatedIn--> kwg-ont:sfWithin kwg-ont:hasImpact--> we do not have this predicate any more. Instead, the relation between an ImpactObservation and a HazardEvent is through sosa:hasFeatureOfInterest (or sosa:isFeatureOfInterestOf reversely)

Class: kwg-ont:Hazard will have subclasses: kwg-ont: Earthquake, kwg-ont:NOAAHazard, kwg-ont:SmokePlumeSnapshot, kwg-ont:Fire

kwg-ont:Fire will have subclasses: kwg-ont:Wildfire (has subclasses kwg-ont:MTBSFire and kwg-ont: NIFCFire), kwg-ont: ComplexFire (has subclasses: kwg-ont: MTBSComplexFire and kwg-ont: NIFCIncidentComplexFire), kwg-ont: OutOfAreaResponseFire (has subclasses: kwg-ont:MTBSOutOfAreaResponseArea) kwg-ont: PrescribedFire (has subclasses: kwg-ont:MTBSPrescribedFire and kwg-ont:NIFCPrescribedFire) kwg-ont: WildlandFireUse (has subclasses: kwg-ont:MTBSWildlandFireUse)

no kwg-ont:UnknowFire

kwg-ont:Hurricane --> kwg-ont:NOAAHurricane

Instances: kwgr:deathDirect --> kwgr:impactObservableProperty.deathDirect kwgr:injuryDirect --> kwgr:impactObservableProperty.injuryDirect

Note: for expert-expertise related terminology (kwg-ont:ExpertiseTopic,kwgr:hazardtopic.storm.aspecttopic.injury), I will come back to you later as the schema is not finalized as I am writing it (but I think there will be no change).

[seilagonzalez]

@ThomasThelen @zilongliu-geo we have to change a bunch of queries, look at all these changes!

[seilagonzalez]

@zhurui0509 thank you so much for all this information, when can we start using the staging graph?

[zilongliu-geo]

Also, I understand while geo:hasGeometry is the same as geosparql:hasGeometry, why do we change the name of the prefix for some zipcode areas? @zhurui0509 @cogan-shimizu

[cogan-shimizu]

I believe this is something weird from graphdb, because they are the same url, but the prefix string has changed. I'm not aware of what caused the actual change in behaviour.

[amoeba]

I bet GraphDB automatically picks up prefixes when data is inserted in an attempt to be helpful. When I look at KWG-Staging I can see the two prefixes:

Are there any downsides to having both? Any of them can be removed.

[cogan-shimizu]

I think the only downside is really usability and convenience. geo: definitely looks better in the tables and queries.

[amoeba]

Seems fine to remove the geosparql one then. Tracking that over on https://github.com/KnowWhereGraph/kwg-seed-graph/issues/361. Thanks @cogan-shimizu.

[zilongliu-geo]

Is it every contributor affiliation connected a level-3 administrative region? I notice that Louisiana State University is only connected to S2 cells but no administrative region is connected to it. @cogan-shimizu @zhurui0509 @seilagonzalez

[seilagonzalez]

passing this issue to thomas so he is aware of this discussion.