We need a way to store custom information on edges like:
MetaId's: A link to attribute collections. This has been fixed by using the edgeids.
Distances: We need to store distances even when they are implicitly defined by the shape of the edges.
Travel times: We can store travel times per profile to efficiently route.
(Edge types: we can store edge types to quickly calculate profiles per type.)
Edge shapes: we store a reference to the edge shape. This has been fixed by using the edgeids.
Some of this info needs to be store inline like the distances, other data is purely meta-data like the meta-id's. We need to make the distinction between data used during routing (stored in-line) or data store for reference (meta-data).
The only issue that is left now is to add the ability to store data in-line along with the edges.
We need a way to store custom information on edges like:
MetaId's: A link to attribute collections.This has been fixed by using the edgeids.Edge shapes: we store a reference to the edge shape.This has been fixed by using the edgeids.Some of this info needs to be store inline like the distances, other data is purely meta-data like the meta-id's. We need to make the distinction between data used during routing (stored in-line) or data store for reference (meta-data).
The only issue that is left now is to add the ability to store data in-line along with the edges.