Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get path as a geometry #2508

Open
latot opened this issue May 4, 2023 · 1 comment
Open

Get path as a geometry #2508

latot opened this issue May 4, 2023 · 1 comment

Comments

@latot
Copy link

latot commented May 4, 2023

Hi all!

Problem
With pgrouting, we can get the costs and paths of practically every node, this is great, but there is no easy way to transform the path, to the traveled geometry, at least in the Cost Matrix.

Improvement
I think would be great, if the functions has a new param, where we set it to true they will return a new geometry column with the traveled path.

Actually, I think can be applied in some ways, like this:

In the MatrixCost, add a new column with the full traveled path in a geometry.
While in the one2one nodes, is possible add a new geom column where is has the traveled path of the seq. Due to this, we would have n-1 linestrings, and one empty (similar to what happens with agg_cost).

Thx!

@latot
Copy link
Author

latot commented May 9, 2023

Oks, I tested a little this, can be... very good and very bad, specially because for many2many cases, the geoms can use a lot of space on disk, really.. eats all my free disk space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant