Alertwise

Latest version: v1.0.6

Safety actively analyzes 723158 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 10

0.6.1

What's Changed
* Refactor alert xml renderer by erick-otenyo in https://github.com/wmo-raf/cap-composer/pull/68


**Full Changelog**: https://github.com/wmo-raf/cap-composer/compare/0.6.0...0.6.1

0.6.0

What's Changed
* Reenable Admin Boundary selector by erick-otenyo in https://github.com/wmo-raf/cap-composer/pull/66


**Full Changelog**: https://github.com/wmo-raf/cap-composer/compare/0.5.9...0.6.0

0.5.9

What's Changed
- Remove `Unknown` option for urgency,severity and certainty choices. This is not recommended and we want to avoid them deliberately in this implementation
- Remove `Ack` and `Error` as MESSAGE_TYPE_CHOICES. These should be used by receiving tools, and this implementation is only for publishing
- Limit event text to 35 characters
- Add WMO Alerting Authority Object Identifier to CAP setting. This will be used to generate the identifier for CAP as speficied in https://library.wmo.int/records/item/54452-administrative-procedure-for-registering-wmo-alerting-identifiers . Each NMHSs is assigned a WMO OID. Previously we used UUID as the identifier, but this field has been renamed to guid. If no WMO OID is set, we fallback to using the uuid as the identifier
- Remove audience fields from CAP settings, and instead allow case by case input, and make it a text field for more characters
- Add Geocode fields to every alert area drawing tool. This way, if a geocode needs to be set, it must be accompanied by a polygon or circle
- Remove the AdminBoundary Selector from list of tools to use for creating the alert area. Unfortunately the Boundaries were notorious for causing errors like intersection errors for multiple areas, large boundaries with many vertices were causing loading issues and exceeding the recommended number of 100 vertices


**Full Changelog**: https://github.com/wmo-raf/cap-composer/compare/0.5.8...0.5.9

0.5.8

What's Changed
- Rename uuid field to guid instead of identifier
- Add wmo_oid to CAP Settings field for use in generating CAP message identifier
- Remove Admin Boundary from options for creating alert areas. Admin Boundary selector was causing alot of alert geometry errors due to topological issues and the large number of nodes


**Full Changelog**: https://github.com/wmo-raf/cap-composer/compare/0.5.7...0.5.8

0.5.7

What's Changed
* Make OSM default basemap


**Full Changelog**: https://github.com/wmo-raf/cap-composer/compare/0.5.6...0.5.7

0.5.6

What's Changed
- Change polygon coordinates truncating precision to 6


**Full Changelog**: https://github.com/wmo-raf/cap-composer/compare/0.5.5...0.5.6

Page 3 of 10

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.