Timeline for Recalculating distance table - is there fast (fast and dirty OK) way?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2022 at 14:50 | vote | accept | Drinkins | ||
| Feb 8, 2022 at 20:26 | answer | added | Paul Ramsey | timeline score: 1 | |
| Feb 7, 2022 at 18:24 | comment | added | Vince | Wow, okay, you can't get any slower unless you move storage to a USB 2.0 thumb drive. Right now you just need to follow best practice: +Store data in the projection in which it will be used, +Build a spatial index, +Use ST_DWithin to limit search distance to probably candidates. But this is all for naught if the table is tiny (say, under 100k rows). See gis.stackexchange.com/questions/247113/… | |
| Feb 7, 2022 at 18:13 | history | edited | Drinkins | CC BY-SA 4.0 |
added 541 characters in body
|
| Feb 7, 2022 at 16:09 | history | edited | Ian Turton |
edited tags
|
|
| Feb 7, 2022 at 15:10 | review | Close votes | |||
| Feb 17, 2022 at 20:31 | |||||
| Feb 7, 2022 at 14:59 | comment | added | Vince | Welcome to GIS SE. As a new user, please take the Tour. Please Edit the Question to include your table definition, a list of indexes, an indication of the row count, the SQL query you are using, and the EXPLAIN plan. There is a likely efficiency to be gained, but we need to know where you are starting. | |
| Feb 7, 2022 at 14:54 | history | edited | Vince | CC BY-SA 4.0 |
naming
|
| S Feb 7, 2022 at 14:42 | review | First questions | |||
| Feb 8, 2022 at 6:58 | |||||
| S Feb 7, 2022 at 14:42 | history | asked | Drinkins | CC BY-SA 4.0 |