... | ... | @@ -50,9 +50,8 @@ smaller size (780x780 px) vs. max size (4000x4000px): |
|
|
|
|
|
|
|
|
|
|
|
We decided to use the more detailed bigger version of the image, as it is much more clear, although it could be considered to decrease the size if you want to save on ressources, as the larger image takes more time to download obviously.
|
|
|
We decided to use the more detailed bigger version of the image, as a smaller image has a smaller resolution as well, which causes the ground overlay to look pixelatzed an "muddy". Although it could be considered to decrease the size if you want to save on resources, as the larger image takes more time to download obviously.
|
|
|
|
|
|
<!--- minx,miny,maxx,maxy -> -71.13,42.32,-71.03,42.42; axis order is set as X=longitude (easting) and Y=latitude (northing), negative values are long --->
|
|
|
|
|
|
# Integration of the WMS Image into Google Earth:
|
|
|
|
... | ... | @@ -85,6 +84,8 @@ To integrate the inage of the map we first built a blueprint of the necessary st |
|
|
```
|
|
|
To create the kml structure that displayed the WMS-Image as a ground overlay in Google Earth, we used the <color> tag to set the colour of the map and thereby the transparency, as the alpha-value of the hexadecimal code, corresponds to the opacity of the item.
|
|
|
|
|
|
We used the gx:LatLonQuad tag to specify the bounding box because we could use the coordinates as i, and didnt have to do any conversions, which would have been necessary if we used the standard LatLonBox.
|
|
|
|
|
|
Below you can see how the WMs-image is shown as a ground overlay with 30% opacity.
|
|
|

|
|
|
|
... | ... | |