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
-
Oamishirasato City Disaster Volunteer Center
Official city source
Social welfare council
The center is operated by the Oamishirasato City Council of Social Welfare. It helps with tasks such as cleaning homes and moving damaged household belongings. According to the city's official notice, the center is open from 9:00 a.m. to 4:00 p.m. Before leaving, check the official sources for how to participate and whether volunteers are being accepted that day.
Oamishirasato City: Opening of the Disaster Volunteer Center (Japanese) / Oamishirasato City Council of Social Welfare: Volunteer Information (Japanese)
Organizations providing recruitment, registration, and current information
-
Chiba Prefecture Council of Social Welfare (Japanese)
Social welfare council
This is the prefecture-wide source for the status of disaster volunteer centers opened by municipalities in response to this heavy rain disaster. -
Japanese Red Cross Society, Chiba Chapter: Red Cross Disaster Preparedness Volunteers (Japanese)
Registration and training
Volunteers register in advance and receive training and drills. During disasters, they may gather information, provide first aid, transport supplies, support evacuation shelters, and help operate disaster volunteer centers. -
Chiba Volunteer Navi (Japanese)
Prefectural matching site
Search current volunteer opportunities in Chiba Prefecture by topic, including disaster relief, as well as by area and eligibility. -
Chiba Prefecture: Disaster Volunteer Information (Japanese)
Official prefectural source
This page links to relevant organizations in the prefecture, the Japan National Council of Social Welfare, disaster support groups, and other sources. -
Japan National Council of Social Welfare: Disaster Area Support and Volunteer Information (Japanese)
Nationwide information
Check where disaster volunteer centers are open and recruiting, how to prepare before volunteering, and volunteer insurance 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.
CivicTechZenChiba
Initial Tasks
- Check that the URLs on the approved list open correctly
- Report incorrect links between municipalities and official websites
- Add one row of official municipal notices: add “slug, kind (risai/waste/disinfect/water/housing/vc/support/hub), title, URL, status, date checked” to
data/supports.csv(if you do not use git, write the same in a GitHub issue). Reports from the public arrive through the report form on municipality pages. Municipalities with few dedicated pages so far include Inzai, Yachimata, Shiroi, Narashino, Nagara, Shirako, Chosei and Sosa - Check that “Last collected” was refreshed in the morning (what to do when it stops)
- Submit requirements as GitHub issues or pull requests
Operations spreadsheet (Anyone with the link can view it. Editing is by invitation only.)
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.
- Check the corrections sheet or the issue and mark it “checking”. If it concerns a municipal official link, set
statustocheckingindata/supports.csv(the site shows a “Being verified” badge) - Verify against official pages only (municipality, prefecture, national government)
- Fix
supports.csv(URL, title, status, date checked) or the page. Mirror any Japanese page change to the English page and runpython scripts/check_bilingual.py - Mark it “resolved” (or “no action” with a reason). Reply briefly if a contact was given
- Review open reports once a week
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.
- 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 headlinesstep. 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 printsall sources failed; keeping previous data. - 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.
- If you do not have access, tell us. Post “daily job stopped” with the run URL in Slack or a GitHub issue.
- Find which source failed. When only some sources fail, they are recorded in
last_errorsinsite/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.