Timeline for Importing multiple .asc files into PostGIS violates check constraint. Why?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2020 at 15:50 | comment | added | John Powell | Yes, indeed, I should have made that more explicit. There is going to be a very different peformance implication if your polygons are very large and cover many small tiles, whereas points are a bit easier to predict. | |
| Feb 14, 2020 at 15:18 | comment | added | ak112358 | This is great analysis-- note that polygon and point Overlay/Intersects performance can be very different. | |
| May 4, 2018 at 22:32 | history | edited | Andre Silva | CC BY-SA 4.0 |
fixed typos
|
| May 4, 2018 at 13:17 | vote | accept | Randomize | ||
| May 4, 2018 at 13:09 | comment | added | John Powell | Smaller than the asc files, for sure. You can always run a few to get an idea of the ratio of asc to raster (plus index size) to see if you will have enough space. Please accept the answer if it has helped you. | |
| May 4, 2018 at 13:04 | comment | added | Randomize | Really thank you! Have you an idea how much the whole imported dataset will take as db storage space? | |
| May 4, 2018 at 12:57 | history | edited | John Powell | CC BY-SA 4.0 |
added 670 characters in body
|
| May 4, 2018 at 12:52 | history | answered | John Powell | CC BY-SA 4.0 |