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
Currently, we're using the vertex indices to specify the endpoints of most edges (walls, lanes, doors, etc.). As we gradually migrate towards GeoJSON, it would be better to generate UUID's for all vertices and store those UUID's in the edges, to avoid having to maintain the vertex index because those change (for example, if a lower-indexed vertex is deleted).
We're already doing this for alignment-features and alignment-constraints; this ticket is to migrate that idea throughout the rest of the code, especially the vertex objects.
The text was updated successfully, but these errors were encountered:
Currently, we're using the vertex indices to specify the endpoints of most edges (walls, lanes, doors, etc.). As we gradually migrate towards GeoJSON, it would be better to generate UUID's for all vertices and store those UUID's in the edges, to avoid having to maintain the vertex index because those change (for example, if a lower-indexed vertex is deleted).
We're already doing this for alignment-features and alignment-constraints; this ticket is to migrate that idea throughout the rest of the code, especially the vertex objects.
The text was updated successfully, but these errors were encountered: