WFO Players - Google Map update feature!

[GalaxyBlue]

Well,

I added my info in the WFO edit page, But i cannot load the map... Server problems again or is it me? :dntknw:

 

[rogdeb]

I went there and put in my coordinates and submitted and the screen froze up. Had to hit cnt/alt/delete just to get computer going again. Logged back into MSN>FJRForum>WFO clicked on the players tab and darned screen froze again. Tried several times and all I get is a freeze. So I can't bring up the Players screen at all.
This happens sometimes when I click on an embedded e-mail address whatchamacallit, so not really isolated quirk. Java-script thing or what, don't know. Probably a software issue on my damned computer. Oh well, I'll know who's going when I get there

+ 1 !! Cleared the cache - still no good.

 

[bvail]

Well,
I added my info in the WFO edit page, But i cannot load the map... Server problems again or is it me? :dntknw:

Did your computer freeze up or the map just won't come up? Suggest you try to empty your brouser cache (what I relate to nuking the history files). I guess that frees up some memory. Worked for me, but now when I clicked on Players, the map came up, but not the balloons. Maybe the repair crew is hard at work fixing things...

 

[FJR_pig]

Worked for me, but now when I clicked on Players, the map came up, but not the balloons. Maybe the repair crew is hard at work fixing things...

Yep, map, but no balloons. I never thought at my age I'd whine about wanting a balloon, yet, here I am...

I will check back in da mornin'.

 

[Warchild]

Something's up with the goodamn Google map..... it comes up eventually in FF ( after stopping/starting the page), but doesn't display at all in IE.

It appears from looking at the XML file (that populates the Google map) that some of you clowns have entered in bogus characters... they look like they may have come from MS Word or some mapping software, ect. Others have entered in degrees/minutes/seconds when you should have entered in your GPS coordinates in decimeal format. <_<

Suspending the Google map until I can chase down this issue

 

[GalaxyBlue]

Suspending the Google map until I can chase down this issue

And to think, I didnt even get to see it yet...

Keep up the great work Warchild, We all Appreciate it greatly! :clapping:

 

[Warchild]

A-ha!!! It WAS youse guys dorking up the map!!!

Check it now... comes up lickety-split in both major browsers!!! B)

WFO Players Map

I won't mention any names - heh - but a good half-dozen of you guys inserted code into your coordinate fields that must have come out of a mapping software program.... some had little "degree" circles in the coordinates, some of you had other sundry machine code (little square boxes or other non-ascii characters), etc, etc

As I've mentioned before, the XML file is *brutally* unforgiving when it is interpreted by the Google Map API; it has to be in an exact, specific format, or it will confuse the Google map interface. The Google Map itself will halt processing, and won't return the web service back to your browser, so your browser eventually stalls.

Guess I have to error-trap the input fields on that form a little more. :glare:

Again, we need the GPS values in DECIMAL format, not "degrees/minutes/seconds".

Also, we do not put a positive sign (+) in front of the latitude coordinates... it's already assumed if you live in Northern Hemisphere, you have a positive latitude coordinate!

Conversley, all North American Longitude coordinates WILL NEED a negative (-) sign placed in your latitude coordinate.... most all WFO players live between -123.xxxx (western Oregon) and -63.xxxxx (eastern Canada).

 

[FJR_pig]

Uh oh, guilty as charged on the plus/minus entry. oster_oops:

 

[escapefjrtist]

George, it looks like you moved from Washington to Michigan. What up with that?

Haven't checked this one for a few days Matt...I only wish the original move had been as easy! 3500 miles outrunning a severe winter storm last year was no fun. See ya in Utah!

--G

 

[Woodstock]

A-ha!!! It WAS youse guys dorking up the map!!!
Check it now... comes up lickety-split in both major browsers!!! B)

WFO Players Map

I won't mention any names - heh - but a good half-dozen of you guys inserted code into your coordinate fields that must have come out of a mapping software program.... some had little "degree" circles in the coordinates, some of you had other sundry machine code (little square boxes or other non-ascii characters), etc, etc

As I've mentioned before, the XML file is *brutally* unforgiving when it is interpreted by the Google Map API; it has to be in an exact, specific format, or it will confuse the Google map interface. The Google Map itself will halt processing, and won't return the web service back to your browser, so your browser eventually stalls.

Guess I have to error-trap the input fields on that form a little more. :glare:

Again, we need the GPS values in DECIMAL format, not "degrees/minutes/seconds".

Also, we do not put a positive sign (+) in front of the latitude coordinates... it's already assumed if you live in Northern Hemisphere, you have a positive latitude coordinate!

Conversley, all North American Longitude coordinates WILL NEED a negative (-) sign placed in your latitude coordinate.... most all WFO players live between -123.xxxx (western Oregon) and -63.xxxxx (eastern Canada).

WC, do you mind if I send the above quote to the, um, "right people", as an improvement suggestion to the Maps API? Did you get any errors back from the API?

 

[Warchild]

WC, do you mind if I send the above quote to the, um, "right people", as an improvement suggestion to the Maps API? Did you get any errors back from the API?

Sure, go ahead.

I am not seeing anything being returned from Google when it runs into a borked XML file... the only way I caught this was using FireBug plugin for FireFox... this is an awesome developer tool! It detected that the script was "hung" and offers you options to abort the script, continue processing, or retry it all together.

Truthfully, I don't know what Google can do about it; if I was a Google developer, I would probably suggest that you don't, um, submit a borked XML file for processing! :lol: I guess they might be able to return a generic javascript alert box to indicate a malformed XML file was submitted, or words to that effect....

 

[Woodstock]

WC, do you mind if I send the above quote to the, um, "right people", as an improvement suggestion to the Maps API? Did you get any errors back from the API?

Sure, go ahead.

I am not seeing anything being returned from Google when it runs into a borked XML file... the only way I caught this was using FireBug plugin for FireFox... this is an awesome developer tool! It detected that the script was "hung" and offers you options to abort the script, continue processing, or retry it all together.

Truthfully, I don't know what Google can do about it; if I was a Google developer, I would probably suggest that you don't, um, submit a borked XML file for processing! :lol: I guess they might be able to return a generic javascript alert box to indicate a malformed XML file was submitted, or words to that effect....

Yea, I'll see what the API guys say here, there might be some way of having a "verify" type call or something else that might make it easier for webpage developers to use, but not mess up users with alert boxes that they can't do much about.

 

[Wolfhound]

I've sent 2 emails trying to get on the map. I have everything entered right but . . . . ? Any ideas besides shut up & get there ?

 

[beemerdons]

Good Morning Robert,

Have you been reading the posts that I'm going to meet up with Fairlaner on 7/25 in Flagstaff? You would be welcome to share the room at Best Western Kings Hotel with me, if you also wanted to ride up with the Californians. Adios, Chuy

 

[Wolfhound]

Hey Don,

I'm keeping up with the post but not sure yet about making plans. I may ride most of the way up 89 on Wed. so I can be there around noon Thurs.

I went up last Sat. leaving Phx at 6 pm & rode in 2 hrs rain before getting to Kanab for the night. Then went on up 89 to Bryce turn (Hwy12) & rode to Hwy 24, then over 95 to Blanding for the night & back thru Mexican Hat & home. AWESOME ROADS ! Great twisties and sweepers thru some of the best sights in UT.

 

[Farkles]

Ok I am stupid can't get my pin on map. :angry2:

 

[bvail]

Ok I am stupid can't get my pin on map. :angry2:

You have a lot of company, including yours truly...

 

[pegscraper]

Ok I am stupid can't get my pin on map. :angry2:

You have a lot of company, including yours truly...

Mine isn't up there either. The real answer is, THEY ran out of pins. :dntknw:

 

[Wolfhound]

question deleted

 

[Warchild]

Ok I am stupid can't get my pin on map. :angry2:

You have a lot of company, including yours truly...

Mine isn't up there either. The real answer is, THEY ran out of pins.

Oh, I don't think so......

The reason you three gentlemen can not see yourselves is most likely due to the fact you are using that POS Micro$oft IE browser, which is not DOM-compliant and is about as fucked up as a soup sandwich! :lol: So how 'bout we go take a look-see using a proper DOM-compliant broswer such as FireFox, hmmmmm?

For example, let's go zoom in on Colorado and see if we can find Mr. Bob Vail on the map..... why, look, there he be! :yahoo:

And what about our famous WFO Photographer, pegscraper? If we bring up the map in Firefox, I don't seem him *exactly* at Temecula, CA..... but I DO see him over near beeroux and GunMD! Looks like the Longitude coordinate used must be off a little. But Firefox shows your pin:

Finally, here you are, Farkles, you show up in Oregon just fine in FireFox.....

So..... if you want to see your pushpin on the map, then "just say no" to that MSIE dog-squeeze browser. Go install Firefox, and start living the Good Life.... :lol: