Hyogo bear activity is visible in public data, but not in one table
A first JP Data archaeology of Hyogo bear records: prefectural sightings/traces, human injury rows, monthly seasonality, and Taka Town warning PDFs read as separate public-data layers rather than one aggregate risk number.
Working finding
Hyogo’s public bear-activity records are usable, but only if the layers stay separate. Sightings/traces, human injuries, mast-year context, local warning PDFs, and permit-category incidents answer different questions. The Taka Town mistaken-capture case shows the gap between physical reality and administrative categories: the bear was trapped, but the local authorization did not match bear capture at that site.
Public notices are public-data signals, not complete biological observations. Taka Town notice counts are warning PDFs from the reviewed sources; they are not total counts for all bear movement, all unreported traces, or all internal municipal records.
Official records
What the public records show
Scope: Hyogo Prefecture · Taka Town · Yachiyo Ward · Kami Ward · Naka Ward. Each panel names where its numbers come from, so prefecture totals, town alerts, and injury documents are not folded into one danger score.
Hyogo R6 sightings/traces
1,128
Major acorn/nut failure year
Hyogo R7 sightings/traces
510
Lower after stronger capture activity and better mast
Hyogo R8 through May
149
Partial year, not annualized here
Taka notices checked
28
R6–R8 town PDF notices in the checked sources
Hyogo: sightings/traces move sharply; injuries are a separate series
The prefectural table tracks sightings and traces. Human injury incidents are a separate, smaller risk series. Keeping the two apart prevents a high-notice year from being treated automatically as an injury year.
Monthly shape: R8 started hot, but the summer/autumn test is still ahead
Through May, R8 is already above the five-year monthly average. But the high-risk read is not complete until June through November fill in.
Human injury rows stay out of the sightings total
This injury layer is intentionally small: it places injury context beside prefectural sightings without pretending both measures are the same thing.
Local warning notices
Local warning records matter because they name districts, dates, and warning context. They still need clear labels: a public notice is evidence of a published warning, not a complete map of bear movement.
Taka Town: the local signal concentrates in Yachiyo
The town notices are public warning PDFs, not a prefectural population estimate. They still matter for local operational attention: in the reviewed R6–R8 notices, Yachiyo Ward accounts for 20 of 28 entries.
Taka Town warning notices by fiscal year
These are reviewed public notices, not a complete map of all movement or unreported traces.
Taka Town warning notices by month
Municipal PDFs can add timing and district detail, but they remain a notice-publication layer rather than a biological movement layer.
Capture and classification records
These records are not sighting totals. They explain administrative handling when the observed animal, trap, permit, or site category does not fit cleanly.
Mistaken-capture category incident
The June 13 R8 notice is modeled separately from sightings and warnings because it answers a different question: what happened when the animal and the local authorization/site category did not line up.
- Place
- Taka Town, Hyogo
- Municipal source layer
- Date
- R8 / FY2026, June 13
- Partial-year incident row
- Category read
- Mistaken capture / release protocol
- Administrative category friction, not a sighting count
How these numbers were counted
- •Prefectural sightings/traces are not injury incidents.
- •MOE injury/context rows are a national comparison layer, not town-level movement data.
- •Municipal warning PDFs are checked public notices, not a complete biological observation system.
- •Mistaken-capture rows belong in an incident/category-friction layer, not the sightings total.
Why this belongs on JP Data
A bear story often reads as wildlife reporting. The data story is more useful: Japan produces many official fragments, but they sit in different administrative containers. A prefectural countermeasure meeting PDF gives annual and monthly sightings/traces. Ministry tables give injury context. Town PDFs give local warning points. A mistaken-capture notice reveals which permit category did not fit the animal in front of officials.
That fragmentation is the finding. The question is not whether bears exist in Hyogo. The question is what the public records can verify without silently merging incompatible rows.
The number that jumps is sightings/traces, not attacks
Hyogo’s R6 / FY2024 row reports 1,128 sightings and traces, more than double the R7 / FY2025 total of 510. The prefectural material ties that R6 jump to a major acorn/nut crop failure. That is an ecological and administrative signal, not a direct count of attacks.
Human injury incidents are a different series. In the same annual summary layer, R6 has two human injury incidents and R7 has one. The sighting series still matters, but as exposure, reporting, and operational pressure rather than as an injury proxy.
- •R6 / FY2024 Hyogo sightings/traces: 1,128
- •R7 / FY2025 Hyogo sightings/traces: 510
- •R8 / FY2026 through May: 149 sightings/traces
- •R6 human injury incidents in the prefectural annual table: 2
- •R7 human injury incidents in the prefectural annual table: 1
Taka Town gives the local drill-down
The town-level PDFs are small documents, but they carry operational detail that the prefectural annual table cannot. They give dates, districts, and source files. In the reviewed R6–R8 Taka Town notices, the concentration is not vaguely townwide. It clusters in Yachiyo Ward.
That local pattern is why the June 13 mistaken-capture case matters. It is not just an unusual bear anecdote. It is a public-data example of category friction: a bear entered a trap, but the capture authorization and site category did not line up with bear capture, so the response moved into mistaken-capture handling and release protocol.
- •Checked Taka Town notices: 28
- •Yachiyo Ward notices: 20 of 28
- •Kami Ward notices: 6 of 28
- •Naka Ward notices: 2 of 28
- •R8 / FY2026 Taka Town notices through June 13: 5
What the data can and cannot say yet
The public data shows year-on-year changes, monthly seasonality, local notice concentration, and the administrative category issue behind the mistaken-capture case. It also shows why R8 deserves attention: April and May are already above the past five-year monthly average in the prefectural table.
The public data cannot yet tell us the final R8 pattern. June through November are the months that will decide whether the year behaves like the lower R7 pattern, the exceptional R6 pattern, or something in between. It also cannot turn town warning PDFs into a complete movement dataset. The right posture is monitor, separate the layers, and keep the source URLs attached.
Dashboard reuse layer
This version now separates the page copy from a reusable dashboard data object: prefectural sightings/traces, injury-context rows, municipal notices, and mistaken-capture/category-friction incidents each live as their own source layer.
That makes the Hyogo/Taka note a template for future municipality pages rather than a one-off article. The design rule is unchanged: do not collapse these rows into one bear-risk score until the source type is visible. Public-data trust comes from showing the seams.