[Vis Tools] Add more examples to landing pages

[juliawu]

Adds some more links to the landing pages of the visualization tools

Pulls some examples from the old landing pages and adds them to the new landing pages. I also added more charts to the Berkeley vs. Piedmont and Palo Alto vs. East Palo Alto examples to show that our timeline tool can show multiple plots on the same page.

I tried to add more examples to the scatter tool, but many of the links don't work, so I left the current scatter tool as-is.

Before:

After:

[gemini-code-assist]

Summary of Changes

Hello @juliawu, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the Vis Tools landing pages by integrating a richer set of example visualizations. The update expands the available demonstrations for both map and timeline tools, providing users with more diverse and illustrative data exploration scenarios. This improvement aims to make the visualization features more discoverable and useful for a broader range of data analysis needs.

Highlights

• New Map Examples: Four new map visualization examples have been added to the landing pages, covering topics such as projected temperature rise, median age, schooling completion rates, and carbon dioxide emissions across various geographical entities.
• New Timeline Examples: Three new timeline visualization examples have been introduced, showcasing comparisons between different locations like Berkeley & Piedmont, Palo Alto & East Palo Alto, and Imperial County & Santa Clara County, highlighting diverse statistical variables.
• Internationalization Updates: The internationalization message definitions have been updated to include titles and descriptions for all the newly added map and timeline examples, ensuring proper display across different locales.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds more example links to the landing pages for the visualization tools. The changes include adding new internationalization strings for the example titles and updating the configuration file with the new links for the map and timeline tools. The implementation is straightforward, but I've found a small typo in one of the new URLs that could cause it to break.

[gemini-code-assist]

There appears to be a typo in the URL. The place parameter contains a double comma (,,) between the geoIds, which is likely unintentional. This could cause the link to fail. It should be a single comma.

Suggested change

url: '/tools/timeline#place=geoId%2F0606000%2C%2CgeoId%2F0656938&statsVar=Median_Income_Person__Percent_Person_18OrMoreYears_WithPoorGeneralHealth__Monthly_Median_GrossRent_HousingUnit__Count_CriminalActivities_CombinedCrime&chart=%7B%22count-none%22%3A%7B%22pc%22%3Afalse%2C%22delta%22%3Afalse%7D%2C%22age-none%22%3A%7B%22pc%22%3Afalse%2C%22delta%22%3Afalse%7D%2C%22grossRent-none%22%3A%7B%22pc%22%3Afalse%2C%22delta%22%3Afalse%7D%2C%22unemploymentRate-none%22%3A%7B%22pc%22%3Afalse%2C%22delta%22%3Afalse%7D%7D',

url: '/tools/timeline#place=geoId%2F0606000%2CgeoId%2F0656938&statsVar=Median_Income_Person__Percent_Person_18OrMoreYears_WithPoorGeneralHealth__Monthly_Median_GrossRent_HousingUnit__Count_CriminalActivities_CombinedCrime&chart=%7B%22count-none%22%3A%7B%22pc%22%3Afalse%2C%22delta%22%3Afalse%7D%2C%22age-none%22%3A%7B%22pc%22%3Afalse%2C%22delta%22%3Afalse%7D%2C%22grossRent-none%22%3A%7B%22pc%22%3Afalse%2C%22delta%22%3Afalse%7D%2C%22unemploymentRate-none%22%3A%7B%22pc%22%3Afalse%2C%22delta%22%3Afalse%7D%7D',

[juliawu]

Good bot. Fixed.

[clincoln8]

Thanks Julia! All of these are nits except for the last question about the "extremes" charts -- why were those chosen? Maybe just add a little extra context to the title would clarify the connection.

And then lastly I noticed that also selecting "Total Population" from the extremes link would add to an existing chart instead of becoming a new chart -- what's the logic for deciding when to make it a separate one vs adding to an existing one?
before: https://screenshot.googleplex.com/65a7QNMSccgDejM
after: https://screenshot.googleplex.com/4ps76i5iF6p6qPP

[clincoln8]

I noticed that this chart shows a per capita option which I don't think makes sense -- https://screenshot.googleplex.com/AjXTGCvVRkQ2Rvs

Is this something that could be addressed as a followup?

[juliawu]

I'll look into it as a follow-up! There's no built-in logic for when a per capita option is shown right now, and I think figuring out what heuristics we want to use to determine when to allow per-capita needs more discussion as a team.

[clincoln8]

another example where having the per capita option doesn't make sense: https://screenshot.googleplex.com/Bt5VKvv9mpSz7Ug

Do we always show that option for this tool? Or is it dynamic based on the statvar?

Also, what are "installations"?

[beets]

We had a URL param that triggered us plotting the locations of power plants on the map. I don't think it works anymore though..

[juliawu]

Hm, in that case, what do you guys think of just removing this example to remove confusion? @beets @miss-o-soup

[beets]

we can remove the example, along with the straggler code for it:
https://github.com/search?q=repo%3Adatacommonsorg/website%20MAP_POINTS_PLACE_TYPE&type=code

(i'd rename the dict key to RESERVED or PREVIOUSLY_USED so we don't re-use that param)

[clincoln8]

same suggestion for Berkeley and piedmont title

[juliawu]

Good suggestion, done!

[clincoln8]

I'm not exactly sure why we selected these statvars to display for "extremes".

[juliawu]

This was originally pulled from the old landing page. I think the original intent was to compare Imperial and Santa Clara Counties because they sit at the opposite ends of the spectrum (Rural vs Urban, Poor vs Rich, etc), but I agree that it's confusing. I've decided to remove this example altogether.