![]() |
![]() |
|||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||
| Accessing Geospatial Data > Encoding Geospatial Data | Page 2 of 17 | |||||||||||||||||||||||||||||||
|
|
Using
GML
Using GML, you can encode the description of the location or spatial extent of a river, roadway or bridge. A GML record includes a geometry representing a bridge or roadway, as well as supporting information for the geometry such as the number of lanes of a road. With GML, you can transfer those descriptions through the Internet, and control how they are displayed. Like XML, GML clearly separates the content from the presentation; in other words, GML delivers the actual geographic data (information about the properties and geometries of objects in the physical world) as opposed to the visualization of that data (colours, line weights, symbols, etc.). Since GML is an XML application, it can be styled into a variety of presentation formats, including vector and raster graphics, text, sound and voice. While maps are one of the most common presentations of GML, GML is not dependent on any particular graphical specification. The GML specification is developed and maintained by the Open Geospatial Consortium, Inc. (OGC), an international industry consortium of over 240 companies, government agencies and universities participating in a consensus process to develop publicly available geo-processing specifications.
|
|||||||||||||||||||||||||||||||
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
||||||||||||||||||||||||||||||||
| Page 2 of 17 | ||||||||||||||||||||||||||||||||