Deprecated: Assigning the return value of new by reference is deprecated in /homepages/12/d87796153/htdocs/wpholiday/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/12/d87796153/htdocs/wpholiday/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/12/d87796153/htdocs/wpholiday/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/12/d87796153/htdocs/wpholiday/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/12/d87796153/htdocs/wpholiday/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/http.php on line 61
Fulton History


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55
July 25th, 2009

fulton-sticky-photo

Although this map has Fulton on it, it is not showing it within the city limits. A story in itself…

 


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

BECAUSE I cannot get this to format properly


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55
April 16th, 2013

PLEASE SEE ANOTHER FULTON BLOG RECENTLY STARTED AT http://fultonhistory.wordpress.com/

SORRY FOR THE INCONVENIENCE!


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

let’s start here


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55
April 3rd, 2013

I’ve been doing neighborhood research on the area east of Ferry Street in Madison, Indiana on what I call my ferrytofulton blog, or Madison, east of Ferry, Neighborhood History from Madison, Indiana’s Ferry to Fulton area. In addition to my exploration of that section of town I am trying to map out the Town of Fulton (not Fulton county) in Madison, Indiana. There is less information available on Fulton than there is/was on the area east of Ferry to the town of Fulton, or that which people have referred to as Fulton in the few mentions I have found. This is going to take a while. This is what I’d call a progression blog…you’re reading wherever I am in the progression of my research.

A few years ago, I started this research because of the city/state plans to put a new bridge through the neighborhood in which I live. At that point, I realized that anything east of Ferry Street, my neighborhood, was a forgotten part of history. I tried to do more research, but I was new at it, and when the courthouse caught fire and then all the records were sent out for cleaning and repair, my research was put on hold. Fortunately, the bridge was replaced on old piers and my research could wait for another day.

I was not reading much about Fulton in the history books, just a few mentions that it was on Madison’s east side, or that it was an addition to Madison. My first real find on my own was a hand-drawn Town of Fulton map, a hand-written copy found at the Jefferson County Historical Society. In the drawing the Ohio River was colored blue, and the description was for the area south of Lawrenceburg Road, now State Road 56.

The Town of Fulton addition to the city of Madison original is back at the courthouse. Just as the copy showed, the original shows that on the south side of what was then Lawrenceburg[h] Road, now State Road 56, there are 4 streets that run north/south within ten sections or blocks. The area south of State Route 56 was officially surveyed for John McIntire in 1844, and the Town of Fulton Addition to the city of Madison was recorded on September 4th, 1846.
The “corporation line” on all the maps I have seen is marked where the road’s name changes from Park Avenue to State Route 56. I have seen instances of the road named as the Madison & Brooksburgh Turnpike, the Lawrenceburg[h] Road, and on census sheets, as E. Second. Since I started my research I have seen lots of reasons to be confused about which road is which, so it is all a matter of comparison.

Throughout the research I have done to date, I looked at map after map and though I said the words, for some reason it did not dawn on me that if the Town of Fulton had been added to the city of Madison, certainly the maps should be showing the addition now within the city limits. All those maps, some 160 years of drawings have continued to show the city corporation line, or city limits, at a line previous to said addition. If property was added or annexed, why was there no change on the maps?

The map I had referred to most often regarding Fulton was that of the 1854 map that I first saw on the wall of the Madison Jefferson County Public Library, and subsequently had a portion of the map enlarged and copied through the Jefferson County Historical Society. Unfortunately, even that map showed the corporation line still west of the Town of Fulton addition. In 1854, there was not a lot shown on the 1854 map just east of that corporation line, but the word FULTON is there and homes and lot lines are shown.

I felt as though I would have to draw a map with whatever found through deed research because anything on the south side of the riverfront road (shown as Fulton Street) between Ferry and the end of Fulton has been wiped off that map. Only a few buildings shown on the 1854 map between what was then Lawrenceburg[h] Road and Fulton Street still exist.

On the north side of State Road 56 is the land known as the John Marsh Add to Fulton. Whatever was added to “Fulton” certainly would then be part of Madison as well, right? I continue my research. On the O’Brien survey, the property shown as lot #1 (north of the road) is split; the western part is in the “city” while the eastern part is “county”, as the neighbor puts it. One day the homeowner for lot #1 (north side) was outside cutting back trees and bushes from the rock wall on the property and told me she was surprised to find out her property was taxed as two separate plots. My neighbor, Dave, showed me his survey work, referred to as the Guerich survey (which referred to Barnard Warren property) and told me the properties were “all part of one, but as the individual lots sold the split occurred”. I saw the words “stone located” and a description, so I decided it makes for a nice beginning. After that, I have to work backwards a little.

By starting at the westernmost boundary of what is specifically in the John Marsh Add to Fulton, I found what I believe to be the notched stone in the woods and from there was able to verify the stone wall on the western side of the property I presently inhabit on the south side of Park Avenue as the reference point mentioned in the 1975 survey for the first few lots on the north side of Park Avenue at the line where it becomes State Route 56, previously known as Lawrenceburgh Road.

The last Park Avenue address on the north side is 1035 Park. A building on the Brushfield property (that property being mentioned in the legal description of the survey), located on lot 3 of the Brushfield addition, has been written throughout history as being the eastern boundary marker for Madison, Indiana. That brick building dates at least to the 1854 map, since it is shown there, but no one can yet say exactly (yet) when it was built. The Brushfield property shows up as the east boundary for the city as well as a boundary for other additions to the city. I have found a deed and maps showing the Brushfield Subdivision, as well as the Fulton Addition.

Though my neighbor’s survey shows he is occupying lots 2, 3 and 4 in the John Marsh Addition to Fulton, one still needs to compare newer versions with older maps to know if this is actually considered property within the city of Madison or county land.

I stopped my research for a couple of years due to health issues, thus I have no elaboration yet on my neighbor’s property. I re-started my research after the post office decided that due to traffic danger they would not be able to continue home delivery on Park Avenue, and provided a cluster box for the neighborhood mail a block away. Since the entire neighborhood would have to traverse the same road and one where there were no sidewalks, to get our mail, I asked the city to negotiate delivery on Park Avenue. The negotiation put us where the post office wanted us all along, with curb delivery. When decisions about where to place posts brought up the city/county line I decided it was time to look into this again, and found the original plat at the courthouse.

When I found the original plat for the addition to the city of Madison, I went to visit the 911 director to ask about coverage for this area. He told me it was covered under the county’s emergency services, not the city. I explained to him my issue with the maps. He said he would be the one to change or correct a map but that would have to go through the city. I walked him to the courthouse, had them print out a copy of the addition to Madison, and decided to follow up on my own.

Stay tuned for history as I write it.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

I’m having “issues”…my blog is not functioning properly :(


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55
April 1st, 2013

THIS BLOG IS CURRENTLY IN GREAT NEED OF REPAIR> AM WORKING ON IT!


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55

Fulton?


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/12/d87796153/htdocs/wpholiday/wp-includes/functions.php on line 55
July 30th, 2009

Fulton, Indiana? Know where that is? Some might think, at first mention, that I was talking about a town in Liberty Township, Fulton County, Indiana, but no, that is much farther north than where my buffalo roam. This is about the Town of Fulton,  an addition to Madison, Indiana on the north bank of the beautiful Ohio River.

Ok… let’s do this again…Fulton? Oh. sure. I know where that is…or was…or maybe I should say what used to be called the”Town of Fulton” which is an area that a lot of people in Madison, Indiana don’t know much about. Those that live there know it is a part of the city of Madison that somehow has been forgotten in the history books.  Forgotten? No, not really. Maybe the history just buried a little. Time for the Fulton revelation.

Research is like peeling an onion;  history reveals itself in layers.shrek-onions Of course, there are those quotes from the movie, Shrek, to remind me that not everyone likes layers. Well, the truth is like that, too; sometimes it makes you a little teary-eyed, like an onion on the chopping block, and sometimes you just savor each unwrapping, maybe even thinking about carmelizing it with some sugar. Of course, good research is like a working marriage, using old and new to make it work, so there is that other Shrek-onion reference where the onion is a carriage. At some point you have to have the imagination and creativity to get you from one place to another. I have a tendency to see things a little differently and know the truth is often buried within something else. It’s like a treasure hunt, at times!

Obviously this is not the typical “history blog”. You will discover that as you read posts here and on the ferrytofulton blog as well. I don’t know if I need two blogs or not, but I am not that conputer savvy yet for a dot come and since these are two separate areas of research and each a unit in itself, it seems easier to do it this way.robertfulton

Where was I? Oh yes, back to Fulton. Should we assume that the town of Fulton is named for Fulton of steamboat fame, maybe it was named after the Reverend Andrew Fulton…anyone remember him? Could the town have been named for someone’s place or origin or a family member? I can’t say for sure but I am leaning toward the first thought, especially since there were a few shipyards in the area. I will have to look at other possibilities, though. ;)

described-1846How about a description of where Fulton was/is? Ok, this from an early subdivision plat map as found at the Jefferson County Historical Society’s facility in Madison, Indiana:

“…on the Ohio River in Jefferson County Indiana, being a part of fractional Section No. One  Township No. Three North of Range Ten east in the Jeffersonville District and adjoining and being east of Brushfield’s Lot Fulton Street  bearing…”  Blah, blah, blah, it’s on the map. The “Jeffersonville District” threw me a little, but I know the description is for Madison, Indiana, not Jeffersonville, Indiana or Port Fulton, Indiana, either. I know it can get confusing at times. So much to sort out, so little time.

Want more?  Stay tuned. Come back for a visit or check out the Ferry to Fulton posts, which are about an area that often overlaps the boundaries.