Ciao Danilo, the native one is the one that is advertised by the underlying source, as such it what it is you can only override or reproject it afterwards. I mean the mechanism you are using has been put in place just because the underlying source has a strange or incorrect or without a valid EPSG code CRS. Regards, Simone Giannecchini == Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information. ==
Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- On Fri, Aug 30, 2013 at 7:43 PM, Danilo da Silveira Figueira <[email protected]> wrote: > My problem is that even after defining a custom CRS, this rule is not > automatically applyed to a new layer and the geoserver still recognizing as > an "UNKNOWN" Native SRS. I can use a custom SRS in the declared field, but > to fill this field the publisher have to know my custom EPSG number. > > There is any way to make the system fill automatically one these fields > ('Native SRS'/''Declared SRS') with my custom EPSG based on the WKT CRS? > > Thanks. ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
