My current understanding is that edge weights can not be made time-dependent. Is this correct?
You can’t do time-dependent routing atm, yes: https://github.com/graphhopper/graphhopper/issues/1494
You can do routing with changing weights based on a fixed time (list of weights per edge) or similar.
ah, so the use of lists of weights per edge sounds interesting. Do you have a link to a use case?
No, but this should not be hard via an array ala weight[edgeId][timeSlice].
I would use DataAccess instead of an array to grow unlimited and have it stored on disc. Additional care needs to be taken for virtual edges but then it should work.
thank you for your answer. I am interested in this topic as well.
May you please provide more detail about your solution?
How can I use a time dependent weighting?