Some Metadata could be derived from the scraps we have in therion.
That will not be 100% accurate, of course, but for ecample if a
centerline shot crosses some pit, this could provide useful routing
information (because we can infer that we need rope and climbing gear
for this leg). Or from
On 2021-11-28 21:33 +, Tarquin Wilton-Jones via Therion wrote:
> > I implemented such functionality (not the visualization) a while ago
> > as a little exercise in Python. If you know how to run a Python
> > script, then you might find this useful.
>
> Awesome!
That is nifty. I've wanted
Hi Thomas,
thank you for the snippet, I succesfully tried it :)
For my convinience, I wrote a small wrapper to ease the call:
- It references my fixed aven file
- It has parameters 1 and 2 reference the respective stations
--snip shortestPath.py--
#!/usr/bin/python
#
# Wrapperskript
I think, when we would have some option to compile the shortest path
between two statoins, this could easily leveraged to the multi-station
approach (I would even do that manually if its not easily to be
automated).
Further wishes could be to be able to specify constraints as options, so
for
This was discussed in 2008 in Therion circles.
https://www.mail-archive.com/therion@speleo.sk/msg02037.html
To be really useful, the user should be able to specify multiple stations,
with the algorithm finding the shortest centreline distance along the
centreline network that passes through all of
