Started on the report

This commit is contained in:
Trygve 2024-04-10 12:32:22 +02:00
parent e219407c82
commit 596bc8c4b1
2 changed files with 10 additions and 7 deletions

View File

@ -1,14 +1,17 @@
## Group: Trygve and Esther ## Group: Trygve and Esther
# What problem will you be working on in your programming project? # Functionality
We will be implementing a marching squares algorithm to produce a contour map from a heightmap image file. Our program usees the marching squares algorithm to create a vector contour map from a raster heightmap.
The cli interface is `gdal_contour [OPTIONS] <src_filename> <dst_filename>` with these options:
```
-i <elevation intervall> Interval between contours
-f <format> Fileformat to output
```
# data structure and input/output
![](ER_diagram.svg)
# Responsibilities: # Responsibilities:
Esther will create the algorithm itself with multitreading. This will essentially be a function that takes a grid of pixels as input and returns a similar grid of cells. Esther will create the algorithm itself with multitreading. This will essentially be a function that takes a grid of pixels as input and returns a similar grid of cells.
Trygve will take care of reading in the tiff file into our own datastructure and creating a vector image from the output of the algorithm. Trygve will take care of reading in the tiff file into our own datastructure and creating a vector image from the output of the algorithm.
# How do you plan to make it easily verifiable that your objectives are reached? # How do you plan to make it easily verifiable that your objectives are reached?
We can compare against the `gdal_contour` cli program which is a implementation widely used in other software. We can compare speed, memory usage and the result itself. We can compare against the `gdal_contour` cli program which is a implementation widely used in other software. We can compare speed, memory usage and the result itself.
Each step in our program also produces a output which we can be worked on and evaluated independently. Each step in our program also produces a output which we can be worked on and evaluated independently.
# ER diagram:
![](ER_diagram.svg)

Binary file not shown.