Will extend the Jupyter Notebook to go through the whole process of the path planning and showing all calculation results inside the notebook.
The result WGS84 points in the right order should be exportable in the end:
Creating a helper function to export the longitude/latitude tuples to file in a selected path should be made.
The base process is already inside extract_multilinestrings.py in the helpers folder.
Well, my project is kinda stalled cause I can't find a lot of time to finish it (at the moment).
The README needs an update to give a short introduction about my project and how to use everything to create paths with the Jupyter Notebook.
Will come soon...
The resulting paths (and their asociated STC tiles) do overlap in different areas but not all the time.
This might be a bug of non-matching tile corner WGS84 coordinates.
My guess would be the shapely operations of within or intersect don't work properly if the edges don't overlap exactly.
The used nprange func to calc the edge lengths of all the different tile sizes might not be the most exact variant... Maybe find a proper geospacial func to define a edge length (from meter) to wgs84 coords.
Will see when I got time for fixing.
It works most of the time so this is low priority.
In the second step, after I created a grid of different tile sizes, the number of tiles per segment should be defined by the maximum path length setting in the settings file.
This calculation is still missing in the start_path_generation.py file.
If the setting of the max path length is 0 there should not be any restriction at all and DARP should never get called.