Timeline for Pros and cons of representing routes as legs or stops?
Current License: CC BY-SA 4.0
Post Revisions
26 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 21, 2021 at 10:59 | comment | added | Flater | You're effectively asking whether a polygon should be described by its vertices or by its edges. The answer is contextual. Is your domain focused on the stops they make, or on the travel between the stops? For example, a user might list a bunch of monuments they want to visit, which is stop-oriented, but if you're working with an Uber-like app, you're going to be interested travel (i.e. leg) related logic. | |
| Jun 20, 2021 at 22:59 | history | edited | Christophe |
edited tags
|
|
| May 10, 2021 at 20:05 | comment | added | leftaroundabout | @Bergi yes – the factor is estimated to be at least 2. That is, a bus can replace two legs (or even more, if it's a parallel bus), and it also gets you faster to the target (except in very short sprints). | |
| May 10, 2021 at 19:43 | comment | added | Bergi | @leftaroundabout bus factor??? | |
| May 10, 2021 at 16:54 | comment | added | leftaroundabout | Pro tip: legs work great for shorter routes, but a stop can be very useful if you have the departure times right, to take full advantage of the bus factor. | |
| May 10, 2021 at 14:59 | comment | added | François Beausoleil | @Bergi, we use a relational database, PostgreSQL specifically. An ordered list of stops is represented as rows with a position field indicating where that stop is in the route. Every route has at least four stops: depot, 1st customer stop, 2nd customer stop, depot. A depot is where vehicles are stored between trips. If I represented the same route as legs I'd have depot -> 1st cust stop, 1st cust stop->2nd cust stop, 2nd cust stop -> depot. | |
| May 10, 2021 at 14:52 | comment | added | Bergi | …or to extend this: what type of database are you using? A document-based one? A relational one? A graph database? Because an "ordered list" is hard to represent in a relational database, that's what @DocBrown and me are picking on. | |
| May 10, 2021 at 12:57 | review | Close votes | |||
| May 15, 2021 at 3:06 | |||||
| May 10, 2021 at 11:02 | comment | added | Doc Brown | @FrançoisBeausoleil: I guess you misunderstood my question. Bergi above asked what the same what I wanted to know, in other words. What's a route based on "stops"? An ordered list of stops? | |
| May 10, 2021 at 4:38 | comment | added | mcalex | From a real-world perspective, are you interested in the journey, or the departure/arrival aspects. I'd lean toward legs if you are interested in the journey aspects and stops/stations if it's more about arrivals/departures. | |
| May 9, 2021 at 21:00 | history | tweeted | twitter.com/StackSoftEng/status/1391498221499863046 | ||
| May 9, 2021 at 20:58 | comment | added | Bergi | What I'm missing in your description is how you'd want to store the "route" object, as a list (?) of legs/stops. Does every item belong to a route? How are they ordered? | |
| May 9, 2021 at 20:55 | answer | added | Bergi | timeline score: 8 | |
| May 9, 2021 at 16:59 | answer | added | Ewan | timeline score: 1 | |
| May 9, 2021 at 16:30 | comment | added | François Beausoleil | @Helena thanks for the suggestion. If I remember correctly, Eric Evans and Martin Fowler both use legs in their books. | |
| May 9, 2021 at 16:30 | comment | added | François Beausoleil | @FilipMilovanović yes, good idea! | |
| May 9, 2021 at 16:29 | comment | added | François Beausoleil | @DocBrown currently, stops have a type: pick up, drop off, pit stop, and others. We also have a way to represent "the driver has reached their maximum driving hours for the day, so they need to sleep here". | |
| May 9, 2021 at 16:18 | history | became hot network question | |||
| May 9, 2021 at 15:49 | answer | added | Karl Bielefeldt | timeline score: 10 | |
| May 9, 2021 at 8:37 | answer | added | Christophe | timeline score: 11 | |
| May 9, 2021 at 8:15 | comment | added | Helena | Eric Evans the author of "Domain Driven Design" amazon.com/gp/product/B00794TAUG/ref=dbs_a_def_rwt_bibl_vppi_i0 uses Cargo shipping as example problem domain in his book and multiple of his presentations, you can find on youtube. It might worth checking those out. | |
| May 9, 2021 at 8:12 | comment | added | Filip Milovanović | Maybe the best thing to do is to try and get some domain experts (people working in the industry you're building the software for) and try to figure out how they think about it from the business perspective (e.g. are they talking and planning in terms of legs or stops and why, do they have to work around the fact that the current system uses a step-based representation or not, do they have their own terminology, etc.) | |
| May 9, 2021 at 5:46 | answer | added | Doc Brown | timeline score: 22 | |
| May 9, 2021 at 5:31 | comment | added | Doc Brown | How are the connections between locations are represented in your current system based on "stops"? | |
| May 9, 2021 at 4:04 | review | First posts | |||
| May 9, 2021 at 4:19 | |||||
| May 9, 2021 at 4:00 | history | asked | François Beausoleil | CC BY-SA 4.0 |