[mapserver-commits] r11992 -
branches/branch-6-0/docs/en/input/vector trunk/docs/en/input/vector
svn at osgeo.org
svn at osgeo.org
Thu Aug 4 08:35:04 EDT 2011
Author: havatv
Date: 2011-08-04 05:35:04 -0700 (Thu, 04 Aug 2011)
New Revision: 11992
Modified:
branches/branch-6-0/docs/en/input/vector/postgis.txt
trunk/docs/en/input/vector/postgis.txt
Log:
Fixed the postgis documentation according to the suggestion in #2959. Also broke long lines and fixed some overfull lines in the PDF documentation (#3947)
Modified: branches/branch-6-0/docs/en/input/vector/postgis.txt
===================================================================
--- branches/branch-6-0/docs/en/input/vector/postgis.txt 2011-08-04 12:04:43 UTC (rev 11991)
+++ branches/branch-6-0/docs/en/input/vector/postgis.txt 2011-08-04 12:35:04 UTC (rev 11992)
@@ -23,22 +23,35 @@
Data Access /Connection Method
------------------------------
-PostGIS is supported directly by MapServer and must be compiled into MapServer to work.
+PostGIS is supported directly by MapServer and must be compiled into
+MapServer to work.
-The PostgreSQL client libraries (libpq.so or libpq.dll) must be present in the system's path environment for functionality to be present.
+The PostgreSQL client libraries (libpq.so or libpq.dll) must be
+present in the system's path environment for functionality to be
+present.
The CONNECTIONTYPE parameter must be set to POSTGIS.
-The CONNECTION parameter is used to specify the parameters to connect to the database. CONNECTION parameters can be in any order. Most are optional. dbname is required. user is required. host defaults to localhost, port defaults to 5432 (the standard port for PostgreSQL).
+The CONNECTION parameter is used to specify the parameters to connect
+to the database. CONNECTION parameters can be in any order. Most are
+optional. dbname is required. user is required. host defaults to
+localhost, port defaults to 5432 (the standard port for PostgreSQL).
-The DATA parameter is used to specify the data used to draw the map. The form of DATA is "[geometry_column] from [table_name|sql_subquery] using unique [unique_key] using srid=[spatial_reference_id]". The "using unique" and "using srid=" clauses are optional, but using them improves performance.
+The DATA parameter is used to specify the data used to draw the map.
+The form of DATA is "[geometry_column] from [table_name|sql_subquery]
+using unique [unique_key] using srid=[spatial_reference_id]". The
+"using unique" and "using srid=" clauses are optional when drawing
+features, but using them improves performance. If you want to make
+MapServer query calls to a PostGIS layer, your DATA parameter must
+include "using unique". Omitting it will cause the query to fail.
Here is a simple generic example:
::
CONNECTIONTYPE POSTGIS
- CONNECTION "host=yourhostname dbname=yourdatabasename user=yourdbusername password=yourdbpassword port=yourpgport"
+ CONNECTION "host=yourhostname dbname=yourdatabasename user=yourdbusername
+ password=yourdbpassword port=yourpgport"
DATA "geometrycolumn from yourtablename"
This example shows specifying the unique key and srid in the DATA line:
@@ -49,37 +62,56 @@
CONNECTION "dbname=yourdatabasename user=yourdbusername"
DATA "the_geom from the_database using unique gid using srid=4326"
-This example shows using a SQL subquery to perform a join inside the database and map the result in MapServer. Note the "as subquery" string in the statement -- everything between "from" and "using" is sent to the database for evaluation:
+This example shows using a SQL subquery to perform a join inside the
+database and map the result in MapServer. Note the "as subquery"
+string in the statement -- everything between "from" and "using" is
+sent to the database for evaluation:
::
CONNECTIONTYPE POSTGIS
CONNECTION "dbname=yourdatabasename user=yourdbusername"
- DATA "the_geom from (select g.gid, g.the_geom, a.attr1, a.attr2 from geotable g join attrtable a on g.gid = a.aid) as subquery unique gid using srid=4326"
+ DATA "the_geom from (select g.gid, g.the_geom, a.attr1, a.attr2 from
+ geotable g join attrtable a on g.gid = a.aid) as subquery
+ unique gid using srid=4326"
-This example shows using a geometry function and database sort to limit the number of features and vertices returned to MapServer:
+This example shows using a geometry function and database sort to
+limit the number of features and vertices returned to MapServer:
::
CONNECTIONTYPE POSTGIS
CONNECTION "dbname=yourdatabasename user=yourdbusername"
- DATA "the_geom from (select g.gid, ST_Simplify(g.the_geom, 10.0) as the_geom from geotable g order by ST_Area(g.the_geom) desc limit 10) as subquery unique gid using srid=4326"
+ DATA "the_geom from (select g.gid, ST_Simplify(g.the_geom, 10.0) as
+ the_geom from geotable g order by ST_Area(g.the_geom) desc
+ limit 10) as subquery unique gid using srid=4326"
-This example shows the use of the !BOX! substitution string to over-ride the default inclusion of the map bounding box in the SQL. By default the spatial box clause is appended to the SQL in the DATA clause, but you can use !BOX! to insert it anywhere you like in the statement. In general, you won't need to use !BOX!, because the PostgreSQL planner will generate the optimal plan from the generated SQL, but in some cases (complex sub-queries) a better plan can be generated by placing the !BOX! closer to the middle of the query:
+This example shows the use of the !BOX! substitution string to
+over-ride the default inclusion of the map bounding box in the SQL. By
+default the spatial box clause is appended to the SQL in the DATA
+clause, but you can use !BOX! to insert it anywhere you like in the
+statement. In general, you won't need to use !BOX!, because the
+PostgreSQL planner will generate the optimal plan from the generated
+SQL, but in some cases (complex sub-queries) a better plan can be
+generated by placing the !BOX! closer to the middle of the query:
::
CONNECTIONTYPE POSTGIS
CONNECTION "dbname=yourdatabasename user=yourdbusername"
- DATA "the_geom from (select g.gid, ST_Union(g.the_geom, 10.0) as the_geom from geotable g where ST_Intersects(g.geom,!BOX!)) as subquery unique gid using srid=4326"
+ DATA "the_geom from (select g.gid, ST_Union(g.the_geom, 10.0) as
+ the_geom from geotable g where ST_Intersects(g.geom,!BOX!)) as
+ subquery unique gid using srid=4326"
OGRINFO Examples
----------------
-OGRINFO can be used to read out metadata about PostGIS tables directly from the database.
+OGRINFO can be used to read out metadata about PostGIS tables directly
+from the database.
-First you should make sure that your GDAL/OGR build contains the PostgreSQL driver, by using the '--formats' command:
+First you should make sure that your GDAL/OGR build contains the
+PostgreSQL driver, by using the '--formats' command:
::
@@ -91,12 +123,14 @@
-> "MySQL" (read/write)
...
-If you don't have the driver, you might want to try the `FWTools`_ or `MS4W`_ packages, which include the driver.
+If you don't have the driver, you might want to try the `FWTools`_ or
+`MS4W`_ packages, which include the driver.
.. _`FWTools`: http://fwtools.maptools.org
.. _`MS4W`: http://www.maptools.org
-Once you have the driver you are ready to try an ogrinfo command on your database to get a list of spatial tables:
+Once you have the driver you are ready to try an ogrinfo command on
+your database to get a list of spatial tables:
::
@@ -108,7 +142,8 @@
::
- >ogrinfo PG:"host=127.0.0.1 user=postgres password=postgres dbname=canada port=5432" province -summary
+ >ogrinfo PG:"host=127.0.0.1 user=postgres password=postgres dbname=canada port=5432"
+ province -summary
INFO: Open of `PG:host=127.0.0.1 user=postgres password=postgres dbname=canada'
using driver `PostgreSQL' successful.
@@ -144,19 +179,25 @@
END
END
-For more info about PostGIS and MapServer see the PostGIS docs: http://postgis.org/documentation/
+For more info about PostGIS and MapServer see the PostGIS docs:
+http://postgis.org/documentation/
Support for SQL/MM Curves
-------------------------
-PostGIS is able to store circular interpolated curves, as part of the SQL Multimedia Applications
-Spatial specification (read about the `SQL/MM specification <http://subs.emis.de/LNI/Proceedings/Proceedings26/GI-Proceedings.26-17.pdf>`__).
-For more information about PostGIS' support, see the *SQL-MM Part 3* section in the PostGIS documentation, such
-as `here <http://www.postgis.org/documentation/manual-1.5/ch04.html#SQL_MM_Part3>`__.
+PostGIS is able to store circular interpolated curves, as part of the
+SQL Multimedia Applications Spatial specification (read about the
+`SQL/MM specification
+<http://subs.emis.de/LNI/Proceedings/Proceedings26/GI-Proceedings.26-17.pdf>`__).
-As of MapServer 6.0, the PostGIS features CircularString, CompoundCurve, CurvePolygon, MultiCurve, and MultiSurface can be
-drawn through MapServer directly.
+For more information about PostGIS' support, see the *SQL-MM Part 3*
+section in the PostGIS documentation, such as `here
+<http://www.postgis.org/documentation/manual-1.5/ch04.html#SQL_MM_Part3>`__.
+As of MapServer 6.0, the PostGIS features CircularString,
+CompoundCurve, CurvePolygon, MultiCurve, and MultiSurface can be drawn
+through MapServer directly.
+
Example#1: CircularString in MapServer
######################################
@@ -164,7 +205,8 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0)', -1), 2);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('CIRCULARSTRING(0 0,
+ 4 0, 4 4, 0 4, 0 0)', -1), 2);
An example MapServer layer might look like:
@@ -196,7 +238,8 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('COMPOUNDCURVE(CIRCULARSTRING(0 0, 1 1, 1 0),(1 0, 0 1))', -1), 3);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('COMPOUNDCURVE(
+ CIRCULARSTRING(0 0, 1 1, 1 0),(1 0, 0 1))', -1), 3);
An example MapServer layer might look like:
@@ -228,7 +271,9 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('CURVEPOLYGON(CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0),(1 1, 3 3, 3 1, 1 1))', -1), 4);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('CURVEPOLYGON(
+ CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0),(1 1, 3 3,
+ 3 1, 1 1))', -1), 4);
An example MapServer layer might look like:
@@ -260,7 +305,8 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('MULTICURVE((0 0, 5 5),CIRCULARSTRING(4 0, 4 4, 8 4))', -1), 6);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('MULTICURVE((0 0,
+ 5 5),CIRCULARSTRING(4 0, 4 4, 8 4))', -1), 6);
An example MapServer layer might look like:
@@ -292,7 +338,10 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('MULTISURFACE(CURVEPOLYGON(CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0),(1 1, 3 3, 3 1, 1 1)),((10 10, 14 12, 11 10, 10 10),(11 11, 11.5 11, 11 11.5, 11 11)))', -1), 7);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('MULTISURFACE(
+ CURVEPOLYGON(CIRCULARSTRING(0 0, 4 0, 4 4, 0 4,
+ 0 0),(1 1, 3 3, 3 1, 1 1)),((10 10, 14 12, 11 10,
+ 10 10),(11 11, 11.5 11, 11 11.5, 11 11)))', -1), 7);
An example MapServer layer might look like:
@@ -331,7 +380,9 @@
TYPE POLYGON
CONNECTIONTYPE postgis
CONNECTION "user=postgres password=postgres dbname=curves host=localhost port=5432"
- DATA "wkb_geometry from (select c.id, ST_CurveToLine(c.g) as wkb_geometry from c) as subquery using unique id using SRID=-1"
+ DATA "wkb_geometry from (select c.id, ST_CurveToLine(c.g) as
+ wkb_geometry from c) as subquery using
+ unique id using SRID=-1"
CLASS
STYLE
COLOR 128 128 128
@@ -345,4 +396,4 @@
-
\ No newline at end of file
+
Modified: trunk/docs/en/input/vector/postgis.txt
===================================================================
--- trunk/docs/en/input/vector/postgis.txt 2011-08-04 12:04:43 UTC (rev 11991)
+++ trunk/docs/en/input/vector/postgis.txt 2011-08-04 12:35:04 UTC (rev 11992)
@@ -23,22 +23,35 @@
Data Access /Connection Method
------------------------------
-PostGIS is supported directly by MapServer and must be compiled into MapServer to work.
+PostGIS is supported directly by MapServer and must be compiled into
+MapServer to work.
-The PostgreSQL client libraries (libpq.so or libpq.dll) must be present in the system's path environment for functionality to be present.
+The PostgreSQL client libraries (libpq.so or libpq.dll) must be
+present in the system's path environment for functionality to be
+present.
The CONNECTIONTYPE parameter must be set to POSTGIS.
-The CONNECTION parameter is used to specify the parameters to connect to the database. CONNECTION parameters can be in any order. Most are optional. dbname is required. user is required. host defaults to localhost, port defaults to 5432 (the standard port for PostgreSQL).
+The CONNECTION parameter is used to specify the parameters to connect
+to the database. CONNECTION parameters can be in any order. Most are
+optional. dbname is required. user is required. host defaults to
+localhost, port defaults to 5432 (the standard port for PostgreSQL).
-The DATA parameter is used to specify the data used to draw the map. The form of DATA is "[geometry_column] from [table_name|sql_subquery] using unique [unique_key] using srid=[spatial_reference_id]". The "using unique" and "using srid=" clauses are optional, but using them improves performance.
+The DATA parameter is used to specify the data used to draw the map.
+The form of DATA is "[geometry_column] from [table_name|sql_subquery]
+using unique [unique_key] using srid=[spatial_reference_id]". The
+"using unique" and "using srid=" clauses are optional when drawing
+features, but using them improves performance. If you want to make
+MapServer query calls to a PostGIS layer, your DATA parameter must
+include "using unique". Omitting it will cause the query to fail.
Here is a simple generic example:
::
CONNECTIONTYPE POSTGIS
- CONNECTION "host=yourhostname dbname=yourdatabasename user=yourdbusername password=yourdbpassword port=yourpgport"
+ CONNECTION "host=yourhostname dbname=yourdatabasename user=yourdbusername
+ password=yourdbpassword port=yourpgport"
DATA "geometrycolumn from yourtablename"
This example shows specifying the unique key and srid in the DATA line:
@@ -49,37 +62,56 @@
CONNECTION "dbname=yourdatabasename user=yourdbusername"
DATA "the_geom from the_database using unique gid using srid=4326"
-This example shows using a SQL subquery to perform a join inside the database and map the result in MapServer. Note the "as subquery" string in the statement -- everything between "from" and "using" is sent to the database for evaluation:
+This example shows using a SQL subquery to perform a join inside the
+database and map the result in MapServer. Note the "as subquery"
+string in the statement -- everything between "from" and "using" is
+sent to the database for evaluation:
::
CONNECTIONTYPE POSTGIS
CONNECTION "dbname=yourdatabasename user=yourdbusername"
- DATA "the_geom from (select g.gid, g.the_geom, a.attr1, a.attr2 from geotable g join attrtable a on g.gid = a.aid) as subquery unique gid using srid=4326"
+ DATA "the_geom from (select g.gid, g.the_geom, a.attr1, a.attr2 from
+ geotable g join attrtable a on g.gid = a.aid) as subquery
+ unique gid using srid=4326"
-This example shows using a geometry function and database sort to limit the number of features and vertices returned to MapServer:
+This example shows using a geometry function and database sort to
+limit the number of features and vertices returned to MapServer:
::
CONNECTIONTYPE POSTGIS
CONNECTION "dbname=yourdatabasename user=yourdbusername"
- DATA "the_geom from (select g.gid, ST_Simplify(g.the_geom, 10.0) as the_geom from geotable g order by ST_Area(g.the_geom) desc limit 10) as subquery unique gid using srid=4326"
+ DATA "the_geom from (select g.gid, ST_Simplify(g.the_geom, 10.0) as
+ the_geom from geotable g order by ST_Area(g.the_geom) desc
+ limit 10) as subquery unique gid using srid=4326"
-This example shows the use of the !BOX! substitution string to over-ride the default inclusion of the map bounding box in the SQL. By default the spatial box clause is appended to the SQL in the DATA clause, but you can use !BOX! to insert it anywhere you like in the statement. In general, you won't need to use !BOX!, because the PostgreSQL planner will generate the optimal plan from the generated SQL, but in some cases (complex sub-queries) a better plan can be generated by placing the !BOX! closer to the middle of the query:
+This example shows the use of the !BOX! substitution string to
+over-ride the default inclusion of the map bounding box in the SQL. By
+default the spatial box clause is appended to the SQL in the DATA
+clause, but you can use !BOX! to insert it anywhere you like in the
+statement. In general, you won't need to use !BOX!, because the
+PostgreSQL planner will generate the optimal plan from the generated
+SQL, but in some cases (complex sub-queries) a better plan can be
+generated by placing the !BOX! closer to the middle of the query:
::
CONNECTIONTYPE POSTGIS
CONNECTION "dbname=yourdatabasename user=yourdbusername"
- DATA "the_geom from (select g.gid, ST_Union(g.the_geom, 10.0) as the_geom from geotable g where ST_Intersects(g.geom,!BOX!)) as subquery unique gid using srid=4326"
+ DATA "the_geom from (select g.gid, ST_Union(g.the_geom, 10.0) as
+ the_geom from geotable g where ST_Intersects(g.geom,!BOX!)) as
+ subquery unique gid using srid=4326"
OGRINFO Examples
----------------
-OGRINFO can be used to read out metadata about PostGIS tables directly from the database.
+OGRINFO can be used to read out metadata about PostGIS tables directly
+from the database.
-First you should make sure that your GDAL/OGR build contains the PostgreSQL driver, by using the '--formats' command:
+First you should make sure that your GDAL/OGR build contains the
+PostgreSQL driver, by using the '--formats' command:
::
@@ -91,12 +123,14 @@
-> "MySQL" (read/write)
...
-If you don't have the driver, you might want to try the `FWTools`_ or `MS4W`_ packages, which include the driver.
+If you don't have the driver, you might want to try the `FWTools`_ or
+`MS4W`_ packages, which include the driver.
.. _`FWTools`: http://fwtools.maptools.org
.. _`MS4W`: http://www.maptools.org
-Once you have the driver you are ready to try an ogrinfo command on your database to get a list of spatial tables:
+Once you have the driver you are ready to try an ogrinfo command on
+your database to get a list of spatial tables:
::
@@ -108,7 +142,8 @@
::
- >ogrinfo PG:"host=127.0.0.1 user=postgres password=postgres dbname=canada port=5432" province -summary
+ >ogrinfo PG:"host=127.0.0.1 user=postgres password=postgres dbname=canada port=5432"
+ province -summary
INFO: Open of `PG:host=127.0.0.1 user=postgres password=postgres dbname=canada'
using driver `PostgreSQL' successful.
@@ -144,19 +179,25 @@
END
END
-For more info about PostGIS and MapServer see the PostGIS docs: http://postgis.org/documentation/
+For more info about PostGIS and MapServer see the PostGIS docs:
+http://postgis.org/documentation/
Support for SQL/MM Curves
-------------------------
-PostGIS is able to store circular interpolated curves, as part of the SQL Multimedia Applications
-Spatial specification (read about the `SQL/MM specification <http://subs.emis.de/LNI/Proceedings/Proceedings26/GI-Proceedings.26-17.pdf>`__).
-For more information about PostGIS' support, see the *SQL-MM Part 3* section in the PostGIS documentation, such
-as `here <http://www.postgis.org/documentation/manual-1.5/ch04.html#SQL_MM_Part3>`__.
+PostGIS is able to store circular interpolated curves, as part of the
+SQL Multimedia Applications Spatial specification (read about the
+`SQL/MM specification
+<http://subs.emis.de/LNI/Proceedings/Proceedings26/GI-Proceedings.26-17.pdf>`__).
-As of MapServer 6.0, the PostGIS features CircularString, CompoundCurve, CurvePolygon, MultiCurve, and MultiSurface can be
-drawn through MapServer directly.
+For more information about PostGIS' support, see the *SQL-MM Part 3*
+section in the PostGIS documentation, such as `here
+<http://www.postgis.org/documentation/manual-1.5/ch04.html#SQL_MM_Part3>`__.
+As of MapServer 6.0, the PostGIS features CircularString,
+CompoundCurve, CurvePolygon, MultiCurve, and MultiSurface can be drawn
+through MapServer directly.
+
Example#1: CircularString in MapServer
######################################
@@ -164,7 +205,8 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0)', -1), 2);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('CIRCULARSTRING(0 0,
+ 4 0, 4 4, 0 4, 0 0)', -1), 2);
An example MapServer layer might look like:
@@ -196,7 +238,8 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('COMPOUNDCURVE(CIRCULARSTRING(0 0, 1 1, 1 0),(1 0, 0 1))', -1), 3);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('COMPOUNDCURVE(
+ CIRCULARSTRING(0 0, 1 1, 1 0),(1 0, 0 1))', -1), 3);
An example MapServer layer might look like:
@@ -228,7 +271,9 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('CURVEPOLYGON(CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0),(1 1, 3 3, 3 1, 1 1))', -1), 4);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('CURVEPOLYGON(
+ CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0),(1 1, 3 3,
+ 3 1, 1 1))', -1), 4);
An example MapServer layer might look like:
@@ -260,7 +305,8 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('MULTICURVE((0 0, 5 5),CIRCULARSTRING(4 0, 4 4, 8 4))', -1), 6);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('MULTICURVE((0 0,
+ 5 5),CIRCULARSTRING(4 0, 4 4, 8 4))', -1), 6);
An example MapServer layer might look like:
@@ -292,7 +338,10 @@
::
- INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('MULTISURFACE(CURVEPOLYGON(CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0),(1 1, 3 3, 3 1, 1 1)),((10 10, 14 12, 11 10, 10 10),(11 11, 11.5 11, 11 11.5, 11 11)))', -1), 7);
+ INSERT INTO test ( g, id ) VALUES ( ST_GeomFromText('MULTISURFACE(
+ CURVEPOLYGON(CIRCULARSTRING(0 0, 4 0, 4 4, 0 4,
+ 0 0),(1 1, 3 3, 3 1, 1 1)),((10 10, 14 12, 11 10,
+ 10 10),(11 11, 11.5 11, 11 11.5, 11 11)))', -1), 7);
An example MapServer layer might look like:
@@ -331,7 +380,9 @@
TYPE POLYGON
CONNECTIONTYPE postgis
CONNECTION "user=postgres password=postgres dbname=curves host=localhost port=5432"
- DATA "wkb_geometry from (select c.id, ST_CurveToLine(c.g) as wkb_geometry from c) as subquery using unique id using SRID=-1"
+ DATA "wkb_geometry from (select c.id, ST_CurveToLine(c.g) as
+ wkb_geometry from c) as subquery using
+ unique id using SRID=-1"
CLASS
STYLE
COLOR 128 128 128
@@ -345,4 +396,4 @@
-
\ No newline at end of file
+
More information about the mapserver-commits
mailing list