Hi Justin, Beginning of this year, with your help, we were able to use Geoserver's REST API.
Requirements on the project changed and we had to change our base layers to google maps and as a result we had to project our Geoserver layers(created via rest) from 4326 to mercator(google base layer's SRS). Projecting any layer that is in Geoserver is not an issue as long as the layer is not created via the REST API. I see that layers that gets created via the REST API don't have the feature attributes(in our case we are using postgis and this means the field names) in the featuretype.xml (feature type attributes also don't populate in GUI...see GUI pic). But if a layer is created using GUI, the GUI as well as the featuretype.xml will have the attributes. Surprisingly, the absence of this features is the only issue that is creating the projection issue explained above for all the Layers created via the REST API. Infact adding the attributes to the xml file fixes the projection issue. Is there a work around to make sure that the feature attributes will be added when creating layers via the REST API? http://osgeo-org.1803224.n2.nabble.com/file/n6668163/geoserver_GUI.png -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Update-feature-type-with-REST-API-tp6107794p6668163.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
