Iowa C.O.R.E.

2020 DSM Hack repo for Iowa C.O.R.E. Rethink Iowa Website

Build Status

Tech Stack

WordPress website using PHP and JavaScript

Hackathon Team

• Tony Brobston
• Mike Kang
• Paul Kang
• Edwin O. Martinez
• Leah Haugh
• Josh Angolano
• Val Yeltman
• Gopo Iyer
• Wesley Ng
• Peter Chodakowski
• Jordan Van Kampen

Future Heatmaps

Ideally we would refactor what we currently have and build some sort of contract or interface, like a function that takes in an api endpoint, the json path to the field we want to use for the heatmap weighting, etc. and return that heatmap weighting value, zip code, and county. If we coded a solution that expects this contract we could create a form to input these values and store them in wordpress, then pull that value in map.php and interate over these form entries to build heatmaps. However this is quite a bit of work and at the hackathon we didn't have time to prove this concept.

For a future developer, to add another heat map you will do something similar to the following. I apologize that this guide will not be complete, so please follow loosly.

1. Assuming you can use docker run docker-compose.yaml
2. Navigate to http://localhost:8080
3. Create a new site (copy the password)
4. Login as admin and navigate to Appearance > Themes and enabled "Iowa Core"
5. Navgiate back to http://localhost:8080 to see the theme
6. At this point you now have a non-production environment to play around (no you won't have data unfortunately).
7. Next we'll make some code changes
8. Make another option here:

   iowa-core/map.php

   Line 29 in ce092ea

   <option value="unemployment-benefits-paid">Number of unemployment benefits paid</option>

9. Use the value from the last step and create another else if here:

   iowa-core/map.php

   Line 287 in ce092ea

   } else if (censusChoice === 'unemployment-statistics') {

10. Make another function call here:

    iowa-core/map.php

    Line 286 in ce092ea

    loadUnemploymentBenefitDollarsPerCounty();

11. Create the function it will call like this one:

    iowa-core/map.php

    Line 127 in ce092ea

    function loadUnemploymentBenefitDollarsPerCounty() {

12. In the function from the last step, you'll need to find another GET Rest endpoint. When calling this endpoint the response data will be in xhr.responseText. You'll need to pull the heatmap weighting value from this data and pass it to the census_variable like this:

    iowa-core/map.php

    Line 150 in ce092ea

    feature.setProperty('census_variable', censusVariable);

13. Assuming you copied another function, you should be able to navigate to http://localhost:8080 and choose your new heatmap from the dropdown in the top left corner of the map.
14. If I had to guess the most challenging part will be returning the correct data through a GET Rest endpoint and then pulling the heatmap weighting value from that data. This requires knowledge in rest endpoints, specifically how to call them and return different data, I can't explain this in 10 words or less 🤷, and JSON (JavaScript Object Notation). The best advice that I can give is reading up on these previously mentioned things and look at the other examples in this repo.

UnemploymentBenefitDollarsPerCounty:

iowa-core/map.php

Line 130 in ce092ea

xhr.open('GET', 'https://data.iowa.gov/resource/aeyn-twxp.json');

iowa-core/map.php

Line 137 in ce092ea

var censusVariable = parseFloat(row.benefits_paid);

UnemploymentStatisticData:

iowa-core/map.php

Line 187 in ce092ea

xhr.open('GET', 'https://data.iowa.gov/resource/tjnj-ed6z.json?$query=SELECT * where area_type=\'County\'');

iowa-core/map.php

Line 193 in ce092ea

var censusVariable = parseFloat(row.unemployment * -1);

15. Once this is working you'll need to FTP these changes to the Wordpress server. At one point I had some CI/CD (continuous integration/continuous deployment) setup which you can find a code sample here: https://github.com/dsmHack/iowa-core/blob/762045f50832290cb8ace716a5f1863d068c5dba/.scripts/deploy.sh The travis-ci likely does not have the correct ftp values set, so those would need updated if we went this route. Using something like Filezilla will work in the short term.
16. Ideally we would refactor to change the code to make it easier to understand and more concise, there is definitely a lot of duplicate code that is unnecessary. Refactoring this is not a requirement.