Top Banner

Click here to load reader

of 65

Incorporating Google Maps and Google Earth into your Remote Sensing Applications J. Freemantle OARS Technical Meeting, Dec 11, 2006

Mar 26, 2015



  • Slide 1

Incorporating Google Maps and Google Earth into your Remote Sensing Applications J. Freemantle OARS Technical Meeting, Dec 11, 2006 Slide 2 Outline Overview of Google Earth Simple examples using keyhole markup language (kml) Using the Google Maps/Earth API Some community examples Questions? Slide 3 Google Earth Client/Server Application Free for basic version Works on Windows (2000/XP), Mac OS 10.3.9, Linux Slide 4 Slide 5 Google Earth Overview Satellite and Airborne Imagery 1-3 years old Spatial resolution in countryside < 15 m. Major US cities less than 1-2 feet (20-40 cm). Parts of Manhattan (Fulton Co.) 10 cm! Slide 6 York University Slide 7 Newmarket Slide 8 Low vs high res. data (Aurora) Slide 9 Toronto Slide 10 New York City (20 cm) Slide 11 New York City (10 cm) Slide 12 10 and 20 cm images compared Slide 13 Primary Data (roads etc) Slide 14 Boundary Errors Slide 15 Why Google? Its free!!! Generally up to date Large user community Developer/programmer friendly Easy to learn Platform independent Its cool! Slide 16 Assumptions/Caveats Check the fine print of End User License (EUL) for your situation. Google Earth 4.0 (Beta), free version. Public/Private data? (choose wisely). Slide 17 Simple Examples using KML Point Pictures Tracks Overlays Links to external data Slide 18 Warning Code Examples! Slide 19 Keyhole Markup Language (kml) Xml grammar and file format for describing geographic features in google earth/maps Points Lines Polygons Models links Slide 20 Keyhole Markup Language (KML) KML files can be shared. KMZ files are a compressed version of KML files. Google Earth processes kml files like web browsers process html files. Slide 21 Kml example: Simple point OARS Meeting Presented by Jim Freemantle Dec 11, 2006 7:00 pm Room 129 Chemistry Building, York University, Toronto. ]]> -79.508,43.773225,0 Slide 22 Simple Point Slide 23 Slide 24 Simple point, with link OARS Meeting details ]]> -79.508,43.773225,0 Slide 25 Simple point with link Slide 26 Simple point, with image OARS Meeting details ]]> -79.508,43.773225,0 Slide 27 Simple point with image Slide 28 Track t0490f13 t0490f13 ]]> -68.8911,48.79734,2470.74 -68.8947,48.79449,2471.35 -68.9127, 48.78028,2466.96,-68.9164,48.77747,2469.82 Slide 29 Track Slide 30 Slide 31 GeoTagging Slide 32 Requirements GPS device Camera with EXIF format jpg files and internal clock Software to sync gps track with time of photo Software to create google earth file (.kml) Slide 33 GeoTagging GPS Devices Used Sony GPS-SC1 ($129.00) Garmin Forerunner 201 Runners GPS ($159.00) Slide 34 GeoTagging Software Used GPSBabel (NMEA to GPX) GPS Image Tracker (Sony) (Not required) iTag Slide 35 GeoTagging Slide 36 Slide 37 Slide 38 Overlays Getting your georeferenced data into Google Earth Need georeferenced data Manually imported, as a jpg image, and matched to Google Earth Slide 39 Overlays Slide 40 Slide 41 Links Images External websites via url Databases Slide 42 Track with link t0489f06 t0489f06 Link to Flight Log ]]> -68.8911,48.79734,2470.74 -68.8947,48.79449,2471.35 -68.9127, 48.78028,2466.96,-68.9164,48.77747,2469.82 Slide 43 Track with link Slide 44Link to Waskesiu data ]]> -106.083,53.916698,550"> Point with link Waskesiu Link to Waskesiu data ]]> -106.083,53.916698,550 Slide 45 Jim's Google Maps JavaScript API Example from M. Brown//"> Jim's Google Maps JavaScript API Example from M. Brown// Slide 48 Google Map API Slide 49 Google Earth API Link to dynamically generated kml No API key required See ml#tracking_point Slide 50