[postgis-devel] POINT(350, 100) == POINT(-10,80)

Paul Ramsey pramsey at cleverelephant.ca
Wed Sep 30 14:24:32 PDT 2009


what about -180 -> 360 as a range? or +/- 360 in both directions (theta/phi)

P

On Wed, Sep 30, 2009 at 1:58 PM, Chris Hodgson <chodgson at refractions.net> wrote:
> Hmm.. something that "automagically" takes my UTM coordinates in the
> 1,000,000 range and mod's it by 180 or 360 to get a lat or long value isn't
> really that helpful.
>
> Chris
>
> Kevin Neufeld wrote:
>>
>> Isn't this comparable in concept to auto type-casting?  The onus of type
>> casting in postgres was placed more heavily on the user to avoid any kind of
>> automagic-behind-the-scenes-unknown-manipulation-of-my-data.
>> -- Kevin
>>
>> Paul Ramsey wrote:
>>>
>>> Right now, in order to be allowed into the system, a GEOGRAPHY must
>>> have longitude in the range of -180,180 and latitude in the range of
>>> -90,90.
>>>
>>> I was just thinking that this restriction is pretty artificial, since
>>> I can coerce and theta (lon) and phi (lat) into the right ranges
>>> automatically. Any reason I should accept all numbers? Or maybe at
>>> least allow the range of -180,360 for longitude?
>>>
>>> P.
>>> _______________________________________________
>>> postgis-devel mailing list
>>> postgis-devel at postgis.refractions.net
>>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>



More information about the postgis-devel mailing list