New answers tagged

0

I used gladinfo gdalinfo input.tif > info_about_info.txt and compared two files; one of which worked in Google Earth while the other threw the Unknown Error. I discovered that the images (who had both one band) had different data types. One featured Float64, the other one Int16. Therefore some gdalwarp to change Float64 to Int16 and that was it. ...


0

You can append the token to the link with the layers. Example: https://myserver:6443/arcgis/services///MyService/MapServer/KmlServer?Composite=false&compatibilityMode=GoogleEarth&LayerIDs=0&token=THE_TOKEN To generate the token in the first place, you can go to: https://myserver:6443/arcgis/tokens/generateToken This is a bit brittle though. ...


4

Use the CRS EPSG:3857. See below. Circle in GE Same KML as WGS 84 in QGIS Same KML again using EPSG:3857 Measure the diameter of your circle and it should be much better.


0

The <coordinates> are in longitude,latitude order. See https://developers.google.com/kml/documentation/kmlreference#syntax_151. So you wanted: <coordinates>0.03888889,51.45</coordinates> This is a pretty common mixup. Much of this stuff is done on a Cartesian plane, so think X-Y coordinates, and it'll make more sense.


0

There is a ArcGIS Tool for converting Maps into Garmin Custom Maps: https://bitbucket.org/wankoelias/maptogarmincustommap/src Its quite similar to your script... i discoverd this after i finished making this Tool :O


3

I have given up on my original idea to stream NMEA into Google Earth.. and found a better solution! I was able to solve this by programmatically generating KML file for each position and attitude change and then opening up an instance of Google Earth with the generated KML file as parameter. This is happening in 250ms loop which makes the transitions smooth....


3

The meridians in your Google Earth picture look like they are displaying at every 0.0035 degrees. It looks like you are measuring the distance between your data, which is placed correctly at 142E, and the 141.9985E meridian. The measured distance between 142E and 141.9985E is right around 170 meters. Your data looks correct, but you are validating ...


4

WGS84 is not a projection, it is a Datum, there is a key difference between the two. You could have WGS84 in a geographic projection, or a UTM projection, or many other projections. You want to make sure that not only are you using WGS 84, but are also using the correct projection. Google Earth uses Simple Cylindrical projection with a WGS84 datum, you are ...


0

If you are seeing an camera icon, then I believe you may be importing the image as a "Photo Overlay" rather than as a georeferenced "Image Overlay" as you appear to intend. It's an unfortunate terminology issue with Google Earth. I've never seen the error message you report, but have seen other weird behavior when I accidentally triggered the "Photo ...


0

How about this program called GeoSetter? http://www.geosetter.de/en This blog post has a decent explanation: http://www.groovypost.com/howto/view-geotagged-photos-google-picasa/ Wow I'm disappointed to see there is no KML link to your geotagged photos on Google Photos... I lived by that feature for so many years... all gone...! Anyway, I thought I had ...



Top 50 recent answers are included