Re: Our small comunity is moving a historic house

In article <1175986474.228733.239990@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"karen.holt@xxxxxxxxx" <karen.holt@xxxxxxxxx> wrote:
House moving is rather expensive - our budget was 80K but that
included removing some utility lines, permits, new foundation &
basement, basic electrical service, etc. The moving piece was a little
over half. The house is very large and we are moving it about 2 miles,
through the fields, over a creek, up a hill, to the new location.

Speaking of house moving, consider this picture:

<http://maps.google.com/maps?ie=UTF8&oe=UTF-8&hl=en&q=&z=18&ll=34.148048,
-118.136576&spn=0.003418,0.004222&t=h&om=1>

(Here's a smaller URL: <http://tinyurl.com/37su4c>).

See the building with the reddish roof in the center, north of the
parking lot? That building was not originally there. It was moved in.

I was living in the apartment building next to it to the north at the
time, and have no idea how the hell they did that move. I saw them
build a foundation for it. They finished that one day, and when I went
to bed, that is all there was there: a foundation with nothing on it. I
had no idea they were going to move something there--I thought they were
building a new building. I didn't see anyone taking down streetlights,
or clearing trees, or anything, around the roads leading to the site.

When I woke up the next morning, the building was sitting in the parking
let, next to the foundation, on 144 wheels. Over the next few days,
they moved it onto the foundation.

What puzzles me is that I can't see how the hell they got it in there.
It was in one piece, as far as I could see. It came from about 8 miles
away (from Temple City, which is to the southeast, if you zoom the map
out a bit). I don't see any route out of that area that is big enough
for that thing.

This is actually the second puzzling movement incident I've seen,
although the other was much smaller. At a place I worked, we had a
machine for printing blueprints. This thing was huge. It was about 10
feet wide, and something like 5 feet deep, and 4 feet tall. It was in
an interior room, with one door. There were two routes to that door.
One from the front door, which went past the secretary and the door to
the co-founder's office. The other went through a long hallway, around
a tight corner, and past a lab.

One day, at just before noon, someone used the blueprint machine, and
then went to lunch. When they got back, it was missing. The secretary
and co-founder had been in during that whole time (and the co-founder's
door was open, giving him a clear view). I was in my office on the long
hallway, with my door open, and I was facing the hall. Same for a
couple other programmers.

We later found out it was repo men. But how the hell did they take it
with no one noticing? It was huge and heavy, and would take at least
two, and probably three, men to slowly move.

--
--Tim Smith
.

Relevant Pages

  • Re: Our small comunity is moving a historic house
    ... The house is very large and we are moving it about 2 miles, ... feet wide, and something like 5 feet deep, and 4 feet tall. ... There were two routes to that door. ...
    (alt.home.repair)
  • spell their restoration on board the introduction
    ... she pushed the door shut, ... in the "bismint" when he had been in front of me, ... The hall of the house was dark. ... A clatter of feet, and the man's head appeared from a dimly ...
    (sci.crypt)
  • Re: Dog haters
    ...  To start with, mailboxes are normally hung ... on the house itself or within 5 feet of the door here. ... I got rid of my entire front hedge of boxwoods at our other house ...
    (rec.pets.dogs.behavior)
  • Re: Small Septc System for Shop
    ... >Go take a leak in the barn or walk the 150 feet to the house.. ... This gets my vote. ... just step out the door and wiz. ...
    (alt.home.repair)
  • Re: Cindy
    ... I think moving next door to OS should be his top priority., If a house isn't ... taking the time to remind Wally that Minnesota is not a warm weather state, ...
    (misc.news.internet.discuss)