DESIGN AND IMPLEMENTATION OF A WEATHER DATA ACQUISITION SYSTEM FOR TEMPERATURE HUMIDITY INDEX CALCULATION

The limited number of Automatic Weather Stations (AWS) available makes it difficult to observe the Temperature Humidity Index (THI). BMKG, as the agency managing AWS reading data, only provides daily data in the form of statistical information on its website. This poses a challenge for observing...

全面介紹

Saved in:
書目詳細資料
主要作者: Haryo Pramudio Bagus A, Bambang
格式: Final Project
語言:Indonesia
在線閱讀:https://digilib.itb.ac.id/gdl/view/86195
標簽: 添加標簽
沒有標簽, 成為第一個標記此記錄!
機構: Institut Teknologi Bandung
語言: Indonesia
實物特徵
總結:The limited number of Automatic Weather Stations (AWS) available makes it difficult to observe the Temperature Humidity Index (THI). BMKG, as the agency managing AWS reading data, only provides daily data in the form of statistical information on its website. This poses a challenge for observing THI because THI observation requires historical data. Another limitation is that micro-scale THI observation cannot use macro-scale satellite imagery. These challenges highlight the need for a THI data acquisition system. To address these issues, a THI data acquisition system is needed to provide micro-scale historical weather data. An AWS system is proposed as a solution for collecting temperature and humidity data, with a web application to provide data to users. The Internet of Things (IoT) concept is employed in the system, utilizing the internet to transmit data from AWS to storage. LoRa technology is used as the medium for communication between the data acquisition components, and MQTT technology is used for transmission from the data acquisition tools to the cloud. System testing is conducted using a black- box method and includes 4 testing stages: unit testing, integration testing, system testing, and acceptance testing. Test results indicate that the system can perform data acquisition, storage, and provision to clients. The designed system has a latency of 816 milliseconds for transmission from endpoint to gateway, 90 milliseconds for data processing at the gateway, and 367 milliseconds for transmission from the gateway to the backend service. Data becomes available on the backend service after 1273 milliseconds from the reading time.