A tool to identify disadvantaged communities due to environmental, socioeconomic and health burdens
Home Page: https://screeningtool.geoplatform.gov/
License: Creative Commons Zero v1.0 Universal
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
Description
This user story is about using real data so in early user research with EVCM participants we can get a sense of how they interact with the live map and datasets, and consequently how they experience seeing the scoring and prioritized communities based on that data.
It's very likely that we won't know what data and map views will be most interesting to particular EVCM people ahead of time, and so seeing how they click/select/interact will be useful user data for us to inform priorities for the end-July version of CEJST.
Solution
Describe alternatives you've considered
Links to user research or other resources
User journey board https://app.mural.co/t/kameronkerger2998/m/kameronkerger2998/1619097401497/d8d8b090c94770d1d72c9c250db564b37676cc69
Definition of "Done"
Live data is incorporated for at least three indicators in early version of CEJST
As a J40 team member, I want to know how our initial score compares to other industry indicators/scores.
Dependency:
Definition of done:
Demo of Done:
Not doing:
Tickets to be created:
Description
As we develop a score, we want to understand how are score deviates or stays consistent with other scores used by communities, researchers, and policymakers.
Solution
Initially we want to spike on what's available and possible for an automated comparison tool. We want to get to a place where we have a card in the backlog addressing the following:
It would be ideal to have an open source script that we can run to compare a given census block group score calculated by our tool with a score for that group by another tool or scoring system. This script would have documentation for open source community members to be able to reuse, and we could write updates about this on our website. Ideally, we are able to incorporate this into the tool somehow so that users can also see how this compares to other scores they may be using. This would be a future user story based on further user research.
Ideally, the tool would generate an automated report each time it's run, so that we can continue to use this each time we generate an updated score.
The report can compare two binary scores, such as "the top 25% of SVI communities" compared to "the top 25% of our custom score", and generate a list of census block groups that are in the former but not the latter, as well as a vice versa (a list of CBGs that are that are in the latter but not the former).
The report can also show CBGs where the difference between two scores is the highest. (E.g., a CBG that's much higher on SVI than it is on the current custom score, and vice versa.)
This would require the output of other tools to be consumable data, eg as CSV.
Describe alternatives you've considered
Links to user research or other resources
Tasks
Definition of "Done"
Description
We need to let people know that our site is a work in progress
Solution
Let's put a large, visible banner (maybe with construction GIF?) to flag that our github pages site is still in progress
Describe alternatives you've considered
Links to user research or other resources
Tasks
Definition of "Done"
In order to get our data processing and scoring pipelines setup, we should prioritize identifying 2-3 datasets, processing them, and combining them into a score.
This will not include a UI for now, just a mapping from census block group to score
Description
We should do time-boxed research/have time-boxed discussions about which tile server to use based on the features we need.
Solution
Create an ADR based on outcome of research for a path forward with a tileserver.
Describe alternatives you've considered
Tasks
Definition of "Done"
Description
This user story is an example of how an EVCM may incorporate CEJST into their own advocacy work. For instance, the EVCM might find a zoom level and/or combination of layers on the CEJST that provides a compelling data case for their community getting specific funding for some remediation project.
This is not the main use case for CEJST obviously or the highest priority, but still, ideally we'd make it easy for our EVCMs to incorporate how they uniquely use CEJST into how they perform their community outreach and advocacy work, and also drive more awareness around CEJST at the same time.
Solution
Describe alternatives you've considered
N/A
Links to user research or other resources
User journey board https://app.mural.co/t/kameronkerger2998/m/kameronkerger2998/1619097401497/d8d8b090c94770d1d72c9c250db564b37676cc69
Definition of "Done"
We get initial feedback from a small number of EVCM stakeholders that they could see easily incorporating snapshots of the tool into presentation materials and reports that they prepare and cite it (i.e. cite version 1.0 or some subsequent verion)
Description
We need to enable static site content updates by non-technical team members so that they can keep the website up to date.
Note that there are some uncertainties, hence this being a spike for now. Look into what is possible and what tradeoffs are. Adding markdown support may be straightforward and worthwhile, or it could be a major PIA.
Solution
The minimum viable option would be to enable markdown content on the site; ideally we integrate with a CMS so that team members have a better and more robust content management experience.
Describe alternatives you've considered
Analysis of alternatives for static sites will be available in #6 (one of the features we consider a requirement is markdown content). Analysis of alternatives for headless CMSes will be available in #7.
Links to user research or other resources
Tasks
Definition of "Done"
We should spec and create a static page with information about the Justice40 Initiative and information about a feedback loop
Description
The intent of this user story is to make explicit that when someone loads CEJST the first time, the first thing they see is a national level view as opposed to an empty space or arbitrary space, etc.
Update: We will create a separate ticket to explore the best way to represent Alaska and Hawaii and territories at the national zoom level so that those community members know they are represented even if they are not in the lower 48. Users will still be able to drag over and find these locations in the map populated with data.
Note, it's likely and needs to be confirmed that the federal programs impacted by Justice40 have funding relevant to the five major US territories but that's not needed for initial user research version of CEJST.
Solution
Describe alternatives you've considered
N/A
Links to user research or other resources
User journey board https://app.mural.co/t/kameronkerger2998/m/kameronkerger2998/1619097401497/d8d8b090c94770d1d72c9c250db564b37676cc69
Definition of "Done"
When EVCM visits URL for the first time, they see a map of the US with CBG boundaries at an appropriate zoom level
Description
Juan Parras raised the great point in our kickoff call that we should be translating our process docs (not just our published website) into the languages of communities impacted by this work and whom we want to ensure are included in the open source processes we are building.
Solution
Provide translations of our process documentation in prioritized languages. Spanish at a minimum, and we should identify others needed.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Links to user research or other resources
Tasks
Definition of "Done"
Translations of the following docs:
Description
We need to define what analytics we want to capture from the beginning and set up an analytics tool to do so. We may get some logging and analytics out of the box with our hosting solution, but instrumenting on the client side will give us better insights on our audience and how visitors use the site. Insights will help us answer questions such as, are users in geographies with overburdened communities accessing our site? Is content in one language being accessed more than another?
Solution
Identify and implement an analytics tool on the site. I advocate for using an open source, privacy-oriented tool like Matomo as opposed to Google Analytics, but we would need to sort out hosting for this.
Describe alternatives you've considered
Not having an analytics tool: However, if we can get insights from the outset, we should. It's easier to start out with the right tooling than add later.
Links to user research or other resources
Tasks
Identify what metrics would be most useful to capture about site traffic
Research what tools we're able to use
Pick on that meets our needs and constraints and implement
Definition of "Done"
Description
This user story has to do with the zoom level of the map interaction for the initial CEJST prototype for user research. We don't need it to be census block level of resolution for the visual map zooming, but the CEJST previewer needs to at least zoom 3 levels in from national level.
Solution
Describe alternatives you've considered
Links to user research or other resources
User journey board https://app.mural.co/t/kameronkerger2998/m/kameronkerger2998/1619097401497/d8d8b090c94770d1d72c9c250db564b37676cc69
Definition of "Done"
Description
We should create a means for non-engineer community members to suggest new ideas for a dataset, using tools familiar to them.
Solution
To make it easy for non-engineer members of the public and advisory bodies such as the WHEJAC to submit suggestions for data sets, we will configure a Google Form that maps to the schema of the data set files. It probably makes the most sense to autogenerate the Google Form out of the Yamale schema for data set descriptions and the accompanying field description file; this will help keep the schema and the Google Form in sync.
This will enable members of the public to fill out a simple form suggesting data without needing to understand Github or other engineering concepts.
At first, these responses can just go into a resulting Google Sheet and be manually copied and converted into data set description files. Later, we can write a script that converts new entries in the Google Sheet automatically into data set file descriptions and opens a pull request. That work is tracked in this ticket
Tasks
Definition of "Done"
Gotchas
Description
Now that we have access, we should investigate the geoplatform.gov feature set and determine if it can host our datasets, layers, services, and/or FE code.
Solution
Create ADR for using Geoplatform based on research from team.
Describe alternatives you've considered
Links to user research or other resources
Research to be included in ADR
Tasks
Definition of "Done"
Description
We should create a means for engineer community members to suggest new ideas for a dataset, using tools familiar to them.
Solution
To start, we'll create a folder in the appropriate repository that can house YAML files, one per data set. Each file will describe the characteristics of the data.
We'll use a Python-based script to load all the files in the directory, and then run a schema validator to ensure all the files have valid entries.
For schema validation, we propose using Yamale. This provides a lightweight schema and validator, and integrates nicely with GitHub actions.
If there's an improper format in any of the files, the schema validator will throw an error.
As part of this milestone, we will also set this up to run automatically with each commit to any branch as part of CI/CD.
Describe alternatives you've considered
Tasks
Definition of "Done"
Description
We should implement the best practices of continuous integration of source code, meaning performing a series of checks for PRs
Solution
Set up minimal pipelines with a chosen CI tool such as Github Actions/Jenkins/TravisCI that implement the above checks
Describe alternatives you've considered
The alternative is to not perform these checks, which can lead to ruin.
Links to user research or other resources
N/A
Tech Tasks
npm audit)license-checker)Definition of "Done"
Description
This milestone is currently the least well-defined. It's important that members of advisory bodies like the WHEJAC and members of the public be able to "upvote" certain data sets for inclusion in the tool.
Solution
One potential for this is to use the Stanford Participatory Budgeting Platform. Here's an example of voting on proposals within a limited budget.
For instance, going into a quarterly planning cycle, the CEJST development team could estimate the amount of time (in developer-weeks) that it would take to clean, analyze, and incorporate each potential data set. For instance, incorporating some already-cleaned census data may take 1 week of a developer's time, while incorporating new asthma data from CMS that's never been publicly released could take 5 weeks. Given a "budget" of the number of developer weeks available (e.g., 2 developers for 13 weeks, or 26 developer-weeks), advisors can vote on their top priorities for inclusion in the tool within the available "budget".
Links to user research or other resources
https://pbstanford.org/
Tasks
Definition of "Done"
Description
We should create a means for non-engineer community members to suggest new ideas for a dataset, using tools familiar to them.
Solution
To make it easy for non-engineer members of the public and advisory bodies such as the WHEJAC to submit suggestions for data sets, we will configure a Google Form that maps to the schema of the data set files, as description in this ticket. At first, these responses will just go into a resulting Google Sheet and be manually copied and converted into data set description files.
As part of this ticket, we can write a script that converts new entries in the Google Sheet automatically into data set file descriptions and opens a pull request. This can be setup to run as a trigger on the addition of new rows to the Google Sheet.
Alternative means of achieving the same goals are also appropriate!
Tasks
Definition of "Done"
Gotchas
Description
This user story is about the preview version of the tool to be used for user research having some draft version of scoring methodology for communities. Even if the preview version of the tool only has four (purely arbitrary small number) indicators and the draft scoring methodology has 10% of all census blocks are the top tranche of prioritized blocks based on a 25/25/25/25% split of weightings between the four indicators, this draft scoring methodology combined with some messaging from us to those previewing CEJST that this is just a prototype to help us get feedback, having some early version of a community scoring methodology will help preview visitors conceptualize how indicator data > ranked community list > prioritized community list could work.
Solution
Describe alternatives you've considered
Links to user research or other resources
User journey board https://app.mural.co/t/kameronkerger2998/m/kameronkerger2998/1619097401497/d8d8b090c94770d1d72c9c250db564b37676cc69
Definition of "Done"
TBD
Description
When someone lands on this public repo, they need to understand what it is, who we are, why we've made this, and how they can interact with this repo or the project.
Solution
Add the standard OSS content:
Describe alternatives you've considered
N/A
Links to user research or other resources
N/A
Tasks
Definition of "Done"
We should spec and create a static page with information about the Justice40 Initiative and information about a feedback loop
We should create a map-based tool to enable community members to see the impact of changing various dataset thresholds.
Description
We need to start figuring out what the nuts and bolts of our data pipeline look like and start piecing them together. This is best done through implementation and learning with a real dataset we may want to use in the product. The goal of this issue is to start getting hands on with data so we can start building out our infrastructure to support the tool's ongoing data roadmap process.
It is important to note that the shortlist of datasets identified in this issue may or may not be in the first release of the tool and score. We will do our best to choose ones we think will be useful in the tool, but will rely on community feedback and guidance from the WHEJAC to make that decision.
Solution
We have a list of 90+ dataset ideas primarily sourced from the WHEJAC as well as from other advisors. We will divide and conquer an initial investigation of this list to identify ones based on the following 4 principles:
We will also ensure the initial shortlist of datasets also spans identified categories of environmental, climate, and economic indicators.
We will then implement our data pipeline and a prototype tool with this shortlist. With the prototype we will get community and WHEJAC feedback and decide whether to continue use of these datasets.
Describe alternatives you've considered
Links to user research or other resources
Tasks
Definition of "Done"
Description
We should document our current thinking about project architecture for future reference, in a way that can be updated and evolved over time with community support
Solution
Utilize mermaid.js to setup a pipeline allowing us to create text-based diagrams and render them as images
Describe alternatives you've considered
Links to user research or other resources
Mermaid - Mermaid is an excellent text-based tool for creating diagrams
Tasks
Description
This one is all about hosting the website!
Solution
Deploy the website with continuous dellivery set up. This will likely be on geoplatform.gov's S3 bucket, pending #18.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Links to user research or other resources
Tasks
Definition of "Done"
Description
We should implement the best practices of continuous integration of source code, meaning performing the following checks for PRs against our data processing scripts (assumed at this stage to be python-based)
Black, flake8) (potentially pre-commit hook?)safety)liccheck2)unittest, pytest, etc)pytest etc)poetry)Solution
Set up minimal pipelines with a chosen CI tool such as Github Actions/Jenkins/TravisCI that implement the above checks, targeting data processing filepaths
Describe alternatives you've considered
The alternative is to not perform these checks, which can lead to ruin.
Links to user research or other resources
N/A
Tasks
Definition of "Done"
Description
This user story has to do with the zoom level of the map interaction for the initial CEJST prototype for user research. We don't need it to be census block level of resolution for the visual map zooming, but the CEJST previewer needs to at least zoom 3 levels in from national level.
Solution
Zoom button or double-click on map interaction that allows CEJST visitor to zoom approximately from national level to state level or region level (approximately) > state regional level > city or county level. There's a lot of latitude the eng team should have for this, and whatever the simplest implementation that gets roughly at this is fine for the initial version.
As the user zooms, labels and landmarks (state borders, etc) should be viewable to orient the user
If supporting this for every city/county in the country in the near term is too challenging, we can strategically pick a handful of regions/cities/counties to implement this with
Describe alternatives you've considered
Static visual mockup of different zoom levels - those might give a good idea to the previewer what the final site might look like, but would not give us a sense of how they would interact. For instance, what if many EVCMs want to zoom in and out to look at neighboring counties, etc.
Enter in a zip code and maps zooms in on that zip code such that there's only one zoom level. We need to discuss that type of interaction more and it would likely need its own user story.
Links to user research or other resources
User journey board https://app.mural.co/t/kameronkerger2998/m/kameronkerger2998/1619097401497/d8d8b090c94770d1d72c9c250db564b37676cc69
Definition of "Done"
Ability to zoom in three levels across the map to at least a strategic set of cities/counties to enable effective user research
Description
This is about making sure internal and external contributors can onboard to the codebase quickly and easily.
Solution
Describe alternatives you've considered
N/A
Links to user research or other resources
N/A
Definition of "Done"
Describe the bug
robots.txt file is set to disallow crawling while we're actively developing. Need to fix for production
Description
We should put up a lightly-styled, representative-content version of our initial site for the sake of forming an informational landing page.
Solution
Following the creation of our static site (#17), we should add some approved content and some basic styling utilizing the US Web Design System.
Describe alternatives you've considered
Links to user research or other resources
N/A
General Tasks
Tech Tasks
Definition of "Done"
Design Needs
Description
We need to setup interim hosting so we are able to run our code from anywhere
Solution
As an initial stab, we should use cloud.gov sandbox for this purpose
Describe alternatives you've considered
Running from one of our machines, but this would require it to always be running; aws, but this would require agency approval
Links to user research or other resources
N/A
Tasks
pg_tileserv tile serverDefinition of "Done"
Description
We need to identify what our front end stack is for our informational site and app.
Here are the features we're looking to prioritize on the front end:
Definition of done
Architecture Decision Record created and approved
Description
Right now, the open source documentation, codebase, and data roadmap is entirely in English. We should explore options for making the documentation, codebase, and data roadmap accessible in other languages, in particular Spanish.
Describe alternatives you've considered
The alternative is to only have the codebase documented in only English, which can exclude people who have important skills and experiences and expertise to contribute to this process who do not use English as a primary language.
Links to user research or other resources
N/A
Tasks
Description
We need to better understand: what are the limits of the OpenLayers library? We've heard anecdotally in a few places that these are the particular concerns:
* Developer usability
* Rendering/performance
* Accessibility
Solution
Let's do a short, time-boxed investigation where we tweak specific parameters and get better measurements to better inform our understanding of the library.
Describe alternatives you've considered
We will keep this decision time-boxed, rather than going too far after having chosen a particular tool to go back.
Links to user research or other resources
Tasks
Definition of "Done"
Description
We should integrate the dataset proposal process with our ticketing system to keep track of work as it progresses.
Solution
For each data set that is being considered for inclusion soon in the tool, the project management team will create a ticket for "Incorporating ___ data set into the database", with a link to the data set detail document. This ticket will be created in the ticket tracking system used by the open source repository, which is ZenHub. This project management system will be public.
At the initial launch, we are not planning for members of the open source community to be able to create tickets, but we would like to consider a process for members of the open source community creating tickets that can go through review by the CEJST team.
This will help developers know what to work on next, and open source community members can also pick up tickets and work to integrate the data sets.
Tasks
Open Questions
Definition of "Done"
Description
Once suggested, we should have a single place where all community members can go to see the current status of a given dataset request.
Solution
Add a script that runs the schema validator on all files and, if successful, posts the results in a tabular format. There are straightforward packages to post a Python dictionary / pandas dataframe to Google Sheets and/or Airtable. As part of this milestone, we will also set this up to run automatically with each commit to main as part of CI/CD.
This will make it easier to filter the data to answer questions like, "which data sources are available at the census block group level"
Describe alternatives you've considered
Tasks
Definition of "Done"
We should define the process for the intake, prioritization, and voting on datasets for inclusion in the Justice40 Tool.
Description
We should add a means of annotating datasets with "problem areas" that describe problems in climate, environmental, and economic justice, in order to allow for higher-level grouping and tracking. This is so that non-data-focused members of the public or the WHEJAC advisory body can suggest we prioritize certain problem areas, with or without ideas for specific data sets that may best address that problem area. For instance, a problem area may be "food insecurity", and a number of data sets can have this as their problem area.
Solution
We should add a field in our dataset description that includes "problem area" in some form.
Open Questions
Still open as to how to do this:
Tasks
Definition of "Done"
Description
We need to choose a license for this repo! If I recall correctly, last time around all US Government projects had to be something like Creative Commons 0 -- absolutely no restrictions. But we should check and make a decision.
Solution
The repo contains a LICENSE.
Tasks
Definition of "Done"
Description
We should analyze frontend mapping visualization libraries and decide on one that both represents our project values and provides for our user needs.
Solution
Create an Action Decision Record to represent our decision and explains our reasoning.
Describe alternatives you've considered
An Analysis of Alternatives is a pretty similar idea, but not directly supported via CLI tooling
Links to user research or other resources
This will be informed by:
Tasks
Definition of "Done"
Our current ADR process is a bit cumbersome. Let's update it by using Github project boards and PRs!
We have created:
Chosen option: use github project boards as described below. Reasoning:
Explanation of new process - to be added as a separate description later (updated diagram also to be posted as a comment here):
Draft: To create a new ADR:
Screenshots/diagrams: If you need to add diagrams or screenshots/pictures, please add them to the comment section of the issue.
Ready for Discussion : The core project maintainers (for now the USDS folks until we have regularized this process) will review - they will:
In Discussion : Once the item is in the "In Discussion" column, you have until the period specified to come to a decision. People can leave comments directly on the ticket There are several outcomes:
Decided: Once the comment period has elapsed, move the issue to "Decided". This is where the issue will wait before you have created a Pull Request. Please at this time add one of the following labels:
Pull Request: Once decided, you should create a pull request to create a file in docs/decisions - name it XXXX where XXXX is one greater than the largest decision record in the directory. Copy and paste the record from the issue. As for diagrams and
.mmd extension and reference filename-mmd.svg in your docs, and Github Actions will automatically create the svg fore you! Preview diagrams with the Mermaid Live Editor.XXXX-files and put supporting ADR material there.Merge: once the PR has been approved, merge and close
e.g. Trello etc.
Description
This will enable EVCMs who are user research participants, or the small set of stakeholders who will preview the tool soon, to interact with indicators and see for themselves how that influences a draft community scoring. This in turn will inform the evolution of the datasets used for CEJST (and how we design the data backlog as well).
Solution
Describe alternatives you've considered
Links to user research or other resources
User journey board https://app.mural.co/t/kameronkerger2998/m/kameronkerger2998/1619097401497/d8d8b090c94770d1d72c9c250db564b37676cc69
Definition of "Done"
Features
Description
Following our decision around static site generators (here ), we should create a template based on this framework and commit to the repo for future iteration.
Solution
Use site generator to create scaffolding for a new site.
Describe alternatives you've considered
See #6
Links to user research or other resources
See above
Tasks
Definition of "Done"
Description:
This user story is about providing community members transparency into the cumulative score calculation (algorithm)
Description
We should add some means of limiting the audience for new features, so as to control the visibility of in-progress work while also getting real users to use our software
Solution
Use feature flagging on in-progress work, control through an allow list
Describe alternatives you've considered
Tasks
Definition of "Done"
Open Questions
Description
CEJST needs to reflect community members' lived experiences. We need a multi-pronged approach. One major part of the approach includes EJ community members co-designing tool and cumulative impact score through written recos, listening sessions, moderated user research sessions, feedback links in the tool, etc. But an additional way is to incorporate very personalized localized on the ground information from users, such as GPS tagged photos of bad pollution emission. To further illustrate, an EVCM may see that other communities in their county are prioritized ahead of theirs in CEJST, but they can take a photo of bad exhaust emitted near their home, in contrast to blue skies everywhere else they can see. They can provide on the ground data showing pollution uniquely burdening their community that is not reflected in the tool.
(This feature is not MVP, but wanted to get on team's radar sooner rather than later. Has far reaching implications. Might warrant being an epic in itself.)
Solution
From the Justice40 Discovery Sprint Report
In California, where they use cumulative impacts score, they spent countless hours on the ground with and in communities in order to ensure that burdens and other factors were being considered. In some cases, the research team who originally developed scoring methodology upon which their geospatial tool, CalEnviroScreen, was built, would go into communities with preliminary maps and “ground-truth” them, block-by-block allowing community members armed with cell phones to capture pictures and tracked GPS locations to redraw them to more accurately reflect their lived experiences.
One potentially feasible solution would be to ask CalEnviroScreen team if they have recent on the ground information that can be shared with us, and we can see if CEJST visual mapping and scoring accurately represents, and potentially get the team's advice as well.
Describe alternatives you've considered
We could potentially conduct these kind of spot checks ourselves, or ask interested and willing EJ community members to help us with providing on the ground information.
Links to user research or other resources
City 311 apps allow community members to upload GPS tagged photos of incidents, sidewalk cleaning, dumping issues, etc. https://apps.apple.com/us/app/sf311/id666635420 for the purposes of city departments remediating. This also creates a measurable traceable body of community generated information.
Tasks
Definition of "Done"
Description
We should propose and document a process for Architecture Decision Records to make it easier to contribute to larger decisions on this project.
Solution
Use a Meta-ADR to document an ADR Process
Describe alternatives you've considered
Tasks
Definition of "Done"
Description
There are a number of methodologies out there for combining scores into a single indicator - let's understand this a bit better and incorporate them into a proof of concept tool. We want to do a spike on the research for this to create a methodology we can begin doing user research with in our MURT.
Solution
Research, consult, make initial decision
Describe alternatives you've considered
This research will include an analysis of various scoring methods
Links to user research or other resources
Tasks
Definition of "Done"
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.