Martin wrote: "was an independant effort and could probably be
replaced by existing ReferencedEnvelope"

Is there a task list or something similar where these housecleaning
items are tracked and delegated?

Landon

On Mon, May 19, 2008 at 3:46 PM, Sunburned Surveyor
<[EMAIL PROTECTED]> wrote:
> It looks like we have a tie between
> org.geotools.geometry.jts.ReferencedEnvelope and
> org.geotools.geometry.Envelope2D. :]
>
> I work a lot with JTS, so I'm tempted to use ReferencedEnvelope...I'm
> a little bit afraid of the ISO geometry stuff. Still, the Envelope2D
> class looks simple enough. Can anyone provide further clarification on
> how to proceed? (Who'd a thought finding an Envelope implementation in
> GeoTools would be so difficult? I think this is why I get lost in the
> GeoTools code so easily.)
>
> Landon
>
>
> On Mon, May 19, 2008 at 2:12 PM, Jody Garnett <[EMAIL PROTECTED]> wrote:
>> ReferencedEnvelope; the page is here:
>> - http://docs.codehaus.org/display/GEOTDOC/01+ReferencedEnvelope
>>
>> If you come from a JTS background: The implementation is a JTS Envelope, and
>> has a couple extra methods to match up some GeoAPI interfaces.
>> If yoy come from an ISO Geometry background: The implementation is a 2D
>> BoundingBox that has a couple methods, such as exapandsToInclude used when
>> collecting bounding information from features.
>>
>> Cheers,
>> Jody
>>
>> Sunburned Surveyor wrote:
>>>
>>> I noticed that the current GPX code in GeoTools defines the
>>> "BoundsType" class, which can be used to represent a rectangular
>>> bounding box. I was hoping I could identify a "universal" bounding box
>>> type commonly used in GeoTools that could be converted to/from or
>>> substituted for this class. I noticed in the GeoTools Javadoc (2.5
>>> branch) the following 5 classes that could be used to represent an
>>> envelope:
>>>
>>> Envelope
>>> Envelope2D
>>> EnvelopeExample
>>> org.geotools.geometry.iso.coordinate.EnvelopeImpl
>>> org.geometry.jts.spatialschema.geometry.EnvelopeImpl
>>>
>>> Is it possible these different envelope classes are represented by a
>>> single interface that I could reference in my code, or do I need to
>>> pick one? Could we refactor these 5 different classes into a single
>>> Envelope2D class/interface?
>>>
>>> Thanks,
>>>
>>> The Sunburned Surveyor
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft Defy all challenges.
>>> Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Geotools-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>
>>
>>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to