Martin Desruisseaux ha scritto: > Andrea Aime a écrit : >> Can't set a value to the parameter "Latitude of natural origin". >> Can't set a value to the parameter "Scale factor at natural origin". > > May be missing aliases. I will look at that we I will have a chance.
Cool, thanks :-) ... >> No transform for classification "Tunisia Mining Grid". > > They are unimplemented map projections, except "Lambert Azimuthal Equal Area" > which is available only on trunk at this time. We need volunter time for > implementing the remaining ones. We can't expect those projections to be > implemented for Geotools 2.3. Yup, as I said, I did not foresee fixes for these. ... >> Type "north-west" is unknow in this context. > > The message is a little bit misleading. On trunk, I'm changing it for "Unknown > axis direction". This is related to http://jira.codehaus.org/browse/GEOT-936 > and > I started to work on it yesterday. I don't plan to port it to the 2.3 branch > however. > > This issue appears in map projections used for North or South poles. Instead > of > "East" and "North" axis directions, map projection has for example the > following > axis: > > * South along 180 deg > * South along 90 deg East > > The referencing module was not prepared to handle this kind of axis > directions, > so supporting them will need some though and will not be fixed in 2.3. I see. Good, no problem. > Geotools provides a hint for forcing units to decimal degrees: > Hints.FORCE_STANDARD_AXIS_UNITS. The idea is similar to > Hints.FORCE_LONGITUDE_FIRST_AXIS_ORDER. By default this hint is not set. > > I suspect that many GIS implementation ignore sexagesimal units and use > decimal > units instead, in the same way than they ignored the (latitude, longitude) > axis > order. However I would need a confirmation of that before changing the > default, > if we change it. Cool, I will enable that hint on geoserver startup too. > I'm not sure that we should change the default since many CRS using > sexagesimal > degrees in the EPSG database have been deprecated and replaced by an other CRS > using decimal degrees. So I assume that if a user ask for a deprecated CRS, he > know what he is doing. That's quite a leap of faith, users sometimes just fiddle around hoping things will start working as they expect :-) > Do we receive bug reports from users about the "Unit > conversion from DMS to ° is non-linear" exception? Nope. See the end of the mail thought >> Unsupported unit: 9120 > > They are different flavour of DMS units. Not all of them are supported, and I > do > not plan to support them shortly (it will be easier after we switch to the > JScience units framework). Ok, everything is cool. Ok, let me go back to the reason I added these error reports in Geoserver. At the moment, users are allowed to add custom projections in a separate file. Error reporting is important for those, so that the use may learn why a projection he added is not being shown by Geoserver. Is there any way to tell which authority did generate a certain CRS, so that I can report CRS decoding failures only for user provided ones? Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
