codeforfoco / cerp-backend Goto Github PK

There is a balance between loading Olivia and getting her excited about the project. We should focus on getting her to focus on putting the data on OpenCity and ingesting it from there.

Testing

Currently, the development environment specified includes the software requirements, but when running the backend on Windows or Mac, some issues are seen with the connection between the backend and frontend, and there are some backend errors while using the API. Investigate the environment-specific issues and fix enough bugs to get the frontend and backend working reliably for new feature development.

It's kinda meaty, ~2ish MB now. Make it smaller via:

• Remove unneeded fields (e.g. SHAPE_LEN, etc.)
• Simplify/reduce vertices
• Reduce coordinate precision (e.g. 40.374187379751248 to 40.37419)
• Minify and commit

Other:

• Test it: zoom in really far, see if vertices look suffish
• Screenshot the old-vs-new savings (just cuz)
• Document procedures (use ogr2ogr if no Node-based modules available)

Wishlist: topojson!

Add the OCR script to the repository for future use.

Document the API endpoints.

Bonus points: consider automated solutions so that as the API evolves we don't need to continue to update the docs. One example would be utilizing build tooling with javadoc style method comments to generate markdown.

Future: expose the documentation on the front end side of the website.

Other Jordan suggested taht we check with the parties to get precinct data.

Current API does not have easy way to look up precinct list, or use the API to get data on a race but not at a precinct level. Also, as of 8/16, some of the API endpoints have errors due to the keys having spaces.

We have been left with a PDF again for 2017. Luckily, the results look to be in a non-image format, but we still need to find out if we can skip the rigamarole of extracting the data and instead get access to the data directly.

Two parts for this issue:
-Investigate SB17-040 and find out if we can leverage it to get the data
-Contact Angela Myers and politely ask for the data. Either get the data or pursue a public pressure campaign to ensure that precinct level data is not released in unusable formats any more.

Replace the flat file system with database.

• Mongo
• PostgreSQL

We need an extensible javascript/HTML5 map that can ingest data from the backend and present it on a larimer county precinct map. Limit to 2016 for now as 2017 may have a different precinct map.

Eventually we want:
-Selector/dropdown that performs a get on the data and populates the map
-Adjustable heatmap properties (color, cutoff, gradient control)
-Export as image, pdf, printable page

This can start as a pretty rudimentary map. We just need an easy way to show off the backend and maybe help debug data and backend changes as well.

Draft a design for the look and feel with the project, potentially with a local designer.

We have a contact at the City of Fort Collins who has access to the elections people for the city, and potentially county contacts. We need to get election data per precinct for at least the presidential election, and hopefully for state and local issues as well.

Olivia Terrell
[email protected]
970-416-2282
215 N. Mason St.

@girokia expressed interest in containerizing the applications various components with Docker and using compose to connect them.

All the areas below that are grey are areas defined in the Larimer County geodata, however aren't shown in the PresidentialElection.json file.

Live example here: http://cerp-code-foco.herokuapp.com/#/

Split front end into the webview repo.

We need to convert the data into an open format for use in python and javascript libraries. This is needed for all heatmap related tasks

The data is located here:
https://www.larimer.org/it/services/gis/digital-data

The output needs to be geojson