* Add additional base layers behind feature flags
- add voyager base layer under vy
- add positron base layer under ps
* Add mapbox base layer
- requires API token
* Add mapbox layers with API token in URL
* Add base map layers from mapTiler
- add comments to mapping components
- add mapTiler base maps behind feature flags
* Comment out intermittent cypress test failures
* Add flag to remove label layer
* Add MapBox Raster and Vector tiles
- tilesets are commented out until more information is provided by Mikel
* Remove white layer on non-prioritized features
- removes makePaint function
- adds Todo to renaming constants
* refactor all contants to have standard naming
- renames layers, sources, colors, opacity, and zoom
- Adds a large amount of comments to understand how this map works
* remove some instances of mapbox-gl
- this the first step in having only maplibre-gl being used in app
* Remove chroma.js
- chroma.js was used in the fill function of makeStyle. This was used to create a gradient between non-prio, threshold and prio. Since these 3 step values are no longer needed this function along with the libraries it used is not removed.
* Add comments on mapbox base layer
- adds apiaccesstoken
* set basemap to mapbox and move all layers to Map
* Add API KEY to .env, adjust opacity of prio'd CBTs
- remove this function as it is no longer being used
- add comments on map
- create a high layer opacity and low layer opacity
- add API KEY to prod and dev .env
- add MapBox API key to deploy_staging
* add logging to troubleshoot API KEY
* Remove temp echo of API KEY
* Add GHA env var to gatsby config
* Remove API KEY from GitHub and GHA
* Install and run pandas-vet
This doesn't fix the errors, but it can give us a starting point for the
discussion of which of these errors we care about.
* Ignore the errors for now
* Ignore eeoc.gov in link checker
Sometimes it seems down from the perspective of github actions.
* Add pyproject.toml to fix docker compose build
Even though we want to use locked dependencies, pyproject.toml is still
required.
* update Dockerfile
Co-authored-by: Jorge Escobar <83969469+esfoobar-usds@users.noreply.github.com>
* Add category header (Indicator and Percentile)
- add local styling
- override accordion-content styles to push into parent container
- intl copy
- update snapshots
* Add latest Living Copy
- refactor dataset cards to allow for any styling in description, used in and responsible party
- add percent for HS edu indicator
- updates snapshots
* Update copy from Living Copy doc
-update snapshots
* Add methodology to copy
* Remove link from readme file based on md checker
* Comment out certain markdown links from checker
* Comment out markdown links that render in browser
* Add missing methodology to Clean Water
* Run markdown link checker only on markdown changes
This makes sure that this action only runs if the pull request is on the
main branch and is changing markdown files.
Fixes: https://github.com/usds/justice40-tool/issues/1114
* Remove push to main trigger
* Ignore eeoc.gov in link checker
Sometimes it seems down from the perspective of github actions.
* Remove requirements.txt as a dependency
This converts both docker and tox to use poetry, eliminating usage of
requirements.txt in both flows.
- In tox, uses the tox-poetry package which installs dependencies from
the lockfile.
- In docker, uses
https://stackoverflow.com/questions/53835198/integrating-python-poetry-with-docker
as a reference.
* Don't copy pyproject.toml
* Remove obsoleted docs about requirements.txt
* Add --full-trace option to pytest
* Fix liccheck
liccheck works with requirements.txt, not with poetry, so there needs to
be an extra translation step.
* TEMP: Add WIP fix for pandas issue
This is just to see if the github actions would pass once this fix gets
merged, but it's being reviewed separately.
* Revert "TEMP: Add WIP fix for pandas issue"
This reverts commit 06e38e8cc77f5f3105c6e7a9449901db67aa1c82.
* Add category header (Indicator and Percentile)
- add local styling
- override accordion-content styles to push into parent container
- intl copy
- update snapshots
* Add latest Living Copy
- refactor dataset cards to allow for any styling in description, used in and responsible party
- add percent for HS edu indicator
- updates snapshots
* Update copy from Living Copy doc
-update snapshots
* Add methodology to copy
* Remove link from readme file based on md checker
* Comment out certain markdown links from checker
* Comment out markdown links that render in browser
* wip - added tests - 1 failing
* added check for empty series + added test
* passing tests
* parallelism in variable assingnment choice
* resolve merge conflicts
* variable name changes
* cleanup logic and move comments out of main code execution + add one more test for an extreme example eith -np.inf
* cleanup logic and move comments out of main code execution + add one more test for an extreme example eith -np.inf
* revisions to handle type ambiguity
* fixing tests
* fix pytest
* fix linting
* fix pytest
* reword comments
* cleanup comments
* cleanup comments - fix typo
* added type check and corresponding test
* added type check and corresponding test
* language cleanup
* revert
* update picke fixture
Co-authored-by: Jorge Escobar <jorge.e.escobar@omb.eop.gov>
* Re-export requirements.txt to fix version errors
The version of lxml in this file had a known vulnerability that got
caught by the "safety" checker, but it is updated in the poetry files.
Regenerated using:
https://github.com/usds/justice40-tool/tree/main/data/data-pipeline#miscellaneous
* Fix lint error
* Run lint on all envs and add comments
* Ignore testst that fail lint because of dev deps
* Ignore medium.com in link checker
It's returning 403s to github actions...
Fixes: https://github.com/usds/justice40-tool/issues/947
This is ensuring we at least have some way to rollback in the worst case
scenario of the data being corrupted somehow, and our upstream data
sources being down in a way that prevents us from regenerating any
datasets. See
https://github.com/usds/justice40-tool/issues/946#issuecomment-989155252
for an analysis of the different ways the pipeline can fail and their
impacts.
This guide is very brittle to pipeline changes, and should be considered
a temporary solution for the worst case. I think that someday the github
actions should run more frequently and write to different paths, perhaps
with a timestamp. That would make rolling back more straightforward, as
a previous version of the data would already exist at some path in s3.
* draft wip
* initial commit
* clear output from notebook
* revert to 65ceb7900f
* draft wip
* initial commit
* clear output from notebook
* revert to 65ceb7900f
* make michigan prefix for readable
* standardize Michigan names and move all constants from class into field names module
* standardize Michigan names and move all constants from class into field names module
* include only pertinent columns for scoring comparison tool
* michigan EJSCREEN standardization
* final PR feedback
* added exposition and summary of Michigan EJSCREEN
* added exposition and summary of Michigan EJSCREEN
* fix typo
Co-authored-by: Saran Ahluwalia <ahlusar.ahluwalia@gmail.com>
* Refactor map click event architecture
- combine territory map clickHandlers
- centers AS on the map
* Center US on the map
- make the east and west coast both viewable
- make clicking on the 48, show the same zoom/lat/long as initial map
- centers Hawaii on map
* Update link to map performance
* Explicitly show links as the links return a 403
* Removes link and spells link out
* Make latest copy changes
- update snapshots
* Update cypress test on feedback link
- update snapshot
* Update side panel and copy
- update snapshots
* Make 2nd EO link open in new tab
* Add latest changes from Living copy
* Add back HS indicator to map
* Add "X of Y thresholds exceed" to side panel
- update snapshots
* Update with latest copy
* Update to latest copy
- make BETA pill in logo bold
- correct exceed to exceeded
- update snapshots
- update page title to Meth & data
* Update total indicators to 21
* Update snapshot
* First pass of updating documentation for new users
Trying to look at this from the perspective of someone new to the
project, and create some pathways to make it easier for people to get to
the content they are looking for.
* Make it clear that docker is doing the setup
* Link installation again from the main README
* Add some docs about the github actions
* Add markdown link check
* Move git installation first
* Add config for markdown link checker
* Fix some links
* Correct handling of repo root relative links
* Fix broken links in data roadmap
* Fix more broken links
* Fix more links
* Ignore link that's returning a 403 to the checker
It actually works if you go in a browser.
* Fix another broken link
* Ignore more urls that don't work
* Update the readme under docs
* Add some more dataset links
* More strongly call out the quickstart
* Try to call out even more the quickstart link
* Fix dead links
* Add note about initialization time
* Remove broken link from spanish install guide
These will be updated later with a full translation
- comment out GU and VI code
- remove search from feature flag
- keep comment on search production bug when wrapping div
- add note on territories
- add territories copy to constants
* Remove un-needed state and useEffect vars
* Add initial Accordion UI to side panel
- abstract out Indicators to separate component
- add snapshot test
- define new indicators in EXPLORE copy
- intl copy to AreaDetail component
* Make side panel indicators styling match design
* Rename export IndicatorCategory -> CategoryCard
* Add disadvangted dots to category and indicators
- add new Category component
- add new DisadvantageDot component
- make copy corrections
- comment out send feedback link in side panel
* Integrate MapLegend's dot into component
- change color to 'blue-warm-70v'
- update map stroke to 'blue-warm-70v'
* Add new indicator names from BE
- add abbreviations and use key in json file to decode
* Update Side Panel Tile Data
* Update Side Panel Tile Data
* Correct indicator names to match csv
* Replace Score with Rate
* Comment out FEMA Loss Rate to troubleshoot
* Removes all "FEMA Loss Rate" array elements
* Revert FEMA to Score
* Remove expected loss rate
* Remove RMP and NPL from BASIC array
* Attempt to make shape mismatch align
- update README typo
* Add Score L indicators to TILE_SCORE_FLOAT_COLUMNS
* removing cbg references
* completes the ticket
* Update side panel fields
* Update index file writing to create parent dir
* Updates from linting
* fixing missing field_names for island territories 90th percentile fields
* Update downloadable fields and fix field name
* Update file fields and tests
* Update ordering of fields and leave TODO
* Update pickle after re-ordering of file
* fixing bugs in etl_score_geo
* Repeating index for diesel fix
* passing tests
* adding pytest.ini
Co-authored-by: Vim USDS <vimal.k.shah@omb.eop.gov>
Co-authored-by: Shelby Switzer <shelby.switzer@cms.hhs.gov>
Co-authored-by: lucasmbrown-usds <lucas.m.brown@omb.eop.gov>
Showing obscure vulnerabilities that only exist in the dev setup creates
more noise and means that they just get ignored (because they are
probably low priority). Silencing them means when we get a vulnerable
dependency alert we know to pay attention to it.
Comes from https://github.com/dependabot/dependabot-core/issues/2521 and
501bbef578.
* switching to low
* fixing score-etl-post
* updating comments
* fixing comparison
* create separate field for clarity
* comment fix
* removing healthy food
* fixing bug in score post
* running black and adding comment
* Update pickles and add a helpful notes to README
Co-authored-by: Shelby Switzer <shelby.switzer@cms.hhs.gov>
* Add first column of Methodology score L
- create a new component MethodologyFormula (MF)
- MF component contain text on formula calculation
- add snapshots
* Add 2nd column to Methodology page
- add LowIncome component
- add USWDS styles on download component
- add margin-top styles to global
- enable all font-sizes to theme file
* Add Categories to Methodology page
- create CategoryCard component
- create Categories component
- add snapshots
* Update datasets
- update styling to match mock
- add additional indicators
- remove additional indicators
- update snapshots
* Add links to categories to datasets
- update snapshots
* Remove additional indicator test as they now N/A
* ensure each DOM ID is unique for a11y
- update snapshots
* Add Category heading for a11y
- removes ScoreSteps tests
- comment out ScoreStep component
- update snapshots
- cypress passes all a11y
* Update to methodology copy
- based on PDF and spreadsheet and Living Copy
-updates snapshots
* Add comments around using IF, AND, ELSE constants
- make indicator constant names more explicit
* Update copy based on living doc
- update snapshots
We originally used the approach in the infrastructure directory when we
thought we would be using Amazon Lambda for different parts of our
deployment pipeline. We have since then moved to using Github Actions
and no longer need this code, and keeping it in `main` has caused
confusion for onboarding new folks. This commit removes the directory
(although this will still be around in version control so we can always
view it or bring it back in the future if we want to).
Co-authored-by: Shelby Switzer <shelby.switzer@cms.hhs.gov>
* Modify copy
- update snapshots
* Fix failing cypress tests
- commented out lat/lng in URL test as it is intermittent
* Removes test on EO link
* Update copy for launch
- adds 404 page verbiage
- fixes survey button to be bottom sticky
* Update copy
* Adds four fields:
* Summer days above 90F
* Percent low access to healthy food
* Percent impenetrable surface areas
* Low third grade reading proficiency
* Each of these four gets added into Definition L in various factors.
* Additionally, I add college attendance fields to the ETL for Census ACS.
* This PR also introduces the notion of "reverse percentiles", relevant to ticket #970.
* Add 4 additional territory buttons
* Fix bug where territories fires multiple times
- move territory handler from J40Map to component
* Update SVGs for all territory buttons
* Update etl constants to use score field_names
Put strings around tract IDs in downloadable CSV
No need to modify the xls file creation because the string type is
preserved and interpreted correctly in Excel already.
One note is that this does cause the ID in the CSV to be have quotes
around it, which might be annoying. Maybe we don't want this behavior?
* Update based on PR feedback and lint needs
* Change field we're using in downloadable
This reverts the downloadable csv field list to use
MEDIAN_INCOME_AS_PERCENT_OF_STATE_FIELD instead of
MEDIAN_INCOME_AS_PERCENT_OF_AMI_FIELD in order to get the test to pass.
The point of this PR is a refactor (and a small change to the CSV
quotations), not to change the output. That will be a different PR
later.
Co-authored-by: Shelby Switzer <shelby.switzer@cms.hhs.gov>
* added fieldnames
* todo pollution, water, health & workforce
* workforce
* work in progress
* add utility function to replace duplicate summation logic
* move fpl series into add columns - run black .
* added revisions - still a wip
* added fieldnames
* todo pollution, water, health & workforce
* workforce
* work in progress
* add utility function to replace duplicate summation logic
* move fpl series into add columns - run black .
* added revisions - still a wip
* revise workforce and water
* revise housing and add incremental counter for workforce
* last PR nit
* revise workforce
* more PR feedback in score l
* more PR feedback in score l
* more PR feedback in score l
* addd FPL_SERIES and update references in score 1
* fix bugs
* reparameterize function
* final revisions in fieldnames
* make computations all consistent so we assing with FPL_200_SERIES
* fieldnames refactor after clarification and PR review
* finalize
* finalize with no typos
* fix length
* added median income var
* swap thresholds
* remove iteration
* remove stray '
* address flake 8
* added f string formatting and fixed typos
* added f string formatting and fixed typos
* move up
* remove dupes
* reformat
* fix bugs
* fix bugs
* initialize
Co-authored-by: Saran Ahluwalia <sarahluw@cisco.com>
