On Thu, Oct 1, 2015 at 7:42 AM, Brad Hards <[email protected]> wrote:
> That does appear to work, but its way too slow - it makes the WMS module > build 6 times slower. > > So I'm thinking of caching results. However I need guidance on whether the > supported codes can possibly change at runtime? If it can change, can it > change in such a way that an existing EPSG code might stop or start > working? > Or will any runtime changes only be new codes? > Not at runtime, but there is an issue, the data dir used in tests is destroyed and rebuilt at every test run (for each class, not method). We could create a blacklist in the user_projections storage, that also has its own problems though, as supported EPSG codes evolve over time, and the data dirs are long lived. > > The other approach is to thin the list of codes that are provided by > GeoTools > to only those that will work (by a combination of removing those that can > never be supported by decode(), and fixing the cases that could be > supported). The problem is that it might still have plugged-in that are not > supportable, and there is a gap between "never supported" and "works > perfectly". > Right, that is another issue, everything in the projection subsystem is pluggable, which makes it hard to setup a query that would return only what's supported. I have witnessed installations that had custom plugins with extra projections support compared to the base GeoServer, for example. > > Another variation would be to have a whitelist of codes that are expected > to > work. That whitelist could be represented in GeoTools by a new function > (like CRS.getDecodeableCodes(String authority) or similar). That would be > a maintenance burden, and we'd lose support for things that might work. > > Any suggestions? > Err... I'm not sure I have a good solution... time ago there was this suggestion to have the WMS caps only report the list of CRS that are actually in use, plus some well known ones (e.g., 3857). This could be a flag in the WMS configuration, enabled by default in the release data directory. It would also have the nice side effect of stop troubling some lesser OGC clients, such as, you know, ArcGis Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -------------------------------------------------------
------------------------------------------------------------------------------
_______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
