<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>T.H. Schee</title>
	<atom:link href="https://blog.schee.info/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.schee.info</link>
	<description></description>
	<lastBuildDate>Sun, 16 Aug 2026 12:56:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>

<image>
	<url>https://blog.schee.info/wp-content/uploads/2017/06/cropped-schee-portrait.jpg?w=32</url>
	<title>T.H. Schee</title>
	<link>https://blog.schee.info</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">37923</site><cloud domain='blog.schee.info' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<atom:link rel="search" type="application/opensearchdescription+xml" href="https://blog.schee.info/osd.xml" title="T.H. Schee" />
	<atom:link rel='hub' href='https://blog.schee.info/?pushpress=hub'/>
	<item>
		<title>A Week on the Move: What a Mobile LoRa Receiver Heard Across Taipei</title>
		<link>https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/</link>
					<comments>https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/#respond</comments>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Sun, 16 Aug 2026 11:34:58 +0000</pubDate>
				<category><![CDATA[taiwan]]></category>
		<category><![CDATA[technology]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17675</guid>

					<description><![CDATA[We took a Meshtastic receiver on the road for seven days. Here&#8217;s what 1,643 packets, 226 nodes, and one very well-traveled node named ure5 taught us about our local mesh network. This is part of the Self-Organized LoRa Emergency Communication Drill series during Urban Resilience Exercise 2026 in Taiwan. Most of the time, when we&#8230; <a class="more-link" href="https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/">Continue reading <span class="screen-reader-text">A Week on the Move: What a Mobile LoRa Receiver Heard Across&#160;Taipei</span> <span class="meta-nav" aria-hidden="true">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">We took a Meshtastic receiver on the road for seven days. Here&#8217;s what 1,643 packets, 226 nodes, and one very well-traveled node named ure5 taught us about our local mesh network. This is part of the <a href="https://ure26.takke.me/">Self-Organized LoRa Emergency Communication Drill series</a> during Urban Resilience Exercise 2026 in Taiwan.</p>



<span id="more-17675"></span>



<p class="wp-block-paragraph">Most of the time, when we log Meshtastic traffic, we do it from a fixed spot — an antenna on a rooftop, quietly listening to whatever drifts by. This time we did something different: we let the receiver ride along, moving through Greater Taipei (and a couple of longer trips beyond it) over seven days, from August 7 to August 13, 2026.</p>



<p class="wp-block-paragraph">The result is a much messier, much more human dataset than usual — and honestly, a lot more fun to dig through.</p>



<h2 class="wp-block-heading">The numbers at a glance</h2>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Metric</th><th>Value</th></tr></thead><tbody><tr><td>Total packets captured</td><td>1,643</td></tr><tr><td>Unique sender nodes</td><td>226</td></tr><tr><td>Listening period</td><td>7 days</td></tr><tr><td>Average SNR</td><td>-3.1 dB</td></tr><tr><td>Median distance</td><td>8.7 km</td></tr><tr><td>Farthest reception</td><td>105.6 km</td></tr><tr><td>Text / chat messages</td><td>781</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">For comparison, our fixed station (ure1) picked up 115 unique nodes over roughly 12 hours. Seven days of mobile listening nearly doubled the node count — moving around really does get you a bigger sample of the network.</p>



<h2 class="wp-block-heading">Activity built up day by day</h2>



<figure class="wp-block-image size-large"><a href="https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png"><img width="1024" height="491" data-attachment-id="17681" data-permalink="https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/01-daily-trend-2/" data-orig-file="https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png" data-orig-size="1125,540" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;,&quot;alt&quot;:&quot;&quot;}" data-image-title="01-daily-trend" data-image-description="" data-image-caption="" data-large-file="https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png?w=739" src="https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png?w=1024" alt="" class="wp-image-17681" srcset="https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png?w=1024 1024w, https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png?w=150 150w, https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png?w=300 300w, https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png?w=768 768w, https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png 1125w" sizes="(max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption"><em>Figure 1: Daily listening activity trend</em></figcaption></figure>



<p class="wp-block-paragraph">Both the packet count and the number of unique nodes climbed steadily through the week, peaking hard on the last day — <strong>August 13</strong>, with 483 packets and 128 unique nodes in a single day. Whether that&#8217;s because the receiver rolled into a signal-rich part of town or because that day just had more people on the air, it&#8217;s a good reminder that a single day&#8217;s snapshot can badly undersell (or oversell) how &#8220;busy&#8221; a mesh network really is.</p>



<h2 class="wp-block-heading">It&#8217;s not just position pings — people are actually talking</h2>



<figure class="wp-block-image size-large"><a href="https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png"><img width="739" height="380" data-attachment-id="17682" data-permalink="https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/02-packet-types/" data-orig-file="https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png" data-orig-size="1050,540" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;,&quot;alt&quot;:&quot;&quot;}" data-image-title="02-packet-types" data-image-description="" data-image-caption="" data-large-file="https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png?w=739" src="https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png?w=739" alt="" class="wp-image-17682" srcset="https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png?w=739 739w, https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png?w=150 150w, https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png?w=300 300w, https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png?w=768 768w, https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png?w=1024 1024w, https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png 1050w" sizes="(max-width: 739px) 100vw, 739px" /></a><figcaption class="wp-element-caption"><em>Figure 2: Packet type distribution</em></figcaption></figure>



<p class="wp-block-paragraph">This was the biggest surprise in the dataset: text and chat messages (781) actually outnumbered standard POSITION_APP broadcasts (593). Digging into those messages turned up:</p>



<ul class="wp-block-list">
<li><strong>Bot traffic</strong> — <code>TPE-BOT</code>, a relay bot based in Wanhua, echoing hop counts and SNR for other nodes; and <code>MeshAI</code>, a rooftop-hosted assistant that answers <code>@mesh</code> queries about weather, PM2.5, earthquakes, and node temperature.</li>



<li><strong>MQTT bridge chatter</strong> — a node nicknamed <em>Fanzaiyuan</em> (板橋浮洲) relaying pings, distances, and hop counts from nodes connected via MQTT.</li>



<li><strong>Plain old testing and small talk</strong> — <code>@ab</code>, <code>test</code>, <code>Hi</code>, <code>安安</code> (a casual Taiwanese &#8220;hey&#8221;), and a thumbs-up emoji here and there.</li>
</ul>



<p class="wp-block-paragraph">In other words, this isn&#8217;t just a network of devices quietly reporting GPS coordinates — it&#8217;s a living community using LoRa mesh for genuine, if lightweight, communication.</p>



<h2 class="wp-block-heading">Who&#8217;s talking the most</h2>



<figure class="wp-block-image size-large"><a href="https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png"><img width="739" height="401" data-attachment-id="17684" data-permalink="https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/03-top-nodes/" data-orig-file="https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png" data-orig-size="1050,570" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;,&quot;alt&quot;:&quot;&quot;}" data-image-title="03-top-nodes" data-image-description="" data-image-caption="" data-large-file="https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png?w=739" src="https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png?w=739" alt="" class="wp-image-17684" srcset="https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png?w=739 739w, https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png?w=150 150w, https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png?w=300 300w, https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png?w=768 768w, https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png?w=1024 1024w, https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png 1050w" sizes="(max-width: 739px) 100vw, 739px" /></a><figcaption class="wp-element-caption"><em>Figure 3: Top 10 active nodes (by packet count)</em></figcaption></figure>



<p class="wp-block-paragraph">The node <code>ure26-field-8</code> topped the activity charts with 128 packets, followed closely by <code>&#x1f431;AK-HELTEC-V4</code> and <code>MeshAI</code>. Several of the most active nodes are bot or bridge nodes rather than simple end-devices — a sign that this part of the mesh has some real infrastructure behind it, not just individual hobbyist radios.</p>



<h2 class="wp-block-heading">Signal quality: more variable on the move</h2>



<figure class="wp-block-image size-large"><a href="https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png"><img loading="lazy" width="739" height="337" data-attachment-id="17685" data-permalink="https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/04-snr-distribution/" data-orig-file="https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png" data-orig-size="1050,480" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;,&quot;alt&quot;:&quot;&quot;}" data-image-title="04-snr-distribution" data-image-description="" data-image-caption="" data-large-file="https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png?w=739" src="https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png?w=739" alt="" class="wp-image-17685" srcset="https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png?w=739 739w, https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png?w=150 150w, https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png?w=300 300w, https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png?w=768 768w, https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png?w=1024 1024w, https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png 1050w" sizes="auto, (max-width: 739px) 100vw, 739px" /></a><figcaption class="wp-element-caption"><em>Figure 4: SNR distribution histogram</em></figcaption></figure>



<p class="wp-block-paragraph">Average SNR came in at -3.1 dB, across a noticeably wider range than our fixed station saw (-16.5 dB to +15.5 dB). That&#8217;s exactly what you&#8217;d expect from a moving receiver: sometimes you&#8217;re right next to a strong node, sometimes you&#8217;re at the ragged edge of coverage. It&#8217;s a nice illustration of why mobile surveys are useful for mapping real-world coverage gaps — a fixed station only ever tells you about its own neighborhood.</p>



<h2 class="wp-block-heading">Where the receiver actually went</h2>



<figure class="wp-block-image size-large"><a href="https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png"><img loading="lazy" width="1024" height="901" data-attachment-id="17686" data-permalink="https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/05-receiver-trajectory/" data-orig-file="https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png" data-orig-size="1125,990" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;,&quot;alt&quot;:&quot;&quot;}" data-image-title="05-receiver-trajectory" data-image-description="" data-image-caption="" data-large-file="https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png?w=739" src="https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png?w=1024" alt="" class="wp-image-17686" srcset="https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png?w=1024 1024w, https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png?w=150 150w, https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png?w=300 300w, https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png?w=768 768w, https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png 1125w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption"><em>Figure 5: Receiver (ure5) movement trajectory (green star = start, red star = end)</em></figcaption></figure>



<p class="wp-block-paragraph">This is the chart unique to a mobile listening session — the path the receiver itself traveled, colored from dark purple (start) to yellow (end) to show the order of movement. Most of the time was spent in and around <strong>Banqiao and Zhonghe</strong> in New Taipei (see the zoomed inset), but the log also shows a couple of longer excursions out toward <strong>Taoyuan and Hsinchu</strong>, reaching as far as roughly 121.03°E, 24.81°N. Coverage kept getting logged even during those longer trips — a nice stress test of how far the mesh actually reaches.</p>



<h2 class="wp-block-heading">Where the other nodes are</h2>



<figure class="wp-block-image size-large"><a href="https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png"><img loading="lazy" width="1024" height="901" data-attachment-id="17688" data-permalink="https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/06-node-map/" data-orig-file="https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png" data-orig-size="1125,990" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;,&quot;alt&quot;:&quot;&quot;}" data-image-title="06-node-map" data-image-description="" data-image-caption="" data-large-file="https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png?w=739" src="https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png?w=1024" alt="" class="wp-image-17688" srcset="https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png?w=1024 1024w, https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png?w=150 150w, https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png?w=300 300w, https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png?w=768 768w, https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png 1125w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption"><em>Figure 6: Sender node geographic distribution (dashed line = ure5 movement path)</em></figcaption></figure>



<p class="wp-block-paragraph">Plotting the senders themselves shows the network is heavily concentrated around Banqiao, Zhonghe, and Xinzhuang — right where the receiver spent most of its time — with a scattering of nodes further out toward Hsinchu and Yilan. The dashed line is the receiver&#8217;s own path for reference, so you can see how closely (or not) the listening route tracked the densest part of the network.</p>



<h2 class="wp-block-heading">What this tells us</h2>



<p class="wp-block-paragraph">A few takeaways from this round of listening:</p>



<ol class="wp-block-list">
<li><strong>Mobile logging finds more of the network.</strong> Nearly 2x the unique nodes compared to a fixed station, in a comparable or shorter listening window.</li>



<li><strong>This mesh is genuinely social.</strong> More than half the non-APP payloads were people (or bots) actually talking, not just machines reporting position.</li>



<li><strong>Coverage is real but uneven.</strong> SNR swings widely depending on where you are relative to the node cluster — useful information if you&#8217;re planning where a fixed relay station might help most.</li>



<li><strong>Bots and bridges matter.</strong> Infrastructure nodes like MeshAI and the MQTT relay are pulling real weight in keeping the network useful day to day.</li>
</ol>



<p class="wp-block-paragraph">Next step: we&#8217;d like to line this mobile dataset up against fixed-station logs (ure1, ure2, ure4, ure7) from the same week, and see whether the activity spike on August 13 lines up with a specific event or drill.</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<p class="wp-block-paragraph"><em>This report is part of an ongoing series of self-organized LoRa emergency communication drills.</em></p>



<p class="wp-block-paragraph"><strong>Questions or want to compare notes?</strong> Reach out at <a href="mailto:hi@sport10.org"></a><a href="mailto:tak.ywtcu@simplelogin.com">tak.ywtcu@simplelogin.com</a><br><strong>More background:</strong> <a href="https://ure26.takke.me/">ure26.takke.me</a></p>



<p class="wp-block-paragraph"><em>— <a href="https://alpha.takke.me/">TAKKE.me</a></em></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.schee.info/2026/08/16/a-week-on-the-move-what-a-mobile-lora-receiver-heard-across-taipei/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17675</post-id>
		<media:thumbnail url="https://blog.schee.info/wp-content/uploads/2026/08/20260726_163707.webp" />
		<media:content url="https://blog.schee.info/wp-content/uploads/2026/08/20260726_163707.webp" medium="image">
			<media:title type="html">20260726_163707</media:title>
		</media:content>

		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>

		<media:content url="https://blog.schee.info/wp-content/uploads/2026/08/01-daily-trend-1.png?w=1024" medium="image" />

		<media:content url="https://blog.schee.info/wp-content/uploads/2026/08/02-packet-types.png?w=739" medium="image" />

		<media:content url="https://blog.schee.info/wp-content/uploads/2026/08/03-top-nodes.png?w=739" medium="image" />

		<media:content url="https://blog.schee.info/wp-content/uploads/2026/08/04-snr-distribution.png?w=739" medium="image" />

		<media:content url="https://blog.schee.info/wp-content/uploads/2026/08/05-receiver-trajectory.png?w=1024" medium="image" />

		<media:content url="https://blog.schee.info/wp-content/uploads/2026/08/06-node-map.png?w=1024" medium="image" />
	</item>
		<item>
		<title>台灣極限消防員國際邀請賽的積極意義</title>
		<link>https://blog.schee.info/2026/08/14/tw-2026-ultimate-firefighter-invitation/</link>
					<comments>https://blog.schee.info/2026/08/14/tw-2026-ultimate-firefighter-invitation/#respond</comments>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Fri, 14 Aug 2026 10:19:03 +0000</pubDate>
				<category><![CDATA[sports]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17670</guid>

					<description><![CDATA[令人驚賞的邀請賽進行完之後，幾點觀察，提供台灣運動產業參考。 這場賽事特別的是「國際規格」。傳統單項運動賽事的「國際規格」大多是繼承全球性單項運動賽事的賽事訓練、賽事規範等來。「極限消防員」是每兩年一次世界警消運動大會的重要比賽項目之一，雖然對國人來說稍嫌陌生，但它的遊戲規則是一樣，有嚴謹的賽事規則。 這和一般純粹以商業市場導向的「體能競賽」，有非常大的差異。新興的體能賽事雖然有市場，但在訓練、賽事規範和裁判培訓，大多是聊備一格。白話來說就是賽事到了才有志工裁判招募，而這些裁判的培訓過程，基本上是零，或是從其他商業賽事領域「挪用」而來。 此種發展路徑的風險在於，商業風潮來來去去，十年河東十年河西。純粹的商業賽事看起來很熱絡，但對於競技成績提昇、運動育才和社會影響，有著很多無法掌握的外部商業利益過度操作痕跡。 台灣極限消防員國際邀請賽沒有這問題，當然每個比賽都會有面臨不等的挑戰，但這個發展軸心只要是賽事舉辦的核心，對台灣各種運動賽事來說，都是很好的樣板。 第二點是，這是由志工和協會團體所領軍舉辦，這在台灣這種以傳統單項運動賽會、學校裁判系統和體育總會等結構所支撐的競賽雖然相似，但成員來源有極大的不同。「極限消防員」等「消防專項競技」，就是台灣先鋒者（Taiwan Pioneers）、台灣戰術肌力與體能協會（TTSACA），還有眾多的消防員（包含義消系統）志工團所聯手打造出來的平台。 我們都知道，台灣的「體育」傳統是以競技選手（又稱體育班選手）為中心。即便是「極限消防員」的能度和訓練早就到達傳統單項運動賽事的水平，但此類對國內大眾來說，仍屬「新興」的項目。今年才被新成立的「運動部」列入「極限運動項目」。極限消防員國際邀請賽的舉辦，實質上是為台灣的運動和訓練打出一條既符合國際遊戲規則，但又有傳統以單項運動項目出發，強化專項訓練、推廣賽事舉辦，以及促進社會發展意義的實現。 從長期來看，這個層面的突破，可能遠比參加世界警消運動大會拿到金牌的數量更值得大書特書。任何一個國家都可以派金牌等級的警消選手參加，但他們不一定有台灣這種平台。 這是非常不簡單的事！更多賽事精采訊息和照片可參考： https://www.instagram.com/taiwanpioneers https://www.facebook.com/nevergiveup.youcan https://www.instagram.com/tsac.tw 自我揭露：本人是極限消防員競技的粉絲。]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">令人驚賞的邀請賽進行完之後，幾點觀察，提供台灣運動產業參考。</p>



<p class="wp-block-paragraph">這場賽事特別的是「國際規格」。傳統單項運動賽事的「國際規格」大多是繼承全球性單項運動賽事的賽事訓練、賽事規範等來。「極限消防員」是每兩年一次世界警消運動大會的重要比賽項目之一，雖然對國人來說稍嫌陌生，但它的遊戲規則是一樣，有嚴謹的賽事規則。</p>



<span id="more-17670"></span>



<p class="wp-block-paragraph">這和一般純粹以商業市場導向的「體能競賽」，有非常大的差異。新興的體能賽事雖然有市場，但在訓練、賽事規範和裁判培訓，大多是聊備一格。白話來說就是賽事到了才有志工裁判招募，而這些裁判的培訓過程，基本上是零，或是從其他商業賽事領域「挪用」而來。</p>



<p class="wp-block-paragraph">此種發展路徑的風險在於，商業風潮來來去去，十年河東十年河西。純粹的商業賽事看起來很熱絡，但對於競技成績提昇、運動育才和社會影響，有著很多無法掌握的外部商業利益過度操作痕跡。</p>



<p class="wp-block-paragraph">台灣極限消防員國際邀請賽沒有這問題，當然每個比賽都會有面臨不等的挑戰，但這個發展軸心只要是賽事舉辦的核心，對台灣各種運動賽事來說，都是很好的樣板。</p>



<p class="wp-block-paragraph">第二點是，這是由志工和協會團體所領軍舉辦，這在台灣這種以傳統單項運動賽會、學校裁判系統和體育總會等結構所支撐的競賽雖然相似，但成員來源有極大的不同。「極限消防員」等「消防專項競技」，就是台灣先鋒者（Taiwan Pioneers）、台灣戰術肌力與體能協會（TTSACA），還有眾多的消防員（包含義消系統）志工團所聯手打造出來的平台。</p>



<p class="wp-block-paragraph">我們都知道，台灣的「體育」傳統是以競技選手（又稱體育班選手）為中心。即便是「極限消防員」的能度和訓練早就到達傳統單項運動賽事的水平，但此類對國內大眾來說，仍屬「新興」的項目。今年才被新成立的「運動部」列入「極限運動項目」。極限消防員國際邀請賽的舉辦，實質上是為台灣的運動和訓練打出一條既符合國際遊戲規則，但又有傳統以單項運動項目出發，強化專項訓練、推廣賽事舉辦，以及促進社會發展意義的實現。</p>



<p class="wp-block-paragraph">從長期來看，這個層面的突破，可能遠比參加世界警消運動大會拿到金牌的數量更值得大書特書。任何一個國家都可以派金牌等級的警消選手參加，但他們不一定有台灣這種平台。</p>



<p class="wp-block-paragraph">這是非常不簡單的事！更多賽事精采訊息和照片可參考：</p>



<p class="wp-block-paragraph"><a href="https://www.instagram.com/taiwanpioneers">https://www.instagram.com/taiwanpioneers</a></p>



<p class="wp-block-paragraph"><strong><a href="https://www.facebook.com/nevergiveup.youcan">https://www.facebook.com/nevergiveup.youcan</a></strong></p>



<p class="wp-block-paragraph"><strong><a href="https://www.instagram.com/tsac.tw">https://www.instagram.com/tsac.tw</a></strong></p>



<p class="wp-block-paragraph">自我揭露：本人是極限消防員競技的粉絲。</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.schee.info/2026/08/14/tw-2026-ultimate-firefighter-invitation/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17670</post-id>
		<media:thumbnail url="https://blog.schee.info/wp-content/uploads/2026/08/5x7a1600.jpg" />
		<media:content url="https://blog.schee.info/wp-content/uploads/2026/08/5x7a1600.jpg" medium="image">
			<media:title type="html">5X7A1600</media:title>
		</media:content>

		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>
	</item>
		<item>
		<title>自主 LoRa 緊急通訊演練</title>
		<link>https://blog.schee.info/2026/07/18/lora-emcomm-ure26/</link>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Sat, 18 Jul 2026 02:19:33 +0000</pubDate>
				<category><![CDATA[taiwan]]></category>
		<category><![CDATA[technology]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17666</guid>

					<description><![CDATA[北部地區 2026 城鎮韌性（防空）演習訂於8月13日14時30分至15時實施， 期間將模擬行動網路受阻情境，請民眾理解屬於常態化的災防演練安排。本次演練將首次大規模在北部和中部縣市進行行動網路受阻演練，所有民眾將面臨30分鐘行動網路受阻， 僅能使用語音和簡訊文字，請提前準備並遵循現場指引。 政府官方訊息散見政府網站和各大小媒體。 TAKKE.me 把握難得的機會，預計以各種 LoRa 節點為基礎，進行以社區為基礎且較為正規的緊急通訊（Emcomm）操作， 讓更多人能熟悉緊急通訊需要的作業原則。 計畫網站（繁中、英文、日文、越南文）https://ure26.takke.me/]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">北部地區 2026 城鎮韌性（防空）演習訂於8月13日14時30分至15時實施， 期間將模擬行動網路受阻情境，請民眾理解屬於常態化的災防演練安排。本次演練將首次大規模在北部和中部縣市進行行動網路受阻演練，所有民眾將面臨30分鐘行動網路受阻， 僅能使用語音和簡訊文字，請提前準備並遵循現場指引。</p>



<p class="wp-block-paragraph">政府官方訊息散見政府網站和各大小媒體。</p>



<span id="more-17666"></span>



<p class="wp-block-paragraph"><a href="https://alpha.takke.me">TAKKE.me</a> 把握難得的機會，預計以各種 LoRa 節點為基礎，進行以社區為基礎且較為正規的緊急通訊（Emcomm）操作， 讓更多人能熟悉緊急通訊需要的作業原則。</p>



<p class="wp-block-paragraph">計畫網站（繁中、英文、日文、越南文）<a href="https://ure26.takke.me/">https://ure26.takke.me/</a></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17666</post-id>
		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>
	</item>
		<item>
		<title>2026台灣極限消防員國際邀請賽 世界頂尖消防運動員齊聚南投</title>
		<link>https://blog.schee.info/2026/07/13/2026-taiwan-ultimate-firefighter-internanationl/</link>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Mon, 13 Jul 2026 00:29:08 +0000</pubDate>
				<category><![CDATA[sports]]></category>
		<category><![CDATA[taiwan]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17662</guid>

					<description><![CDATA[一場結合力量、速度與專業精神的國際賽事即將在台灣登場——「2026台灣極限消防員國際邀請賽」將於8月1日至2日，在內政部消防署訓練中心A15戰技館盛大展開。這場賽事消防員之間的競技較量，也是一場展現全球消防精神的國際盛會，誠摯邀請所有民眾親臨現場，共同見證這場屬於勇者的競技舞台。 賽事地點與時間 本次賽事地點位於南投縣竹山鎮社寮里大公街100號，也就是內政部消防署訓練中心的A15多功能消防戰技館。賽事時間訂於2026年8月1日至8月2日，為期兩天，分別安排個人賽與團體賽及民眾組競賽。 近千名國際好手齊聚一堂 本屆邀請賽匯集了來自六個國家的頂尖消防運動員，包括地主台灣、捷克、巴西、葡萄牙、波蘭與斯洛伐克。近千名世界級消防運動員將齊聚台灣,在賽場上展現他們平日訓練的成果與極限體能，場面精彩可期。這是台灣少見能近距離接觸國際消防好手競技的機會，絕對值得一探究竟。 兩天賽程 精彩不間斷 8月1日 個人賽 上午8點至12點30分為上午賽程，緊接著進行長官與貴賓致詞及紀念品發放。下午1點至5點為下午賽程，最終在下午5點至6點舉行選手頒獎與紀念品發放儀式，為第一天賽事畫下句點。 8月2日 團體賽及民眾組 上午賽程同樣於8點展開,持續至中午12點,接著進行貴賓致詞與紀念品發放。下午賽程自12點30分開始，持續至下午3點30分，最終於下午3點30分至4點30分舉行頒獎典禮，為整場賽事完美收場。 主辦與支持單位 本次賽事由內政部消防署擔任指導機構，台灣戰術肌力與體能協會及台灣先鋒者共同主辦，並獲得台灣消防發展與交流協會的大力支持。賽事實況也將由 TAIWAN SBD 和「永不放棄的運動線上」進行官方媒體轉播，讓無法親臨現場的民眾也能透過線上管道感受賽事熱度。 誠摯邀請 現場感受消防員的極限精神 消防員平日肩負著保護民眾生命財產安全的重任，而這場賽事正是讓大眾看見他們專業之外、堅韌不拔的另一面。無論是負重前行、體能挑戰，還是團隊默契的展現，每一個環節都凝聚著消防員長期訓練的心血與汗水。 這場賽事誠摯邀請社會大眾在8月1日至2日撥冗前往南投竹山，親自到場為這些來自世界各地的消防勇士們加油喝采。這不僅是一場體育競技，更是一次向消防員致敬、認識國際消防文化交流的絕佳機會。讓我們一起走進現場，用掌聲與熱情，見證這場世界消防競技的精神盛宴！]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">一場結合力量、速度與專業精神的國際賽事即將在台灣登場——「<a href="https://www.facebook.com/TaiwanTSCPioneer/posts/-2026-%E7%AC%AC%E4%BA%8C%E5%B1%86%E5%8F%B0%E7%81%A3%E6%A5%B5%E9%99%90%E6%B6%88%E9%98%B2%E5%93%A1%E5%9C%8B%E9%9A%9B%E9%82%80%E8%B3%BD2026-the-2nd-taiwan-ultimate-firefighter-international-invit/1433667468773460/">2026台灣極限消防員國際邀請賽</a>」將於8月1日至2日，在內政部消防署訓練中心A15戰技館盛大展開。這場賽事消防員之間的競技較量，也是一場展現全球消防精神的國際盛會，誠摯邀請所有民眾親臨現場，共同見證這場屬於勇者的競技舞台。</p>



<span id="more-17662"></span>



<h3 class="wp-block-heading">賽事地點與時間</h3>



<p class="wp-block-paragraph">本次賽事地點位於南投縣竹山鎮社寮里大公街100號，也就是內政部消防署訓練中心的A15多功能消防戰技館。賽事時間訂於2026年8月1日至8月2日，為期兩天，分別安排個人賽與團體賽及民眾組競賽。</p>



<h3 class="wp-block-heading">近千名國際好手齊聚一堂</h3>



<p class="wp-block-paragraph">本屆邀請賽匯集了來自六個國家的頂尖消防運動員，包括地主台灣、捷克、巴西、葡萄牙、波蘭與斯洛伐克。近千名世界級消防運動員將齊聚台灣,在賽場上展現他們平日訓練的成果與極限體能，場面精彩可期。這是台灣少見能近距離接觸國際消防好手競技的機會，絕對值得一探究竟。</p>



<h3 class="wp-block-heading">兩天賽程 精彩不間斷</h3>



<p class="wp-block-paragraph"><strong>8月1日 個人賽</strong></p>



<p class="wp-block-paragraph">上午8點至12點30分為上午賽程，緊接著進行長官與貴賓致詞及紀念品發放。下午1點至5點為下午賽程，最終在下午5點至6點舉行選手頒獎與紀念品發放儀式，為第一天賽事畫下句點。</p>



<p class="wp-block-paragraph"><strong>8月2日 團體賽及民眾組</strong></p>



<p class="wp-block-paragraph">上午賽程同樣於8點展開,持續至中午12點,接著進行貴賓致詞與紀念品發放。下午賽程自12點30分開始，持續至下午3點30分，最終於下午3點30分至4點30分舉行頒獎典禮，為整場賽事完美收場。</p>



<h3 class="wp-block-heading">主辦與支持單位</h3>



<p class="wp-block-paragraph">本次賽事由內政部消防署擔任指導機構，台灣戰術肌力與體能協會及<a href="https://www.instagram.com/taiwanpioneers/">台灣先鋒者</a>共同主辦，並獲得台灣消防發展與交流協會的大力支持。賽事實況也將由 <a href="https://www.instagram.com/sbdtaiwan/">TAIWAN SBD</a> 和「<a href="https://www.dragonboat.tw/">永不放棄的運動線上</a>」進行官方媒體轉播，讓無法親臨現場的民眾也能透過線上管道感受賽事熱度。</p>



<h3 class="wp-block-heading">誠摯邀請 現場感受消防員的極限精神</h3>



<p class="wp-block-paragraph">消防員平日肩負著保護民眾生命財產安全的重任，而這場賽事正是讓大眾看見他們專業之外、堅韌不拔的另一面。無論是負重前行、體能挑戰，還是團隊默契的展現，每一個環節都凝聚著消防員長期訓練的心血與汗水。</p>



<p class="wp-block-paragraph">這場賽事誠摯邀請社會大眾在8月1日至2日撥冗前往南投竹山，親自到場為這些來自世界各地的消防勇士們加油喝采。這不僅是一場體育競技，更是一次向消防員致敬、認識國際消防文化交流的絕佳機會。讓我們一起走進現場，用掌聲與熱情，見證這場世界消防競技的精神盛宴！</p>



<figure class="wp-block-image size-large"><a href="https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg"><img loading="lazy" width="1024" height="1024" data-attachment-id="17664" data-permalink="https://blog.schee.info/2026/07/13/2026-taiwan-ultimate-firefighter-internanationl/photo_6214991439263895344_y/" data-orig-file="https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg" data-orig-size="1254,1254" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;,&quot;alt&quot;:&quot;&quot;}" data-image-title="photo_6214991439263895344_y" data-image-description="" data-image-caption="" data-large-file="https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg?w=739" src="https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg?w=1024" alt="" class="wp-image-17664" srcset="https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg?w=1024 1024w, https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg?w=150 150w, https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg?w=300 300w, https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg?w=768 768w, https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg 1254w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17662</post-id>
		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>

		<media:content url="https://blog.schee.info/wp-content/uploads/2026/07/photo_6214991439263895344_y.jpg?w=1024" medium="image" />
	</item>
		<item>
		<title>Humanitarian Aid and Disaster Resilience Workshop (TaiwanAID)</title>
		<link>https://blog.schee.info/2026/07/07/humanitarian-aid-and-disaster-resilience-workshop-taiwanaid/</link>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Tue, 07 Jul 2026 09:29:18 +0000</pubDate>
				<category><![CDATA[taiwan]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17658</guid>

					<description><![CDATA[When disasters strike, beyond passion and a sense of mission—and beyond disaster preparedness and emergency medical knowledge—understanding the core principles and relevant standards of the&#160;Sphere Humanitarian Charter&#160;is essential for effectively enhancing disaster resilience. The Humanitarian Aid and Disaster Resilience Workshop, organized by the Taiwan Alliance in International Development (Taiwan AID), was held from June 25 to&#8230; <a class="more-link" href="https://blog.schee.info/2026/07/07/humanitarian-aid-and-disaster-resilience-workshop-taiwanaid/">Continue reading <span class="screen-reader-text">Humanitarian Aid and Disaster Resilience Workshop&#160;(TaiwanAID)</span> <span class="meta-nav" aria-hidden="true">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">When disasters strike, beyond passion and a sense of mission—and beyond disaster preparedness and emergency medical knowledge—understanding the core principles and relevant standards of the&nbsp;<strong>Sphere Humanitarian Charter</strong>&nbsp;is essential for effectively enhancing disaster resilience.</p>



<span id="more-17658"></span>



<p class="wp-block-paragraph">The <strong>Humanitarian Aid and Disaster Resilience Workshop</strong>, organized by the Taiwan Alliance in International Development (Taiwan AID), was held from June 25 to June 27, 2026 at the Chien Tan Overseas Youth Activity Center. The workshop invited Japanese instructor Sawako to come to Taiwan to teach, attracting approximately 31 participants from various sectors, including government agencies (military, police, and fire departments), NGOs, associations, corporations, schools, and medical institutions. Together, they studied the core principles and practical tools of international humanitarian aid, with the aim of improving Taiwan&#8217;s effectiveness in disaster prevention, relief, and post-disaster reconstruction—ultimately helping affected populations restore their daily lives with dignity.</p>



<p class="wp-block-paragraph">Full post in Chinese: <a href="https://www.facebook.com/share/p/18wKy2KRqt/">https://www.facebook.com/share/p/18wKy2KRqt/</a> </p>



<p class="wp-block-paragraph">Photo: <a href="https://www.taiwanaid.org/">TaiwanAID</a></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17658</post-id>
		<media:thumbnail url="https://blog.schee.info/wp-content/uploads/2026/07/742208368_1025729826739433_1928054960014867334_n.jpg" />
		<media:content url="https://blog.schee.info/wp-content/uploads/2026/07/742208368_1025729826739433_1928054960014867334_n.jpg" medium="image">
			<media:title type="html">742208368_1025729826739433_1928054960014867334_n</media:title>
		</media:content>

		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>
	</item>
		<item>
		<title>網路自由小聚 [6月] ：TAKKE.ME &#8211; 災防、搜救、通訊知識交流平台</title>
		<link>https://blog.schee.info/2026/06/12/internetfreedom-jun2026/</link>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Fri, 12 Jun 2026 15:15:14 +0000</pubDate>
				<category><![CDATA[taiwan]]></category>
		<category><![CDATA[technology]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17650</guid>

					<description><![CDATA[TAKKE（TAK Knowledge Exchange） 是聚焦台灣的災防、搜救、通訊與戶外社群知識交流平台，致力於連結技術與實務，促進跨領域的協作與對話。 p.s. “TAK KE” 為台語逐家 “tak-ke” 大家、眾人之意。 本次聚會將超高速圍繞以下四大構面展開分享： 城鎮韌性演習專題 本次也將特別探討本年度在某縣市城鎮韌性演習的實戰經驗，探討在疏散、救災與收容各階段中，如何建立有效的共同作業圖像（Common Operating Picture），以及伺服器之間 federation 的想法。 誰適合參加？ 無論你的背景如何，只要符合以下任一描述，這場就是為你而設： 什麼是 TAK? TAK 是美國國防部及空軍研究實驗室（AFRL）開發的戰術與團隊覺知軟體。它是一款安裝在手機或平板上的強大地理資訊與指管 App，能讓軍隊、特種部隊或搜救人員在任務中獲得類似「上帝視角」的作戰優勢。 ATAK 是一款設計用於 Android 設備上的移動地圖應用程式，主要功能是提供用戶即時的位置資訊、地圖顯示和團隊協作工具，最初是為軍事和政府用途開發，而 ATAK-CIV 則是釋出給民用（如急救人員、執法單位、緊急應變、一般聯邦雇員等）的版本。有組織的志工當然也可以運用。 報名&#160;https://ocftw.kktix.cc/events/internetfreedom-jun2026]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><a href="https://alpha.takke.me">TAKKE</a>（TAK Knowledge Exchange） 是聚焦台灣的災防、搜救、通訊與戶外社群知識交流平台，致力於連結技術與實務，促進跨領域的協作與對話。</p>



<p class="wp-block-paragraph">p.s. “TAK KE” 為台語逐家 “tak-ke” 大家、眾人之意。</p>



<span id="more-17650"></span>



<p class="wp-block-paragraph">本次聚會將超高速圍繞以下四大構面展開分享：</p>



<ul class="wp-block-list">
<li>戶外生活應用構面</li>



<li>組織政策考量構面</li>



<li>實務導入成本構面</li>



<li>戰術通信安全構面</li>
</ul>



<p class="wp-block-paragraph"><strong>城鎮韌性演習專題</strong></p>



<p class="wp-block-paragraph">本次也將特別探討本年度在某縣市城鎮韌性演習的實戰經驗，探討在疏散、救災與收容各階段中，如何建立有效的共同作業圖像（Common Operating Picture），以及伺服器之間 federation 的想法。</p>



<p class="wp-block-paragraph"><strong>誰適合參加？</strong></p>



<p class="wp-block-paragraph">無論你的背景如何，只要符合以下任一描述，這場就是為你而設：</p>



<ul class="wp-block-list">
<li>沒有技術背景，但有具體業務項目需要推動</li>



<li>缺乏技術概念，但有動機想了解這個領域</li>



<li>擁有技術能力，但想了解實務端的業務關切是什麼</li>
</ul>



<p class="wp-block-paragraph"><strong>什麼是 TAK?</strong></p>



<p class="wp-block-paragraph">TAK 是美國國防部及空軍研究實驗室（AFRL）開發的戰術與團隊覺知軟體。它是一款安裝在手機或平板上的強大地理資訊與指管 App，能讓軍隊、特種部隊或搜救人員在任務中獲得類似「上帝視角」的作戰優勢。</p>



<p class="wp-block-paragraph">ATAK 是一款設計用於 Android 設備上的移動地圖應用程式，主要功能是提供用戶即時的位置資訊、地圖顯示和團隊協作工具，最初是為軍事和政府用途開發，而 ATAK-CIV 則是釋出給民用（如急救人員、執法單位、緊急應變、一般聯邦雇員等）的版本。有組織的志工當然也可以運用。</p>



<ul class="wp-block-list">
<li>時間：6/18（四）19:30 &#8211; 21:30</li>



<li>地點：摩茲工寮 （台北市中正區重慶南路一段 99 號 1105 室世界大樓 11 樓）</li>



<li>語言：中文</li>



<li>參與方式：實體 / 線上參與，線上不保證連線品質</li>



<li>本聚會採用 <a href="https://zh.wikipedia.org/zh-tw/%E6%9F%A5%E8%BE%BE%E5%A7%86%E7%A0%94%E7%A9%B6%E6%89%80%E8%A7%84%E5%88%99">Chatham House rule</a>，參加會議的任何人都可以自由使用討論中的資訊，但不得透露誰發表了任何特定評論。</li>



<li>為保障參與者的權益，於聚會中如需拍攝任何照片、影片，請預先告知在場所有人，避免有些人不想要被拍攝。</li>
</ul>



<p class="wp-block-paragraph">報名&nbsp;<a href="https://ocftw.kktix.cc/events/internetfreedom-jun2026">https://ocftw.kktix.cc/events/internetfreedom-jun2026</a></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17650</post-id>
		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>
	</item>
		<item>
		<title>七天連續戰術體能挑戰：US Army CFT、Rucking、Murph 和四個 Hero WODs 的實測記錄</title>
		<link>https://blog.schee.info/2026/06/07/hero-wods/</link>
					<comments>https://blog.schee.info/2026/06/07/hero-wods/#comments</comments>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Sun, 07 Jun 2026 09:35:01 +0000</pubDate>
				<category><![CDATA[sports]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17638</guid>

					<description><![CDATA[七天，全程 30°C 以上，除一項外全部在戶外施作，沒有受傷完成。 「計畫」的起點是想在一週內系統性地測試幾個不同的戰術體能指標——從美國陸軍最新的 Combat Field Test（CFT）、Rucking，到 CrossFit 的經典 Hero WODs 等。七項 workout 橫跨心肺耐力、負重耐力、最大力量和速度間歇，彼此之間沒有完整的恢復日。 D1：Army Combat Field Test（CFT） 成績：25 分鐘完成 及格標準：30 分鐘以內 CFT 是美國陸軍在 2026 年 4 月剛推出的新測驗。七項連續不停歇：1 英里跑步 → 30 個放手伏地挺身 → 100 米衝刺 → 40 磅沙包舉高 16 次 → 50 米提水桶行進（左右各 40 磅）→ 50 米高姿匍匐加 3-5 秒衝刺臥倒 → 再跑 1 英里。全程不分年齡性別，同一標準。 25 分鐘的意思是比及格線快五分鐘（17%）。體感上，前段跑步還算輕鬆，沙包舉高和水桶搬運是真正的消耗點，後段第二個英里在高溫下明顯感受到核心溫度上升。如果在涼爽環境測，保守估計可以再快&#8230; <a class="more-link" href="https://blog.schee.info/2026/06/07/hero-wods/">Continue reading <span class="screen-reader-text">七天連續戰術體能挑戰：US Army CFT、Rucking、Murph 和四個 Hero WODs&#160;的實測記錄</span> <span class="meta-nav" aria-hidden="true">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">七天，全程 30°C 以上，除一項外全部在戶外施作，沒有受傷完成。</p>



<p class="wp-block-paragraph">「計畫」的起點是想在一週內系統性地測試幾個不同的戰術體能指標——從美國陸軍最新的 Combat Field Test（CFT）、Rucking，到 CrossFit 的經典 Hero WODs 等。七項 workout 橫跨心肺耐力、負重耐力、最大力量和速度間歇，彼此之間沒有完整的恢復日。</p>



<span id="more-17638"></span>



<h2 class="wp-block-heading">D1：Army Combat Field Test（CFT）</h2>



<p class="wp-block-paragraph"><strong>成績：25 分鐘完成</strong></p>



<p class="wp-block-paragraph"><strong>及格標準：30 分鐘以內</strong></p>



<p class="wp-block-paragraph">CFT 是美國陸軍在 2026 年 4 月剛推出的<a href="https://sport10.org/2026/04/23/us-army-combat-field-test/">新測驗</a>。七項連續不停歇：1 英里跑步 → 30 個放手伏地挺身 → 100 米衝刺 → 40 磅沙包舉高 16 次 → 50 米提水桶行進（左右各 40 磅）→ 50 米高姿匍匐加 3-5 秒衝刺臥倒 → 再跑 1 英里。全程不分年齡性別，同一標準。</p>



<p class="wp-block-paragraph">25 分鐘的意思是比及格線快五分鐘（17%）。體感上，前段跑步還算輕鬆，沙包舉高和水桶搬運是真正的消耗點，後段第二個英里在高溫下明顯感受到核心溫度上升。如果在涼爽環境測，保守估計可以再快 2-3 分鐘。</p>



<p class="wp-block-paragraph">CFT 測的不是單項能力，而是在疲勞狀態下的動作轉換效率。這項的 RPE（Rating of Perceived Exertion）約莫是 7.5 左右。</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading">D2：Ruck March</h2>



<p class="wp-block-paragraph"><strong>成績：負重 11 kg，6.38 km，58 分鐘，配速 9:06/km</strong></p>



<p class="wp-block-paragraph"><strong>美陸軍步兵標準：≤ 12:00/km</strong></p>



<p class="wp-block-paragraph">考量這次的挑戰有七天的週期，所以這個配速的安排並不快，而且&nbsp;<a href="https://sport10.org/?s=rucking">rucking 我比較有經驗</a>。</p>



<p class="wp-block-paragraph">9:06/km 比標準快 24%，這個數字在 CFT 後第二天的條件下算是穩健。負重行進的訓練遷移性一直是我認為被低估的——它訓練的是「帶著重量長時間移動」的能力，和純跑步是完全不同的神經肌肉刺激模式，跟登山的關聯性也很直接。CFT 測的不是單項能力，而是在疲勞狀態下的動作轉換效率。</p>



<p class="wp-block-paragraph">這項的 RPE（Rating of Perceived Exertion）約莫是 6 左右。</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading">D3：Hero WOD Murph Challenge（無負重）</h2>



<p class="wp-block-paragraph"><strong>成績：55 分鐘</strong>&nbsp;<strong>動作：1 英里跑 + 100 pull-ups（kipping）+ 200 push-ups + 300 squats + 1 英里跑</strong></p>



<p class="wp-block-paragraph">Murph 一向是傳說中的大魔王，我是在第三天做，體感會如何也很難預料。最後 55 分鐘結束（無負重版本），pull-ups 則是用 kipping（擺盪式）完成。高溫是這一天最大的敵人，在 30°C 以上完成 200 個伏地挺身，乳酸堆積的速度比正常環境明顯更快。</p>



<p class="wp-block-paragraph">同齡（45-49 歲）無負重 Murph 的中位數大約在 60-70 分鐘，55 分鐘應該可算落在前段。這項的 RPE（Rating of Perceived Exertion）約莫是 9 左右。</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading">D4：Hero WOD Griff（RX）</h2>



<p class="wp-block-paragraph"><strong>成績：15 分 03 秒（負向分段）</strong>&nbsp;<strong>動作：800m 跑 → 400m 倒退跑 → 800m 跑 → 400m 倒退跑</strong></p>



<p class="wp-block-paragraph">分段：</p>



<ul class="wp-block-list">
<li>第 1 段（800m 正跑）：3’50″</li>



<li>第 2 段（400m 倒退跑）：3’55″</li>



<li>第 3 段（800m 正跑）：3’35″ ↑</li>



<li>第 4 段（400m 倒退跑）：3’43″ ↑</li>
</ul>



<p class="wp-block-paragraph">Griff 是七天計畫中刻意安排的「減壓日」，純跑步，沒有力量動作，讓前三天壓爛的上肢肌群喘一口氣。</p>



<p class="wp-block-paragraph">值得記錄的是負向分段——後半段比前半段快，正跑進步 15 秒，倒退跑進步 12 秒。在第四天疲勞狀態下出現負向分段，代表前三段是主動控速而不是跑不動，有氧效率在這個強度區間仍然有餘裕。倒退跑我沒跑過四百米，怕摔倒因此跑的很保守。<br><br>這項的 RPE（Rating of Perceived Exertion）約莫是 7 左右。</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading">D5：Hero WOD McGhee（RX）</h2>



<p class="wp-block-paragraph"><strong>成績：12 rounds，30 分鐘 AMRAP</strong>&nbsp;<strong>動作：275 磅（125 kg）硬舉 × 5 → 13 push-ups → 24″ box jump × 9</strong></p>



<p class="wp-block-paragraph">125 kg 硬舉做了 60 次。總移動重量 7,500 kg，平均每輪 2 分 30 秒。RX 的參考標準大約是 10 rounds 及格、12-14 rounds 良好，12 rounds 落在良好區間的下緣。</p>



<p class="wp-block-paragraph">第五天做最大力量的訓練，生理邏輯上不是最優的安排，但這次的目的就是在疲勞條件下測試力量的保留率。結論是：60 次 125 kg 硬舉在連續五天後仍然可以完成，後鏈的抗疲勞能力比預期好。動作品質到最後幾輪有小幅下降，這是誠實的自評。</p>



<p class="wp-block-paragraph">AMRAP 格式讓節奏控制變得關鍵，前五輪不要跑太快，在第 8-9 輪的疲勞谷底撐住，是這個 WOD 的核心策略。</p>



<p class="wp-block-paragraph">這項的 RPE（Rating of Perceived Exertion）約莫是 8.5 左右。</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading">D6：400m × 10 間歇（臨時改動）</h2>



<p class="wp-block-paragraph"><strong>成績：均速 106 秒（102-110s 範圍），負向分段</strong>&nbsp;<strong>條件：大雨，一般道路，每圈六個轉彎，逆時鐘，靜止休息 2 分鐘</strong></p>



<p class="wp-block-paragraph">原計畫是 Hero WOD Forrest，幾乎都是上身的動作，但今日大雨讓單槓濕滑，放棄。臨場改 400m 間歇。</p>



<p class="wp-block-paragraph">路線是一般道路，一圈有六個轉彎，採取逆時鐘跑。標準田徑場是兩個彎，六個轉彎代表減速轉向的次數多，每一個彎都是額外的煞車和加速，估計每趟比田徑場慢 6-10 秒。加上大雨路滑（再 +3-5 秒）和一般道路凹凸（再 +2-3 秒），修正後的實際配速能力大約接近 3:45-3:55/km。</p>



<p class="wp-block-paragraph">分段仍然是負向，前五趟均速約 108 秒，後五趟約 104 秒。這是第二次在疲勞狀態下出現負向分段（D4 Griff 是第一次）。</p>



<p class="wp-block-paragraph">這項的 RPE（Rating of Perceived Exertion）約莫是 8 左右。</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading">D7：Hero WOD Brenton（RX）</h2>



<p class="wp-block-paragraph"><strong>成績：負重 20 磅，完成成績 15 分 28 秒，5 rounds</strong>&nbsp;<strong>動作：Bear crawl 100 feet → Standing broad jump 100 feet（每 5 跳做 3 個 burpees）</strong></p>



<p class="wp-block-paragraph">分段：</p>



<ul class="wp-block-list">
<li>Lap 1：2:24.74</li>



<li>Lap 2：2:47.99</li>



<li>Lap 3：3:08.11</li>



<li>Lap 4：3:28.93</li>



<li>Lap 5：3:38.27</li>
</ul>



<p class="wp-block-paragraph">這是七天的收尾，也是唯一的正向分段（越來越慢）。Lap 1 到 Lap 5 相差 1 分 13 秒，減速幅度約 50%。</p>



<p class="wp-block-paragraph">正向分段在這一天完全合理，畢竟這是第七天的最後一項，身體的疲勞已累積到頂點。值得記錄的是 Lap 1 仍然跑出 2:24，代表第七天早上的爆發力儲備沒有完全清空。後段的減速是真實疲勞反應，已經不是配速的問題。</p>



<p class="wp-block-paragraph">這項的 RPE（Rating of Perceived Exertion）約莫是 9 左右。</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading">整體回顧</h2>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>天</th><th>WOD</th><th>成績</th><th>特殊條件</th></tr></thead><tbody><tr><td>D1</td><td>Army CFT</td><td>25:00</td><td>高溫，穿戰鬥服靴</td></tr><tr><td>D2</td><td>Ruck March</td><td>58:00 / 9:06/km</td><td>高溫，CFT 後隔天</td></tr><tr><td>D3</td><td>Murph</td><td>55:00</td><td>高溫，無負重</td></tr><tr><td>D4</td><td>Griff RX</td><td>15:03</td><td>高溫，負向分段</td></tr><tr><td>D5</td><td>McGhee RX</td><td>12 rounds</td><td>高溫，125kg</td></tr><tr><td>D6</td><td>400m × 10</td><td>均速 106s</td><td>大雨，六彎道，負向分段</td></tr><tr><td>D7</td><td>Brenton RX</td><td>15:28</td><td>高溫，正向分段</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><strong>高溫的代價是真實的。</strong>&nbsp;全程高溫讓每一項的成績都比標準條件慢，估計修正幅度在 5-15% 之間，視動作強度而定。最大的影響是心率的天花板。高溫下心率比正常環境高出 10-15 BPM，相同強度消耗更多。不過我前一週已經做了五天的熱適應，所以這週如此安排，才能「吃的下來」。</p>



<p class="wp-block-paragraph"><strong>負向分段出現了三次。</strong>&nbsp;CFT 後段、Griff、400m 間歇，三次都在疲勞狀態下越跑越快，這是說明配速策略有在運作：前段保守留力，後段再推。在高強度多日週期裡，配速控制比單次表現重要。</p>



<p class="wp-block-paragraph"><strong>力量在疲勞下的保留率比有氧好。</strong>&nbsp;McGhee 的 125 kg 硬舉在第五天仍然完成了 60 次（無裝無護腰），但 Murph 的跑步配速在第三天已經明顯受到影響。這和一般的認知相反，但在短週期（七天）內，無氧力量的下降比有氧能力的下降慢，尤其是當訓練量不到過度訓練門檻的時候。</p>



<p class="wp-block-paragraph"><strong>第七天無論如何要完成。</strong>&nbsp;Brenton 在計畫裡是「收尾」，強度最低，但它做了一件重要的事：讓身體用主動方式結束週期，而不是停下來等待。Bear crawl 的動態活動度刺激和廣跳的輕度爆發力輸出，對恢復的幫助比完全靜止休息好。</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading">七項 Workout 六維體能分析</h2>



<p class="wp-block-paragraph">1 = 低要求 · 5 = 極高要求雷達圖評分表維度排名</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th class="has-text-align-left" data-align="left">Workout</th><th class="has-text-align-left" data-align="left">Endurance</th><th class="has-text-align-left" data-align="left">Stamina</th><th class="has-text-align-left" data-align="left">Strength</th><th class="has-text-align-left" data-align="left">Power</th><th class="has-text-align-left" data-align="left">Speed</th><th class="has-text-align-left" data-align="left">Flexibility</th><th class="has-text-align-left" data-align="left">總分</th></tr></thead><tbody><tr><td>CFT</td><td>4</td><td>5</td><td>3</td><td>4</td><td>4</td><td>2</td><td>22</td></tr><tr><td>Ruck</td><td>5</td><td>4</td><td>2</td><td>1</td><td>1</td><td>1</td><td>14</td></tr><tr><td>Murph</td><td>4</td><td>5</td><td>3</td><td>2</td><td>2</td><td>2</td><td>18</td></tr><tr><td>Griff</td><td>5</td><td>3</td><td>1</td><td>1</td><td>3</td><td>1</td><td>14</td></tr><tr><td>McGhee</td><td>2</td><td>4</td><td>5</td><td>3</td><td>2</td><td>2</td><td>18</td></tr><tr><td>400m×10</td><td>3</td><td>4</td><td>1</td><td>3</td><td>5</td><td>1</td><td>17</td></tr><tr><td>Brenton</td><td>1</td><td>2</td><td>1</td><td>3</td><td>2</td><td>3</td><td>12</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">2026年上半年即將結束，這週的連續七個相對艱難的 workout，多說無益，就當成是一個具有驗證價值的測驗吧。</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.schee.info/2026/06/07/hero-wods/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17638</post-id>
		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>
	</item>
		<item>
		<title>TAKKE.me 和 TAK/ATAK 的台灣實踐</title>
		<link>https://blog.schee.info/2026/05/28/takke-me/</link>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Thu, 28 May 2026 13:41:48 +0000</pubDate>
				<category><![CDATA[government]]></category>
		<category><![CDATA[taiwan]]></category>
		<category><![CDATA[technology]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17636</guid>

					<description><![CDATA[在災害應變和搜救協調的領域裡，「態勢感知」（situational awareness）已經是個聽起來非常正確的詞彙。PowerPoint 簡報的標題會寫著「跨域協調」、「實時資訊共享」、「任務驅動協同」，投影片背景是磨砂藍灰，講者的氣勢十足，最後還會補一句「我們的目標是達成零遺漏的資訊透明」。 然後你走進實際的任務現場，才發現自己掉進了另一個世界。 東西很好，但卡在「人」 這大概就是 TAKKE.me 想要解決的問題。不是軟體本身不夠聰明，也不是地圖不夠詳細，而是：在一個訊號微弱、事情緊急、人員異質、角色混亂的現場，我們怎麼確保隊伍真的在用同一份地圖、傳的是同一套訊息格式、理解的是同一個座標？ TAK/ATAK 確實是個成熟的平台。美軍用了二十多年，不少屬於公共安全領域的組織也都在用，例如消防、搜救、社區安全等。但「全球都在用」不代表「台灣團隊立刻就能用」。中間的鴻溝關鍵不在技術，在於流程、訓練和本土化。 特別值得一提的是，ATAK 的民用版本（CivTAK）在 2020 年被開源釋出，這意味著我們不是被綁在某個付費平台裡。TAK 生態系統包括 Android 的 ATAK、iOS 的 iTAK、Windows 的 WinTAK 等多個版本，而且 TAK Server 這個戰術資訊管理平台也已經開源，可以從官方網站和 GitHub 下載。這代表什麼？你不用依賴商業軟體廠商，可以根據自己的需求去部署、修改、甚至自行維護。 TAKKE.me 的角色就很清楚了：我們不是在賣軟體，而是在賣「怎麼讓開源的 TAK/ATAK 生態在台灣搜救、防災和山野場景真的派上用場」的答案。 我們在做什麼 TAKKE 未來將提供三個層級的東西： 為什麼這很重要 在災害或搜救現場，資訊落差就是生死邊界。當指揮所和現場對於「隊伍在哪」、「風險區域怎麼標」、「要回報什麼」有認知落差時，再好的軟體也救不了。 我們做的是把這些模糊的東西系統化。不只是說「用 ATAK」，而是說「用 ATAK 的時候，台灣的地圖圖層怎麼配、LoRa 和衛星通訊怎麼混搭、隊伍通聯節點怎麼設計、訊息格式怎麼標準化」。 換句話說，我們在做的是把一個開源的、經過美軍驗證的成熟平台，透過系統化的訓練和在地化的流程設計，轉換成台灣搜救和防災社群真的用得到、真正能掌控的工具。沒有商業授權費用的枷鎖，沒有遠程數據回傳的疑慮——因為開源意味著我們可以清楚看到代碼裡在做什麼。 有什麼沒說的 當然，任何推廣性質的介紹都會強調亮點。我們的觀察是：真正的挑戰不在 TAKKE 這層，而在上游——各防災單位、消防機關、山岳協會之間的協調和標準化。我們再努力，如果協調體系本身還是各自為政，軟體就只會淪成「好用的私房工具」，而不是「跨隊協同的共同語言」。 還有一件事：開源不等於自動安全。開源的好處是透明，但這也代表責任轉移到了使用者身上。你得知道自己在做什麼，得確保部署的基礎設施是牢固的。如果防災團隊對 IT 基礎設施一無所知，那光有開源軟體也白搭。 但這也恰好是我們說的「台灣任務的共同作業語言」——這個表述其實暗示了，我們知道這是一個系統問題，不只是工具問題。 值得一試 如果你在搜救、防災或山域安全的領域工作，TAKKE.me 的免費課程是值得花幾個小時吸收的。特別是如果你的組織還在用紙條、無線電頻率簿，或者是試著用 LINE&#8230; <a class="more-link" href="https://blog.schee.info/2026/05/28/takke-me/">Continue reading <span class="screen-reader-text">TAKKE.me 和 TAK/ATAK&#160;的台灣實踐</span> <span class="meta-nav" aria-hidden="true">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">在災害應變和搜救協調的領域裡，「態勢感知」（situational awareness）已經是個聽起來非常正確的詞彙。PowerPoint 簡報的標題會寫著「跨域協調」、「實時資訊共享」、「任務驅動協同」，投影片背景是磨砂藍灰，講者的氣勢十足，最後還會補一句「我們的目標是達成零遺漏的資訊透明」。</p>



<p class="wp-block-paragraph">然後你走進實際的任務現場，才發現自己掉進了另一個世界。</p>



<span id="more-17636"></span>



<h4 class="wp-block-heading">東西很好，但卡在「人」</h4>



<p class="wp-block-paragraph">這大概就是 TAKKE.me 想要解決的問題。不是軟體本身不夠聰明，也不是地圖不夠詳細，而是：在一個訊號微弱、事情緊急、人員異質、角色混亂的現場，我們怎麼確保隊伍真的在用同一份地圖、傳的是同一套訊息格式、理解的是同一個座標？</p>



<p class="wp-block-paragraph">TAK/ATAK 確實是個成熟的平台。美軍用了二十多年，不少屬於公共安全領域的組織也都在用，例如消防、搜救、社區安全等。但「全球都在用」不代表「台灣團隊立刻就能用」。中間的鴻溝關鍵不在技術，在於流程、訓練和本土化。</p>



<p class="wp-block-paragraph">特別值得一提的是，ATAK 的民用版本（CivTAK）在 2020 年被開源釋出，這意味著我們不是被綁在某個付費平台裡。TAK 生態系統包括 Android 的 ATAK、iOS 的 iTAK、Windows 的 WinTAK 等多個版本，而且 TAK Server 這個戰術資訊管理平台也已經開源，可以從官方網站和 GitHub 下載。這代表什麼？你不用依賴商業軟體廠商，可以根據自己的需求去部署、修改、甚至自行維護。</p>



<p class="wp-block-paragraph">TAKKE.me 的角色就很清楚了：我們不是在賣軟體，而是在賣「怎麼讓開源的 TAK/ATAK 生態在台灣搜救、防災和山野場景真的派上用場」的答案。</p>



<h4 class="wp-block-heading">我們在做什麼</h4>



<p class="wp-block-paragraph">TAKKE 未來將提供三個層級的東西：</p>



<ol class="wp-block-list">
<li>首先是免費的線上短片課程——8 部影片，從 ATAK 的介面說起，一路到台灣圖資匯入、座標回報、團隊協同、LoRa 電台整合。這些不是軟體教學影片，而是針對台灣防災任務情景的工作流程導入。長度都控制在 3～8 分鐘，意思就是你可以在出勤前或訓練間隙吸收。</li>



<li>其次是訓練模組。從「快速上手」到「高階指揮節點操作」，階梯式的課程設計。最有趣的是「情境演練設計」和「標準化任務回報」——這才是我們真正的痛點。不是教你怎麼點按鈕，而是教你怎麼設計演練腳本、怎麼定義回報格式讓協同不落差。更重要的是，因為 ATAK-CIV 是開源的，我們可以根據台灣的具體情況去調整、部署，而不是被某家商業廠商的功能限制住。</li>



<li>最後是顧問服務。客製化的部署規劃、圖層整合、通訊流程設計。這一塊特別重要，因為每支隊伍的組織型態、通訊資源、人員背景都不同。有了開源的基礎，我們可以更靈活地為不同的組織設計獨特的解決方案。</li>
</ol>



<h4 class="wp-block-heading">為什麼這很重要</h4>



<p class="wp-block-paragraph">在災害或搜救現場，資訊落差就是生死邊界。當指揮所和現場對於「隊伍在哪」、「風險區域怎麼標」、「要回報什麼」有認知落差時，再好的軟體也救不了。</p>



<p class="wp-block-paragraph">我們做的是把這些模糊的東西系統化。不只是說「用 ATAK」，而是說「用 ATAK 的時候，台灣的地圖圖層怎麼配、LoRa 和衛星通訊怎麼混搭、隊伍通聯節點怎麼設計、訊息格式怎麼標準化」。</p>



<p class="wp-block-paragraph">換句話說，我們在做的是把一個開源的、經過美軍驗證的成熟平台，透過系統化的訓練和在地化的流程設計，轉換成台灣搜救和防災社群真的用得到、真正能掌控的工具。沒有商業授權費用的枷鎖，沒有遠程數據回傳的疑慮——因為開源意味著我們可以清楚看到代碼裡在做什麼。</p>



<h4 class="wp-block-heading">有什麼沒說的</h4>



<p class="wp-block-paragraph">當然，任何推廣性質的介紹都會強調亮點。我們的觀察是：真正的挑戰不在 TAKKE 這層，而在上游——各防災單位、消防機關、山岳協會之間的協調和標準化。我們再努力，如果協調體系本身還是各自為政，軟體就只會淪成「好用的私房工具」，而不是「跨隊協同的共同語言」。</p>



<p class="wp-block-paragraph">還有一件事：開源不等於自動安全。開源的好處是透明，但這也代表責任轉移到了使用者身上。你得知道自己在做什麼，得確保部署的基礎設施是牢固的。如果防災團隊對 IT 基礎設施一無所知，那光有開源軟體也白搭。</p>



<p class="wp-block-paragraph">但這也恰好是我們說的「台灣任務的共同作業語言」——這個表述其實暗示了，我們知道這是一個系統問題，不只是工具問題。</p>



<h4 class="wp-block-heading">值得一試</h4>



<p class="wp-block-paragraph">如果你在搜救、防災或山域安全的領域工作，TAKKE.me 的免費課程是值得花幾個小時吸收的。特別是如果你的組織還在用紙條、無線電頻率簿，或者是試著用 LINE 群組協調現場位置，那更應該看看。</p>



<p class="wp-block-paragraph">而且，既然 ATAK 的民用版已經是開源的，你不用擔心某家商業公司突然停止支援或漲價。這本身就改變了這個決策的風險計算。</p>



<p class="wp-block-paragraph">不是說 ATAK 就能解決所有問題，而是說，至少把台灣情境下「怎麼用開源的 ATAK 生態」的流程搞清楚，並建立起一套屬於我們自己的部署和操作標準，本身就是往前走了一大步。</p>



<p class="wp-block-paragraph"><img src="https://s0.wp.com/wp-content/mu-plugins/wpcom-smileys/twemoji/2/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> 網站&nbsp;<a href="https://alpha.takke.me/">https://alpha.takke.me/</a><a href="https://substack.com/@thschee"></a></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17636</post-id>
		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>
	</item>
		<item>
		<title>[Exercise Notes] Are We Drilling &#8220;Urban Resilience&#8221; or?</title>
		<link>https://blog.schee.info/2026/05/25/exercise-notes-are-we-drilling-urban-resilience-or-just-the-bureaucratic-roll-call/</link>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Mon, 25 May 2026 14:27:29 +0000</pubDate>
				<category><![CDATA[government]]></category>
		<category><![CDATA[taiwan]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17626</guid>

					<description><![CDATA[I recently participated in a local-level urban resilience exercise. On the surface, the terminology was cutting-edge, the slides were polished, and the leadership speeches were impeccable. However, if you strip away the outer veneer of &#8220;resilience&#8221; and &#8220;cross-domain coordination,&#8221; the skeletal structure underneath remains the same old departmental silos and administrative red tape we have&#8230; <a class="more-link" href="https://blog.schee.info/2026/05/25/exercise-notes-are-we-drilling-urban-resilience-or-just-the-bureaucratic-roll-call/">Continue reading <span class="screen-reader-text">[Exercise Notes] Are We Drilling &#8220;Urban Resilience&#8221; or?</span> <span class="meta-nav" aria-hidden="true">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">I recently participated in a local-level <a href="https://www.taipeitimes.com/News/front/archives/2026/03/20/2003854136">urban resilience exercise</a>. On the surface, the terminology was cutting-edge, the slides were polished, and the leadership speeches were impeccable. However, if you strip away the outer veneer of &#8220;resilience&#8221; and &#8220;cross-domain coordination,&#8221; the skeletal structure underneath remains the same old departmental silos and administrative red tape we have been accustomed to for thirty years.</p>



<span id="more-17626"></span>



<p class="wp-block-paragraph">The irony is that this gap does not exist due to a lack of exposure. For years, various local governments in Taiwan have proactively sought international disaster management expertise. For instance, Taichung City&#8217;s disaster rescue and prevention teams have explicitly <a target="_blank" rel="noopener" href="https://www.facebook.com/tccfwebfans/posts/2054469374583970/">undergone professional training in the U.S. FEMA ESF framework</a>, attempting to internalize these modular, function-based concepts. Yet, despite these training initiatives, when it comes to actual implementation during major drills or real-world operations, many municipalities still instinctively default to their traditional, rigid bureaucratic unit groupings.</p>



<p class="wp-block-paragraph">This brings to mind the true operational essence of FEMA’s <a href="https://www.fema.gov/emergency-managers/national-preparedness/frameworks/national-response/emergency-support-functions" target="_blank" rel="noopener">Emergency Support Functions (ESF)</a> framework. Its core logic is to abstract communication and information functions away from individual agencies and establish them as an independent, operational brain.</p>



<p class="wp-block-paragraph">During the exercise, it became evident that Taiwanese local governments excel at certain functional groupings, such as emergency repairs of municipal utilities (water, electricity, gas), maintaining public order, or social welfare sheltering. The common denominator among these successful functions is clear: they fall either under the absolute enforcement power of local authorities (such as the police and environmental cleaning crews) or under highly regulated, state-owned enterprises (such as Taipower and Taiwan Water). A single administrative order from a local chief executive, or long-standing open contracts for emergency repairs, allows for an exceptionally smooth, linear deployment of physical resources.</p>



<p class="wp-block-paragraph">However, the moment the scenario touches upon ESF #2 (Communications), ESF #5 (Information and Planning), and ESF #15 (External Affairs)—the very core of the U.S. ESF mechanism—Taiwan’s system immediately plunges into an awkward vacuum. These three functions involve the exact digital and social networks that represent the weakest links in Taiwan&#8217;s emergency response, areas that cannot be resolved simply through central centralization or local administrative decrees.</p>



<p class="wp-block-paragraph">The exercise exposed three structural blind spots in the field:</p>



<h3 class="wp-block-heading">1. Communications Treated as &#8220;General Logistics&#8221;</h3>



<p class="wp-block-paragraph">In one specific scenario during the drill, a sudden concentration of personnel within a short timeframe caused mobile networks congesting to a grind halt. The field solution? A single mobile communication vehicle from Chunghwa Telecom was rolled in, left isolated to support the site. As a result, when first responders attempted to connect back to their internal agency systems, network speeds remained agonizingly slow, making real-time data transmission almost impossible. Worse still, when the site urgently needed to scale up response capacity by integrating alternative military service (conscription) personnel or external civilian volunteers, it was discovered that internal core systems could not grant access permissions to these &#8220;non-staff&#8221; entities.</p>



<p class="wp-block-paragraph">Ultimately, the exercise floor witnessed a stroke of dark humor: with information systems inaccessible and telecom networks bottlenecked, responders abandoned the high-tech digital dashboards and quietly reverted to paper-based operations. To maintain field coordination, everyone ultimately relied on the LINE chat groups on their personal smartphones.</p>



<p class="wp-block-paragraph">Compared to the straightforward path of power grids—where a blackout prompts the immediate dispatch of a utility truck—the telecommunications market is heavily privatized and commercialized. In the logic of FEMA&#8217;s <a href="https://www.fema.gov/sites/default/files/2020-07/fema_national-response-framework_esf-2-communications.pdf" target="_blank" rel="noopener">ESF #2 (Communications)</a>, communications are tactical infrastructure. It requires cross-carrier roaming coordination, switching between public and private networks, and even international integration with low-Earth orbit (LEO) satellites. This involves complex commercial interests and central ministry regulations; local governments have no jurisdiction over this, and the central government cannot simply command private enterprises to surrender bandwidth. When the information and communication architecture lacks dynamic provisioning of permissions and bandwidth elasticity, high-pressure testing instantly strips away the high-tech veneer, forcing a regression to raw paper and unencrypted commercial messaging apps.</p>



<h3 class="wp-block-heading">2. EMIC Designed for &#8220;Ticketing and Closure&#8221; While Civic Tech Data Drifts in Parallel</h3>



<p class="wp-block-paragraph">Taiwanese local governments are highly efficient at environmental cleanup and shelter placement because those operations follow a rigid, top-down administrative chain of command. Inside the Emergency Operations Center (EOC), personnel fluidly type away at the EMIC (Emergency Management Information System): village chiefs report incidents, the fire department inputs them, the system dispatches a ticket to the public works bureau, the public works bureau clears the fallen tree, and the ticket is closed. The essence of this system is administrative document workflow management, used primarily for post-incident audits, tracking accountability, and verifying &#8220;closure.&#8221;</p>



<p class="wp-block-paragraph">True resilience, however, requires the concept of FEMA’s <a href="https://www.fema.gov/sites/default/files/2020-07/fema_national-response-framework_esf-5-information-planning.pdf" target="_blank" rel="noopener">ESF #5 (Information and Planning)</a>—extracting fragmented data to conduct big data strategic assessments and generate a standard <a href="https://www.fema.gov/emergency-managers/nims" target="_blank" rel="noopener">Common Operating Picture (COP)</a>.</p>



<p class="wp-block-paragraph">We saw the raw power of alternative data pipelines during last year&#8217;s Guangfu Flood catastrophe. As hundreds of thousands of <a href="https://www.theguardian.com/world/2025/oct/02/thousands-descend-taiwan-town-clean-up-after-devastating-flood--gym-bros-monks-retirees">digital &#8220;volunteers&#8221; suddenly mobilized online</a>, dozens of crowdsourced <a href="https://g0v.hackmd.io/@kiang/Fata-an_BarrierLake-casestudies">disaster response platforms and makeshift dashboards sprouted overnight</a>. Iterating rapidly based on immediate field feedback, these civic platforms utilized various algorithmic filters to aggregate, sort, and map massive volumes of citizen-reported data in near real-time.</p>



<p class="wp-block-paragraph">Yet, as documented in international studies like the UN OCHA&#8217;s <a target="_blank" rel="noopener" href="https://www.unocha.org/publications/report/world/disaster-relief-20-future-information-sharing-humanitarian-emergencies"><em>Disaster Relief 2.0</em> report</a>, this kind of disconnect between digital humanitarianism and traditional command structures is a well-known systemic vulnerability. These civic systems and spontaneous instances of &#8220;information creation&#8221; are typically sporadic and remain entirely decoupled from the official public sector response apparatus. The bureaucracy clings to a permission-locked, bandwidth-constrained EMIC system, while the civilian sphere operates a parallel track of open-source maps and reporting tools. The two cannot interface at the data flow level. The information systems of various bureaus (water resources, transportation, fire) operate like feudal fiefdoms separated by administrative firewalls. Meanwhile, data collected spontaneously by the public cannot penetrate the official decision-making brain. Because these decentralized assets cannot be co-opted or centralized, the two information pipelines run in parallel, entirely isolated from one another. This deprives the overall disaster assessment of a holistic, global view. When the brain is starved of information and the limbs are disconnected, moving faster is simply futile.</p>



<h3 class="wp-block-heading">3. Crisis Communication Reduced to &#8220;Leadership PR&#8221;</h3>



<p class="wp-block-paragraph">Another fluidly operating component of Taiwan&#8217;s EOC is the &#8220;Public Order and Traffic Control Group.&#8221; Under the command of local leaders, the police force executes road closures, area cordons, and disaster zone security with high administrative enforcement power.</p>



<p class="wp-block-paragraph">In sharp contrast, the role of the &#8220;Press Release Group&#8221; during the drill remained confined to traditional media public relations—issuing press releases, organizing press conferences, and managing the leader&#8217;s public image. This runs entirely counter to the purpose of establishing a Joint Information Center (JIC) under FEMA&#8217;s <a href="https://www.fema.gov/sites/default/files/2020-07/fema_national-response-framework_esf-15-external-affairs.pdf" target="_blank" rel="noopener">ESF #15 (External Affairs)</a>. The core of a JIC is information equity and comprehensive coverage.</p>



<p class="wp-block-paragraph">In today&#8217;s fragmented information ecosystem, when misinformation spreads uncontrollably across LINE, TikTok, or various social platforms, or when migrant workers are stranded due to language barriers, crisis communication expands far beyond a local news department&#8217;s capacity to issue statements. Research from organizations like the U.S. National Academies on <a href="https://nap.nationalacademies.org/catalog/24935/public-response-to-alerts-and-warnings-using-social-media-and" target="_blank" rel="noopener">Public Response to Alerts and Warnings Using Social Media</a> highlights how decentralized media ecosystems render top-down, centralized information control obsolete. This modern crisis landscape cannot be solved by a top-down, centralized command over the internet. It demands a joint information framework capable of real-time coordination with multinational tech platforms, horizontally blocking political interference in rescue operations, and ensuring that vulnerable groups receive multilingual, accessible emergency alerts simultaneously. This is precisely the domain where the some of Taiwanese bureaucratic systems are most inexperienced and lacks both legal and governance toolsets.</p>



<h3 class="wp-block-heading">Conclusion: Digital Transformation of Institutions Must Be Structural</h3>



<p class="wp-block-paragraph">&#8220;Urban Resilience&#8221; cannot be performed through a montage of trendy buzzwords.</p>



<p class="wp-block-paragraph">As this exercise demonstrates, as long as an operation involves the linear deployment of physical resources under a &#8220;Command &amp; Control&#8221; model—such as utility repairs or law enforcement sheltering—Taiwan&#8217;s simulations run flawlessly. But the moment the system encounters the non-linear flows of &#8220;Coordination &amp; Integration&#8221;—such as telecom bottlenecks, rigid permission barriers for conscripted support, parallel civilian data pipelines, and multi-channel crisis communication—it suffers immediate paralysis.</p>



<p class="wp-block-paragraph">The fact that cities like Taichung have undergone ESF training shows that the problem is not a lack of conceptual knowledge, but institutional inertia. If our response mechanism remains permanently defined by &#8220;Who&#8221; (which department you belong to dictates what you do) rather than &#8220;What&#8221; (what function the field requires dictates how we cross boundaries to reorganize resources), then when a true Black Swan event arrives, our prized EOCs will fail. Even with telecom trucks rolled in and alternative service personnel deployed, the system will devolve into a collection of individuals using ballpoint pens on paper pads and sending photos via LINE, operating a sophisticated bureaucratic machine where official and civilian information ecosystems continue to drift apart in parallel isolation.</p>



<p class="wp-block-paragraph">I have seen huge progresses over this years, but Taiwan’s dedicated disaster prevention and response system still requires a genuine transformation of its organizational architecture and data flows. It is a painful process because it demands dismantling departmental firewalls and official-civilian barriers. Yet, it remains the only viable path toward true resilience.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17626</post-id>
		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>
	</item>
		<item>
		<title>《臺灣災害管理參考手冊》（Taiwan Disaster Management Reference Handbook）</title>
		<link>https://blog.schee.info/2026/05/22/tw-disaster-mgmt-ref-book/</link>
		
		<dc:creator><![CDATA[T.H.]]></dc:creator>
		<pubDate>Fri, 22 May 2026 14:29:33 +0000</pubDate>
				<category><![CDATA[government]]></category>
		<category><![CDATA[taiwan]]></category>
		<guid isPermaLink="false">http://blog.schee.info/?p=17613</guid>

					<description><![CDATA[這次 CFE-DM 在 2026 年 4 月端出的這本《臺灣災害管理參考手冊》（Taiwan Disaster Management Reference Handbook）。這是一份非常少見、從美軍視角出發，把臺灣整個防災、民防到全社會韌性骨架一次拆解的參考手冊。筆者曾經接受此單位委託的學術研究人員針對若干事務進行訪談。這本參考手冊的付梓對台灣來說也是一件美事。 對於長期有關注數位政府、開放資料和防災事務的人來說，這本手冊很值得讀。我把它的核心結構和背後的「美方視角」幫大家快篩成幾大重點。 CFE-DM 是什麼來頭？ 很多人看到這個單位會覺得神祕，其實它的全名是災害管理與人道救援卓越中心（Center for Excellence in Disaster Management &#38; Humanitarian Assistance）。 快篩摘要：臺灣災害管理體系的三個骨幹與觀察 手冊把臺灣定位為一個「高脆弱性但高韌性」的實驗場。手冊的核心觀察有以下幾個： 1. 九二一後的「單一災害主管制」（Single-Hazard Approach） 臺灣沒有一個像美國 FEMA 那樣包山包海的單一國家防災總署。手冊裡點出，臺灣是典型的依災害類型分權： 2. 從天然災害到「全社會防衛韌性」的轉型 這是這份 2026 年報告最關鍵的時代背景。手冊特別著墨臺灣從 2024 年開始推動的「全社會防衛韌性委員會」。 3. 臺灣的國際孤立與台美邊界突破 因為非聯合國成員，臺灣長期被排除在國際傳統救援協調機制（如聯合國 OCHA）之外。但手冊點出一個突破點： 後記： 這份手冊是一面很好的鏡子。美方把臺灣的防災法律、部會權責、人口高齡化的社會脆弱性，甚至到台美合作的執行細節全串了起來。想從西方視角理解臺灣如何在天然災害與地緣政治的雙重壓力下練就這身「韌性肌肉」的對外敘事脈絡？這算是一個好的起點。此外，其內容的豐富程度，也適合本地研究者和實踐者作為案頭大書閱讀。]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">這次 <a href="https://www.cfe-dmha.org/">CFE-DM</a> 在 2026 年 4 月端出的這本《臺灣災害管理參考手冊》（<em><a href="https://www.cfe-dmha.org/LinkClick.aspx?fileticket=FPHgeL25yoo%3d&amp;portalid=0">Taiwan Disaster Management Reference Handbook</a></em>）。這是一份非常少見、從美軍視角出發，把臺灣整個防災、民防到全社會韌性骨架一次拆解的參考手冊。筆者曾經接受此單位委託的學術研究人員針對若干事務進行訪談。這本參考手冊的付梓對台灣來說也是一件美事。</p>



<p class="wp-block-paragraph">對於長期有關注數位政府、開放資料和防災事務的人來說，這本手冊很值得讀。我把它的核心結構和背後的「美方視角」幫大家快篩成幾大重點。</p>



<span id="more-17613"></span>



<h3 class="wp-block-heading">CFE-DM 是什麼來頭？</h3>



<p class="wp-block-paragraph">很多人看到這個單位會覺得神祕，其實它的全名是災害管理與人道救援卓越中心（Center for Excellence in Disaster Management &amp; Humanitarian Assistance）。</p>



<ul class="wp-block-list">
<li>本質是美軍的智庫與協調節點：它直屬於美國國防部（DoD），但編制上是直接向美國印太司令部（USINDOPACOM）匯報，基地就在夏威夷珍珠港。</li>



<li>核心功能：這個單位不是去第一線救災的，而是美軍用來扮演「民、軍、國際組織」之間黏著劑的專家小組。他們在做的事情，就是協助美軍和盟友在印太地區發生危機或大災難時，搭起一條互通的溝通橋梁與行動框架。這本手冊，筆者認為就是拿來給美軍和國際救援人員看的「臺灣防災攻略」。</li>
</ul>



<h3 class="wp-block-heading">快篩摘要：臺灣災害管理體系的三個骨幹與觀察</h3>



<p class="wp-block-paragraph">手冊把臺灣定位為一個「高脆弱性但高韌性」的實驗場。手冊的核心觀察有以下幾個：</p>



<h4 class="wp-block-heading">1. 九二一後的「單一災害主管制」（Single-Hazard Approach）</h4>



<p class="wp-block-paragraph">臺灣沒有一個像美國 FEMA 那樣包山包海的單一國家防災總署。手冊裡點出，臺灣是典型的依災害類型分權：</p>



<ul class="wp-block-list">
<li>內政部消防署（NFA）：扛起最核心的風災、震災。手冊特別提到南投的消防訓練中心，在 2025 年擴建後，已經是亞洲最大、世界第三大的科技防災基地。</li>



<li>各部會分工：例如水災歸經濟部、土石流歸農業部、毒化災歸環境部。</li>



<li>運作邏輯：走中央、縣市、鄉鎮三級制的「地方第一線、中央調資源」模式。</li>
</ul>



<h4 class="wp-block-heading">2. 從天然災害到「全社會防衛韌性」的轉型</h4>



<p class="wp-block-paragraph">這是這份 2026 年報告最關鍵的時代背景。手冊特別著墨臺灣從 2024 年開始推動的「全社會防衛韌性委員會」。</p>



<ul class="wp-block-list">
<li>這不再只是傳統的天然災害演習，而是把基礎設施防護（電力、水務、通訊）、民間物資供應鏈、以及「軍民協調」全部框在一起。</li>



<li>報告有注意到一個重要的典範轉移（Paradigm Shift）：臺灣近年開始刻意減少「排練好的劇本演練」，轉向無腳本、更具實戰性的抗災整備。這部份的描述對於本地的實務工作者而言，參考價值不能說很多。</li>
</ul>



<h4 class="wp-block-heading">3. 臺灣的國際孤立與台美邊界突破</h4>



<p class="wp-block-paragraph">因為非聯合國成員，臺灣長期被排除在國際傳統救援協調機制（如聯合國 OCHA）之外。但手冊點出一個突破點：</p>



<ul class="wp-block-list">
<li>台美機制的實體化：2023 年台美簽署了《人道救援與災害啟動合作備忘錄》，而這本手冊的出版單位 CFE-DM，正是美方的實體執行窗口，對口的就是臺灣的國家災害防救科技中心（NCDR）。</li>



<li>臺灣透過 GCTF（全球合作暨訓練架構）和自組符合國際標準的搜救隊（SAR），正在用技術與實務經驗，實質參與全球的防災網絡。</li>
</ul>



<p class="wp-block-paragraph"><strong>後記：</strong> 這份手冊是一面很好的鏡子。美方把臺灣的防災法律、部會權責、人口高齡化的社會脆弱性，甚至到台美合作的執行細節全串了起來。想從西方視角理解臺灣如何在天然災害與地緣政治的雙重壓力下練就這身「韌性肌肉」的對外敘事脈絡？這算是一個好的起點。此外，其內容的豐富程度，也適合本地研究者和實踐者作為案頭大書閱讀。</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">17613</post-id>
		<media:content url="https://0.gravatar.com/avatar/39089ed95d7b4e39d0e2e673c3bfeb3bad67c5c613c3fc4cd795ee21d1ff71fd?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">schee</media:title>
		</media:content>
	</item>
	</channel>
</rss>
