Comments on: Google half bakes WMS support http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/ Not another GIS blog Wed, 02 Jun 2010 04:13:39 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Google Earth WMS still undercooked at Chris’ GISmo’s http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-6696 Google Earth WMS still undercooked at Chris’ GISmo’s Mon, 22 Jan 2007 05:03:45 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-6696 [...] It’s been 4 months since my last rant on Google’s half-baked support of WMS. To be honest i haven’t looked at recent BETA versions but I have v4.0.2722 and a little bit of time up my sleeve so lets have a look at my gripes from last time, [...] [...] It’s been 4 months since my last rant on Google’s half-baked support of WMS. To be honest i haven’t looked at recent BETA versions but I have v4.0.2722 and a little bit of time up my sleeve so lets have a look at my gripes from last time, [...]

]]> By: Lance Dyas http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-1938 Lance Dyas Thu, 12 Oct 2006 12:45:49 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-1938 One thing worth noting the on region refresh as implemented has some problems for layers with transparency... essentially the lower resolution images are still visible around the edges of higher resolution "updates" which are overlayed on top... What is needed is a way to say replace the main regions information with the contents of the results of this set of subregions, if that makes any sense to anyone? One thing worth noting the on region refresh as implemented has some problems for layers with
transparency… essentially the lower resolution
images are still visible around the edges of higher resolution “updates” which are overlayed on top…
What is needed is a way to say replace the main regions information with the contents of the results of this set of subregions, if that makes any sense to anyone?

]]> By: Lance Dyas http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-1762 Lance Dyas Wed, 27 Sep 2006 13:11:11 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-1762 TNTmap uses a kml reflector with on region based refresh, supports 1.3.0, imagetype selection (does default to gifs if the WMS has it, as google earth has poor png support) The locator view is used to show extents of the data as you mouse over the layers list before selecting the layers (or after) Check out what can be done via the onregion based refresh http://www.microimages.com/ogc/ load it into your web pane of google earth use the sites pane to select a wms, then select layers and click the GE icon. TNTmap uses a kml reflector with on region based refresh, supports 1.3.0, imagetype selection (does default to gifs if the WMS has it, as google earth has poor png support)

The locator view is used to show extents of the data as you mouse over the layers list before selecting the layers (or after)

Check out what can be done via the onregion based refresh
http://www.microimages.com/ogc/
load it into your web pane of google earth use the sites pane to select a wms, then select layers and click the GE icon.

]]> By: Chris Tweedie http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-1686 Chris Tweedie Fri, 15 Sep 2006 13:36:21 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-1686 Morten, thats a given. I mentioned using in_image to get around Googles extremely poor error handling events. Of course, xml is always the better option to return :) Morten, thats a given. I mentioned using in_image to get around Googles extremely poor error handling events. Of course, xml is always the better option to return :)

]]> By: Morten http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-1685 Morten Fri, 15 Sep 2006 11:28:36 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-1685 I can't make v1.3.0 servers work either. I disagree that errors should be displayed in the image. Instead an XML exception should be requested and returned to the user. Usually these exceptions can give you a better idea of what is wrong than the very limited error-message GE gives you. Placing error messages in an image is a really poor way of handling errors. I can’t make v1.3.0 servers work either.
I disagree that errors should be displayed in the image. Instead an XML exception should be requested and returned to the user. Usually these exceptions can give you a better idea of what is wrong than the very limited error-message GE gives you. Placing error messages in an image is a really poor way of handling errors.

]]> By: Chris Tweedie http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-1683 Chris Tweedie Fri, 15 Sep 2006 09:50:31 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-1683 Actually, i'd have to disagree Brian. Check out the worldwind forums and WMS is one of the more popular features since it has been added ... even for the non "GIS" professionals. Actually, i’d have to disagree Brian. Check out the worldwind forums and WMS is one of the more popular features since it has been added … even for the non “GIS” professionals.

]]> By: Brian Timoney http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-1682 Brian Timoney Fri, 15 Sep 2006 08:14:52 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-1682 Chris: Not to be a GE apologist, but WMS support is something that, while important to we in the GIS community, is something the mass market may not really "get". So not making the option front-and-center in the menu scheme is (a little) understandable. (And anyone used to XP or the most widely used desktop GIS is certainly used to having to deal with multi-tiered menus and obscurely located dialog boxes). Actually, my biggest disappointment is that the WMS implementation didn't use any of the new Regions functionality--Jason Birch's sample scripts provide a good glimpse of what's possible in that realm. BT Chris:

Not to be a GE apologist, but WMS support is something that, while important to we in the GIS community, is something the mass market may not really “get”. So not making the option front-and-center in the menu scheme is (a little) understandable. (And anyone used to XP or the most widely used desktop GIS is certainly used to having to deal with multi-tiered menus and obscurely located dialog boxes).

Actually, my biggest disappointment is that the WMS implementation didn’t use any of the new Regions functionality–Jason Birch’s sample scripts provide a good glimpse of what’s possible in that realm.

BT

]]> By: Chris Tweedie http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-1681 Chris Tweedie Fri, 15 Sep 2006 02:37:36 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-1681 Hey thanks for the pointers eric. I will certainly have to sit down to play for a bit longer Of course you can always build the whole wms string yourself, but that makes having a wms "client" pointless! Hey thanks for the pointers eric. I will certainly have to sit down to play for a bit longer

Of course you can always build the whole wms string yourself, but that makes having a wms “client” pointless!

]]> By: eric http://blog.webmapper.com.au/2006/09/15/google-half-bakes-wms-support/comment-page-1/#comment-1680 eric Thu, 14 Sep 2006 23:48:11 +0000 http://chris.narx.net/2006/09/15/google-half-bakes-wms-support/#comment-1680 I agree totally, but at least it's a something. Here are some of my observations: 1. You can tweak/edit the request URL and put what ever you need in there. Even though the interface doesn't have a lot of flexibility as far as the GUI, at least you can hack together a 'proper' request string and it'll work right. That means you can get your PNG! You can also specific a larger image to grab (I like 1024x1024 instead of 512x512) 2. You can change the 'View Bound Scale' to 1 to make the WMS image be full screen. 3. Several of the WMS servers on the provided list say they have no layers that GE can display. But if you chose them anyway, you can again build the URL by hand and it seems to work fine. I sure hope they polish this off. It COULD be REALLY cool... I agree totally, but at least it’s a something.

Here are some of my observations:

1. You can tweak/edit the request URL and put what ever you need in there. Even though the interface doesn’t have a lot of flexibility as far as the GUI, at least you can hack together a ‘proper’ request string and it’ll work right. That means you can get your PNG! You can also specific a larger image to grab (I like 1024×1024 instead of 512×512)

2. You can change the ‘View Bound Scale’ to 1 to make the WMS image be full screen.

3. Several of the WMS servers on the provided list say they have no layers that GE can display. But if you chose them anyway, you can again build the URL by hand and it seems to work fine.

I sure hope they polish this off. It COULD be REALLY cool…

]]>