| Issue 130: | Feature: Support for Web Map Service (WMS) Raster +Web Feature Service (WFS) Vector | |
| 40 people starred this issue and may be notified of changes. | Back to list |
Feature: Support for Web Map Service (WMS) Raster +Web Feature Service (WFS) Vector http://en.wikipedia.org/wiki/Web_Map_Service http://en.wikipedia.org/wiki/Web_Feature_Service Comments: Would be great if users could easily add WMS layers to their Google Map Layers. The easiest way is just those that support Mercator (EPSG:41001), but even better would be to do the transform from lat/long (EPSG:4326) to google maps. There is some code to do this at: http://docs.codehaus.org/display/GEOSDOC/Google+Maps, and http://openlayers.org also has a nice API for adding WMS layers - would be great to be compatible with that. If there is real concern over this bringing down WMS servers since it hits them hard with tiles, I would recommend the WMS Tiling Client Recommendation, which is implemented by TileCache. Or else just cache the WMS, like how Google caches web pages, and then would be able to display it even more quickly on google maps and google earth. Request by: Chris Holmes, Matthew Hanna, Steve White, Mapperz, Chris Marx, Craig Wolff (CA Dept of Public Health)
Feb 6, 2008
#1
pamela.fox
Labels:
Supported-6
May 31, 2008
(No comment was entered for this change.)
Labels:
ApiType-Javascript
May 24, 2009
Changing status of "Accepted" issues to "Acknowledged", to clarify their state. We may not be able to resolve all bugs or fulfill all feature requests, but we do thank you for filing them, and we will continually revisit all acknowledged issues and evaluate their feasibility. Thanks!
Status:
Acknowledged
Jun 29, 2010
(No comment was entered for this change.)
Labels:
-ApiType-Javascript ApiType-Javascript3
Jun 29, 2010
(No comment was entered for this change.)
Owner:
thor.mitchell
Aug 9, 2010
Is there a recommended WMS interface for GoogleMaps? I have been useing WMS236 for years with no real problems until you try to port to v3! Why hasn't Google taken this code optimised it and included in the API? This certainly is a very big omission that other proprietary APIs support! Cheers,
Sep 3, 2014
Issue 7103 has been merged into this issue. |
|
| ► Sign in to add a comment |