Program Options: other options about osm2pgrouting HOT 3 OPEN

refers to #41 also

from osm2pgrouting.

It would be nice if the multilevel preprocessing, were available for other networks in pgRouting. So one idea would be to implement it in a way that it could be used for either. Some ideas to consider are:

1. implement it in pgrouting and call it from osm2pgrouting
2. implement it as a generic algorithm that could be wrapped into either or both products
   Since multilevel routing is not implemented in pgRouting yet, it might be hard to know what is best, so I leave this comment for consideration in this discussion.

from osm2pgrouting.

Things are related, yes, but the idea of osm2pgrouting is from OSM, store
into the database the data that is needed to do routing.
How the pre-processing is done for the levels will be done on pgRouting.

So the first Q that arises is what is:

1. What do we consider the basic data useful to make levels.
   After answering the previous Q then we have the next Q:
2. How many levels can we have based on OSM information.
   Also we have this other Q:
3. how are we going to let the user define levels depending on his
   particular needs

On Fri, Oct 16, 2015 at 8:40 AM, Stephen Woodbridge <
[email protected]> wrote:

It would be nice if the multilevel preprocessing, were available for other
networks in pgRouting. So one idea would be to implement it in a way that
it could be used for either. Some ideas to consider are:

1. implement it in pgrouting and call it from osm2pgrouting
2. implement it as a generic algorithm that could be wrapped into either
   or both products
   Since multilevel routing is not implemented in pgRouting yet, it might be
   hard to know what is best, so I leave this comment for consideration in
   this discussion.

—
Reply to this email directly or view it on GitHub
#55 (comment)
.

Georepublic UG & Georepublic Japan
Mail: [email protected]: https://georepublic.info

from osm2pgrouting.