network profile
| bio | website | |
|---|---|---|
| location | Portlandia | |
| age | ||
| visits | member for | 1 year, 3 months |
| seen | Nov 18 '12 at 23:30 | |
| stats | profile views | 5 |
Slowly migrating from years of proprietary desktop GIS software in Windows into the beautifully complex and challenging world of open source webmapping in Linux. Learning curve: STEEEEP.
|
Oct 24 |
awarded | Popular Question |
|
Sep 20 |
awarded | Popular Question |
|
Mar 11 |
comment |
Path to proxy.cgi for GeoServer is not accessible in browser YES, thank you for the input, and sorry for the delayed reply. However, the website on which the map will ultimately be placed may not be very accessible to me in terms of doing anything but adding an html file. That said, I ended up making the map on the same domain as my GeoServer, then using a full-page iframe on the destination site: greengeography.org/projects/oregonwild/tests/test2.html . I realize how cheeky this is, but it seems to work and bypasses the cross-domain issue entirely. |
|
Feb 15 |
asked | Path to proxy.cgi for GeoServer is not accessible in browser |
|
Feb 10 |
comment |
What causes this unexpectedly poor GeoServer/PostGIS/OpenLayers performance? And in my catalina.out log: SEVERE: The web application [/geoserver] created a ThreadLocal with key of type... and SEVERE: The web application [/geoserver] appears to have started a thread named [GWC DiskQuota Usage Stats Gathering Thread-1] Any relationship between these and the GS error? |
|
Feb 9 |
comment |
What causes this unexpectedly poor GeoServer/PostGIS/OpenLayers performance? After making a few of these changes, performance is great, but only for the first few actions or so (i.e. zooming/panning). After that it gets very, very slow. It's like GeoServer can only handle a few requests, then it's done. Any thoughts? If it helps, I've been seeing a lot of these errors in my GS logs: ERROR [geoserver.ows] - org.geoserver.platform.ServiceException: This requested used more time than allowed and has been forcefully stopped. Max rendering time is 60.0s |
|
Feb 9 |
comment |
What causes this unexpectedly poor GeoServer/PostGIS/OpenLayers performance? Initially my layers were in EPSG:2992, but I am in the process of projecting them all to what ESRI calls Web Mercator, which should hopefully be equivalent to 900913, and then re-uploading them to Geoserver. I've also been using GWC on them, so that should help. Thanks! |
|
Feb 9 |
comment |
What causes this unexpectedly poor GeoServer/PostGIS/OpenLayers performance? It took some doing, but I got it installed. Thanks for the tip! |
|
Feb 8 |
awarded | Student |
|
Feb 7 |
asked | What causes this unexpectedly poor GeoServer/PostGIS/OpenLayers performance? |
