Repository navigation
Add carto keys - #168
Merged
Merged
Add carto keys#168
Conversation
wagnerlmichael
marked this pull request as ready for review
October 1, 2026 18:58
jeancochrane
approved these changes
Oct 1, 2026
jeancochrane
left a comment
Member
There was a problem hiding this comment.
Great work, thanks for taking this on!
I do think we'll need to redeploy past years, but we should be fine to select the option "Only generate reports for PINs that are eligible for reports" because only eligible PINs have maps. I think we should probably deploy year-by-year, and start with a staging deployment for each year so that we can make sure it works properly. How does that sound to you?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a carto API key (account created with assessor data email address), so that the maps in the homeval html pages render correctly.
Prod and staging URLs added as referrers to this key, nothing else. In attempting to add the localhost, I realized that two separate accounts (and emails) are needed. For this reason and security reasons I'm going to plan to tackle local host in a separate issue, likely with an API key per dev strategy and adding documentation.
One pin updated on prod and staging:
Staging: https://modval-stage.cookcountyassessoril.gov/2026/16074030360000.html
Prod: https://homeval.cookcountyassessoril.gov/2026/16074030360000.html
Note: For the map to function properly we will need to redeploy. I'm assuming we redeploy back to 2025 and 2024 as well?