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

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

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

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

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

[Geoserver-users] OpenLayers with App-Schemas

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

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] xlink:ref not well encoded in WFS response (app schema)

I noticed a similar problem with WFS version 2.0.0. I'm using app-schema configuration and get schema resolution with the following WFS GetFeature request GetFeature-AppSchema.xml http://osgeo-org.1560.x6.nabble.com/file/n5060964/GetFeature-AppSchema.xml :

Re: [Geoserver-users] FW: App Schema Resolution

Thanks for the advice in not using CQL in the gml:id - it is not mandatory that our 'objectid' show there. We figured out why the data was being returned in the incorrect fields in a GetFeature request: Our tables were created using ArcMap, which did not actually specify the OBJECTID as the

Re: [Geoserver-users] App Schema Resolution

Please see the attached DDL for the table. As you can see, the objected is never null, and isn't be big - it is numbered 1 - 1949. Thank you, Christy azboreholetemperaturesDDL.xml http://osgeo-org.1560.n6.nabble.com/file/n5041936/azboreholetemperaturesDDL.xml -- View this message in

Re: [Geoserver-users] App Schema Resolution

Thank you for the suggestion. I no longer get the error, but it still doesn't use my objectid in the idExpression: http://osgeo-org.1560.n6.nabble.com/file/n5042761/GetFeature_20130325.png -- View this message in context:

Re: [Geoserver-users] App Schema Resolution

We have achieved schema resolution! That is, as long as we use the getId() idExpression. However, because we'd like to use our integer field 'objectid', we need to figure out how to concatenate an integer with that field OR make that read as a string. We tried the following, but we get that