-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graph discrepancies from KW Panels #4
Comments
@antreac Can you please narrow down which queries are causing these problems? For example, which queries construct a |
Please note this issue is still in progress. I will comment again when it is finalized |
Ok @antreac , I've completed this issue description so go ahead, and let me know if you have any questions. |
I have updated the construct-queries.md document so it will be available once Cogan merge the pull request, after that please let me know if there are any more questions. I will check the issues mentioned above and reach out to you with questions. @fritosxii |
Issue 1 I have included a new predicate in the graph to capture the specific hazard/disaster type of the HazardEvent. So for e.g. the example pointed above in issue 1 is now a Winter Storm. |
Is this consistent across all HazardTypes, i.e., there are no more subclasses to HazardEvent? |
For definition,
KW Panel compliant
refers to a HazardEvent that hashasName
andhasKWGEntity
defined, or a Place that hashasKWGEntity
andhasPlaceType
defined (hasName
is optional currently on Place entities because the main graph has many non named places)Here is the Google Sheets spreadsheet that lead me to the following conclusions: https://docs.google.com/spreadsheets/d/1enzC86uybXngr6BBtf-Vi8NGfcwHVgvHWQOvlEgqGUw/edit#gid=934262946
Hazards
hasImpacted
is connected to several fires, but all those fires are not KW Panel compliant, and seem to only havehasImpacted
as a propertyaffectedAreaInAcres
anddamageToCropsInDollars
are also present but only attached to entities that are not KW Panel compliant:Places
sfWithin
andsfTouches
do not point to any KW Panel compliant Place entities.sfContains
has the same problem, but there is 1 valid relationsfOverlaps
has the same problem, but there are 27 valid relationsimpactedBy
does not point to any KW Panel compliant HazardEvent entities.Place Year Data
hasKWGEntity
property, and therefore are not KW Panel compliant. Here's an example from 1 of those properties:The text was updated successfully, but these errors were encountered: