azaion/satellite-provider
1
0
Fork 0
mirror of https://github.com/azaion/satellite-provider.git synced 2026-04-22 09:26:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

add route description

Browse Source
This commit is contained in:
Anton Martynenko
2025-11-01 15:25:44 +01:00
parent f13f3eea6b
commit 96ab109277
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
goal.md
+11
View File
@@ -36,6 +36,17 @@ We should have API endpoint POST /api/satellite/request which will do the follow
-- Create file region_{id}_summary.txt where write a summary of how many tiles were downloaded, how many we reused from cache, time taken and othe usefull summary information
- API endpoint GET /api/satellite/region/{id} should return path to file region_{id}_ready.csv when all tiles are ready and the file is created, otherwise it should return response indicating that download is in progress.
4. Plan route, split it into overlapping regions
We should have API endpoint POST /api/satellite/route which will do the following:
- Create a route on the map defined by an array of points where the first point is "start" and the last point is "end" of the route
- for each node in the route the service should calculate coordinates of intermediate points such as:
-- If the distance between node start and node end is less than 200 meters, no intermediate points needed
-- If the distance between node start and node end is more than 200 meters, the service should create intermediate points on the same line as the line defined by node start and node end
-- Intermidiate points should have equal distance between each other and node start and node end but not more than 200 meters
-- Each point and intermediate point on the route will define a center of a region on maps
- We should store routes in the database, each route should have unique ID
- We should have API endpoint GET /api/satellite/route/{id} which will return information of the route including intermidiate points
The service will be running in docker container, we also need to run postgres database also in docker container. I also want to use integration tests as a separate app running as a console app in a separate docker container. We would need two docker compose files:
- docker-compose.svc.yml - will run the service and its dependencies
- docker-compose.tests.yml - will run the integration tests, the service and its dependencies