Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-06 Thread Andrea Aime
On Fri, Sep 6, 2013 at 5:01 AM, Ben Caradoc-Davies ben.caradoc-dav...@csiro.au wrote: Ryan, I had a look at a recent deployment using apache2 ProxyPass (proxy_http) to tomcat6 on localhost:8080 and Everything Just Works (Capabilities and OpenLayers), even without setting Proxy Base URL. I

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-05 Thread christy@azgs
Hey Ben, I already have the Proxy Base URL listed as http://data.usgin.org/azgs_bedrock_geology and am using v2.3.0 of GeoServer. I changed it after creating these layers, so do I need to do the work over, after the Proxy has been indicated? -- View this message in context:

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-05 Thread Christy Caudill
: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea Aime Sent: Thursday, September 05, 2013 10:07 AM To: Christy Caudill Cc: GeoServer Mailing List List Subject: Re: [Geoserver-users] OpenLayers with App-Schemas On Thu, Sep 5, 2013 at 6:50 PM, christy@azgs christy.caud

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-05 Thread Ryan Clark
Ben - We got things to work by adjusting the Host header on the proxy server (nginx in this case), but before doing that we were seeing 127.0.0.1 addresses in the GetCapabilities and OpenLayers previews even though we had set the Geoserver proxy base url. We're using 2.3, so I'm curious why we

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-05 Thread Andrea Aime
On Thu, Sep 5, 2013 at 6:50 PM, christy@azgs christy.caud...@azgs.az.govwrote: Okay, so you can see that the OnlineResource in the GetCapabilities still references 127.0.0.1 http://data.usgin.org/azgs_bedrock_geology/gsmlp/wms?service=WMSversion=1.3.0request=GetCapabilities Do you have

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-05 Thread christy@azgs
Okay, so you can see that the OnlineResource in the GetCapabilities still references 127.0.0.1 http://data.usgin.org/azgs_bedrock_geology/gsmlp/wms?service=WMSversion=1.3.0request=GetCapabilities And attached is a screen shot that the Proxy has been set, but is being ignored:

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-05 Thread Ben Caradoc-Davies
Ryan, I had a look at a recent deployment using apache2 ProxyPass (proxy_http) to tomcat6 on localhost:8080 and Everything Just Works (Capabilities and OpenLayers), even without setting Proxy Base URL. I suspect that apache is setting similar headers. Your nginx solution is quite useful and

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-04 Thread christy@azgs
Adding that to the request seems to work fine: http://data.usgin.org/azgs_bedrock_geology/gsmlp/ows?service=WFSversion=1.1.0request=GetFeaturetypeName=gsmlp:GeologicUnitViewmaxFeatures=2srsName=http://www.opengis.net/def/crs/EPSG/0/4326 -- View this message in context:

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-04 Thread christy@azgs
I am having some trouble with the newest Nightly version Rini suggested (when I try to Submit an SLD, it bonks with an error message java.lang.IllegalStateException: Form too large22477820). Any help there would be great On another front, in the 2.3.0 version of GeoServer that I've been

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-04 Thread Ben Caradoc-Davies
Christy, notice how the extra parameter changes the axis order to latitude/longitude as expected? The values look correct. In my mind, this confirms that you do not have an axis order problem. Nice to see it working with a shapefile! Kind regards, Ben. On 04/09/13 23:22, christy@azgs wrote:

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-04 Thread Ben Caradoc-Davies
Christy, tl;dr: not an app-schema problem, please set your Global / Settings / Proxy Base URL to: http://data.usgin.org/azgs_bedrock_geology/ Long version: This is not an app-schema problem. If you look at the source of the OpenLayers JavaScript that is delivered to the client by GeoServer,

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-04 Thread Ben Caradoc-Davies
Also not an app-schema problem. See advice here: http://osgeo-org.1560.x6.nabble.com/SLD-file-too-large-td3791883.html On 05/09/13 01:03, christy@azgs wrote: I am having some trouble with the newest Nightly version Rini suggested (when I try to Submit an SLD, it bonks with an error message

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-03 Thread Ben Caradoc-Davies
On 03/09/13 12:55, John Callahan wrote: As FYI, to create a valid idExpression (one without a leading integer and not using a CQL function), I need to create a column in my database view to represent the id. An example output of id would be fid.sand.898. I concatenated fields in my Postgres

[Geoserver-users] OpenLayers with App-Schemas

2013-09-03 Thread christy@azgs
We cannot get SLDs to show return with OpenLayers using App-Schemas configurations. Data from some layers are pulling from shapefiles and some are pulling from PostGIS, but all using app-schemas. OpenLayers won't return an image; either Click on the map to get feature info is the only text, or the

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-03 Thread christy@azgs
Rini, For the Nightly 2.5-snapshot download, which version of app-schemas will work with that? Version geoserver-2.4-RC1-app-schema-plugin? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075888.html Sent from the GeoServer - User

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-03 Thread Ben Caradoc-Davies
Christy, that axis order looks correct to me for a WMS 1.1 request centred on Arizona. Your WFS response does not contain any srsName attributes on the geometries. It looks like it is encoded in longitude/latitude axis order (guessing Arizona again). What do you get if you append:

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-02 Thread John Callahan
I have the same problem as Christy. The bug fix you reference looks promising. As FYI., from looking in the geoserver log file, I see the following error: 2013-09-02 01:48:30,367 DEBUG [geotools.jdbc] - CREATE CONNECTION 2013-09-02 01:48:30,367 TRACE [geotools.core] - ENTRY 4 2013-09-02

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-02 Thread Rini.Angreani
To: Angreani, Rini (CESRE, Kensington) Cc: geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] OpenLayers with App-Schemas I have the same problem as Christy. The bug fix you reference looks promising. As FYI., from looking in the geoserver log file, I see the following error: 2013

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-02 Thread Rini.Angreani
#idexpression-optional Cheers Rini From: John Callahan [mailto:john.calla...@udel.edu] Sent: Monday, 2 September 2013 2:24 PM To: Angreani, Rini (CESRE, Kensington) Cc: geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] OpenLayers with App-Schemas I have the same problem as Christy

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-02 Thread John Callahan
@lists.sourceforge.net *Subject:* Re: [Geoserver-users] OpenLayers with App-Schemas ** ** I have the same problem as Christy. The bug fix you reference looks promising. As FYI., from looking in the geoserver log file, I see the following error: ** ** 2013-09-02 01:48:30,367 DEBUG

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-01 Thread Ben Caradoc-Davies
Christy, please looks in the geoserver logs to see what WMS requests are being generated. In particular, I am interested in the request WMS version, SRS/CRS, and BBOX. One common problem is a mismatch between the axis order of your data and the WMS requests:

Re: [Geoserver-users] OpenLayers with App-Schemas

2013-09-01 Thread Rini Angreani
Hi Christy, Apart from Ben's suggestions, I also made a very recent bug fix relating to WMS with app-schema: https://jira.codehaus.org/browse/GEOT-4550. Please try the latest from trunk if you're not already using it. Cheers Rini -- View this message in context: