Occultation Maps for North America: Compatability Issues

Occultation Maps for North America

Your browser doesn't support JavaScript or JavaScript suport has been disabled.

You will not be able to view the interactive maps linked to from this page.

Map Index
Compatibility Issues	Time Conversions
How It's Done	Change Log

Things You Need To Know

The maps to which the listings link were created using the Google Maps API which has recently come out of beta testing but still may not be compatible with all browsers. Listed below are user reports of compatibility/incompatibility,

8.0.2

Compatibility Tests
Browser	Version	Platform	Result
AOL		WinXP Home	Works
AOL Explorer	1.1.4234.1042	WinXP Pro	Works
Avant Broswer	10.1 Build 22	WinXP Pro	Works
Deepnet Explorer	1.5	WinXP Pro	Works
Deer Park	1.0+ Alpha 2	WinXP Pro	Works
Firefox	1.5	WinXP Pro	Works
	1.0.6	WinXP Pro	Works
	1.0.6	WinME	Works
	1.0.4	WinME	Works
Internet Explorer	5	Mac OS9	Does not show maps.
	6.0.2900.2180.xsp_sp2_gdr.050301-1519IC	WinXP Pro	Works
	6.0.2900	WinXP	Works
	6.0.2800.1106IC	WinME	Sometimes it works and sometimes it doesn't. Mostly the page displays and the map displays but without the navigation controls. Then the browser crashes and can't be closed or killed.
		Win2K	Worked
		Win98	Crashes the OS.
Mozilla	1.7.11	WinXP Pro	Works
Mozilla	1.0.1	Mac OS9	Maps display and navigation works some of the time.
Netscape	8.0.3.3	WinXP Pro	Works
	WinME	Set up to use only the Firefox browser engine. Extremely s-l-o-w, but it works.
	7.2	Mac OS10.3.9	Works
Opera	8.5 build 7700	WinXP Pro	Works
	8.02	WinXP Pro	Works
	8.0	WinME	It works but isn't pretty. Maps don't zoom and pan well. Each tile has to be downloaded again with each change of scale or position.
	6.0.5	WinME	Displays the page but not the map.
Safari	1.3	OS 10.3.9	Works

Your mileage may vary.

Best Viewed With Mozilla

Because of repeated compatability problems with Internet Explorer family browsers I am strongly recommending that you view these pages (and the Internet in general) with a Mozilla family browser. These maps seem to break when viewed with and IE based browser every time Microsoft performs a Windows Update but keep on ticking if you are using a Mozilla based browser. I expect this will continue to be the case for some time to come as Mozilla is not at war with Google and everyone else who writes computer software. I use Firefox to test thes maps before they go live on the site so know when they are not working. I don't use IE so don't know when Microsoft has broken them.

You can download a Mozilla browser from www.mozilla.org.

Mozilla Based Browsers	IE Based Browsers
AOL Navigator (also uses IE) Camino Deer Park Firefox Mozilla Netscape Browser Opera	AOL Navigator (also uses Mozilla) Avant Browser Deepnet Explorer iNetAdviser Internet Explorer

Known Issues That Could Affect These Maps
There is an issue affecting the positional accuracy of lines or their ability to display. This kicks in at high magnification. It doesn't happen the same with all browser/platform combinations or on all maps viewed on a given machine. My experience is that when it does happen lines begin to change position or fail to display at zoom settings above 3 or 4 clicks down from maximum zoom (see illustration). The line may shift location in some areas on the map and fail to draw in others. Google is aware of this problem and is working to resolve it. There is no work around for it. This does not happen with Google Earth. Currently the Google Maps API cannot deal with lines crossing the 180° meridian. Google Maps is aware of this problem and working to resolve it. In the meantime, my work around it to show only that portion of a track lying east of -179°. This is not an issue in Google Earth and the posted TRACK.KML files contain the entire track.

Known Issues That Could Affect These Maps

There is an issue affecting the positional accuracy of lines or their ability to display. This kicks in at high magnification. It doesn't happen the same with all browser/platform combinations or on all maps viewed on a given machine. My experience is that when it does happen lines begin to change position or fail to display at zoom settings above 3 or 4 clicks down from maximum zoom (see illustration). The line may shift location in some areas on the map and fail to draw in others. Google is aware of this problem and is working to resolve it. There is no work around for it. This does not happen with Google Earth.
Currently the Google Maps API cannot deal with lines crossing the 180° meridian. Google Maps is aware of this problem and working to resolve it. In the meantime, my work around it to show only that portion of a track lying east of -179°. This is not an issue in Google Earth and the posted TRACK.KML files contain the entire track.

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License.