CTZC Chiba Heavy Rain Portal

For supporters. This is not an application desk.

People gathered around a map and computer to discuss recovery from the August 2026 Chiba heavy rain disaster. Organized by CivicTechZenChiba.

For Supporters and Partners

We are working to support the fastest possible recovery from the heavy rain disaster. We are starting by collecting public information from government agencies and news organizations and making it easier for Chiba residents to find. We will also consider and carry out new forms of support.

Join us on Slack Vote on future ideas

Disaster Volunteer Information in Chiba Prefecture

Always check the latest official information before traveling to a disaster area. Even when a disaster volunteer center has opened, recruitment may not have started or may be temporarily suspended. Some centers accept only residents of the municipality or prefecture. Check whether advance registration is required, the activity dates, what to bring, and volunteer insurance requirements. Do not arrive without a reservation.

Service desk confirmed open for this heavy rain disaster

Checked on August 17, 2026. The Chiba Prefecture Council of Social Welfare states that it is still checking the status of local centers and asks people to avoid contacting affected municipalities or social welfare councils individually whenever possible.

Organizations providing recruitment, registration, and current information

What Would Help After a Disaster? Vote on Ideas

We have listed ideas for information, features, and actions, including how to explain disaster damage certificates, a support program calendar, and how to document damage with photos. Vote for the ideas you believe are needed. The results will help guide future features and new services.

View the ideas and vote

CivicTechZenChiba

Initial Tasks

Operations spreadsheet (Anyone with the link can view it. Editing is by invitation only.)

GitHub repository

Handling “this is wrong or outdated” reports from readers

Every page has a “Report” link at the bottom, and each municipal official link has a small “Report” next to it. Reports arrive in the “訂正” (corrections) sheet of the operations spreadsheet (Google Form responses); until the form is configured they arrive as GitHub issues. Report contents are not published.

  1. Check the corrections sheet or the issue and mark it “checking”. If it concerns a municipal official link, set status to checking in data/supports.csv (the site shows a “Being verified” badge)
  2. Verify against official pages only (municipality, prefecture, national government)
  3. Fix supports.csv (URL, title, status, date checked) or the page. Mirror any Japanese page change to the English page and run python scripts/check_bilingual.py
  4. Mark it “resolved” (or “no action” with a reason). Reply briefly if a contact was given
  5. Review open reports once a week

If an emergency (rescue, injury) arrives through the form, direct the person to 119/110 and the municipality. This site does not handle emergencies.

When the daily collection stops

Every day at 06:00 (JST) GitHub Actions collects from the prefectural disaster portal, the Fire and Disaster Management Agency and the Japan Meteorological Agency, and updates the site. If “Last collected” on the top page is still older than yesterday, the collection did not succeed.

  1. Open the collect step; do not rely on the run colour. Open the latest run of “Daily collect and GitHub Pages” and read the Collect official headlines step. That step is set to keep going on failure, so the run can be green while nothing was collected. When every source is down it prints all sources failed; keeping previous data.
  2. If you have write access, run it by hand. Use “Run workflow” on the same screen, branch main. If at least one source is up, “Last collected” refreshes within a few minutes. While every source is down, “Last collected” does not move — the previous data is kept as is. An unchanged timestamp means the sources themselves are down.
  3. If you do not have access, tell us. Post “daily job stopped” with the run URL in Slack or a GitHub issue.
  4. Find which source failed. When only some sources fail, they are recorded in last_errors in site/data/collection.json. When every source fails that file is not rewritten, so read the Actions log instead. A failed source keeps its previous value; only the sources that responded are refreshed.

The public pages keep showing the previous data when collection stops. Readers always see the note to check official sources for the latest information.

Information for residents

Key points from this page in a portrait A4 graphic. Tapping the graphic will not open a link; use the buttons above. Save the image
Portrait A4 summary graphic. The graphic itself is not interactive. Use the buttons above to join Slack or vote.