From: geowolf <and...@ge...> - 2011-04-29 13:17:34
|
mbedward wrote: > >> I see that both Ben and Christian voted it down though... with an >> invalid vote btw. >> Per our procedures everyone voting -1 has to provide an alternative, just >> saying >> "no" is not allowed: > > That rule seems harsh. If someone has good reasons for thinking that a > proposal is invalid or not practical, but have no alternative to > suggest immediately, how should they vote ? -1 seems most > appropriate. > These voting rules have been for a long time in the developer guide, as far as I rememeber they were introduced the day we introduced the concept of a proposal. We ask every new committer to review the developer guide, so one can legitimaltely assume the rule is known, I was just reminding of it. The rule has been set so that no one can down-vote a proposal out of a personal grudge or mere personal preference without having to put some (minimal) effort into it. Making a proposal requires effort, taking it down should require similar effort. It's your right to prepare a proposal asking that rule to be changed, if you indent to discuss if further please open a separate thread though, (just to avoid this one getting derailed in unrelated topics). > Within GeoTools itself I think a null CRS best communicates the idea > of no CRS. Not being a GeoServer user I don't understand the specifics > of this issue in that context. > I agree it's also a good idea... however it also means making even more effort than using CRS:1, try getting a transformation from null to any CRS or getting the EPSG code of "null" and you'll see what I mean. I don't have the time to follow this path. Just let me know if there is any chance of getting a EPSG code associated to a wildcard CRS in Geotools, if not I'll try in the GeoServer community, if that does not work either I'll make a private fork of the project for this instead of contributing to it (don't like either idea, just listing the options). Cheers Andrea-- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Adding-support-for-a-new-EPSG-code-EPSG-0-tp6312618p6316739.html Sent from the geotools-devel mailing list archive at Nabble.com. |