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
Within the docs, comments, and code itself we refer variously to roads, streets, edges, lines, links, etc.
In our last meeting during the discussion where we decided the final package name we mentioned that it is nice to be agnostic in terms of types of network (streets, bike paths, waterways, etc.).
So considering this, should we be more deliberate in terminology. Perhaps (trying to) stick with the more abstract [edges, lines, links] over the more specific [roads, streets] where possible?
The text was updated successfully, but these errors were encountered:
@jGaboardi good point, suggestion from @martinfleis (and I agree) to first fix terminology everywhere in the paper and once that is done, propagate here
Within the docs, comments, and code itself we refer variously to roads, streets, edges, lines, links, etc.
In our last meeting during the discussion where we decided the final package name we mentioned that it is nice to be agnostic in terms of types of network (streets, bike paths, waterways, etc.).
So considering this, should we be more deliberate in terminology. Perhaps (trying to) stick with the more abstract [edges, lines, links] over the more specific [roads, streets] where possible?
The text was updated successfully, but these errors were encountered: