If I run the gs:IntersectionFeatureCollection process over 2 vector layers (both defined in GeoServer and stored in PostGIS DB) with different geometry names, I get the following error:
An error occurred while encoding the results of the process Property 'way' could not be found in simple_layer_1 If I change the geometry column name (or make an alias in a view) in either of this two layers to match the geometry column name of the other layer, the process works as expected (no error).
In the GeoServer's WPS Request Builder I'm not able to set the geometry column names for each layer. Also, I can't find any mention of this limitation in the Boundless's documentation.
I'm just starting to learn how to use WPS and i guess I must be missing something.
I'm using:
gs:IntersectionFeatureCollection first feature collection second feature collection result The structure of the simple_layer_1 table:
Column | Type ------------+---------------------- gid | integer id | integer atr_string | character varying(80) atr_decima | double precision the_geom | geometry(Polygon) The table planet_osm_polygon_goo is an OpenStreetMaps polygons table, imported using the osm2pgsql. It has A LOT of attributes, which is why I'm not including the whole structure here. It's geometry attribute name is "way".
To recap after such a long post: is it possible to use the gs:IntersectionFeatureCollection process with two vector layers having different geometry attribute names?
Thanks a lot!
أكثر...
An error occurred while encoding the results of the process Property 'way' could not be found in simple_layer_1 If I change the geometry column name (or make an alias in a view) in either of this two layers to match the geometry column name of the other layer, the process works as expected (no error).
In the GeoServer's WPS Request Builder I'm not able to set the geometry column names for each layer. Also, I can't find any mention of this limitation in the Boundless's documentation.
I'm just starting to learn how to use WPS and i guess I must be missing something.
I'm using:
- GeoServer 2.7.0 with WPS and WPS Hazelcast extensions
- PostgreSQL 9.4 with PostGIS 2.1.7 r13414
gs:IntersectionFeatureCollection first feature collection second feature collection result The structure of the simple_layer_1 table:
Column | Type ------------+---------------------- gid | integer id | integer atr_string | character varying(80) atr_decima | double precision the_geom | geometry(Polygon) The table planet_osm_polygon_goo is an OpenStreetMaps polygons table, imported using the osm2pgsql. It has A LOT of attributes, which is why I'm not including the whole structure here. It's geometry attribute name is "way".
To recap after such a long post: is it possible to use the gs:IntersectionFeatureCollection process with two vector layers having different geometry attribute names?
Thanks a lot!
أكثر...