[mapserver-commits] r8080 - in trunk/docs/references: input
input/vector_data output
svn at osgeo.org
svn at osgeo.org
Mon Nov 24 15:00:04 EST 2008
Author: hobu
Date: 2008-11-24 15:00:04 -0500 (Mon, 24 Nov 2008)
New Revision: 8080
Added:
trunk/docs/references/input/index.txt
trunk/docs/references/input/vector_data/index.txt
trunk/docs/references/output/index.txt
Modified:
trunk/docs/references/input/vector_data/ArcInfo.txt
trunk/docs/references/input/vector_data/S57.txt
trunk/docs/references/input/vector_data/VirtualSpatialData.txt
trunk/docs/references/input/vector_data/arcsde.txt
trunk/docs/references/input/vector_data/dgn.txt
trunk/docs/references/input/vector_data/format_types.txt
trunk/docs/references/input/vector_data/gml.txt
trunk/docs/references/input/vector_data/inline.txt
trunk/docs/references/input/vector_data/kml.txt
trunk/docs/references/input/vector_data/mapinfo.txt
trunk/docs/references/input/vector_data/mygis.txt
trunk/docs/references/input/vector_data/ntf.txt
trunk/docs/references/input/vector_data/oracle_spatial.txt
trunk/docs/references/input/vector_data/pgeo.txt
trunk/docs/references/input/vector_data/postgis.txt
trunk/docs/references/input/vector_data/sdts.txt
trunk/docs/references/input/vector_data/shapefiles.txt
trunk/docs/references/input/vector_data/tiger.txt
trunk/docs/references/input/vector_data/wfs.txt
Log:
vector data guide
Added: trunk/docs/references/input/index.txt
===================================================================
--- trunk/docs/references/input/index.txt (rev 0)
+++ trunk/docs/references/input/index.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -0,0 +1,12 @@
+.. _input:
+
+*****************************************************************************
+ Data Input
+*****************************************************************************
+
+
+.. toctree::
+ :maxdepth: 2
+
+ vector_data/index
+ raster_data
Modified: trunk/docs/references/input/vector_data/ArcInfo.txt
===================================================================
--- trunk/docs/references/input/vector_data/ArcInfo.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/ArcInfo.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _arcinfo:
+
+*****************************************************************************
+ ArcInfo
+*****************************************************************************
+
ESRI ArcInfo Coverage Files are also known as simply as
Coverages and less commonly as ADF files.
Modified: trunk/docs/references/input/vector_data/S57.txt
===================================================================
--- trunk/docs/references/input/vector_data/S57.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/S57.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _s57:
+
+*****************************************************************************
+ S57
+*****************************************************************************
+
Also known as S57. The IHO S-57 format is a vector interchange
format used for maritime charts. It was developed by the International Hydrographic Organisation (IHO). For more information about the IHO see: http://www.iho.shom.fr/
Modified: trunk/docs/references/input/vector_data/VirtualSpatialData.txt
===================================================================
--- trunk/docs/references/input/vector_data/VirtualSpatialData.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/VirtualSpatialData.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _virtual_vector:
+
+*****************************************************************************
+ Virtual Spatial Data
+*****************************************************************************
+
.. contents:: Table of Contents
:depth: 2
:backlinks: top
Modified: trunk/docs/references/input/vector_data/arcsde.txt
===================================================================
--- trunk/docs/references/input/vector_data/arcsde.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/arcsde.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -9,35 +9,35 @@
commercial database management systems like Oracle, Microsoft SQL Server,
Sybase, IBM DB2, and Informix.
-What MapServer 5.0 currently supports with SDE
+Supported ArcSDE Operations
-------------------------------------------------------------------------------
- * Versioned queries (query geometry and attributes from a specified version)
- * queryByAttributes (select geometry and attributes based on the
- values of an attribute)
- * Limited join support for within-database tables</li>
- * queryByRect (select geometry based on an extent)
- * Projection on the fly
- * SDE for Coverages (a read-only type of SDE for coverage,
- shapefile, and ArcStorm/ArcLibrarian repositories)
- * SDE 8.1, 8.2, 8.3, 9.0, 9.1, and 9.2
- * Linux, Windows, and Solaris (platforms that have SDE C API support)
+* Versioned queries (query geometry and attributes from a specified version)
+* queryByAttributes (select geometry and attributes based on the
+ values of an attribute)
+* Limited join support for within-database tables</li>
+* queryByRect (select geometry based on an extent)
+* Projection on the fly
+* SDE for Coverages (a read-only type of SDE for coverage,
+ shapefile, and ArcStorm/ArcLibrarian repositories)
+* SDE 8.1, 8.2, 8.3, 9.0, 9.1, and 9.2
+* Linux, Windows, and Solaris (platforms that have SDE C API support)
-What MapServer 5.0 currently DOES NOT support with SDE:
+Unsupported ArcSDE Operations
-------------------------------------------------------------------------------
- * queryByShape (pass in a shape with MapScript and use it for queries)
- * Direct Connect (bypass SDE to connect directly to the database with the SDE C API)
+* queryByShape (pass in a shape with MapScript and use it for queries)
+* Direct Connect (bypass SDE to connect directly to the database with the SDE C API)
How to make a connection to SDE:
-------------------------------------------------------------------------------
- * Install the SDE C API client libraries for your platform (preferably
- matched to the server version you are using, ie 8.2 client -> 8.2 server,
- 8.3 client -> 8.3 server)
- * Compile MapServer with SDE support
- :ref:`MapServer Unix Compilation Howto <unix>` for specific details)
- * Define a LAYER block in a MapFile that uses SDE as the CONNECTIONTYPE
+* Install the SDE C API client libraries for your platform (preferably
+ matched to the server version you are using, ie 8.2 client -> 8.2 server,
+ 8.3 client -> 8.3 server)
+* Compile MapServer with SDE support
+ :ref:`MapServer Unix Compilation Howto <unix>` for specific details)
+* Define a LAYER block in a MapFile that uses SDE as the CONNECTIONTYPE
::
@@ -72,38 +72,38 @@
CONNECTION - Order is important!
...............................................................................
- * **sdemachine.iastate.edu** - The name of the machine you are connecting to.
- In some instances, this may need to be the IP address of the machine rather
- than the name if the server running MapServer is not configured to cascade DNS lookups
- * **port:5151** - The port number of SDE. The *port:* is important as SDE expects you
- to define the **service** in this slot, and it can be other names like **sde:oracle**
- (for direct connect) or **esri_sde** (for systems with port 5151 defined as
- esri_sde in /etc/services)
- * **sde** - The database username that the SDE server is using to connect to your
- database. It is often only important for SDE setups that are connecting to
- Oracle (and even then, not so important). Just leave it as **sde** if you don't
- know what it should be.
- * **username** - The username that will be connecting to SDE. This user must have
- been granted rights to select the layer that you will be specifying in the *DATA*
- directive. You can use ArcCatalog or the SDE command-line utilities to grant
- the appropriate rights to layers.
- * **password** - Password of the user connecting to SDE. **Case Sensitive**.
+* **sdemachine.iastate.edu** - The name of the machine you are connecting to.
+ In some instances, this may need to be the IP address of the machine rather
+ than the name if the server running MapServer is not configured to cascade DNS lookups
+* **port:5151** - The port number of SDE. The *port:* is important as SDE expects you
+ to define the **service** in this slot, and it can be other names like **sde:oracle**
+ (for direct connect) or **esri_sde** (for systems with port 5151 defined as
+ esri_sde in /etc/services)
+* **sde** - The database username that the SDE server is using to connect to your
+ database. It is often only important for SDE setups that are connecting to
+ Oracle (and even then, not so important). Just leave it as **sde** if you don't
+ know what it should be.
+* **username** - The username that will be connecting to SDE. This user must have
+ been granted rights to select the layer that you will be specifying in the *DATA*
+ directive. You can use ArcCatalog or the SDE command-line utilities to grant
+ the appropriate rights to layers.
+* **password** - Password of the user connecting to SDE. **Case Sensitive**.
DATA - Order is important!
...............................................................................
- * **HOBU.STATES_LAYER** - The layer name you are querying. This the *full*
- name of the table in which the layer resides. If you are using Oracle or
- Microsoft SQL Server as the DB for SDE, the schema name must also be supplied.
- * **SHAPE** - The column that contains the geometry. SDE technically allows
- for storage of multiple geometry types in the same layer, but in practice
- this isn't desirable. Also, expect to have problems if there are invalid
- or null geometries in the layer (or versions of the layer).
- * **SDE.DEFAULT** - As of MapServer 4.2, you can query against a specific
- version of the layer. SDE supports multi-user editing with versions. If a
- layer has been Registered with the GeoDatabase and Registered as Versioned
- (ArcGIS terms), MapServer can query against specified versions of those edits.
- If not specified, *SDE.DEFAULT* will be used for all queries. **Case Sensitive**.
+* **HOBU.STATES_LAYER** - The layer name you are querying. This the *full*
+ name of the table in which the layer resides. If you are using Oracle or
+ Microsoft SQL Server as the DB for SDE, the schema name must also be supplied.
+* **SHAPE** - The column that contains the geometry. SDE technically allows
+ for storage of multiple geometry types in the same layer, but in practice
+ this isn't desirable. Also, expect to have problems if there are invalid
+ or null geometries in the layer (or versions of the layer).
+* **SDE.DEFAULT** - As of MapServer 4.2, you can query against a specific
+ version of the layer. SDE supports multi-user editing with versions. If a
+ layer has been Registered with the GeoDatabase and Registered as Versioned
+ (ArcGIS terms), MapServer can query against specified versions of those edits.
+ If not specified, *SDE.DEFAULT* will be used for all queries. **Case Sensitive**.
.. note::
Note! this is located in a different spot than MapServer 4.2, which had
@@ -112,11 +112,11 @@
TEMPLATE
...............................................................................
- * **/where/the/template/file/is/located* - A template directive must be
- specified (can point to a dummy file) in order for MapServer to be able to
- query attributes from SDE. If you are only going to be drawing layers,
- this directive is unnecessary and will slow down the query operations of
- SDE (especially for layers with lots of attribute columns).
+* **/where/the/template/file/is/located* - A template directive must be
+ specified (can point to a dummy file) in order for MapServer to be able to
+ query attributes from SDE. If you are only going to be drawing layers,
+ this directive is unnecessary and will slow down the query operations of
+ SDE (especially for layers with lots of attribute columns).
PROCESSING
...............................................................................
@@ -125,7 +125,7 @@
WHERE clause that was defined in your FILTER statement first, without
attempting to hit the spatial index. Only in very special cases will
you want to do this.
-* **PROCESSING "OBJECTID=OBJECTID" - If you are having trouble with the
+* **PROCESSING "OBJECTID=OBJECTID"** - If you are having trouble with the
SDE driver detecting your unique ID column, you can override it with
this processing parameter. Doing so will also have a slight performance
benefit because it will save a couple of extra queries to the database.
@@ -146,12 +146,12 @@
activated through PROCESSING options.
- * **PROCESSING "JOINTABLE=SDE_MASTER.GEOSERVWRITE.JOINTABLE"* - The JOINTABLE
- processing option tells the driver which table you are joining the current layer to.
- * **CLASSITEM "SDE_MASTER.GEOSERVWRITE.JOINTABLE.VAL" - A CLASSITEM or LABELITEM
- for a joined table using this mechanism must be fully qualified.
- * **FILTER "SDE_MASTER.GEOSERVWRITE.JOINTABLE.AQ_TAG=SDE_MASTER.GEOSERVWRITE.JOINTESTLAYER.AQ_TAG" -
- An important part of the join is defining how the join is to be made.
- Use a FILTER to do so.
+* **PROCESSING "JOINTABLE=SDE_MASTER.GEOSERVWRITE.JOINTABLE"** - The JOINTABLE
+ processing option tells the driver which table you are joining the current layer to.
+* **CLASSITEM "SDE_MASTER.GEOSERVWRITE.JOINTABLE.VAL"** - A CLASSITEM or LABELITEM
+ for a joined table using this mechanism must be fully qualified.
+* **FILTER "SDE_MASTER.GEOSERVWRITE.JOINTABLE.AQ_TAG=SDE_MASTER.GEOSERVWRITE.JOINTESTLAYER.AQ_TAG"** -
+ An important part of the join is defining how the join is to be made.
+ Use a FILTER to do so.
.. ESRI: http://www.esri.com
Modified: trunk/docs/references/input/vector_data/dgn.txt
===================================================================
--- trunk/docs/references/input/vector_data/dgn.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/dgn.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _dgn:
+
+*****************************************************************************
+ DGN
+*****************************************************************************
+
File listing
-------------
Modified: trunk/docs/references/input/vector_data/format_types.txt
===================================================================
--- trunk/docs/references/input/vector_data/format_types.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/format_types.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,6 +1,9 @@
-Data Format Types
-------------------------------------
+.. _format_types:
+*****************************************************************************
+ Data Format Types
+*****************************************************************************
+
Each type of data is made up of a data source and (one or more) layers. These two definitions
apply to MapServer and OGR.
Modified: trunk/docs/references/input/vector_data/gml.txt
===================================================================
--- trunk/docs/references/input/vector_data/gml.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/gml.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _gml:
+
+*****************************************************************************
+ GML
+*****************************************************************************
+
Also known as Geographic Markup Language and GML/XML. GML is a text-based, XML format that can represent vector and attribute data. This is an Open Geospatial Consortium specification for data interchange. More information is available at http://www.opengeospatial.org/standards/gml
File listing
Added: trunk/docs/references/input/vector_data/index.txt
===================================================================
--- trunk/docs/references/input/vector_data/index.txt (rev 0)
+++ trunk/docs/references/input/vector_data/index.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -0,0 +1,96 @@
+.. _vector:
+
+*****************************************************************************
+ Vector Data
+*****************************************************************************
+
+:Date: 2008/09/09
+:Author: Tyler Mitchell
+:Contact: tmitchell at osgeo.org
+:Author: Jeff McKenna
+:Contact: jmckenna at gatewaygeomatics.com
+
+This work is licensed under the Creative Commons Attribution-ShareAlike License.
+To view a copy of this license, visit:
+http://creativecommons.org/licenses/by-sa/2.0/ca/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
+
+What is vector data? This quote from is a good description of what vector data is:
+
+.. pull-quote::
+ Vector: "An abstraction of the real world where positional data is
+ represented in the form of coordinates. In vector data, the basic units
+ of spatial information are points, lines and polygons. Each of these
+ units is composed simply as a series of one or more coordinate points.
+ For example, a line is a collection of related points, and a polygon is a
+ collection of related lines. Vector images are defined mathematically as a
+ series of points joined by lines. Vector-based drawings are resolution
+ independent. This means that they appear at the maximum resolution of the
+ output device, such as a printer or monitor. Each object is self-contained,
+ with properties such as color, shape, outline, size, and position on the
+ screen."
+
+ From: http://coris.noaa.gov/glossary/glossary_l_z.html#v
+
+
+MapServer can access vector file formats and database connections. It can also
+access raster or image data. This is a summary of the vector and database
+formats with particular focus on how to use them in a MapServer map file and
+access them using command line tools like **ogrinfo**.
+
+MapServer and vector data access
+------------------------------------
+
+MapServer has two main methods for accessing data:
+
+* Through built-in, format-specific, data access capabilities.
+
+.. note::
+ The most basic form of data access uses the built-in capabilities
+ that were linked into MapServer when it was compiled. These
+ capabilities are limited to only a few types of vector data,
+ such as ESRI Shapefile, PostGIS, Oracle Spatial and ArcSDE. The
+ default, built-in, format for MapServer is the ESRI Shapefile format.
+
+* Using the capabilities of third-party data access libraries.
+
+.. note::
+ One of the most powerful features of MapServer is the ability to use data
+ formats through a pseudo plug-in environment. The most significant
+ third party library being used is GDAL/OGR. This includes raster
+ (GDAL) and vector (OGR) data.
+
+Using OGR
+------------------------------------
+
+OGR is used behind the scenes by MapServer when requested. MapServer does not
+require OGR in order to run. Some users may never need the additional
+capabilities OGR offers, but many users find them absolutely necessary. Because
+MapServer is capable of accessing data via OGR, there is less need to program
+specific types of data format support directly into MapServer. Instead, further
+additions can be made to OGR and then be used by MapServer. In essence, the
+background libraries allow MapServer to bring the data into an internal,
+memory-based format that MapServer can use. For the most part, using
+OGR-related formats is seamless and intuitive.
+
+.. toctree::
+ :maxdepth: 1
+
+ format_types
+ format_introduction
+ arcsde
+ ArcInfo
+ pgeo
+ shapefiles
+ gml
+ S57
+ inline
+ kml
+ mapinfo
+ dgn
+ mygis
+ ntf
+ sdts
+ tiger
+ VirtualSpatialData
+ wfs
+
Modified: trunk/docs/references/input/vector_data/inline.txt
===================================================================
--- trunk/docs/references/input/vector_data/inline.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/inline.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _inline:
+
+*****************************************************************************
+ Inline
+*****************************************************************************
+
Inline features refer to coordinates entered directly into the map
file. They are not a file or database format and do not require any
DATA or CONNECTION parameters. Instead they use a FEATURE section
Modified: trunk/docs/references/input/vector_data/kml.txt
===================================================================
--- trunk/docs/references/input/vector_data/kml.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/kml.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,6 +1,9 @@
-Keyhole Markup Language (KML)
--------------------------------
+.. _kml:
+*****************************************************************************
+ KML - Keyhole Markup Language
+*****************************************************************************
+
Keyhole Markup Language (KML) is an XML-based language for managing the display of 3D geospatial data.
Modified: trunk/docs/references/input/vector_data/mapinfo.txt
===================================================================
--- trunk/docs/references/input/vector_data/mapinfo.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/mapinfo.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _mapinfo:
+
+*****************************************************************************
+ MapInfo
+*****************************************************************************
+
File listing
-----------------
Modified: trunk/docs/references/input/vector_data/mygis.txt
===================================================================
--- trunk/docs/references/input/vector_data/mygis.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/mygis.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _mygis:
+
+*****************************************************************************
+ MyGIS
+*****************************************************************************
+
MyGIS reference
---------------
The MyGIS reference documentation can be found at:
Modified: trunk/docs/references/input/vector_data/ntf.txt
===================================================================
--- trunk/docs/references/input/vector_data/ntf.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/ntf.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _ntf:
+
+*****************************************************************************
+ NTF
+*****************************************************************************
+
NTF files are mostly used by the United Kingdom Ordnance Survey (OS). For more on the Ordnance Survey, see their website at: http://www.ordnancesurvey.co.uk
File listing
Modified: trunk/docs/references/input/vector_data/oracle_spatial.txt
===================================================================
--- trunk/docs/references/input/vector_data/oracle_spatial.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/oracle_spatial.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _oci:
+
+*****************************************************************************
+ Oracle Spatial
+*****************************************************************************
+
MapServer can support Oracle Spatial through OGR. With this method, OGR must be compiled with Oracle Spatial support and MapServer must be compiled to use OGR.
In addition, MapServer also supports Oracle Spatial natively.
Modified: trunk/docs/references/input/vector_data/pgeo.txt
===================================================================
--- trunk/docs/references/input/vector_data/pgeo.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/pgeo.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,6 +1,9 @@
-ESRI Personal Geodatabase (MDB)
--------------------------------
+.. _pgeo:
+*****************************************************************************
+ ESRI Personal Geodatabase (MDB)
+*****************************************************************************
+
ESRI Personal Geodatabases are basically Microsoft Access files that contain spatial information. For more information see the ESRI `description page`_.
.. _`description page`: http://www.esri.com/software/arcgis/geodatabase/index.html
Modified: trunk/docs/references/input/vector_data/postgis.txt
===================================================================
--- trunk/docs/references/input/vector_data/postgis.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/postgis.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _postgis:
+
+*****************************************************************************
+ PostGIS/PostgreSQL
+*****************************************************************************
+
PostGIS/PostgreSQL
------------------
Modified: trunk/docs/references/input/vector_data/sdts.txt
===================================================================
--- trunk/docs/references/input/vector_data/sdts.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/sdts.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _sdts:
+
+*****************************************************************************
+ SDTS
+*****************************************************************************
+
This is a United States Geological Survey (USGS) format. SDTS has a raster and a vector format. The raster format is not supported in MapServer. Only the vector formats are supported, including VTP and DLG files.
File listing
Modified: trunk/docs/references/input/vector_data/shapefiles.txt
===================================================================
--- trunk/docs/references/input/vector_data/shapefiles.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/shapefiles.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,6 +1,9 @@
-ESRI Shapefiles (SHP)
-------------------------
+.. _shapefiles:
+*****************************************************************************
+ ESRI Shapefiles (SHP)
+*****************************************************************************
+
Also known as ESRI ArcView Shapefiles or ESRI Shapefiles. ESRI is the company
that introduced this format. ArcView was the first product to use shapefiles.
Modified: trunk/docs/references/input/vector_data/tiger.txt
===================================================================
--- trunk/docs/references/input/vector_data/tiger.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/tiger.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _tiger:
+
+*****************************************************************************
+ USGS TIGER
+*****************************************************************************
+
TIGER/Line files are created by the US Census Bureau and cover the
entire US. They are often referred simply as TIGER files. For more
information see: http://www.census.gov/geo/www/tiger/.
Modified: trunk/docs/references/input/vector_data/wfs.txt
===================================================================
--- trunk/docs/references/input/vector_data/wfs.txt 2008-11-24 19:30:52 UTC (rev 8079)
+++ trunk/docs/references/input/vector_data/wfs.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -1,3 +1,9 @@
+.. _wfs:
+
+*****************************************************************************
+ WFS
+*****************************************************************************
+
WFS is an Open Geospatial Consortium (OGC) specification. For more information about the format itself, see: http://www.opengeospatial.org/standards/wfs
WFS allows a client to retrieve geospatial data encoded in Geography Markup
Added: trunk/docs/references/output/index.txt
===================================================================
--- trunk/docs/references/output/index.txt (rev 0)
+++ trunk/docs/references/output/index.txt 2008-11-24 20:00:04 UTC (rev 8080)
@@ -0,0 +1,20 @@
+.. _output:
+
+*****************************************************************************
+ Output Generation
+*****************************************************************************
+
+
+.. toctree::
+ :maxdepth: 2
+
+ agg
+ antialias
+ dynamic_charting
+ flash
+ html_legend
+ imagemaps
+ pdf
+ svg
+ tile_mode
+
More information about the mapserver-commits
mailing list