Files
notifications-admin/requirements.txt

214 lines
4.3 KiB
Plaintext
Raw Normal View History

#
# This file is autogenerated by pip-compile
# To update, run:
#
# pip-compile requirements.in
#
ago==0.0.93
# via -r requirements.in
awscli-cwlogs==1.4.6
# via -r requirements.in
2021-04-14 10:57:38 +01:00
awscli==1.19.51
# via
# awscli-cwlogs
# notifications-utils
bleach==3.3.0
# via notifications-utils
blinker==1.4
# via
# -r requirements.in
# gds-metrics
2021-04-14 10:57:38 +01:00
boto3==1.17.51
# via notifications-utils
2021-04-14 10:57:38 +01:00
botocore==1.20.51
# via
# awscli
# boto3
# s3transfer
cachetools==4.2.1
# via notifications-utils
certifi==2020.12.5
# via requests
chardet==4.0.0
# via requests
click==7.1.2
# via flask
2021-04-13 10:11:51 +01:00
colorama==0.4.3
# via awscli
2021-04-13 10:11:51 +01:00
dnspython==1.16.0
# via eventlet
docopt==0.6.2
# via notifications-python-client
2021-04-13 10:11:51 +01:00
docutils==0.15.2
# via awscli
et-xmlfile==1.0.1
# via openpyxl
2021-03-08 13:55:04 +00:00
eventlet==0.30.2
# via -r requirements.in
flask-login==0.5.0
# via -r requirements.in
flask-redis==0.4.0
# via notifications-utils
flask-wtf==0.14.3
# via -r requirements.in
flask==1.1.2
# via
# -r requirements.in
# flask-login
# flask-redis
# flask-wtf
# gds-metrics
# notifications-utils
gds-metrics==0.2.4
# via -r requirements.in
geojson==2.5.0
# via notifications-utils
govuk-bank-holidays==0.8
# via
# -r requirements.in
# notifications-utils
git+https://github.com/alphagov/govuk-frontend-jinja.git@v0.5.8-alpha#egg=govuk-frontend-jinja==0.5.8-alpha
# via -r requirements.in
greenlet==1.0.0
# via eventlet
2021-04-05 14:55:04 +01:00
gunicorn==20.1.0
# via -r requirements.in
2021-04-12 14:55:03 +01:00
humanize==3.4.0
# via -r requirements.in
2021-04-13 10:11:51 +01:00
idna==2.10
# via requests
itsdangerous==1.1.0
# via
# -r requirements.in
# flask
# flask-wtf
# notifications-utils
jinja2==2.11.3
# via
# flask
# govuk-frontend-jinja
# notifications-utils
jmespath==0.10.0
# via
# boto3
# botocore
lml==0.1.0
# via
# pyexcel
# pyexcel-io
lxml==4.6.3
# via
# pyexcel-ezodf
# pyexcel-ods3
markupsafe==1.1.1
# via
# jinja2
# wtforms
mistune==0.8.4
# via notifications-utils
notifications-python-client==6.0.2
# via -r requirements.in
Estimate number of phones in an arbitrary polygon We want to know how many phones are in a user-supplied polygon, so we can show the impact of a broadcast, in the same way that we do when users pick areas from our library. We already know how many phones are in each electoral ward. But there are challenges with an arbitrary polygon: - where it does overlap a ward, the overlap could be partial - it could overlap more than one ward - finding out which wards it overlaps by brute force (looping through all the wards and seeing which ones intersect with our polygon) would be way to slow to do in real time Instead we can use a data structure called an R-tree[1] to build an index which provides a much, much faster way of looking up which polygons overlap another. We can build this tree in advance and save it somewhere, which means there’s a lot of computation we don’t need to do in real time. The R-tree returns a set of objects (ward IDs) which we can go and look up in our library of electoral wards. These wards will be the ones that might have some overlap with our custom polygon. Once we have this small set of wards which might overlap our ward, we can look at the size of the area of overlap (relative to the size of the whole ward) and multiply that by the known count of phones in that ward to get an approximation of the count of phones in the overlap area. Summing these approximations give an estimate for the whole area of the custom polygon. 1. https://en.wikipedia.org/wiki/R-tree
2021-03-18 23:02:32 +00:00
git+https://github.com/alphagov/notifications-utils.git@44.2.0#egg=notifications-utils==44.2.0
# via -r requirements.in
2021-03-15 13:55:08 +00:00
openpyxl==3.0.7
# via pyexcel-xlsx
orderedset==2.0.3
# via notifications-utils
packaging==20.9
# via bleach
phonenumbers==8.12.21
# via notifications-utils
prometheus-client==0.10.1
# via
# -r requirements.in
# gds-metrics
pyasn1==0.4.8
# via rsa
pyexcel-ezodf==0.3.4
# via pyexcel-ods3
pyexcel-io==0.6.4
# via
# -r requirements.in
# pyexcel
# pyexcel-ods3
# pyexcel-xls
# pyexcel-xlsx
pyexcel-ods3==0.6.0
# via -r requirements.in
pyexcel-xls==0.6.2
# via -r requirements.in
pyexcel-xlsx==0.6.0
# via -r requirements.in
pyexcel==0.6.6
# via -r requirements.in
pyjwt==2.0.1
# via notifications-python-client
pyparsing==2.4.7
# via packaging
pypdf2==1.26.0
# via notifications-utils
python-dateutil==2.8.1
# via
# awscli-cwlogs
# botocore
python-json-logger==2.0.1
# via notifications-utils
pytz==2021.1
# via
# -r requirements.in
# notifications-utils
pyyaml==5.4.1
# via
# awscli
# notifications-utils
redis==3.5.3
# via flask-redis
requests==2.25.1
# via
# awscli-cwlogs
# govuk-bank-holidays
# notifications-python-client
# notifications-utils
2021-03-08 13:55:12 +00:00
rsa==4.7.2
# via awscli
rtreelib==0.2.0
Estimate number of phones in an arbitrary polygon We want to know how many phones are in a user-supplied polygon, so we can show the impact of a broadcast, in the same way that we do when users pick areas from our library. We already know how many phones are in each electoral ward. But there are challenges with an arbitrary polygon: - where it does overlap a ward, the overlap could be partial - it could overlap more than one ward - finding out which wards it overlaps by brute force (looping through all the wards and seeing which ones intersect with our polygon) would be way to slow to do in real time Instead we can use a data structure called an R-tree[1] to build an index which provides a much, much faster way of looking up which polygons overlap another. We can build this tree in advance and save it somewhere, which means there’s a lot of computation we don’t need to do in real time. The R-tree returns a set of objects (ward IDs) which we can go and look up in our library of electoral wards. These wards will be the ones that might have some overlap with our custom polygon. Once we have this small set of wards which might overlap our ward, we can look at the size of the area of overlap (relative to the size of the whole ward) and multiply that by the known count of phones in that ward to get an approximation of the count of phones in the overlap area. Summing these approximations give an estimate for the whole area of the custom polygon. 1. https://en.wikipedia.org/wiki/R-tree
2021-03-18 23:02:32 +00:00
# via -r requirements.in
2021-04-14 10:57:38 +01:00
s3transfer==0.3.7
# via
# awscli
# boto3
shapely==1.7.1
# via
# -r requirements.in
# notifications-utils
six==1.15.0
# via
# awscli-cwlogs
# bleach
# eventlet
# govuk-bank-holidays
# python-dateutil
smartypants==2.0.1
# via notifications-utils
statsd==3.3.0
# via notifications-utils
texttable==1.6.3
# via pyexcel
urllib3==1.26.4
# via
# botocore
# requests
webencodings==0.5.1
# via bleach
werkzeug==1.0.1
# via flask
wtforms==2.3.3
# via flask-wtf
2021-04-13 10:11:51 +01:00
xlrd==1.2.0
# via pyexcel-xls
xlwt==1.3.0
# via pyexcel-xls
# The following packages are considered to be unsafe in a requirements file:
# setuptools