-
-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trsp and tsp name change to be more descriptive #427
Comments
|
@dkastl |
currently TRSP and because of acronym usage, without looking at the documentation do you know what the acronym mean? comparing with a well known acronym (TSP): So for TSP I am OK with using the acronym. |
about TRSPI want to remove the acronym SP = shortest path, not true with the current implementation Example: The shortest path from vertex 1 to vertex 1, well there should be no route
So being "Shortest Path" a false statement. Then pgr_TRP, pgr_TR ??? FYI, IDA BTAM WYDKWTM = For your information, I dislike acronyms, because they are meaningless when you don't now what they mean the function's name options
Note that the word "Shortest" is not there any more. |
Vote for |
Vote for |
Since the result is a path, it should be part of the name in my opinion. What about the little change to |
Daniel +1 on pgr_turnRestrictedPath
…Sent from my iPhone
On Jun 12, 2018, at 11:45 AM, Daniel Kastl ***@***.***> wrote:
Since the result is a path, it should be part of the name in my opinion.
What about the little change to pgr_turnRestrictedPath?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sorry for the back and forth voting. I was undecided between pgr_turnRestrictionsPath and pgr_turnRestrictedPath. I still sort of am. It seems like "Turn Restricted Shortest Path" term is used slightly more than "Turn Restrictions Shortest Path" e.g you have it here as that The docs seem to be a mixed flavor of both, so should be standardized to whatever naming you decide on: |
+1 pgr_turnRestrictedPath
…On Fri, 15 Jun 2018 at 10:13 PM, Regina Obe ***@***.***> wrote:
Sorry for the back and forth voting. I was undecided between
pgr_turnRestrictionsPath and pgr_turnRestrictedPath. I still sort of am.
It seems like "Turn Restricted Shortest Path" term is used slightly more
than "Turn Restrictions Shortest Path"
e.g you have it here as that
https://github.com/pgRouting/pgrouting/wiki/Turn-Restricted-Shortest-Path-(TRSP)
The docs seem to be a mixed flavor of both, so should be standardized to
whatever naming you decide on:
https://docs.pgrouting.org/latest/en/pgr_trsp.html#trsp
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#427 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AExSmV-vHpi36mZCZ0eY_BBgqDcpLjoiks5t8-QqgaJpZM4GiYOc>
.
|
|
Forgot to mention, related to #2238 |
Change the names to be more descriptive for example:
pgr_travelingSalesman
pgr_turnRestrictions
If someone likes short names they can wrap them on a function.
So, I can wrap it as:
pgr_vv <--- hey in spanish is vendedor viajante
The text was updated successfully, but these errors were encountered: