Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\AppServ\www\wp-includes\functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\AppServ\www\wp-includes\functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the top-10 domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\AppServ\www\wp-includes\functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the jetpack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\AppServ\www\wp-includes\functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-wp-migration domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\AppServ\www\wp-includes\functions.php on line 6114
天兔颱風台南市加強整備及大力清淤 無重大淹水發生 - 99k新聞網

天兔颱風台南市加強整備及大力清淤 無重大淹水發生

發稿單位:水利局

發稿時間:113年11月16日19:10

 

今年第25號天兔颱風在今(16)日上午11時減弱為熱帶性低氣壓,本次颱風市長黃偉哲於15日上午即啟動三級應變中心開設,為因應強降雨影響並指示水利局於今(16)日上午6時加強三級應變開設進駐水情中心守視天氣狀況及應變,即時掌握排水狀況及處置可能的積淹水狀況,此次颱風期間本市並無重大淹水情事發生。

 

水利局說明,今(16)日0時至上午11時,本市最大累積雨量為安平區148.5毫米、最大時雨量為安平區52.5毫米、最大10分鐘雨量為南區、仁德區13毫米;全市抽水站計26站共62台啟動抽水,總抽水量約110萬噸,其中易受強降雨產生積淹水地區如仁德區民安路二段與德糖路口、東區自由路與東門路、南區明興路及安南區淵東里、溪心里及淵中里部分低漥地區等,在德糖路T幹線雨水下水道、東區文忠調節池、南區停20(喜灣)抽水站及海東D2(淵中)抽水站工程,於今年陸續完工已發揮效用無積淹水情形。此外,小東及林森車行地下道亦無積淹水正常通行,全市皆未有重大淹水情事發生。

 

另報載有關內政部劉部長世芳特提到台南安平區淹水案,台南市政府極為重視且落實各排水路清淤維護工作,截至113年10月底區域排水已清疏約500公里、9.1萬立方公尺;雨水下水道箱涵約120公里、2.6萬立方公尺,合計長度620公里、總清淤量達11.7萬立方公尺,清淤數量是全國數一數二,黃市長偉哲為加強清淤再動用第二預備金2,000萬,確保汛期排水路順暢。 此次颱風僅有安平區漁光路81號以南後抽水站1處短暫路面積水,雨小即退,積水時間大約半小時左右,經查安平區的安平雨量站最大10分鐘11.5mm、1小時52.5mm,3小時雨量為116mm;短延時強降雨已超過道路側溝的設計標準,導致道路側溝無法容納而產生路面積水狀況,因淹水感測器設置於低窪處,實際路面積淹水不到10公分,且在半小時內立即退水,該位置也並非市中心主要道路也沒有影響到交通,針對每次降雨事件造成積淹水地區,除平時加強道路側溝清理外,台南市相關單位正全力改善。

  • IMG_1341
  • IMG_1340
臉書留言

(這個頁面共進入 1 次, 今天進入 1 次)