Timeline for Increase Tiles Caching Speed (TileStache)
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2016 at 11:27 | history | edited | bugmenot123 | CC BY-SA 3.0 |
added 367 characters in body
|
| Apr 27, 2016 at 11:25 | comment | added | bugmenot123 |
For your example the column used for lookup in the query is priority, so for example CREATE INDEX idx_roads_priority ON roads(priority);.
|
|
| Apr 27, 2016 at 9:59 | comment | added | Hasan Mustafa | How would I go about doing that, on what basis should I make the indexes? | |
| Apr 27, 2016 at 9:48 | comment | added | bugmenot123 | Then create an index on each column you use in a WHERE clause. You can also create multi-column indexes if needed. | |
| Apr 27, 2016 at 9:43 | comment | added | Hasan Mustafa | Yes to both, I have alot of rows in some of the tables, My POI table has around 975k rows and my roads shapefile was 8.5gb before importing into Postgres. I am using queries to filter data based on zoom levels: "10":"SELECT wkb_geometry AS geometry,priority,name,route_num FROM roads WHERE priority IN (5,4,3)" this is a query I am using to return roads on zoom level 10. | |
| Apr 27, 2016 at 9:40 | comment | added | bugmenot123 | Do you have a lot of rows? Is your vector tile generation dependant on other attributes (eg subselections of the data)? | |
| Apr 27, 2016 at 9:34 | comment | added | Hasan Mustafa | I used the plug-in "PostGIS Shapefile and DBF loader" in Postgres, it created an index: CREATE INDEX scale_geom_idx ON scale USING gist(geom). , automatically when I imported my shapefiles. Should I look to make additional indexes? | |
| Apr 27, 2016 at 8:42 | history | answered | bugmenot123 | CC BY-SA 3.0 |