gml.h
Go to the documentation of this file.
1 /* Copyright (C) 2008 National Institute For Space Research (INPE) - Brazil.
2 
3  This file is part of the TerraLib - a Framework for building GIS enabled applications.
4 
5  TerraLib is free software: you can redistribute it and/or modify
6  it under the terms of the GNU General Public License as published by
7  the Free Software Foundation, either version 3 of the License,
8  or (at your option) any later version.
9 
10  TerraLib is distributed in the hope that it will be useful,
11  but WITHOUT ANY WARRANTY; without even the implied warranty of
12  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
13  GNU General Public License for more details.
14 
15  You should have received a copy of the GNU General Public License
16  along with TerraLib. See COPYING. If not, write to
17  TerraLib Team at <terralib-team@terralib.org>.
18  */
19 
20 /*!
21  \file gml.h
22 
23  \brief This file contains include headers for TerraLib GML module.
24  */
25 #ifndef __TERRALIB_INTERNAL_GML_H
26 #define __TERRALIB_INTERNAL_GML_H
27 
28 // TerraLib
29 #include "gml/Config.h"
30 #include "gml/Envelope.h"
31 
32 namespace te
33 {
34  /*!
35  \brief This is the namespace for the GML module.
36 
37  The OpenGIS Geography Markup Language Encoding Standard (GML
38  is an XML grammar for expressing geographical features. GML serves
39  as a modeling language for geographic systems as well as an open
40  interchange format for geographic transactions on the Internet.
41  <br>
42  As with most XML based grammars, there are two parts to the
43  grammar the schema that describes the document and the instance
44  document that contains the actual data.
45  <br>
46  A GML document is described using a GML Schema.
47  This allows users and developers to describe generic geographic
48  data sets that contain points, lines and polygons. However, the
49  developers of GML envision communities working to define
50  community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas]
51  that are specialized extensions of GML. Using application schemas,
52  users can refer to roads, highways, and bridges instead of points,
53  lines and polygons. If everyone in a community agrees to use the same
54  schemas they can exchange data easily and be sure that a road is still a road when they view it.
55  <br>
56  Clients and servers with interfaces that implement
57  the OpenGIS Web Feature Service Interface
58  Standard [http://www.opengeospatial.org/standards/wfs] read and write GML data.
59  GML is also an ISO standard (ISO 19136:2007)
60  [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ].
61  <br>
62  Most of the documentation used in GML classes were extracted
63  from the specificaton available at: http://www.opengeospatial.org/standards/gml.
64 
65  \note See the te namespace comments for any detail on using namespaces.
66  */
67  namespace gml
68  {
69  } // end namespace gml
70 } // end namespace te
71 
72 #endif // __TERRALIB_INTERNAL_GML_H
Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimension...
URI C++ Library.
Configuration flags for the GML module of TerraLib.