The North Dakota-wide Burkle
addressing system is wise. But let's see if we can be wiser.
So burkle-up your seat belts folks. Let's
unburkle the Burkle system, replacing it with our
single
axis (parameters: --fold 250 --axis w2n
).
Images: zoomed in to the center (0, 0) of Burkle's system, and the values of the same points and more, in our system (the single axis of which is off the screen.)
→
All we are doing is simply giving the value 250 to Burkle's 0 E/W, and 750 to Burkle's 0 N/S.
So our single axis starts at a some unimportant point southeast of our state of North Dakota, in Minnesota. Then it advances westward 500 miles, now southwest of our state, all the way over in Wyoming in fact. Whereupon it turns north, going 500 more miles, ending up somewhere in Saskatchewan, Canada.
We disposed of Burkle's reliance on "NE", "SE", "SW", "NW".
No more "Street" vs. "Avenue" either. Let's call ours all just "Road" to not confuse them with Burkle.
We kept Burkle's connection to the underlying Public Land Survey System (PLSS) though. That allows us to "mow" through correction lines without a hiccup.
(If this were Xinshe I would call 250th Road "Lane 25000", i.e., roads and addresses needing no multipliers between them.)
So our center is at 25000 750th Rd. (75000 250th Rd.) To make a rural / urban "one size fits all" system, we would need to call our (same) center 250000 750th Rd. (750000 250th Rd.) Err, Umm... I think I will just stick to my goal of yanking out Burkle's two axes and replacing with my single one, and not change anything else!
Note we are in no way avocation overthrow of the Burkle system. Now that it is implemented they should stick with it. We are just doing a "what if" fantasy simulation.
Last modified: 2024-08-14 02:07:18 UTC