Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your email address or mobile phone number.

Atlas of Historical County Boundaries North Carolina

5 out of 5 stars 1 customer review
ISBN-13: 978-0133664690
ISBN-10: 0133664694
Why is ISBN important?
ISBN
This bar-code number lets you verify that you're getting exactly the right version or edition of a book. The 13-digit and 10-digit formats both work.
Scan an ISBN with your phone
Use the Amazon App to scan ISBNs and compare prices.
Have one to sell? Sell on Amazon
This book is not available.
Out of Print--Limited Availability.
Free Two-Day Shipping for College Students with Amazon Student Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student


Save Up to 90% on Textbooks Textbooks
Out of Print--Limited Availability.
NO_CONTENT_IN_FEATURE



Product Details

  • Series: Atlas of Historical County Boundaries
  • Hardcover: 434 pages
  • Publisher: Charles Scribner's Sons (May 1998)
  • Language: English
  • ISBN-10: 0133664694
  • ISBN-13: 978-0133664690
  • Product Dimensions: 11.2 x 8.8 x 1.3 inches
  • Shipping Weight: 4.3 pounds
  • Average Customer Review: 5.0 out of 5 stars  See all reviews (1 customer review)
  • Amazon Best Sellers Rank: #8,126,881 in Books (See Top 100 in Books)

Customer Reviews

5 star
100%
4 star
0%
3 star
0%
2 star
0%
1 star
0%
See the customer review
Share your thoughts with other customers

Top Customer Reviews

This book is the best I have ever seen for showing the chronology of county boundary changes. The maps not only show the changing boundaries vs time, but show the location of the various cities, rivers, creeks, etc. A great book for genealogists with ancestors in North Carolina.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse