meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 3 months |
| seen | May 17 at 21:04 | |
| stats | profile views | 29 |
|
Apr 15 |
awarded | Caucus |
|
Feb 7 |
awarded | Necromancer |
|
Dec 13 |
comment |
Why does tool take longer to run when in Python script? I would guess that your next step then is to look into speeding up your ArcGIS start time if that 1-2 minutes is unacceptable. here's a previous question I found related to getting Arc to start quicker gis.stackexchange.com/questions/20437/… |
|
Dec 11 |
comment |
Why does tool take longer to run when in Python script? How much extra time are you taking in actual minutes/hours? The overhead I'm taking about should be a flat 1-2 minutes at most on top of the normal running time. |
|
Dec 6 |
answered | Python: find a method to calculate the “inner centroid” (also known as labelPoint in arcmap) of a polygon |
|
Dec 6 |
awarded | Revival |
|
Dec 5 |
answered | Why does tool take longer to run when in Python script? |
|
Dec 5 |
awarded | Scholar |
|
Dec 5 |
accepted | Disappearing Point Features in Geoserver using WMS |
|
Dec 5 |
answered | Disappearing Point Features in Geoserver using WMS |
|
Dec 3 |
comment |
Disappearing Point Features in Geoserver using WMS As I have been unable to resolve this using the shapefile data store, I imported the data into postGIS using shp2pqsql and set up geoserver to read from there. IT works fine after that, so I will just modify my setup & scripts to use PostGIS. |
|
Dec 3 |
comment |
Disappearing Point Features in Geoserver using WMS @Mintx - missed your question for a while. Yes, I have, with no change. |
|
Nov 30 |
comment |
Disappearing Point Features in Geoserver using WMS /geoserver/DM/wms?LAYERS=DM%3ATest&STYLES=&FORMAT=image%2Fpng&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS=EPSG%3A3857&CQL_FILTER=VENUE_TYPE%3D'Animal%20Park'&BBOX=-22170578.766354,-1698674.8632535,4235254.0862946,9444451.5323653&WIDTH=782&HEIGHT=330 |
|
Nov 29 |
awarded | Nice Question |
|
Nov 27 |
awarded | Commentator |
|
Nov 27 |
comment |
Disappearing Point Features in Geoserver using WMS In an attempt to anonymize the data I removed all columns from the shapefile except for the Venue_Type column which I re-coded as single letter codes. I still saw the exact same scenario as detailed above. However, I still had to move points around spatially to fully anonymize the data, except for the points I showed in the screenshots. After I did that, the 3 points did still disappear, but at different zoom levels (further out). I also reexported the shapefile using QGIS to rule out ArcGIS, but to no avail. Still seeking permission to post anonymized data however... |
|
Nov 27 |
comment |
Disappearing Point Features in Geoserver using WMS If I can anonymize the data, and still have it exhibit this problem, I will post it. |
|
Nov 26 |
comment |
Disappearing Point Features in Geoserver using WMS I removed all features with a venue_type that contained anything other than english letters just to rule that out. The same thing occured. I've opened this shapefile in arcGIS succesfully and re-exported it as well. The shapefile is valid as far as I can tell. There are other fields in this shapefile that contain some non-latin characters, but I can't imagine that would be causing this issue since I'm not filtering on those columns |
|
Nov 26 |
comment |
Disappearing Point Features in Geoserver using WMS @tomfumb I looked over the values in the VENUE_TYPE column and they are all english alphanumeric except for an occasional forward slash '/' or ampersand '&'. I'll take out the records with the slashes and ampersands and see if that makes a difference. As a side note, this shapefile's DBF is encoded in UTF-8 which I set in geoserver as well. Could that make a difference? |
|
Nov 26 |
comment |
Disappearing Point Features in Geoserver using WMS @unicoletti On the layer displayed in the screenshot, there are scale dependencies, but I see the same result when I use the default 'point' style provided by Geoserver, which has no scale dependencies I see the exact same points disappearing at the same scales. |
