meta user
network profile
| bio | website | pablumfication.co.uk |
|---|---|---|
| location | England, United Kingdom | |
| age | 25 | |
| visits | member for | 1 year, 10 months |
| seen | May 9 at 9:34 | |
| stats | profile views | 10 |
|
Mar 27 |
comment |
geoserver PointStacker For anyone interested in it I made more progress with this issue on the geoserver mailing list. Due to time constraints I had to ditch using geoserver and go with mapserver which provides a much better clustering solution ( at the moment ). I intend to go back and attempt to make the it work in geoserver when I have the time. |
|
Mar 27 |
awarded | Tumbleweed |
|
Mar 20 |
asked | geoserver PointStacker |
|
Dec 18 |
awarded | Excavator |
|
Dec 18 |
revised |
OpenLayers: How to create a rectangle? Fixed Syntax Error and formatting |
|
Dec 18 |
suggested | suggested edit on OpenLayers: How to create a rectangle? |
|
Dec 10 |
comment |
Caching / Preloading data for use with WMS queries The client is using OpenLayers. |
|
Dec 10 |
comment |
Caching / Preloading data for use with WMS queries Now this I like the sound of :) Going to have a look into it. |
|
Dec 10 |
comment |
Caching / Preloading data for use with WMS queries Performing an ST_Intersects JOIN on ~3 million points of data in 2.5 minutes isn't exactly slow. Yes of course it could be faster but I've got advise on improving the performance on here and its as fast as it can be for now. |
|
Dec 10 |
comment |
Caching / Preloading data for use with WMS queries thanks for your input. How up to date the data is isn't cripplingly important. But because the user can select date ranges to query from and from many datasets to use in aggregate there isn't really anyway I could do what you suggest. Although if I can export a query to a shape file do you know if there is anyway I can get geoserver to just read that file passing its path as part of the query? |
|
Dec 10 |
comment |
Caching / Preloading data for use with WMS queries Thanks for your suggestions I've had a good look through them, but unfortunately none of them seem to be suitable unless I've missed something. Implementing tile caching might help a little but the data is updated quite regularly and because the tiles are generated from user queries each query will generate quite different results and just changing the temporal part of a query to add another month or whatever would mean caching an entire other set of tiles. |
|
Dec 10 |
comment |
Caching / Preloading data for use with WMS queries Thanks for your reply. Just a note your link to TileCache is wrong missed out the second 'c'. Looking into your suggestions at the moment. |
|
Dec 6 |
asked | Caching / Preloading data for use with WMS queries |
|
Nov 25 |
awarded | Benefactor |
|
Nov 25 |
awarded | Commentator |
|
Nov 25 |
comment |
PostGIS Intermittent INDEX Performance @unicoletti Thank you very much for your input will certainly give you suggestions a go and will report back on the results soon. I've actually got the PostgreSQL 9.0 High Performance book totally agree highly recommend reading know I need to read it more myself to make sure get every little performance boost I can. |
|
Nov 25 |
comment |
PostGIS Intermittent INDEX Performance This is looking very promising paul after pushing the rest of the non-spatial queries up into the WITH clause. I've been off work ill for the last 2 days so haven't had chance to 100% confirm that its solving the issue, but I'm going to award you the bounty as all your advise both here and on the postgis-users list has been very helpful. Will report back once I know for sure. |
|
Nov 20 |
awarded | Teacher |
|
Nov 20 |
revised |
Django client install postgresql/postgis on Ubuntu 12.04 added 119 characters in body |
|
Nov 20 |
comment |
Django client install postgresql/postgis on Ubuntu 12.04 Cool have updated my answer to reflect that. |
