Got an idea (feel free to shoot down). Right now I have a program that generates the function list <http://docs geotools function list> for the geotools docs, I keep meaning to add that into the maven build (so the docs are always up to date).
Could we do the same thing for a generated epsg-blacklist.properties? Idea would be to have each line be an sys code to "skip" and the value would be the reason why. EPSG:22300=No transform for classification "Tunisia Mining Grid" We could use the blacklist to "filter" the contents of the gt-epsh-hsql.jar to only those that are supportable by our reference implementation. -- Jody Garnett On 1 October 2015 at 05:10, Andrea Aime <[email protected]> wrote: > On Thu, Oct 1, 2015 at 1:26 PM, Brad Hards <[email protected]> wrote: > >> > 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). >> I'm less concerned that tests are slow, but more concerned that >> GetCapabilities becomes slow in production. >> > > Making tests slower is definitely not an option, they are already too slow, > we actually have spent code sprints (Vienna, 3 days) and several personal > hours > to make them faster in face of the growing system and growing number > of modules. On my machine GS il building in 12-13 minutes, without all > that effort we'd be around 20-30 minutes by now. > > Presumably those custom plugins work though, so the blacklist (or >> whitelist by >> exception) would only apply to those that we "know" about. Are the custom >> ones >> in the EPSG namespace? >> > > Sometimes they are, other times not, it's all over the place. > > >> >> > > 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. >> So the "Limited SRS list" would be the default. We could do a subset with >> no >> code changes, just by modifying the data dirs. >> >> It would need to cycle through all the layers to find out the CRS that >> are in >> use though. >> > > Indeed, it would require two cycles, one to generate the list of CRS, one > to > actually produce the caps document. > Unless the list is gathered once and then cached and maintained up to date > using catalog listeners. > > 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 > >
------------------------------------------------------------------------------
_______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
