Abstract
Spatial database applications for satellite remote sensing data which usually as big data need a data structure that allows spatial query performed at high speed. Selection of storage engine types in MySQL database affects of performances of a spatial query. In this paper, we analyzed performance of a spatial query on various MySQL storage engine types. The test data are radiances of several bands of MODIS sensor on the satellite AQUA/TERRA. Spatial databases are created with selecting storage engine that supports a column of type geometry. To get a good metric performance i.e. query run time, storage engines must support spatial index. A store procedure was created to provide query run time of a spatial query. The query run time consists of three criteria, i.e. execution, transfer and total time in second. The test results showed that MyISAM storage engine type generally provides faster spatial query than InnoDB storage engine type. We found that a large delay in the transfer speed causes the query run total on InnoDB longer than MyISAM. Developer has developed the ARIA storage engine on MariaDB server that has advantages than MyISAM and supports features such as the InnoDB transactional.
Published Version
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call