Surveyor Use of Traverse/Meander Lines Violates U.S. Constitution and Federal Laws
All use of traverse and meander lines in the creation of subdivisions and land divisions by certified surveys pursuant to Michigan legislation such as the Plat Act of 1929, the Land Division Act of 1967 and the Certified Surveys Act of 1972, violate the Property and Supremacy Clauses of the United States Constitution and the federal Land Acts. Traverse or meander lines were solely tools of the original federal government surveyors in the creation of 30 states of this nation including Michigan. Only the original federal government surveyors created waters as boundaries which made them riparian.
Unfortunately, there are many thousands of these waterfront subdivisions throughout the state, and more are continually being created. These surveys serve as as evidence of a state absolutely out-of-control of its power and authority. Local governments, developers, their agents and other professionals are exposed to liability in the buying and transferring of waterfront and water access lots to the extent that these surveys interfere with the original boundary and meander lines established by the federal government. The reasons for this risk exposure are many but, primarily, that the subdivision plats and certified surveys created under state law by surveyors are fraudulent representations by them that lots have riparian rights based upon state mandated traverse or meander lines in the documents. For an entire century, buyers have been informed by surveyor use of meander and traverse lines that owning property adjacent to any water-covered land gives them further ownership to the center of it. However, the state has no jurisdiction to create water body boundaries from land patented to private owners by the federal government. For that entire century, buyers have been continually duped.
Refrain from buying lakefront or riverfront lots in a subdivision in Michigan which was created in 1929 or later, without contacting Lake Property Law at email@example.com