On Mon, May 28, 2012 at 7:59 PM, Justin Deoliveira <[email protected]> wrote: > Well my thought about the use case is not handling cases with pre-configured > layers such as this one but one that is fairily common one among our clients > that goes like this: > > 1. user (via rest api) posts a new layer to the server > 2. user gets xml representation of the new layer to get all configuration > info > 3. user uses config info, bounds, srs, etc... to make a proper OGC service > request
The change affects only the native srs, the declared one is filled by the rest api doing a full scan at line 384 of DataStoreFileResource, calling builder.lookupSRS(ftinfo, true); The native srs is something that we expose for mere information, but it's not what the clients should use, since the declared SRS is the one actually being exposed to services. The declared SRS is always going to be a code since it's hand filled from the GUI p.o.v., and forcefully filled by full scan by the rest API. Is there some use case that I'm missing? Cheers Andrea -- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 339 8844549 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
