latitude, longitude, Source, external_id & unit_of_measurement, all show up in the UI
but none of the properties about each event are being pulled through. Not sure if a custom component needs to be created to read the specific JSON properties of the GeoNet Quake & Volcanic API or its a config error on my part.
@exxamalte i see you did a lot of work on the other GeoJSON integrations any chance you could lend a hand?
The reason for this is that the geo_json_events platform is really just a generic GeoJSON integration and none of the additional properties are standardised.
A specific integration for each feed would be required to pull all the information in and present it in a meaningful way.
I have built a couple of Python libraries for GeoJSON/GeoRSS integrations, and itâs not really complicated to implement some more. I am currently in the process of migrating the existing GeoJSON libraries to an async model which will hopefully work better and faster with HA and will allow us to create config flows so that you can configure the integration from within the user interface.
I could maybe use GeoNetâs earthquake feed as a trial for this new approach.
Give me a bit of time, and hopefully you can live with the simple geo_json_events integration in the meantime.
Hey I have an earthquake report (2 actually) that seem to have moved location. (can be seen on the history graph). Is this Geonet correcting the positioning once they get better data?
i always noted that they say once there was a quake that the estimated location and depth was this and that and then later they update the exact locations and depth
Why do the magnitudes of posted earthquakes sometimes change?
Earthquakes are posted to the website as soon as data start to come in. They are now located automatically without being reviewed by a duty officer or analyst. The magnitude and precise position of the quake may change when more data become available or if they are reviewed by the duty officer or analyst.
The integration always uses the latest data from the feed to calculate the exact distance to your home.
FYI - release 0.103 contains the GeoNet NZ Volcanic Alert Level integration which adds a sensor for each volcanoe in the specified radius. The sensorâs value is the current alert level.
Please let me know if this is useful or if you feel that anything is missing.