[mapserver-commits] r8221 - trunk/docs/input/vector
svn at osgeo.org
svn at osgeo.org
Tue Dec 9 15:36:57 EST 2008
Author: hobu
Date: 2008-12-09 15:36:57 -0500 (Tue, 09 Dec 2008)
New Revision: 8221
Removed:
trunk/docs/input/vector/formats_intro.txt
Modified:
trunk/docs/input/vector/format_types.txt
trunk/docs/input/vector/index.txt
Log:
clean up organization of vector data doc a bit
Modified: trunk/docs/input/vector/format_types.txt
===================================================================
--- trunk/docs/input/vector/format_types.txt 2008-12-09 20:34:47 UTC (rev 8220)
+++ trunk/docs/input/vector/format_types.txt 2008-12-09 20:36:57 UTC (rev 8221)
@@ -4,16 +4,18 @@
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.
+Each type of data is made up of a data source and (one or more) layers. These
+two definitions apply to MapServer and OGR.
-**Data Source** - a group of layers stored in a common repository. This may be a file that
-handles several layers within it, or a folder that has several files.
+**Data Source** - a group of layers stored in a common repository. This may be
+a file that handles several layers within it, or a folder that has several
+files.
-**Layer** - a sub-set of a data source often containing information in one type of vector format (point, line, polygon).
+**Layer** - a sub-set of a data source often containing information in one
+type of vector format (point, line, polygon).
-There are three types of data mapping and GIS data formats. Each type is handled differently.
-Below are the types and some example formats:
+There are three types of data mapping and GIS data formats. Each type is
+handled differently. Below are the types and some example formats:
* File-based- Shapefiles, Microstation Design Files (DGN), GeoTIFF images
* Directory-based - ESRI ArcInfo Coverages, US Census TIGER
@@ -22,65 +24,75 @@
File-based Data
------------------------------------
-File-based data consists of one or more files stored in any arbitrary folder. In many cases
-a single file is used (e.g. DGN) but ESRI Shapefiles, for example, consist of at least 3
-files each with a different filename extension: SHP, DBF, SHX. In this case all 3 files
-are required because they each perform a different task internally.
+File-based data consists of one or more files stored in any arbitrary folder.
+In many cases a single file is used (e.g. DGN) but ESRI Shapefiles, for
+example, consist of at least 3 files each with a different filename extension:
+SHP, DBF, SHX. In this case all 3 files are required because they each perform
+a different task internally.
-Filenames usually serve as the data source name and contain layers that may or may not be
-obvious from the filename. In Shapefiles, for example, there is one data source per
-shapefile and one layer which has the same name as that of the file.
+Filenames usually serve as the data source name and contain layers that may or
+may not be obvious from the filename. In Shapefiles, for example, there is one
+data source per shapefile and one layer which has the same name as that of the
+file.
Directory-based Data
------------------------------------
-Directory-based data consists of one or more files stored in a particular way within a
-parent folder. In some cases (e.g. Coverages) they may also require additional folders
-in other locations in the file tree in order to be accessed. The directory itself may
-be the data source. Different files within the directory often represent the layers of
-data available.
+Directory-based data consists of one or more files stored in a particular way
+within a parent folder. In some cases (e.g. Coverages) they may also require
+additional folders in other locations in the file tree in order to be
+accessed. The directory itself may be the data source. Different files within
+the directory often represent the layers of data available.
-For example, ESRI ArcInfo Coverages consist of more than one file with an ADF file
-extension, within a folder. The PAL.ADF file represents the Polygon data. ARC.ADF
-holds the arc or line string data. The folder holds the data source and each ADF file
-is a layer.
+For example, ESRI ArcInfo Coverages consist of more than one file with an ADF
+file extension, within a folder. The PAL.ADF file represents the Polygon data.
+ARC.ADF holds the arc or line string data. The folder holds the data source
+and each ADF file is a layer.
Database Connections
------------------------------------
-Database Connections are very similar to file and directory-based structures in one
-respect: they provide geographic coordinate data for MapServer to interpret. That may
-be oversimplifying what is happening inside MapServer, but in essence all you need is
-access to the coordinates making up the vector datasets.
+Database Connections are very similar to file and directory-based structures
+in one respect: they provide geographic coordinate data for MapServer to
+interpret. That may be oversimplifying what is happening inside MapServer, but
+in essence all you need is access to the coordinates making up the vector
+datasets.
-Database connections provide a stream of coordinate data that is temporarily stored
-(e.g. in memory) and read by MapServer to create the map. Other attribute or tabular
-data may also be required, but the focus of this guide is coordinate data.
+Database connections provide a stream of coordinate data that is temporarily
+stored (e.g. in memory) and read by MapServer to create the map. Other
+attribute or tabular data may also be required, but the focus of this guide is
+coordinate data.
-One important distinction between databases must be made. The databases discuss here
-are spatial databases, those which can hold geographic data in its own data type.
-This is opposed to strictly tabular databases which cannot hold geographic coordinates
-in the same way. It is possible to store some very simple coordinate data in regular
-tables, but for anything but the most simple use a spatial database is required.
-There are spatial extensions to many databases (open source and commercial). One of
-the most robust is the PostGIS extension to the PostgreSQL database. This database
-not only allows the storage of geographic data, but also allows the manipulation of
-that data using SQL commands. The other open source database with spatial
-capabilities is MySQL.
+One important distinction between databases must be made. The databases
+discuss here are spatial databases, those which can hold geographic data in
+its own data type. This is opposed to strictly tabular databases which cannot
+hold geographic coordinates in the same way. It is possible to store some very
+simple coordinate data in regular tables, but for anything but the most simple
+use a spatial database is required. There are spatial extensions to many
+databases (open source and commercial). One of the most robust is the PostGIS
+extension to the PostgreSQL database. This database not only allows the
+storage of geographic data, but also allows the manipulation of that data
+using SQL commands. The other open source database with spatial capabilities
+is MySQL.
-Connections to databases usually consist of the following pieces of connection information:
+Connections to databases usually consist of the following pieces of connection
+information:
**Host** - Directions to the server or computer hosting the database.
-**Database name** - The name of the database you wish to access that is running on the host.
+**Database name** - The name of the database you wish to access that is
+running on the host.
**User name / passwords** - Access privileges are usually restricted by user.
- Some databases (e.g. Oracle) use a name service identifier that includes
- both the host and database names.
+.. note::
+ Some databases (e.g. Oracle) use a name service identifier that includes
+ both the host and database names.
+
Access to specific pieces of coordinate data usually require:
-**Table/View name** - The name of the table or view holding the coordinate data.
+**Table/View name** - The name of the table or view holding the coordinate
+data.
**Geographic column name** - Where the geometry or coordinates are stored.
\ No newline at end of file
Deleted: trunk/docs/input/vector/formats_intro.txt
===================================================================
--- trunk/docs/input/vector/formats_intro.txt 2008-12-09 20:34:47 UTC (rev 8220)
+++ trunk/docs/input/vector/formats_intro.txt 2008-12-09 20:36:57 UTC (rev 8221)
@@ -1,34 +0,0 @@
-The rest of this document is the data format guide. This guide is structured to
-show the fundamentals of each MapServer supported data format. Each section
-discusses one format, ranging from one to several pages in length. The sections
-typically start with a summary of the most important information about the
-format, followed by examples of file listings, connection methods, ogrinfo usage
-and MapServer map file syntax examples.
-
-Each section has been designed to stand alone, so you may notice that certain
-warnings and comments are repeated or redundant. This is intentional. Each
-format is presented in rough order of popular use, based on a survey of the
-MapServer community.
-
-The following formats are included:
-
-* ESRI Shapefiles (SHP)
-* PostGIS / PostgreSQL Database
-* MapInfo Files (TAB/MID/MIF)
-* Oracle Spatial Database
-* Web Feature Service (WFS)
-* Geography Markup Language (GML)
-* Virtual Spatial Data (ODBC/OVF)
-* TIGER Files
-* ESRI Binary Coverages (ADF)
-* ESRI ArcSDE (SDE)
-* Microstation Design Files (DGN)
-* IHO S-57 Files
-* Spatial Data Transfer Standard (SDTS)
-* Inline MapServer Features
-* National Transfer Format (NTF)
-* Mysql MYGIS Format
-
- MySQL spatial database is only partially covered in this guide at this time due to
- lack of familiarity by the authors. Future contributions by MySQL users
- are welcome in this guide.
\ No newline at end of file
Modified: trunk/docs/input/vector/index.txt
===================================================================
--- trunk/docs/input/vector/index.txt 2008-12-09 20:34:47 UTC (rev 8220)
+++ trunk/docs/input/vector/index.txt 2008-12-09 20:36:57 UTC (rev 8221)
@@ -10,9 +10,10 @@
: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.
+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:
@@ -32,29 +33,43 @@
From: http://coris.noaa.gov/glossary/glossary_l_z.html#v
+The rest of this document is the data format guide. This guide is structured to
+show the fundamentals of each MapServer supported data format. Each section
+discusses one format, ranging from one to several pages in length. The sections
+typically start with a summary of the most important information about the
+format, followed by examples of file listings, connection methods, ogrinfo usage
+and MapServer map file syntax examples.
+Each section has been designed to stand alone, so you may notice that certain
+warnings and comments are repeated or redundant. This is intentional. Each
+format is presented in rough order of popular use, based on a survey of the
+MapServer community.
+
+The following formats are included:
+
+
.. toctree::
:maxdepth: 1
format_types
- formats_intro
+ shapefiles
+ postgis
ogr
+ mapinfo
+ wfs
+ gml
+ VirtualSpatialData
+ ArcInfo
arcsde
- ArcInfo
+ dgn
+ S57
pgeo
- postgis
- shapefiles
- gml
- S57
inline
kml
- mapinfo
oracle_spatial
- dgn
mygis
ntf
sdts
tiger
- VirtualSpatialData
- wfs
+
More information about the mapserver-commits
mailing list