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 primary key. Not knowing this, when we created the mapping file for Geoserver app-schema, we did not indicate this objectid field anywhere. Yet it was still being read as a data field and being put into the first field (ObservationURI) regardless of what the mapping file said. Anyway, we assigned the objectid as the primary key in the table using PGAdmin and this cleared the issue. GetFeature requests are now correctly reading the data table and schema. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Re-App-Schema-Resolution-tp5040030p5043586.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
