For definition, KW Panel compliant refers to a HazardEvent that has hasName and hasKWGEntity defined, or a Place that has hasKWGEntity and hasPlaceType 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
- There are some hazards that are only HazardEvent, and don't have a specific type like Tornado. Should we include these entities?
- There are also random entities that aren't of type HazardEvent, but have a specific hazard type. Should we ignore these?
- For extra context, there are 1000+ NOAAWildfires in the graph, but only 1 is actually attached to HazardEvent:
- Lastly I should note that these 1000+ fires are not KW Panel compliant, while the one fire that is a HazardEvent has the expected data:
- Hurricane and Earthquake also have the same issue of having 1000s of records, but none of them are HazardEvents, and none are KW Panel compliant:
hasImpacted is connected to several fires, but all those fires are not KW Panel compliant, and seem to only have hasImpacted as a property
affectedAreaInAcres and damageToCropsInDollars are also present but only attached to entities that are not KW Panel compliant:
Places
sfWithin and sfTouches do not point to any KW Panel compliant Place entities.
sfContains has the same problem, but there is 1 valid relation
sfOverlaps has the same problem, but there are 27 valid relations
impactedBy does not point to any KW Panel compliant HazardEvent entities.
Place Year Data
- For this I am going to let the Google Sheets above speak for itself
- For the 2018-2022 data, these properties exist and work, but some of them just aren't present in KWG Lite (so I assume they also are not in the main graph)
- For the Jan2021-Dec2021 temperature properties, they all exist and have data, but are all attached to climate divisions that do not have a
hasKWGEntity property, and therefore are not KW Panel compliant. Here's an example from 1 of those properties:
For definition,
KW Panel compliantrefers to a HazardEvent that hashasNameandhasKWGEntitydefined, or a Place that hashasKWGEntityandhasPlaceTypedefined (hasNameis 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
hasImpactedis connected to several fires, but all those fires are not KW Panel compliant, and seem to only havehasImpactedas a propertyaffectedAreaInAcresanddamageToCropsInDollarsare also present but only attached to entities that are not KW Panel compliant:Places
sfWithinandsfTouchesdo not point to any KW Panel compliant Place entities.sfContainshas the same problem, but there is 1 valid relationsfOverlapshas the same problem, but there are 27 valid relationsimpactedBydoes not point to any KW Panel compliant HazardEvent entities.Place Year Data
hasKWGEntityproperty, and therefore are not KW Panel compliant. Here's an example from 1 of those properties: