[
http://jira.codehaus.org/browse/GEOT-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jody Garnett reopened GEOT-3045:
--------------------------------
Test case supplied so I can now reproduce the problem as reported.
> GeneralEnvelope constructed as isNull
> -------------------------------------
>
> Key: GEOT-3045
> URL: http://jira.codehaus.org/browse/GEOT-3045
> Project: GeoTools
> Issue Type: Improvement
> Components: core referencing
> Affects Versions: 2.6.3
> Reporter: Jody Garnett
> Assignee: Jody Garnett
> Fix For: 2.6.4, 2.7-M0
>
>
> From email:
> {panel}
> Hello there
> I found out what seems to be a strange behavior in public
> GeneralEnvelope(final Envelope envelope) (the constructor that receives
> another envelope as an argument, GeneralEnvelope.java line 178).
> What happens is that it simply throws an exception if the provided Envelope
> is a null Envelope (that is, [0,0,-1,-1]). And that exception happens
> because it explicitly calls a checkCoordinates() method that
> throws the exception if xmin >= xmax or ymin >= ymax.
> So, questions are:
> - Should GeneralEnvelope be "general" enough to handle the null Envelope
> case? (I'd say it should)
> - How should it manage it? Which comes to the question of what's the real
> intention when calling that checkCoodinates() method.
> Cheers
> Milton
> {panel}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
