Re: Use of LatLonPoint Object

Hi Karl,

The main reasons:

1) It's historical. The precursor to OpenMap had graphic objects that
were written that way, and it seemed like the right thing to do at the
time.

2) It's one less thing to allocate. We found that the data sources
provide the lat/lon as primitives, and it made more sense to simply pass
those values directly to the OMGraphic constructors, instead of creating
another object to pass instead. Also, for the polygon, the constructors
have been set up to work as efficiently as possible with the projection
objects, to get the best performance. If we used LatLonPoint arrays, it
would really slow things down to allocate all the LLP, and then roll
through them.

3) I know we didn't add constructors for LatLonPoints in order to
prevent the number of constructors getting too high for each OMGraphic
type.

Hope this helps,

Don

On Wednesday, October 24, 2001, at 12:07 PM, Karl Stuempfle wrote:

> I have been playing with creating different types of OMGraphics, and I
> have
> a question....
>
> Why is it that none of the OMGraphic types accept arrays of LatLonPoint
> (or
> DMSLatLonPoint) objects in their constructors? I am sure there is a
> reason,
> and I am just curious as to what it is.
>
> Karl...
>
>
> --
> [To unsubscribe to this list send an email to "majdart@bbn.com"
> with the following text in the BODY of the message "unsubscribe
> openmap-users"]
>
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Donald Dietrick, dietrick@bbn.com
BBN Technologies, Cambridge, MA
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

--
[To unsubscribe to this list send an email to "majdart@bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]