self-hosted/postgis
self-hosted/postgis
1
0
Fork 0
mirror of https://git.osgeo.org/gitea/postgis/postgis synced 2024-10-23 08:32:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Put legacy.sql in varname tag so prints out as courier and stands out more. Some clarification on the geography/geometry choice question

Browse source 
git-svn-id: http://svn.osgeo.org/postgis/trunk@7336 b70326c6-7e19-0410-871a-916f4a2858ee
This commit is contained in:
Regina Obe 2011-06-07 13:04:23 +00:00
parent 4f98edfa67
commit d82984cacf
1 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/faq.xml
View file

@ -12,10 +12,10 @@
<para>A lot of deprecated functions were removed from the PostGIS code base in PostGIS 2.0. This has affected applications in addition to third-party tools such as
Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There are a couple of ways to resolve this. For the third-party apps, you can try to upgrade to the latest versions
of these which have many of these issues fixed. For your own code, you can change your code to not use the functions removed. Most of these functions are non ST_ aliases of ST_Union, ST_Length etc.
and as a last resort, install the whole of legacy.sql or just the
portions of legacy.sql you need.</para>
and as a last resort, install the whole of <varname>legacy.sql</varname> or just the
portions of <varname>legacy.sql</varname> you need.</para>
<para>The legacy.sql file is located in the same folder as postgis.sql. You can install this file after you have installed postgis.sql and spatial_ref_sys.sql
<para>The <varname>legacy.sql</varname> file is located in the same folder as postgis.sql. You can install this file after you have installed postgis.sql and spatial_ref_sys.sql
to get back all the 200 some-odd old functions we removed.</para>
</answer>
</qandaentry>
@ -82,12 +82,15 @@ SELECT MAX(ST_NPoints(geom)) FROM sometable;</programlisting>
</question>
<answer>
<para>Short Answer: geography is a new data type that supports long range distances measurements. If
<para>Short Answer: geography is a new data type that supports long range distances measurements, but most computations on it are currently
slower than they are on geometry. If
you use geography -- you don't need to learn much about planar coordinate systems. Geography is generally best
if all you care about is measuring distances and lengths and you have data from all over the world.
Geometry datatype is an older data type that has many functions supporting it and enjoys great support from third party tools.
Its best if you are pretty comfortable with spatial reference systems or you are dealing with localized data
Geometry data type is an older data type that has many more functions supporting it, enjoys greater support from third party tools,
and operations on it are generally faster -- sometimes as much as 10 fold faster for larger geometries.
Geometry is best if you are pretty comfortable with spatial reference systems or you are dealing with localized data
where all your data fits in a single <link linkend="spatial_ref_sys">spatial reference system (SRID)</link>, or you need to do a lot of spatial processing.
Note: It is fairly easy to do one-off conversions between the two types to gain the benefits of each.
Refer to <xref linkend="PostGIS_TypeFunctionMatrix" /> to see what is currently supported and what is not.
</para>
<para>