You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The link shapes should represent the link direction by how the polylines are defined. This way, when one uses GIS to show an arrow head to represent direction or using a line offset to separate the drawing of bidirectional links, the direction is visible when the link is rendered. Currently, this is not the case.
In the attached image, the link layer has a symbology with both an arrowhead on the end, plus a link offset. Two links are selected (see right pane) and they are meant to be the reverse of each other (they have A1==B2 and B1==A2) but only one link is rendered implying the link geometry is the same rather than reversed.
- Use geofeather as intermediate format (since it's much faster)
- Add a lot of documentation inline
- Add reverse geometries for reverse links ( fixes#56 )
- Don't aggregate up to shared street links just yet -- punt to later step
- Performance improvements
The link shapes should represent the link direction by how the polylines are defined. This way, when one uses GIS to show an arrow head to represent direction or using a line offset to separate the drawing of bidirectional links, the direction is visible when the link is rendered. Currently, this is not the case.
In the attached image, the link layer has a symbology with both an arrowhead on the end, plus a link offset. Two links are selected (see right pane) and they are meant to be the reverse of each other (they have A1==B2 and B1==A2) but only one link is rendered implying the link geometry is the same rather than reversed.
(MTC asana task)
The text was updated successfully, but these errors were encountered: