[Dev] Fwd: proj4j experiments...

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Dev] Fwd: proj4j experiments...


---------- Forwarded message ----------
From: David Smiley <[hidden email]>
Date: Fri, Mar 23, 2012 at 9:27 AM
Subject: Re: proj4j experiments...
To: Ryan McKinley <[hidden email]>

On Mar 23, 2012, at 3:42 AM, Ryan McKinley wrote:

> On Wed, Mar 21, 2012 at 11:41 AM, [hidden email]
> <[hidden email]> wrote:
>> On Wed, Mar 21, 2012 at 2:23 PM, Ryan McKinley <[hidden email]> wrote:
>>> Overall we need to drop the idea of geo vs not -- perhaps isProjected?
>>>  There are thousands of 'geo' projections that are used all the time.
>>> WGS84 is the most common since it is used in GPS and gives reasonable
>>> results in the USA.  (Once you start dealing with shapes and distances
>>> in places like New Zealand, WGS84 is super distorted)
>> I am not clear on what you are trying to convey to me.  Of course there are
>> various geospatial projections and all aren't good for everything; I know
>> that.  Wouldn't your suggestion of "isProjected()==true" imply a geospatial
>> use?
> I'm trying to get away from the term 'geo' since it seems to apply to
> both the case where you need to use a projection or can simplify to
> flat.
> Things can be geographic, but not projected (think simple surveying... w/o GPS)

Okay.  But "projected", at least to me implies coordinate transformation.  Is this wrong?  There hasn't been any coordinate transformation thus far -- direct lat-lon interpretation, and so it's not projected, and thus not geo but it is geo?

dev mailing list
[hidden email]