Timeline for Should I create a separate table for geo-location points?
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2018 at 3:15 | history | edited | Evan Carroll |
edited tags
|
|
| S Feb 16, 2018 at 5:36 | history | bounty ended | Thanassis | ||
| S Feb 16, 2018 at 5:36 | history | notice removed | Thanassis | ||
| Feb 14, 2018 at 5:55 | vote | accept | Thanassis | ||
| Feb 13, 2018 at 23:18 | comment | added | RDFozz | Given what you've described (street addr identifies lat/long), storing the lat/long in the bookings table, and having the street addr in a location table w/ lat/long as a key might work. However, there are potential issues with that; sometimes, Google might map an address to the middle of its zip code if it can't get closer, and that might give you multiple addresses with the same lat/long; also, that lat/long might get fixed at some point and be different. You might still want to store street addr in its own table (that's likely to repeat over time), but probably need lat/long in bookings. | |
| Feb 13, 2018 at 22:20 | history | edited | Thanassis | CC BY-SA 3.0 |
deleted 10 characters in body
|
| Feb 13, 2018 at 20:56 | answer | added | WillisJohnson | timeline score: 2 | |
| Feb 13, 2018 at 0:21 | history | edited | Evan Carroll |
edited tags
|
|
| Feb 13, 2018 at 0:10 | answer | added | Evan Carroll | timeline score: 3 | |
| Feb 11, 2018 at 20:53 | history | tweeted | twitter.com/StackDBAs/status/962791725268946944 | ||
| Feb 11, 2018 at 19:37 | answer | added | Abel Melquiades Callejo | timeline score: 3 | |
| S Feb 9, 2018 at 5:51 | history | bounty started | Thanassis | ||
| S Feb 9, 2018 at 5:51 | history | notice added | Thanassis | Draw attention | |
| Feb 9, 2018 at 5:50 | history | edited | Thanassis | CC BY-SA 3.0 |
added 4 characters in body
|
| Feb 6, 2018 at 5:57 | history | edited | Thanassis | CC BY-SA 3.0 |
added 45 characters in body
|
| Feb 6, 2018 at 3:15 | history | edited | Thanassis | CC BY-SA 3.0 |
more detailed explanations
|
| Feb 5, 2018 at 12:35 | comment | added | Thanassis | The locations are determined via the street address. In the sense that the user enters a street address. The frontend uses this input and the google maps api to convert this to a verifiable address, and in the process also gets latitude and longitude. All of this is passed to the backend. In the backend, a location is identified uniquely by the latitude and longitude. Past locations that map to a different street address in the present (say a street rename) are kept with their historic mapping. | |
| Feb 5, 2018 at 9:24 | comment | added | user1822 | Are those pre-defined locations that can't change? Do you identify them through the latitude/logintude or through a name (e.g. "Some Company") Is it allowed to change the actual place of a pick-up location? (e.g. if "Some Company" moves to different address) or is that a new location? If yes what should happen to existing requests that used that location? | |
| Feb 5, 2018 at 8:36 | review | First posts | |||
| Feb 5, 2018 at 8:44 | |||||
| Feb 5, 2018 at 8:33 | history | asked | Thanassis | CC BY-SA 3.0 |