Sorry, autocorrect modified my last email. To enable, do: `cmake -DDEBUG_GEOMETRY=ON ..`
daniel > On Nov 11, 2015, at 5:22 PM, Sotorrio, Pedro <[email protected]> wrote: > > Thanks, Daniel! > > —Pedro > > From: Daniel Patterson <[email protected] <mailto:[email protected]>> > Reply-To: Mailing list to discuss Project OSRM <[email protected] > <mailto:[email protected]>> > Date: Wednesday, November 11, 2015 at 2:16 PM > To: Mailing list to discuss Project OSRM <[email protected] > <mailto:[email protected]>> > Subject: Re: [OSRM-talk] Extended graph output file > > Pedro, > > There is some work-in-progress on the `edge_segment_lookup` branch that can > give you some insight. If you enable the `-DDEBUG_GEOMETRY` flag with > `make`, then `osrm-extract` and `osrm-prepare` can be instructed (with a new > command-line parameter) to dump out some geometry information in GeoJSON > format. > > `osrm-extract` will dump out turn and stop-sign penalties with coordinates > and bearings. > `osrm-prepare` will dump out individual segment weights (deciseconds) and > speed values used in the final routing graph. > > It's not super-easy to use, but it gives complete insight into the routing > graph in a visual form. You can load the files into QGIS for visualization. > > daniel > > >> On Nov 11, 2015, at 4:32 PM, Sotorrio, Pedro <[email protected] >> <mailto:[email protected]>> wrote: >> >> Thanks a lot, Daniel! >> >> —Pedro >> >> From: Daniel Hofmann <[email protected] <mailto:[email protected]>> >> Reply-To: Mailing list to discuss Project OSRM <[email protected] >> <mailto:[email protected]>> >> Date: Wednesday, November 11, 2015 at 1:26 PM >> To: Mailing list to discuss Project OSRM <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [OSRM-talk] Extended graph output file >> >> The edge-expanded graph already gets written to disk; this was introduced in >> the following commit: >> >> https://github.com/Project-OSRM/osrm-backend/commit/e45656e5bfb0b61a2859f0c754e66322996f1640 >> >> <https://github.com/Project-OSRM/osrm-backend/commit/e45656e5bfb0b61a2859f0c754e66322996f1640> >> >> which is not yet in the latest release, so you have to build from the >> develop branch. >> >> >> If you search for ebg you will see related files: >> >> https://github.com/Project-OSRM/osrm-backend/search?utf8=%E2%9C%93&q=ebg >> <https://github.com/Project-OSRM/osrm-backend/search?utf8=%E2%9C%93&q=ebg> >> >> >> Word of caution: the serialization in OSRM is done by just dumping internal >> datastructures in binary format. >> This is neither a portable between operating systems, compilers or even >> standard libraries, nor a stable format, and in particular not intended to >> be read from other programs. >> You would have to get the data structure layout right, in order to make use >> of the ebg file from other programs. >> >> On Wed, Nov 11, 2015 at 4:15 PM, Sotorrio, Pedro <[email protected] >> <mailto:[email protected]>> wrote: >>> Hello, >>> >>> I’m new in OSRM but my understanding is that the graph output file in OSRM >>> is a binary file, correct? >>> >>> Is there a way to write out the edged expanded graph (with turns) to a >>> readable file? >>> >>> Thanks a lot in advance, >>> >>> Pedro >>> >>> >>> >>> _______________________________________________ >>> OSRM-talk mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.openstreetmap.org/listinfo/osrm-talk >>> <https://lists.openstreetmap.org/listinfo/osrm-talk> >>> >> >> _______________________________________________ >> OSRM-talk mailing list >> [email protected] <mailto:[email protected]> >> https://lists.openstreetmap.org/listinfo/osrm-talk >> <https://lists.openstreetmap.org/listinfo/osrm-talk> > > _______________________________________________ > OSRM-talk mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/osrm-talk
_______________________________________________ OSRM-talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/osrm-talk
