grimley1968
DIS Veteran
- Joined
- Apr 2, 2005
- Messages
- 5,780
Swim across the canal and be done with it!
Nah. They should build a tunnel. Surely that wouldn't be expensive, right?

Swim across the canal and be done with it!

Swim across the canal and be done with it!

I have two words for you: Big DigNah. They should build a tunnel. Surely that wouldn't be expensive, right?![]()

A small trampoline on each side of the canal. Have a bit of a run up and then bounce over.![]()
They keep all the other boats at the various resorts - not an option for the ELP floats. As for workable solution, apparently Disney has determined there's not a need to invest money on something that, most likely its own research has shown, will be utilized by relatively few Guests.steve76 said:Er, if it's a drawbridge then it can be at any height you want. It can be at the same level as the path. Alternatively they could just keep the EWP floats somewhere else, like where they keep all of the other boats. I really don't think it's beyond Disney's capability to find a workable solution to getting across a canal!
Why not?They keep all the other boats at the various resorts - not an option for the ELP floats.
Now you are just making stuff up. All we know is Disney chooses not to connect the path. Just like they choose not to connect paths all over WDW. No need to make up an assumption that Disney has done research on how many people would or wouldn't use the path.As for workable solution, apparently Disney has determined there's not a need to invest money on something that, most likely its own research has shown, will be utilized by relatively few Guests.
Why? Why should Disney relocate the floats which have started and ended at the same location since the EWP's inception?Why not?
No. You must have missed where I qualified my response with "apparently" and "most likely". Everybody else in this thread appears to be allowed to make assumptions without being attacked. I'm surmising based on common sense. People have been walking since, well, forever. Disney knows this. The parks allow/require a great deal of walking to experience. In all the year the Grand Floridian has existed, Disney has apparently determined (i.e. not seen sufficient demand, or much need) that such a route would not be used enough to justify spending the money.Now you are just making stuff up.
I didn't say Disney *should* relocate the boats. I merely challenged your assumption that moving the boats "wasn't an option." It's one thing to say Disney chooses not to move the boats. It's another to say they can't.Why? Why should Disney relocate the floats which have started and ended at the same location since the EWP's inception?
I got those. I just don't see anything that would make it apparent that Disney has conducted a survey, nor do I see any reason that it is most likely that Disney had conducted a survey.You must have missed where I qualified my response with "apparently" and "most likely".
Sorry if I was a bit strong there. My bad. I do see a difference between people thinking something, supposing something, suggesting maybe something - and the words "apparently" and "most likely". I'm also a bit frustrated by the many attempts by people in this thread to suggest that the distance is far too for people to walk, or that people wouldn't want to.Everybody else in this thread appears to be allowed to make assumptions without being attacked.
I'm surmising based on common sense. People have been walking since, well, forever. Disney knows this. The parks allow/require a great deal of walking to experience. In all the year the Grand Floridian has existed, Disney has apparently determined (i.e. not seen sufficient demand, or much need) that such a route would not be used enough to justify spending the money.
Safety makes perfect sense to me as one of the reasons Disney might not walk people to walk. There are lots of possible reasons, or combination of reasons. I don't know.What about safety? Sure, the GF side is already lit, per grimley's research. But the path appears to be somewhat isolated; whereas the walkway to the Contemporary is visible and apparent. If there was an emergency, vehicles can get to Guests efficiently on this latter route - less feasible in relation to a walking path/bridge/overpass. Then, too, the MK-GF route seems to open itself to the possibility of 'stupid guest tricks', given its relative isolation.
Thirty-eight years of Electric Water Pageant, maybe, combined with a likely lack of requests? I'm sure there's no formal survey - but what about a general tally of how many GF Guests ask about walking between the resort and the park?DisneyWalker44 said:I got those. I just don't see anything that would make it apparent that Disney has conducted a survey, nor do I see any reason that it is most likely that Disney had conducted a survey.

There are actually several thousand bricks down that path. I would hate to be one who purchased a brick, then found out it was WAY down at the end where no one would see it.![]()

What makes you think it doesn't? People *like* walkways. People like having walking access to theme parks (even if they already have boat and/or monorail access). Read what people write on the resorts that have walking access and you'll see that's true.How much research does it take to figure out that adding a walking path doesn't produce revenue or cut costs?
![]()
The Walk Around the World project was originally announced as a path that would go all the way around the Lagoon. This could be another case of Marketing and Facilities not communicating with each other.

How much research does it take to figure out that adding a walking path doesn't produce revenue or cut costs?
![]()
DisneyWalker44 said:What makes you think it doesn't? People *like* walkways. People like having walking access to theme parks (even if they already have boat and/or monorail access). Read what people write on the resorts that have walking access and you'll see that's true.
There you go! That resolves any issue with a connection being non-revenue-producing!Steve Mouse said:2 words: toll bridge
![]()