OSGeo - User contributions [en]

SVG Map

2011-02-03T10:28:13Z

Wiki-Takagi: /* See Also */

= Introduction =

SVG Map is a specification for the map service platform on WWW that uses [http://www.w3.org/Graphics/SVG/ SVG]. It offers the essential functions for interoperability of Map Services as a basic function by fully applying the hyper-document that is the basic structure of WWW.

A dynamic web server is not indispensable for SVG Map. Of course, it is possible to use it as an option. Because it is possible to construct it as a set of a mere files, even http is not indispensable either. Therefore, SVG Map is also possible stand-alone operation using local file system. This characteristic is the same as HTML that is the basis of the Web architecture. It may turn out that this feature is important by investigating the [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] architecture thoroughly. And, it might dramatically decrease the cost of the map data publication and map services.

== Protocol ==

The basis of the protocol for SVG Map is simply a file access by URI. SVG Map doesn't restrict anything for it. Even query-part of URI which often becomes the argument in REST is not limited at all. Furthermore "file:" is acceptable as a scheme of URI. In other words, various REST-based map services with different query rules and even local files can cooperate in SVG Map easily.

== Functionality ==

Interoperability that is the most important functionality for Web Mapping platform is realized by hyper-documents (SVG documents linked by hyper-link). Needless to say, hyper document is the most essential characteristic of WWW.

SVG Map achieves following important functions of map services without a dynamic server.

*Not only raster map but also vector map support
*Geographic coordinates identification
*Tiling by hyper-document
*Layering (MashUp, Interoperation of map services) by hyper-document
*Stand-alone operation

== History ==

The basic architecture of SVG Map was designed in 1996. Its part was standardized as [http://www.w3.org/Graphics/SVG/ SVG]1.1 ([http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]) that had been recommended by [http://www.w3.org/ W3C] in 2003. (See also, SVG Mobile Requirements - [http://www.w3.org/TR/SVGMobileReqs#sec-usage Usage Scenarios] , [http://www.w3.org/2003/01/svg11-faq SVG 1.1 and SVG Mobile FAQ]) And [http://blog.svg-map.com/ SVG Map Consortium] to promote it was established in 2007, and the reference implementation of the viewer was published.

= Specification =

The specifications of SVG Map are very compact by depending on SVG. Therefore the specifications for SVG Map may be called Tiling and Layering Module for SVG.

The latest specification for SVG Map is published at following URL by SVG Map Consortium.

*[http://blog.svg-map.com/2010/11/1-abstract-this-specification-defines-the-features-and-syntax-for-tiling-and-layering-module-for-svg-12-tiny-this-specific.html Tiling and Layering Module 1.0 Specification for SVG 1.2 Tiny (DRAFT)]

*[http://blog.svg-map.com/2008/07/the-index-of-sv.html instruction for SVG Map]

In addition, please pay attention to standardization in the W3C. [http://www.w3.org/Graphics/SVG/IG/wiki/Japanese_SVG_Task_Force JSTF]

= Reference implementation =

== Client ==

*[http://map.gissoken.org/maps/tech_kddi/ Emulation of SVG Map implementation by AJAX]

*[http://blog.svg-map.com/svg_map_toolkit/index.html SVG Map Toolkit : Not OSS : ActiveX for IE8]

Note: The full potential of SVG Map will be shown by native implementation on the Web browser. Implementation to [http://webkit.org/ WebKit] is in progress.

== Server ==

Because the server of the minimum implementation is not dynamic, the minimum implementation is a mere map data file itself. Therefore, you can view the examples of such static map data which were shown below. There are some examples which used well known dynamic services.

*[http://map.gissoken.org/maps/tech_kddi/ Emulation of SVG Map implementation by AJAX]

In addition, tool which converts shapefile into SVG Map is shown.

*[http://blog.svg-map.com/2010/08/shapefile-to-tiled-svg-map-converter.html Shapefile to TILED SVG Map converter java code]

= See Also =

*[[TilingStandard]]
*W3C SVG1.1 specification [http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]
*[[REST]]
*[http://esw.w3.org/topic/GeoMetadataOverSvg GeoMetadataOverSvg]
*Some [http://blog.svg-map.com/svgmapservices/index.html tools] for SVG Map services
*[http://en.wikipedia.org/wiki/Linked_Data Linked Data]

[[Category:Standards]]
[[Category:Tiling]]

SVG Map

2011-02-03T10:24:21Z

Wiki-Takagi: /* See Also */

= Introduction =

SVG Map is a specification for the map service platform on WWW that uses [http://www.w3.org/Graphics/SVG/ SVG]. It offers the essential functions for interoperability of Map Services as a basic function by fully applying the hyper-document that is the basic structure of WWW.

A dynamic web server is not indispensable for SVG Map. Of course, it is possible to use it as an option. Because it is possible to construct it as a set of a mere files, even http is not indispensable either. Therefore, SVG Map is also possible stand-alone operation using local file system. This characteristic is the same as HTML that is the basis of the Web architecture. It may turn out that this feature is important by investigating the [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] architecture thoroughly. And, it might dramatically decrease the cost of the map data publication and map services.

== Protocol ==

The basis of the protocol for SVG Map is simply a file access by URI. SVG Map doesn't restrict anything for it. Even query-part of URI which often becomes the argument in REST is not limited at all. Furthermore "file:" is acceptable as a scheme of URI. In other words, various REST-based map services with different query rules and even local files can cooperate in SVG Map easily.

== Functionality ==

Interoperability that is the most important functionality for Web Mapping platform is realized by hyper-documents (SVG documents linked by hyper-link). Needless to say, hyper document is the most essential characteristic of WWW.

SVG Map achieves following important functions of map services without a dynamic server.

*Not only raster map but also vector map support
*Geographic coordinates identification
*Tiling by hyper-document
*Layering (MashUp, Interoperation of map services) by hyper-document
*Stand-alone operation

== History ==

The basic architecture of SVG Map was designed in 1996. Its part was standardized as [http://www.w3.org/Graphics/SVG/ SVG]1.1 ([http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]) that had been recommended by [http://www.w3.org/ W3C] in 2003. (See also, SVG Mobile Requirements - [http://www.w3.org/TR/SVGMobileReqs#sec-usage Usage Scenarios] , [http://www.w3.org/2003/01/svg11-faq SVG 1.1 and SVG Mobile FAQ]) And [http://blog.svg-map.com/ SVG Map Consortium] to promote it was established in 2007, and the reference implementation of the viewer was published.

= Specification =

The specifications of SVG Map are very compact by depending on SVG. Therefore the specifications for SVG Map may be called Tiling and Layering Module for SVG.

The latest specification for SVG Map is published at following URL by SVG Map Consortium.

*[http://blog.svg-map.com/2010/11/1-abstract-this-specification-defines-the-features-and-syntax-for-tiling-and-layering-module-for-svg-12-tiny-this-specific.html Tiling and Layering Module 1.0 Specification for SVG 1.2 Tiny (DRAFT)]

*[http://blog.svg-map.com/2008/07/the-index-of-sv.html instruction for SVG Map]

In addition, please pay attention to standardization in the W3C. [http://www.w3.org/Graphics/SVG/IG/wiki/Japanese_SVG_Task_Force JSTF]

= Reference implementation =

== Client ==

*[http://map.gissoken.org/maps/tech_kddi/ Emulation of SVG Map implementation by AJAX]

*[http://blog.svg-map.com/svg_map_toolkit/index.html SVG Map Toolkit : Not OSS : ActiveX for IE8]

Note: The full potential of SVG Map will be shown by native implementation on the Web browser. Implementation to [http://webkit.org/ WebKit] is in progress.

== Server ==

Because the server of the minimum implementation is not dynamic, the minimum implementation is a mere map data file itself. Therefore, you can view the examples of such static map data which were shown below. There are some examples which used well known dynamic services.

*[http://map.gissoken.org/maps/tech_kddi/ Emulation of SVG Map implementation by AJAX]

In addition, tool which converts shapefile into SVG Map is shown.

*[http://blog.svg-map.com/2010/08/shapefile-to-tiled-svg-map-converter.html Shapefile to TILED SVG Map converter java code]

= See Also =

*[[TilingStandard]]
*W3C SVG1.1 specification [http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]
*[http://esw.w3.org/topic/GeoMetadataOverSvg GeoMetadataOverSvg]
*Some [http://blog.svg-map.com/svgmapservices/index.html tools] for SVG Map services
*[http://en.wikipedia.org/wiki/Linked_Data Linked Data]

[[Category:Standards]]
[[Category:Tiling]]

TilingStandard

2011-02-03T10:20:59Z

Wiki-Takagi: /* See also */

==Preamble==

Tile-based web mapping is taking the world by storm. Tile-based web map clients are already a huge category of software, running from completely browser-based Javascript implementations like OpenLayers or the Google Maps API, to 100% desktop-based 3D worlds like Worldwind and Google Earth. What they all have in common is that they access map images from servers as fixed-size image tiles, and they expect high performance response to tile requests.

Thus far, most tiled map systems have been implemented as bound client-server pairs, with a particular protocol for describing tiles and an implicit understanding of a number of parameters like scales, projections, formats and so on. Some recent clients have been implemented that speak all the different tile server dialects and can consume from multiple servers.

''In an ideal world, tile-based clients would be able to swap tile sources on the fly and use many different sources of tiles without recoding to new specifications each time.''

In the "dynamic tile" world of the OGC Web Map Server (WMS) specification, this is already possible. However, dynamic mapping requires the server to render new tiles for every request, which is often a very slow process. Tile-based mapping is all about speed.

''In an ideal world, tile-based clients would be able to use the data already published in WMS servers, but at a speed high enough to satisfy their end-users.''

==Cacheability==

These standards will provide two approaches to enhancing "cacheability" in tile servers. The first approach will enhance the cacheability of existing WMS servers. The second approach will provide a standardized tile server API with strong cacheability.

===Not Caching===

Neither approach will say anything in particular about caching. Particular mechanisms of caching will differ from implementation to implementation, but the mechanism of caching should '''not''' affect the general goal of cacheability.

===Not Rendering===

Neither approach will say anything in particular about rendering. Cartographic rendering in a tile-based mapping system is a difficult problem, but it is orthogonal to the problem of enhancing cacheability.

==Cacheability through Client Behavior==

The "[[WMS Tiling Client Recommendation]]" is a non-binding recommendation paper for the authors of tiling clients. The paper provides a set of best practices for accessing legacy WMS servers which enhance the ability of the server maintainers to insert caching mechanisms in front of their servers without re-configurating or re-deploying the core WMS application. Standardization is provided for parameters, parameter order, projection, scale levels, bounding box rounding, and so on.

==Cacheability through Server Standardization==

The "[[Tile Map Service Specification]]" is a standards paper for the authors of interoperable tiling web map servers and clients. The paper provides a simple specification in the spirit of the original Web Map Server specification, providing the basis for a discoverable, interoperable server of tiled map images. The TMS specification will allow degrees of freedom on things like projection, format, scale levels, and so on, that are not possible with a single, global standard for tiles.

==See also==
* [[Tiled imagery layer]]
* [http://openlayers.org/pipermail/users/2006-November/000102.html on caching WMS via HTTP proxy versus WMS-C]
* [[SVG_Map]]
[[Category:Standards]]
[[Category:Tiling]]

SVG Map

2011-02-03T10:05:36Z

Wiki-Takagi: updated

= Introduction =

SVG Map is a specification for the map service platform on WWW that uses [http://www.w3.org/Graphics/SVG/ SVG]. It offers the essential functions for interoperability of Map Services as a basic function by fully applying the hyper-document that is the basic structure of WWW.

A dynamic web server is not indispensable for SVG Map. Of course, it is possible to use it as an option. Because it is possible to construct it as a set of a mere files, even http is not indispensable either. Therefore, SVG Map is also possible stand-alone operation using local file system. This characteristic is the same as HTML that is the basis of the Web architecture. It may turn out that this feature is important by investigating the [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] architecture thoroughly. And, it might dramatically decrease the cost of the map data publication and map services.

== Protocol ==

The basis of the protocol for SVG Map is simply a file access by URI. SVG Map doesn't restrict anything for it. Even query-part of URI which often becomes the argument in REST is not limited at all. Furthermore "file:" is acceptable as a scheme of URI. In other words, various REST-based map services with different query rules and even local files can cooperate in SVG Map easily.

== Functionality ==

Interoperability that is the most important functionality for Web Mapping platform is realized by hyper-documents (SVG documents linked by hyper-link). Needless to say, hyper document is the most essential characteristic of WWW.

SVG Map achieves following important functions of map services without a dynamic server.

*Not only raster map but also vector map support
*Geographic coordinates identification
*Tiling by hyper-document
*Layering (MashUp, Interoperation of map services) by hyper-document
*Stand-alone operation

== History ==

The basic architecture of SVG Map was designed in 1996. Its part was standardized as [http://www.w3.org/Graphics/SVG/ SVG]1.1 ([http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]) that had been recommended by [http://www.w3.org/ W3C] in 2003. (See also, SVG Mobile Requirements - [http://www.w3.org/TR/SVGMobileReqs#sec-usage Usage Scenarios] , [http://www.w3.org/2003/01/svg11-faq SVG 1.1 and SVG Mobile FAQ]) And [http://blog.svg-map.com/ SVG Map Consortium] to promote it was established in 2007, and the reference implementation of the viewer was published.

= Specification =

The specifications of SVG Map are very compact by depending on SVG. Therefore the specifications for SVG Map may be called Tiling and Layering Module for SVG.

The latest specification for SVG Map is published at following URL by SVG Map Consortium.

*[http://blog.svg-map.com/2010/11/1-abstract-this-specification-defines-the-features-and-syntax-for-tiling-and-layering-module-for-svg-12-tiny-this-specific.html Tiling and Layering Module 1.0 Specification for SVG 1.2 Tiny (DRAFT)]

*[http://blog.svg-map.com/2008/07/the-index-of-sv.html instruction for SVG Map]

In addition, please pay attention to standardization in the W3C. [http://www.w3.org/Graphics/SVG/IG/wiki/Japanese_SVG_Task_Force JSTF]

= Reference implementation =

== Client ==

*[http://map.gissoken.org/maps/tech_kddi/ Emulation of SVG Map implementation by AJAX]

*[http://blog.svg-map.com/svg_map_toolkit/index.html SVG Map Toolkit : Not OSS : ActiveX for IE8]

Note: The full potential of SVG Map will be shown by native implementation on the Web browser. Implementation to [http://webkit.org/ WebKit] is in progress.

== Server ==

Because the server of the minimum implementation is not dynamic, the minimum implementation is a mere map data file itself. Therefore, you can view the examples of such static map data which were shown below. There are some examples which used well known dynamic services.

*[http://map.gissoken.org/maps/tech_kddi/ Emulation of SVG Map implementation by AJAX]

In addition, tool which converts shapefile into SVG Map is shown.

*[http://blog.svg-map.com/2010/08/shapefile-to-tiled-svg-map-converter.html Shapefile to TILED SVG Map converter java code]

= See Also =

*[[TilingStandard]]
*W3C SVG1.1 specification [http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]
*[http://esw.w3.org/topic/GeoMetadataOverSvg GeoMetadataOverSvg]
*Some [http://blog.svg-map.com/svgmapservices/index.html tools] for SVG Map services
*[http://en.wikipedia.org/wiki/Linked_Data Linked Data]

SVG Map

2010-02-25T15:15:34Z

Wiki-Takagi: /* Specification */

=Introduction=
SVG Map is a specification for the map service platform that uses [http://www.w3.org/Graphics/SVG/ SVG]. It achieves essential functions of Map Services as a basic function by fully applying the function of SVG and enhancing a little geospatial metadata.

A dynamic web server for SVG Map is not indispensable. Of course, it is possible to use it as an option. Because it is possible to construct it as a set of a mere files, even http is not indispensable either. Therefore, SVG Map is also possible stand-alone operation based on the local file system. This characteristic is the same as HTML that is the basis of the Web architecture. It may turn out that this feature is important by investigating the [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] architecture thoroughly. And, it might dramatically decrease the cost of the map services.

==Protocol==
The basis of the protocol for SVG Map is simply a file access by URL. Basically, SVG Map doesn't restrict anything for it. The scheme of URL might be "file:" though it might be "http:". That is, even query part for http is an option in SVG Map.

==Functionality==
Nevertheless, SVG Map achieves following important functions of map services as a basic function without a dynamic server.
* Not only raster map but also vector map support
* Geographic coordinates identification
* Tiled map system
* Hyper-Layering (MashUp of map services)
* Stand-alone operation

==History==
The basic architecture of SVG Map was designed in 1996. Its part was standardized as [http://www.w3.org/Graphics/SVG/ SVG]1.1 ([http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]) that had been recommended by [http://www.w3.org/ W3C] in 2003. (See also, SVG Mobile Requirements - [http://www.w3.org/TR/SVGMobileReqs#sec-usage Usage Scenarios] , [http://www.w3.org/2003/01/svg11-faq SVG 1.1 and SVG Mobile FAQ]) And [http://blog.svg-map.com/ SVG Map Consortium] to promote it was established in 2007, and the reference implementation of the viewer was published.

=Specification=
The specification for SVG Map is published at following URL by SVG Map Consortium.
* [http://blog.svg-map.com/2009/09/tiling-and-laye.html Overview of Tiling and Layering Module for SVG 1.2 Tiny]
* [http://lists.w3.org/Archives/Public/public-svg-ig-jp/2009OctDec/0000.html Draft Specifications of SVG Tiling and Layering Module]

* [http://blog.svg-map.com/2008/07/the-index-of-sv.html SVG Map Profile 1.0 for SVG 1.1]

=Reference implementation=
==Client==
It is a viewer because it targets even the stand-alone operation.
* [http://blog.svg-map.com/svg_map_toolkit/index.html SVG Map Toolkit]

==Server==
The minimum implementation is a mere map data file. Because the server of the minimum implementation is not dynamic, it doesn't have the program code.
* [http://blog.svg-map.com/svgbasemap/index.html Examples of the basic SVG map data]

=See Also=
* [[TilingStandard]]
* W3C SVG1.1 specification [http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]
* [http://esw.w3.org/topic/GeoMetadataOverSvg GeoMetadataOverSvg]
* Some [http://blog.svg-map.com/svgmapservices/index.html tools] for SVG Map services

SVG Map

2008-08-01T05:30:43Z

Wiki-Takagi:

=Introduction=
SVG Map is a specification for the map service platform that uses [http://www.w3.org/Graphics/SVG/ SVG]. It achieves essential functions of Map Services as a basic function by fully applying the function of SVG and enhancing a little geospatial metadata.

A dynamic web server for SVG Map is not indispensable. Of course, it is possible to use it as an option. Because it is possible to construct it as a set of a mere files, even http is not indispensable either. Therefore, SVG Map is also possible stand-alone operation based on the local file system. This characteristic is the same as HTML that is the basis of the Web architecture. It may turn out that this feature is important by investigating the [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] architecture thoroughly. And, it might dramatically decrease the cost of the map services.

==Protocol==
The basis of the protocol for SVG Map is simply a file access by URL. Basically, SVG Map doesn't restrict anything for it. The scheme of URL might be "file:" though it might be "http:". That is, even query part for http is an option in SVG Map.

==Functionality==
Nevertheless, SVG Map achieves following important functions of map services as a basic function without a dynamic server.
* Not only raster map but also vector map support
* Geographic coordinates identification
* Tiled map system
* Hyper-Layering (MashUp of map services)
* Stand-alone operation

==History==
The basic architecture of SVG Map was designed in 1996. Its part was standardized as [http://www.w3.org/Graphics/SVG/ SVG]1.1 ([http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]) that had been recommended by [http://www.w3.org/ W3C] in 2003. (See also, SVG Mobile Requirements - [http://www.w3.org/TR/SVGMobileReqs#sec-usage Usage Scenarios] , [http://www.w3.org/2003/01/svg11-faq SVG 1.1 and SVG Mobile FAQ]) And [http://blog.svg-map.com/ SVG Map Consortium] to promote it was established in 2007, and the reference implementation of the viewer was published.

=Specification=
The specification for SVG Map is published at following URL by SVG Map Consortium.
* [http://blog.svg-map.com/2008/07/the-index-of-sv.html SVG Map Profile 1.0]

=Reference implementation=
==Client==
It is a viewer because it targets even the stand-alone operation.
* [http://blog.svg-map.com/svg_map_toolkit/index.html SVG Map Toolkit]

==Server==
The minimum implementation is a mere map data file. Because the server of the minimum implementation is not dynamic, it doesn't have the program code.
* [http://blog.svg-map.com/svgbasemap/index.html Examples of the basic SVG map data]

=See Also=
* [[TilingStandard]]
* W3C SVG1.1 specification [http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]
* [http://esw.w3.org/topic/GeoMetadataOverSvg GeoMetadataOverSvg]
* Some [http://blog.svg-map.com/svgmapservices/index.html tools] for SVG Map services

SVG Map

2008-07-25T11:19:23Z

Wiki-Takagi: New page: =Introduction= SVG Map is a specification for the map service platform that uses [http://www.w3.org/Graphics/SVG/ SVG]. It achieves essential functions of Map Services as a basic function ...

=Introduction=
SVG Map is a specification for the map service platform that uses [http://www.w3.org/Graphics/SVG/ SVG]. It achieves essential functions of Map Services as a basic function by fully applying the function of SVG and enhancing a little geospatial metadata.

A dynamic web server for SVG Map is not indispensable. Of course, it is possible to use it as an option. Because it is possible to construct it as a set of a mere files, even http is not indispensable either. Therefore, SVG Map is also possible stand-alone operation based on the local file system. This characteristic is the same as HTML that is the basis of the Web architecture. It may turn out that this feature is important by investigating the [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] architecture thoroughly. And, it might dramatically decrease the cost of the map services.

==Protocol==
The basis of the protocol for SVG Map is simply a file access by URL. Basically, SVG Map doesn't restrict anything for it. The scheme of URL might be "file:" though it might be "http:". That is, even query part for http is an option in SVG Map.

==Functionality==
Nevertheless, SVG Map achieves following important functions of map services as a basic function without a dynamic server.
* Not only raster map but also vector map support
* Geographic coordinates identification
* Tiled map system
* Hyper-Layering (MashUp of map services)
* Stand-alone operation

==History==
The basic architecture of SVG Map was designed in 1996. Its part was standardized as [http://www.w3.org/Graphics/SVG/ SVG]1.1 that had been recommended by [http://www.w3.org/ W3C] in 2003. And [http://blog.svg-map.com/ SVG Map Consortium] to promote it was established in 2007, and the reference implementation of the viewer was published.

=Specification=
The specification for SVG Map is published at following URL by SVG Map Consortium.
* [http://blog.svg-map.com/2008/07/the-index-of-sv.html SVG Map Profile 1.0]

=Reference implementation=
==Client==
It is a viewer because it targets even the stand-alone operation.
* [http://blog.svg-map.com/svg_map_toolkit/index.html SVG Map Toolkit]

==Server==
The minimum implementation is a mere map data file. Because the server of the minimum implementation is not dynamic, it doesn't have the program code.
* [http://blog.svg-map.com/svgbasemap/index.html Examples of the basic SVG map data]

=See Also=
* [[TilingStandard]]
* W3C SVG1.1 specification [http://www.w3.org/TR/SVG11/coords.html#GeographicCoordinates Geographic Coordinate Systems]
* [http://esw.w3.org/topic/GeoMetadataOverSvg GeoMetadataOverSvg]
* Some [http://blog.svg-map.com/svgmapservices/index.html tools] for SVG Map services