Opened 11 years ago

Closed 11 years ago

#285 closed task (fixed)

FAQ When should I use geography over geometry

Reported by: robe Owned by: robe
Priority: medium Milestone: PostGIS 1.5.0
Component: postgis Version: master
Keywords: Cc:

Description

Someone asked me this and it sounds like a question we will be getting often from both novices as well as existing users.

I was thinking in the geography side of things -- could whip up a feature matrix (an autogenerated one with some xsl voodoo magic that)

For each function that takes as input geography/geometry mark off whether it supports geometry/geography like with T meaning it uses a geometry transform operation so not native and yes/no being native or non-existent. We can put a special tag in each function description to easily pull the transform question out.

function geometry geography ST_Buffer yes T ST_Distance yes yes ST_DWithin yes yes

Then we need the descriptive FAQ of what geometry/geography offers from a performance/use case perspective I guess. E.g. support by third party tools and loaders etc. What range (are you dealing with regional or all over the world) -- etc.

So kind of like a questionaire type thing to consider before using one or the other.

Attachments (1)

geography_howto.txt (7.4 KB) - added by pramsey 11 years ago.
Some content

Download all attachments as: .zip

Change History (6)

comment:1 Changed 11 years ago by robe

Owner: changed from pramsey to robe

I guess we should also decide where this should go.

Changed 11 years ago by pramsey

Attachment: geography_howto.txt added

Some content

comment:2 Changed 11 years ago by pramsey

Here's some content to integrate and close this ticket with :)

comment:3 Changed 11 years ago by pramsey

Summary: FAQ When should I user geography over geometryFAQ When should I use geography over geometry

comment:4 Changed 11 years ago by robe

Milestone: PostGIS 1.5.0PostGIS Future

I might get to incorporating Paul's changes, but not this week. Though I'm not sure the best place in the manual for this.

I'll move back out if I have time before release.

comment:5 Changed 11 years ago by robe

Milestone: PostGIS FuturePostGIS 1.5.0
Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.