[Geoserver-users] OpenLayers with App-Schemas

GeoServer GeoServer User
1

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 scale is given, but no image. Help!

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

For more info, attached are a mapping file and SLD for one layer.
GeologicUnitViewAZGS.xml
<http://osgeo-org.1560.x6.nabble.com/file/n5075323/GeologicUnitViewAZGS.xml&gt;
USAZ_AZGS_1M_Lithostratigraphy_azgsOneGeologyGUV.sld
<http://osgeo-org.1560.x6.nabble.com/file/n5075323/USAZ_AZGS_1M_Lithostratigraphy_azgsOneGeologyGUV.sld&gt;

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075323.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

3

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:
http://docs.geoserver.org/stable/en/user/services/wms/basics.html#axis-ordering

For example, if your data is defined as lon/lat but the srs is declared as lat/lon, you will likely see nothing on your maps (or it will be flipped in x=y).

What do you get in gsmlp:shape if you make a WFS 1.1.0 request for a single gsmlp:GeologicUnitView? By manual inspection, are the GML coordinates encoded in lat/lon or lon/lat or eastings/northings or nothings/easting? Then we can compare with the declared srsName and see whether they are consistent.

Note also that the_geom in postgis must have a spatial index for WMS to work.

Kind regards,
Ben.

On 31/08/13 04:43, christy@anonymised.com wrote:

For more info, attached are a mapping file and SLD for one layer.
GeologicUnitViewAZGS.xml
<http://osgeo-org.1560.x6.nabble.com/file/n5075323/GeologicUnitViewAZGS.xml&gt;
USAZ_AZGS_1M_Lithostratigraphy_azgsOneGeologyGUV.sld
<http://osgeo-org.1560.x6.nabble.com/file/n5075323/USAZ_AZGS_1M_Lithostratigraphy_azgsOneGeologyGUV.sld&gt;

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075323.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

4

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: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075509.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

5

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 01:48:30,367 DEBUG [geotools.filter] - exporting PropertyName
2013-09-02 01:48:30,367 DEBUG [geotools.filter] - exporting LiteralExpression
2013-09-02 01:48:30,367 DEBUG [geotools.jdbc] - SELECT “public”.“geosci_geolunitview100k”.“identifier”,encode(ST_AsEWKB(“public”.“geosci_geolunitview100k”.“geom”),‘base64’) as “geom” FROM “public”.“geosci_geolunitview100k” INNER JOIN ( SELECT DISTINCT FROM “public”.“geosci_geolunitview100k” WHERE “geom” && ST_GeomFromText(‘POLYGON ((135058.6446566685 -28179.470173503414, 135058.6446566685 282487.40294382145, 265105.24270579155 282487.40294382145, 265105.24270579155 -28179.470173503414, 135058.6446566685 -28179.470173503414))’, 26957) ) “temp_alias_used_for_filter” ON ( )
2013-09-02 01:48:30,382 DEBUG [geotools.jdbc] - CLOSE CONNECTION
2013-09-02 01:48:30,382 ERROR [geotools.rendering] - java.io.IOException
java.lang.RuntimeException: java.io.IOException
at org.geotools.data.store.ContentFeatureCollection.features(ContentFeatureCollection.java:168)

…
…

… 116 more
Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near “FROM”
Position: 206

I confirm this error by executing the SQL SELECT statement directly to postgis. Coordinate ordering seems fine and the exact same data table works well through a non-app-schema based service.

···
  • John

John Callahan
Research Scientist
Delaware Geological Survey
University of Delaware
http://www.dgs.udel.edu

john.callahan@anonymised.com

On Mon, Sep 2, 2013 at 1:13 AM, Rini Angreani <Rini.Angreani@anonymised.com> wrote:

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: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075509.html

Sent from the GeoServer - User mailing list archive at Nabble.com.

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

6

Hi John,

Judging by the SQL error, your problem seems to be different from the bug I fixed.

I’ll have a look at your workspaces (from Ben) and see if I could spot a configuration issue.

Cheers

Rini

···

From: John Callahan [mailto:john.callahan@anonymised.com]
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. 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 01:48:30,367 DEBUG [geotools.filter] - exporting PropertyName

2013-09-02 01:48:30,367 DEBUG [geotools.filter] - exporting LiteralExpression

2013-09-02 01:48:30,367 DEBUG [geotools.jdbc] - SELECT “public”.“geosci_geolunitview100k”.“identifier”,encode(ST_AsEWKB(“public”.“geosci_geolunitview100k”.“geom”),‘base64’) as “geom” FROM “public”.“geosci_geolunitview100k” INNER JOIN ( SELECT DISTINCT FROM “public”.“geosci_geolunitview100k” WHERE “geom” && ST_GeomFromText(‘POLYGON ((135058.6446566685 -28179.470173503414, 135058.6446566685 282487.40294382145, 265105.24270579155 282487.40294382145, 265105.24270579155 -28179.470173503414, 135058.6446566685 -28179.470173503414))’, 26957) ) “temp_alias_used_for_filter” ON ( )

2013-09-02 01:48:30,382 DEBUG [geotools.jdbc] - CLOSE CONNECTION

2013-09-02 01:48:30,382 ERROR [geotools.rendering] - java.io.IOException

java.lang.RuntimeException: java.io.IOException

at org.geotools.data.store.ContentFeatureCollection.features(ContentFeatureCollection.java:168)

…

…

… 116 more

Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near “FROM”

Position: 206

I confirm this error by executing the SQL SELECT statement directly to postgis. Coordinate ordering seems fine and the exact same data table works well through a non-app-schema based service.

  • John

John Callahan

Research Scientist

Delaware Geological Survey

University of Delaware
http://www.dgs.udel.edu

john.callahan@anonymised.com

On Mon, Sep 2, 2013 at 1:13 AM, Rini Angreani <Rini.Angreani@anonymised.com.367…> wrote:

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: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075509.html

Sent from the GeoServer - User mailing list archive at Nabble.com.

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

7

Hi John,

This looks like a bug when idExpression is not specified: https://jira.codehaus.org/browse/GEOT-4554.

While I’m fixing the bug, you can use a workaround by specifying idExpression to your database id column.

http://docs.geoserver.org/latest/en/user/data/app-schema/mapping-file.html#idexpression-optional

Cheers

Rini

···

From: John Callahan [mailto:john.callahan@anonymised.com]
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. 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 01:48:30,367 DEBUG [geotools.filter] - exporting PropertyName

2013-09-02 01:48:30,367 DEBUG [geotools.filter] - exporting LiteralExpression

2013-09-02 01:48:30,367 DEBUG [geotools.jdbc] - SELECT “public”.“geosci_geolunitview100k”.“identifier”,encode(ST_AsEWKB(“public”.“geosci_geolunitview100k”.“geom”),‘base64’) as “geom” FROM “public”.“geosci_geolunitview100k” INNER JOIN ( SELECT DISTINCT FROM “public”.“geosci_geolunitview100k” WHERE “geom” && ST_GeomFromText(‘POLYGON ((135058.6446566685 -28179.470173503414, 135058.6446566685 282487.40294382145, 265105.24270579155 282487.40294382145, 265105.24270579155 -28179.470173503414, 135058.6446566685 -28179.470173503414))’, 26957) ) “temp_alias_used_for_filter” ON ( )

2013-09-02 01:48:30,382 DEBUG [geotools.jdbc] - CLOSE CONNECTION

2013-09-02 01:48:30,382 ERROR [geotools.rendering] - java.io.IOException

java.lang.RuntimeException: java.io.IOException

at org.geotools.data.store.ContentFeatureCollection.features(ContentFeatureCollection.java:168)

…

…

… 116 more

Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near “FROM”

Position: 206

I confirm this error by executing the SQL SELECT statement directly to postgis. Coordinate ordering seems fine and the exact same data table works well through a non-app-schema based service.

  • John

John Callahan

Research Scientist

Delaware Geological Survey

University of Delaware
http://www.dgs.udel.edu

john.callahan@anonymised.com

On Mon, Sep 2, 2013 at 1:13 AM, Rini Angreani <Rini.Angreani@anonymised.com.367…> wrote:

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: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075509.html

Sent from the GeoServer - User mailing list archive at Nabble.com.

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

8

Thanks! I added the idExpression in the mapping file and that did the trick. Using Layers Preview, I can now view the WMS for the app-schema WFS service. It is extremely slow but at least it works. A GetFeatureInfo pulls additional fields separate from those defined in app-schema mapping. I believe these are from the ‘parent’ GML schema??? (not sure of terminology.)

http://maps.dgs.udel.edu/geoserver/gsmlp/wms?service=WMS&version=1.1.0&request=GetMap&layers=gsmlp:GeologicUnitView&styles=&bbox=168047.207459393,50089.3156893812,232116.679903062,204218.617080925&width=212&height=512&srs=EPSG:26957&format=application/openlayers

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 view as below.

CREATE myView AS
SELECT ((‘fid.’::text || datatable.“formationCode”::text) || ‘.’::text) || spatialtable.gid AS id, …

Thanks again.

···
  • John

John Callahan
Research Scientist
Delaware Geological Survey
University of Delaware
http://www.dgs.udel.edu

john.callahan@anonymised.com

On Mon, Sep 2, 2013 at 11:56 PM, <Rini.Angreani@anonymised.com> wrote:

Hi John,

This looks like a bug when idExpression is not specified: https://jira.codehaus.org/browse/GEOT-4554.

While I’m fixing the bug, you can use a workaround by specifying idExpression to your database id column.

http://docs.geoserver.org/latest/en/user/data/app-schema/mapping-file.html#idexpression-optional

Cheers

Rini

From: John Callahan [mailto:john.callahan@anonymised.com]
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. 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 01:48:30,367 DEBUG [geotools.filter] - exporting PropertyName

2013-09-02 01:48:30,367 DEBUG [geotools.filter] - exporting LiteralExpression

2013-09-02 01:48:30,367 DEBUG [geotools.jdbc] - SELECT “public”.“geosci_geolunitview100k”.“identifier”,encode(ST_AsEWKB(“public”.“geosci_geolunitview100k”.“geom”),‘base64’) as “geom” FROM “public”.“geosci_geolunitview100k” INNER JOIN ( SELECT DISTINCT FROM “public”.“geosci_geolunitview100k” WHERE “geom” && ST_GeomFromText(‘POLYGON ((135058.6446566685 -28179.470173503414, 135058.6446566685 282487.40294382145, 265105.24270579155 282487.40294382145, 265105.24270579155 -28179.470173503414, 135058.6446566685 -28179.470173503414))’, 26957) ) “temp_alias_used_for_filter” ON ( )

2013-09-02 01:48:30,382 DEBUG [geotools.jdbc] - CLOSE CONNECTION

2013-09-02 01:48:30,382 ERROR [geotools.rendering] - java.io.IOException

java.lang.RuntimeException: java.io.IOException

at org.geotools.data.store.ContentFeatureCollection.features(ContentFeatureCollection.java:168)

…

…

… 116 more

Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near “FROM”

Position: 206

I confirm this error by executing the SQL SELECT statement directly to postgis. Coordinate ordering seems fine and the exact same data table works well through a non-app-schema based service.

  • John

John Callahan

Research Scientist

Delaware Geological Survey

University of Delaware
http://www.dgs.udel.edu

john.callahan@anonymised.com

On Mon, Sep 2, 2013 at 1:13 AM, Rini Angreani <Rini.Angreani@anonymised.com.367…> wrote:

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: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075509.html

Sent from the GeoServer - User mailing list archive at Nabble.com.

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

9

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 view as below.
CREATE myView AS
SELECT (('fid.'::text || datatable."formationCode"::text) || '.'::text)
|| spatialtable.gid AS id, .....

Good, that is just what I do. Much better than CQL in the mapping file.

Although I have not yet used them (only in Oracle), PostgreSQL 9.3 has materialised views (although there has been a community recipe out for a while):
http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-materialized-views/

Matviews give you the option of indexing your string-concatenated id for improved performance. Don't forget to index your other columns, as a matview does not copy indexes or constraint!

Kind regards,

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

10

Hi Ben, thanks for the reply. Before I try the newest patch with the
mentioned bug fixes, here is my GeoServer Logs error report and the 1.1.0
GetFeature request. This layer is pulling data from a shapefile.

logs_OpenLayersError.txt
<http://osgeo-org.1560.x6.nabble.com/file/n5075856/logs_OpenLayersError.txt&gt;

GetFeature20130903.xml
<http://osgeo-org.1560.x6.nabble.com/file/n5075856/GetFeature20130903.xml&gt;

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075856.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

11

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 mailing list archive at Nabble.com.

12

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:

&srsName=http://www.opengis.net/def/crs/EPSG/0/4326

to a GET request?

This should force reprojection to a latitude/longitude axis order; failure to reproject would indicate that there is something wrong with the configuration of the SRS of the data source. I am not sure where this should happen with a shapefile data source. I have not tested app-schema WMS with a shapefile.

In any case, try a GeoServer with Rini's patch and see if it resolves the problem.

Kind regards,
Ben.

On 03/09/13 23:29, christy@anonymised.com wrote:

Hi Ben, thanks for the reply. Before I try the newest patch with the
mentioned bug fixes, here is my GeoServer Logs error report and the 1.1.0
GetFeature request. This layer is pulling data from a shapefile.

logs_OpenLayersError.txt
<http://osgeo-org.1560.x6.nabble.com/file/n5075856/logs_OpenLayersError.txt&gt;

GetFeature20130903.xml
<http://osgeo-org.1560.x6.nabble.com/file/n5075856/GetFeature20130903.xml&gt;

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075856.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

13

Adding that to the request seems to work fine:

http://data.usgin.org/azgs_bedrock_geology/gsmlp/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=gsmlp:GeologicUnitView&maxFeatures=2&srsName=http://www.opengis.net/def/crs/EPSG/0/4326

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5076048.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

14

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 large224778>200000). Any help
there would be great....

On another front, in the 2.3.0 version of GeoServer that I've been using, it
appears that the WFS 1.1.0 app-schema GetFeature AND the WMS works fine, as
long as you indicate that the WMS is an image format and not OpenLayers.
Still will not display in OpenLayers. Hopefully that is the fix that's
covered in Rini's new release?

http://data.usgin.org/azgs_bedrock_geology/gsmlp/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=gsmlp:GeologicUnitView&maxFeatures=2

http://data.usgin.org/azgs_bedrock_geology/gsmlp/wms?service=WMS&version=1.1.0&request=GetMap&layers=gsmlp:GeologicUnitView&styles=&bbox=-114.81520329099993,31.33200514100008,-109.04450001699993,37.00378056300007&width=512&height=503&srs=EPSG:4326&format=image/png

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5076067.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

15

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@anonymised.com wrote:

Adding that to the request seems to work fine:

http://data.usgin.org/azgs_bedrock_geology/gsmlp/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=gsmlp:GeologicUnitView&maxFeatures=2&srsName=http://www.opengis.net/def/crs/EPSG/0/4326

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5076048.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

16

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, you will see a bunch of references starting with:
http://127.0.0.1:8080/azgs_bedrock_geology/

These links point to the client's loopback address and so the client cannot load these resources. The cause of the problem is that your GeoServer is behind an HTTP proxy (like apache) and does not know its real address; although proxies can rewrite HTTP headers, they do not typically rewrite the content of payloads. Setting your Global / Settings / Proxy Base URL to be the externally visible base URL http://data.usgin.org/azgs_bedrock_geology/ allows GeoServer to ensure that the OpenLayers JavaScript includes links that are usable by a remote client.

This should work since the fixing of this bug:
https://jira.codehaus.org/browse/GEOS-4930

Kind regards,
Ben.

On 05/09/13 01:03, christy@anonymised.com wrote:

On another front, in the 2.3.0 version of GeoServer that I've been using, it
appears that the WFS 1.1.0 app-schema GetFeature AND the WMS works fine, as
long as you indicate that the WMS is an image format and not OpenLayers.
Still will not display in OpenLayers. Hopefully that is the fix that's
covered in Rini's new release?

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

17

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@anonymised.com 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
java.lang.IllegalStateException: Form too large224778>200000). Any help
there would be great....

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

18

Christy,

that is an excellent result! Nice work.

Kind regards,
Ben.

On 05/09/13 01:03, christy@anonymised.com wrote:

http://data.usgin.org/azgs_bedrock_geology/gsmlp/wms?service=WMS&version=1.1.0&request=GetMap&layers=gsmlp:GeologicUnitView&styles=&bbox=-114.81520329099993,31.33200514100008,-109.04450001699993,37.00378056300007&width=512&height=503&srs=EPSG:4326&format=image/png

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

19

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: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5076259.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

20

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=WMS&version=1.3.0&request=GetCapabilities

And attached is a screen shot that the Proxy has been set, but is being
ignored:
<http://osgeo-org.1560.x6.nabble.com/file/n5076290/Proxy.jpg&gt;

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5076290.html
Sent from the GeoServer - User mailing list archive at Nabble.com.