This is an implementation of the Quad-Tree data structure in C++.
[[TOC]]
The project includes a meson.build file for building the project using Meson. Experienced users may modify this file or use it as reference for alternate build profiles. However, the following requirements and instructions are only intended for the original build profile.
Execute the following commands to setup a ./build directory and compile the program.
meson setup build
meson compile -C build
The generated ./build directory contains an Index binary for executing the program.
For easy of use, link the binary to the root directory.
ln -s build/Index .
Optional - Users may link the compile_commands.json file to the root as well for linting purposes.
ln -s build/compile_commands.json .
The project configuration lies in include/config.hpp. The options are explained in the comments.
constexpr bool BULKLOAD = true; // Set it to true if bulk loading the data set, and false otherwise.
constexpr bool EVAL = true; // Set it to true for execute the operation file.
constexpr bool DEBUG = false; // Set it to true for debugging query results.
constexpr bool SNAPSHOT = false; // Set it to true for creating a snapshot of the index.
constexpr unsigned int PAGECAP = 204; // Set the page capacity here.
constexpr unsigned long BLL = 1e7; // Short for bulk loading limit.Execute the program with two command line arguments, first is the path to the data file and second is the path to the operation file.
./Index <Path to the data file> <Path to the operation file>
Execute the program with a single command line argument, i.e. the path to the operation file.
./Index <Path to the operation file>
The data file is used for bulk loading the index and must contain a record on each line. A record consists of an integer for the id, and two floats for the point.
<id> <x-axis coordinate> <y-axis coordinate>
Note: Users may need to modify the program to supply any metadata in the subsequent fields to satisfy their usecase. The original program only supports the simplest case of spatial indexing.
The operation file must contain an operation description on each line. Each operation entry begins with a character to distinguish the operation followed by operation specific description. The format of all three is detailed below.
- Insertion (i): Requires a point (two floats) and an id (integer).
i <x-axis coordinate> <y-axis coordinate> <id>
- k-NN query (k): Requires a point (two floats) and the value of k (integer).
k <x-axis coordinate> <y-axis coordinate> <k>
- Range query (r): Requires an MBR (four floats) and size (float; size is only used for logging purposes when evaluating the index, and denotes the ratio of each side of the MBR and the data set extent).
r <lower x-axis coordinate> <lower y-axis coordinate> <higher x-axis coordinate> <higher y-axis coordinate> <size>
- Log (l): Requires no additional information. Used to output the performance measurements.
l
- Reset (z): Requires no additional information. Used to reset the performance measurements.
z
After each execution, the program outputs a log.txt file detailing all statistics of the previous run.
When SNAPSHOT is enabled in the config file, the program outputs Index.csv. Run the python script drawIndex.py to create the snapshot Index.png to get an overview of index partitions.
python drawIndex.py
The script may require the Plotly library to be installed.
The example.sh setups the build directory, compiles the program and executes the program for the sample files in the Example directory.
chmod u+x example.sh
./example.sh
Make sure to enable BULKLOAD in the config file before executing this script.
The program runs fine for benchmarking purposes, but may undergo refactoring to improve overall readability and code aesthetics. Users are advised to clone the main branch for the best version of the program. Follow this link to access the repository.
Name: Moin Hussain Moti
Email: mhmoti@connect.ust.hk