Google Earth Mac problem...

- D
- Don Lancaster
  
  Contact options for registered users
posted
11 years ago

Sun, Sep 16, 2012 5:12 PM

I need your help on a little problem: We are using Google Earth for some of our new Hanging Canal papers. This file

formatting link

works just fine for PC users, but one Mac user ends up with a symptom of "stuck on South America".

Does the file work for you on a Mac? It is supposed to show zoomable and panable Safford basin prehistoric canals.

The problem could be the user's JavaScript, not waiting for a full load, ISP issues with carriage returns versus linefeeds ( we already elimated all of these from the coordinate data string ), or my own .kml coding errors.

Note that a .kml file can be viewed in any word processor.

--
Many thanks,

Don Lancaster                          voice phone: (928)428-4073
Synergetics   3860 West First Street   Box 809 Thatcher, AZ 85552
rss: http://www.tinaja.com/whtnu.xml   email: don@tinaja.com

Please visit my GURU's LAIR web site at http://www.tinaja.com

- E
- Ecnerwal
  
  Contact options for registered users
Vote on answer
posted
11 years ago

Sun, Sep 16, 2012 5:27 PM

Hi Don,

Seems to work spiffy for me. Or it takes me to SW USA, not south america, and there are a bunch of purple lines which I assume are your canals.

Mac OS 10.7.4

Google Earth 6.1.0.5001

--
Cats, coffee, chocolate...vices to live by
Please don't feed the trolls. Killfile and ignore them so they will go away.

- J
- Jeff Liebermann
  
  Contact options for registered users
Vote on answer
posted
11 years ago

Sun, Sep 16, 2012 5:33 PM

Try having the user clear his cache:

That usually clears up oddities and anomalies.

Your canals KML looks fine on my XP box. I haven't tried it on my antique Mac G4 yet.

--
Jeff Liebermann     jeffl@cruzio.com
150 Felker St #D    http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann     AE6KS    831-336-2558

- D
- Don Lancaster
  
  Contact options for registered users
Vote on answer
posted
11 years ago

Sun, Sep 16, 2012 6:32 PM

Thank you.

The problem apparently turned out to be an extra ending Marijilda comma, which parsed differently on their particular MAC implementation.

The root cause of it all, of course, was when they went from 110 Baud to

150. Its been hell in a handbasket ever since.

BTW - besides being an electronic type (THE electronic type?), these canals are orders of magnitude beyond world class engineering for energy efficiency and creativity.