Legal Opinion

Township of Highland Grove v. Village of Winnipeg Junction

Supreme Court of Minnesota

Decided April 24, 1914No. Nos. 18,500 — (29)PublishedCited by 2 opinions

Action in the district court for Clay county against the village of Winnepeg Junction, and the treasurer and trustees of that village, to restrain defendants from distributing the balance collected from taxes by defendant village and to direct them to pay it over to plaintiff as the legal successor of defendant village. The ease was tried before Taylor, J., who made findings and ordered the dismissal of the action.

Read the full summary

Action in the district court for Clay county against the village of Winnepeg Junction, and the treasurer and trustees of that village, to restrain defendants from distributing the balance collected from taxes by defendant village and to direct them to pay it over to plaintiff as the legal successor of defendant village. The ease was tried before Taylor, J., who made findings and ordered the dismissal of the action. From an order denying plaintiff’s motion for a new trial, Nye, J., plaintiff appealed.

1Opinion of the CourtBrown, C. J.

Winnipeg Junction, some time during the year 1901, was duly incorporated under the general statutes as a village, and thereafter continued to conduct its affairs as such until dissolved as presently *281to be stated. The territory included within the village boundaries was comprised of a little over a section of land located wholly within the township of Highland Grove, Clay county. It was a small hamlet with a population of between 150 and 200 inhabitants, a store or two with the usual saloon, and was a junction point on the Northern Pacific Railroad, many of its inhabitants being railroad…

2Cited by2 opinions

  1. University of North Carolina v. City of High PointSupreme Court of North Carolina · 1932
  2. Addison Township School District v. Somerfield Borough School District, Pennsylvania Court of Common Pleas, Somerset County1943

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API