It doesn't look like PhantomNode's forward_node_id and reverse_node_id are
indexes into InternalDataFacade's m_coordinate_list (and hence the
m_osmnodeid_list I created). When I look up forward_node_id/reverse_node_id
I get OSM nodes that are far away from the query point.
(PhantomNode.name_id and
Kerrick,
The node ids you have refer to nodes in the edge-based graph. That's a level
removed from what you want, so you'll need to work your way backwards.
This shows how to unpack the edge-based-node ids into a sequence of node ids
in the node-based graph (that you can then convert to
Hi Kerrick,
Yup, the node ids are renumbered to pack them more densely and ensure that
values fit inside an unsigned int (32 bits).
The mapping *is* written to the `.nodes` file though, here:
Hey Kerrick,
the data is not available in the server anymore, but you can load it
to memory if you like (which will increase the memory consumption
quite a bit on large datasets). The idea is to adapt this [1] function
to load a exteractor::ExternalMemoryNode vector to array that can
translate
