Thank you for your interest in reviewing and using the I3 Connectivity Explorer. The application is now available to selected users. The application is very much a work in progress. Your feedback will help to shape its future. When you get the chance, take it for a test drive and then share your comments with the team.
1. Request an Account and Join the Mailing List
An account on GitHub will be useful, but its not strictly necessary. See Step 3 for more about GitHub usage.
2. Explore the application
Once you have an account on the application, use it to explore one or more places that you’re interested in. The application has been loaded with the most recent data for all of the 50 states, plus the District of Columbia and the territories. You can view data for a state, a county, a named place, a county subdivision (which tend to align with named places), a school district, a congressional district, or a tribal nation as defined by the US Census.
While you’re exploring the app, think about the following:
- Did the application do what you expected? If not, what did you expect, and how did it fall short?
- Is the data what you needed? If not, how can it be improved?
- Are there errors, omissions, or misstatements? A copy of the page URL is important here!
- Are there datasets or visualizations that should be included?
- Are there other improvements to be made?
The full set of comments is hosted in an private repository on GitHub. “Private” means that only selected GitHub users can see the comments. Remember, though, that your GitHub contributions are visible to other team members. By submitting an issue, you’re agreeing to its publication.
If you want to participate via Github, you’ll need to do the following:
- Create an account on GitHub if you don’t already have one.
- Send an email email@example.com with your GitHub user name requesting access to the I3-Connectivity-Explorer repository.
- Once you’re granted access to the repository, you can visit the repository and create one or more GitHub Issues. The Contributing page on GitHub has more about the process.
If you prefer to email your comments, send them to firstname.lastname@example.org. If you’re emailing a problem report, please include
- A description of the issue.
- The locations you’re looking at, (e.g. Santa Fe, NM).
- Links to the specific page where the issue arose, including choices of view parameters.
- If the issues might be device or browsers specific, the device and browser you are using.
And again, thanks for helping out!