<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tractplotter.com Development Blog</title>
	<atom:link href="http://www.tractplotter.com/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.tractplotter.com/blog</link>
	<description>Plotting Tracts, one day at a time</description>
	<lastBuildDate>Wed, 02 Jun 2010 03:12:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A Primer on Metes and Bounds Descriptions, Part I</title>
		<link>http://www.tractplotter.com/blog/?p=7</link>
		<comments>http://www.tractplotter.com/blog/?p=7#comments</comments>
		<pubDate>Mon, 26 Oct 2009 08:44:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.tractplotter.com/blog/?p=7</guid>
		<description><![CDATA[Well, a week has passed since my last entry, so I guess it&#8217;s time to write again.  First off, here&#8217;s this week&#8217;s Plot of the Week:

This plot describes a tract 37.7 acres in area with a closure of less than 0.004 feet!  Now that is just amazing.  I love the graceful curve that forms the [...]]]></description>
			<content:encoded><![CDATA[<p>Well, a week has passed since my last entry, so I guess it&#8217;s time to write again.  First off, <a href="http://tractplotter.com/?Submit=Submit&amp;calls_string=S40.39.35W%20822.28FT%0D%0AS40.00.27E%20362.83FT%0D%0AS40.16.11W%20198.00FT%0D%0AS08.14.07E%20653.90FT%0D%0AS46.33.56W%20506.22FT%0D%0AS74.56.13W%20498.30FT%0D%0AS43.48.47E%20288.92FT%0D%0AN74.51.13E%20545.16FT%0D%0AN39.08.13E%201129.42FT%0D%0AS75.07.13E%20752.78FT%0D%0AN48.50.07E%20157.82FT%0D%0AN00.47.13E%2071.25FT%0D%0AN12.59.59E%20123.90FT%0D%0AN12.39.26W%2049.74FT%0D%0AN63.15.17W%2042.98FT%0D%0AS80.26.35W%2071.27FT%0D%0AN72.56.36W%2069.19FT%0D%0AN58.21.15W%20407.77FT%0D%0AN57.55.12W%20145.20FT%0D%0AN47.02.45W%2089.63FT%0D%0AN37.53.11W%2044.04FT%0D%0AN28.11.10W%2070.72FT%0D%0AN19.53.37W%20175.58FT%0D%0AN25.51.25W%2091.05FT%0D%0AN15.45.18W%2088.63FT%0D%0AN00.12.39E%2073.29FT%0D%0AN22.12.15E%2079.97FT%0D%0AN13.05.57E%2056.05FT%0D%0AN14.24.09W%2044.77FT%0D%0AN57.58.43W%2066.78FT%0D%0AS86.30.17W%2084.03FT%0D%0AN77.05.05W%2060.91FT%0D%0AN41.31.00W%2056.50FT%0D%0AN13.23.57W%2077.66FT">here&#8217;s</a> this week&#8217;s Plot of the Week:</p>
<p><img src="http://tractplotter.com/plotted-images/d747399ae4b5a0b3976bb2084f935da4.png" /></p>
<p>This plot describes a tract 37.7 acres in area with a closure of less than 0.004 feet!  Now that is just amazing.  I love the graceful curve that forms the northeast side of the tract.  It must be a river or creek.  Of course, the &#8220;curve&#8221; is all made up of straight lines, but there are enough of them to give a very impressive curve effect.</p>
<p>Now, on to the main subject of this entry.  This entry is for the beginners out there who have found the site and know that they need to use it somehow, but don&#8217;t really know what they&#8217;re doing.  Maybe they&#8217;re a landowner looking at the deed to their own property, or somebody just getting started in the real estate business.  Well, this little primer should be able to get you on your way to plotting tracts in just a few minutes.</p>
<p>In general, there are four ways of legally describing a piece of land.  The first (and least precise) way is to list the tracts that surround it.  While it may have been sufficient at one point in the past to say that Farmer Eli&#8217;s farm is east of Farmer Abe&#8217;s, south of Farmer Bob&#8217;s, north of Farmer Coy&#8217;s, and west of Farmer Doc&#8217;s, such descriptions don&#8217;t hold much water in today&#8217;s world.  The second method (more about which later) is a metes and bounds description.  The third method is to refer to a plat or map which contains a drawing of the tract, which includes measurements, angles and possibly other information as well.  This is the usual method for describing tracts within cities and subdivisions; a plat is filed with the County Clerk or other government registrar, and subsequent references to the tracts therein are referred to by numbered spaces on the plat, usually Blocks and Lots.  The fourth and final way is by referring to the Public Lands Survey System method by which most of the United States was surveyed.  I may talk about that method another day, but for now suffice it to say that Tract Plotter does NOT currently recognize such tracts.</p>
<p>Tract Plotter is a way of bridging the gap between the 2nd and 3rd methods of tract description; that is, it is a way to create a visual plat from a metes and bounds legal description.  However, a plat is only as good as the information fed into it.  If your description has many lines like &#8220;in a northerly direction to an Elm tree 14 inches in diameter,&#8221; then you might as well give up now.  There is simply no way to create a decent plat from such imprecise measurements.  &#8220;Northerly&#8221; is not a direction.  If you come across such a description, however, all is not lost.  You can still reconstruct a description for the tract on the basis of other, later descriptions.  For example, if the tract was divided into two separate tracts which were later sold separately, hopefully there were decent descriptions for both of those descendant tracts, and you can piece the two together in order to figure out how the original tract was shaped.  Sometimes you may have to follow the tract through two or three generations before you can get a reliable description; but when you have one, you can work your way backwards to get a description for the original tract.</p>
<p>Now, what makes for a <em>good</em> legal description?  Every call needs to have a solid numerical distance and a bearing.  The distance part is fairly easy to understand.  A distance could be 20 feet, 90 yards, 33 varas, 92 links, or what have you.  Each distance contains a number and a unit.  There are many units that have been used to describe land in the US, and Tract Plotter understands most of them.  (Let me know if there are any that I&#8217;ve missed!  I&#8217;m particularly interested to know of varas other than Texas varas, which are 33 1/3 inches.)  So distance is no problem as long as you know the units.  Most modern tracts in the US are measured in feet, and feet are the default unit in Tract Plotter.  So if your description uses feet, you don&#8217;t have to worry about including units in your input.</p>
<p>The only &#8220;gotcha&#8221; when it comes to units is compound units, e.g. feet and inches.  Tract Plotter only uses decimal representations of single units, and as such, does not recognize compound units.  For example, if you have a legal description that says &#8220;104 feet, 5 inches&#8221; then you will need to manually translate this distance into 104.416f.</p>
<p>Bearings, on the other hand, have been known to cause confusion.  Cardinal directions, such as due North, are easy enough to understand.  However, most tracts do not run in pure cardinal directions.  A typical bearing might read &#8220;North 30 West&#8221;.  All that this means is that the line runs 30 degrees westward of North.  Here is what North 30 West looks like:<br />
<img src="http://tractplotter.com/plotted-images/6f1ae12b7ced5f3302134cfa961961de.png" alt="" /><br />
Note the blue dot.  That is the starting point.  The line travels N30W from that starting point.  To show you why this is important, here is South 30 East:<br />
<img src="http://tractplotter.com/plotted-images/66b97bf9496a1ed4d6081e0dbec5dd8c.png" alt="" /><br />
&#8220;But that&#8217;s the same line!&#8221; you protest.  Indeed it is.  However, the starting point is different.  In this example we have started at a point (the blue dot) and then travelled along a line headed 30 degrees East of South.  So, here we have our first important finding: <strong>Every boundary line in a tract can be described in two different ways.</strong> You can start at one end and work your way in one direction, or you can start at the other end and work your way the other direction.  The way to switch directions is pretty simple; simply swap the &#8220;N&#8221; or &#8220;S&#8221;, and the &#8220;W&#8221; or &#8220;E&#8221; in the bearing.  Leave the bearing degrees, minutes, and seconds alone; and leave the distance alone.  However, both the N/S and the E/W parts of the bearing must be swapped.  Look at the example above and you will see why.  A line that runs NW is the same as a line that runs SE, but different from a line that runs NE or SW.</p>
<p>Now, a couple more things to finish up the treatment of bearings.  You may recall that there are 360 degrees in a circle.  However, since we effectively divide up the circle into 4 quadrants with the N/S and E/W bearing calls, we really only have to deal with 90 degrees as the maximum number in the bearing.  Tract Plotter accepts cardinal bearings such as &#8220;N&#8221; or &#8220;W&#8221;, so you don&#8217;t have to waste your time if a bearing says &#8220;North 90 degrees West&#8221;, which translates as due west.  You can just enter &#8220;W&#8221; into Tract Plotter and save a little time, although &#8220;N90W&#8221; is valid as well.  Tract Plotter will also handle nonsensical bearings such as&#8221;N120W&#8221; (which really should be written S60W), although, if you find such a bearing in a description, it is likely to be in error.  I will probably fix this at one point and restrict the maximum bearing angle to 90 degrees, but for now I will leave it as is.</p>
<p>Finally, we get to the issue of degrees, minutes, and seconds.  As stated above, there are 360 degrees in a circle, but we only really use up to 90 of them in a bearing.  A degree is divided into 60 minutes, and each minute is divided into 60 seconds.  The usual symbol to indicate degrees is a little circle like this: °.  Minutes and seconds are usually denoted in the same way that they are in the context of time; i.e., a single quote &#8216; for minutes, and a double-quote &#8221; for seconds.  However, these often are not terribly practical for data entry purposes (especially the degree symbol, which is not on most keyboards and requires a special key combination to enter into most computers).  For this reason, Tract Plotter simply uses the standard period to delineate between degrees, minutes, and seconds.  For example, the translation of the deed call <i>North 48 degrees 32 minutes 19 seconds West</i> or <i>N 48° 32&#8242; 19&#8243; W</i> would be <i>N48.32.19W</i>.  If your deed lacks minutes and/or seconds, simply leave them out.  If you have a leading zero for any of the units, e.g. <i>N 08° 03&#8242; 06&#8243; W</i> then you can omit the zeroes: <i>N8.3.6W</i> (although you may want to include them for your own sake; personally, I usually include all digits, including zeroes, so that all of my deed calls line up in the Tract Plotter entry box).</p>
<p>Well, that wraps up this week&#8217;s blog entry.  Please comment if you have any questions or feel that I left out anything basic in this post.  Next week I will get more into some of the finer points of metes and bounds descriptions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tractplotter.com/blog/?feed=rss2&amp;p=7</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wow, it&#8217;s been a while!</title>
		<link>http://www.tractplotter.com/blog/?p=6</link>
		<comments>http://www.tractplotter.com/blog/?p=6#comments</comments>
		<pubDate>Mon, 19 Oct 2009 10:08:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.tractplotter.com/blog/?p=6</guid>
		<description><![CDATA[My apologies for the long delay since last writing.  I am just writing now to let you know that I have made some updates to the site code.  There were previously some errors in certain situations.  Most notably, when tracts had a straight north-south line, in a small percentage of cases, the acreages could be [...]]]></description>
			<content:encoded><![CDATA[<p>My apologies for the long delay since last writing.  I am just writing now to let you know that I have made some updates to the site code.  There were previously some errors in certain situations.  Most notably, when tracts had a straight north-south line, in a small percentage of cases, the acreages could be computed wrongly (and would usually end up smaller than they should have been).  Also, I have made some refinements to the way that areas are computed in general, although these should not be noticable in most cases, as the refinements only apply to very very small areas (ten-thousandths of an acre or less).</p>
<p>As always, please feel free to let me know if you come across a plot where the acreage is obviously wrong.  Please only do this if you are sure that the plot is otherwise well-formed, i.e. it closes fairly cleanly and no errors are shown.  If you do come across this, please leave a comment on the blog.</p>
<p>I am getting &#8220;back into the swing of things&#8221; after a hiatus from programming.  I must admit that I had a bit of a mental block to getting the above-mentioned errors fixed, as they meant a re-writing of a large portion of the site&#8217;s most basic programming.  However, now that that&#8217;s done, I am free to move towards larger changes.  In particular, I want to get the site to a revenue-generating state by the end of the year for tax purposes.  I have a game-plan in mind for how to implement arcs, which will only be available in the paid version.  Also, paid users will be able to save any plot and come back to it at a later time.  Joining of multiple plots will also be easy and fast (although I have noticed that some people have figured out a way to do this with the existing site by careful manipulation of the deed calls).  Of course paid users will also be able to resize the plat size as large as I can practically make them (at least big enough to fill an 8&#215;11 sheet of paper).</p>
<p>From time to time, I browse the submitted plots (I have all of them saved) and I am frequently amazed by some of the huuuuge plots you guys are making!  Not necessarily huge in terms of acreage, but huge in terms of having many calls which create very interesting-looking tracts.  <a href="http://tractplotter.com/?calls_string=s00.13.50w+2241.69f%0D%0As89.47.56w+989.75f%0D%0As00.13.11e+311.39f%0D%0An89.51.00w+912.47f%0D%0An00.40.50w+2906.09f%0D%0As89.40.21w+1194.23f%0D%0An00.26.42w+1128.54f%0D%0An89.58.08e+607.38f%0D%0An00.15.45w+1436.17f%0D%0An89.47.27e+1857.09f%0D%0As00.19.26e+30.50f%0D%0As89.27.46e+32.77f%0D%0As00.06.03w+1405.90f%0D%0As89.57.38e+949.42%0D%0As00.25.59w+1319.66f%0D%0As89.31.36w+1215.35f%0D%0As+623.50f%0D%0Ae+526.58f%0D%0An+472.99f%0D%0An89.52.48e+380.43&#038;Submit=Submit">Here</a> is an example of what I&#8217;m talking about.</p>
<p><img src="http://tractplotter.com/plotted-images/e7901bfee4214985627b4931ba5c8f38.png" /><br />
<br />
This tract is 264 acres in area and has a perimeter of over 20,000 linear feet.  And it closes to within 28 feet!  Nice work!  I like the little 30-foot square chunk out of the northmost northeast corner.  I think I will make a weekly thing out of this, posting a new and interesting tract every week.  Privacy should not be a concern, as everything is completely anonymous, and of course nobody knows where a given tract is actually located in the country, or even in the world.  Yes, we even have some users from the UK and a few other locations outside the United States that apparently use metes and bounds descriptions.  </p>
<p>In fact, I will give some site statistics as well, as it&#8217;s kind of a fun thing and I&#8217;m happy with the site&#8217;s growth so far.  As of today, there have been over 7,000 unique users of the site (people who have come to the site and submitted a plot at least once).  You have submitted just over 92,000 plots since the site opened in February of 2007.  The current rate is approximately 400 users per month and 3000-4000 plots per month.  Almost 800 of you have signed up for update e-mails, of which I have not yet sent any.  Based on a simplistic reading of these e-mail addresses, we have real estate agents, landmen, real estate developers, lawyers, and members of state and federal government agencies using the site.  Pretty neat!  I never thought the site would find such a wide range of uses.</p>
<p>Well, that wraps up this edition of the blog.  I hope to make more regular posts in the future and have some definite progress on the paid site.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tractplotter.com/blog/?feed=rss2&amp;p=6</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Percent Error and Area</title>
		<link>http://www.tractplotter.com/blog/?p=5</link>
		<comments>http://www.tractplotter.com/blog/?p=5#comments</comments>
		<pubDate>Mon, 17 Nov 2008 11:46:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.tractplotter.com/blog/?p=5</guid>
		<description><![CDATA[I just had a realization about the area error (&#8220;+/- X acres&#8221;) that I&#8217;ve been computing.  The way it is currently calculated is very simple.  Take the perimeter error percentage (also displayed in the results), multiply that by the computed area, and voila.  A simple way of expressing the potential error of the calculated area.  [...]]]></description>
			<content:encoded><![CDATA[<p>I just had a realization about the area error (&#8220;+/- X acres&#8221;) that I&#8217;ve been computing.  The way it is currently calculated is very simple.  Take the perimeter error percentage (also displayed in the results), multiply that by the computed area, and voila.  A simple way of expressing the potential error of the calculated area.  If your closure is 10% of the perimeter (now that I think of it, there are two ways of thinking about the perimeter; inputted perimeter (total distance of all deed calls inputted) and final perimeter (including any computed closure); the current implementation is the first way, which in one sense is correct, but in another sense overstates the percent error; I guess it&#8217;s better to err on the safe side and call the error bigger than it might actually be) (sorry for all the parenthesis folks, this is just how programmers think) then the area +/- is 10% of the calculated area.  Simple, no?  Perhaps too simple.</p>
<p>One of the first things you learn in geometry is that area is proportional to the square of linear distance.  The perimeter is a linear distance; the area is proportional to the square of the perimeter, therefore the calculated area error should be proportional to the square of the perimeter area.  As soon as I think of a way of implementing this without going completely nuts with the acreage error, I will fix it.</p>
<p>By the way, my reason for including this figure at all is just to draw the your attention to the fact that you have a problem of some severity with your plot.  Competing products (*ahem, &lt;REDACTED**&gt;*) will just adjust the calculated acreage, based on the error, and never inform you of that fact.  So if you input a square tract 200ft on a side, you will get 40,000 sf; but if you make an &#8220;error&#8221; and make one of the sides 205ft instead of 200, &lt;REDACTED&gt; will tell you that the actual acreage is MORE than 40,000 sf!  I know that a lot of sophisticated analysis probably went into solving this problem in &lt;REDACTED&gt;, but in my opinion this is the wrong way to go, and in fact it is a fairly ludicrous proposition.  I would rather leave that sort of judgment call to the user instead of having a one-size-fits-all calculated solution.  If the plot doesn&#8217;t close properly, the user can decide whether the acreage is right or not, and whether it should be adjusted up or down, or even whether the deed calls themselves should be altered to fix the problem (I know we have all come across transposed digits, missing digits, or otherwise mutilated deed calls).  I would rather give the &#8220;right&#8221; acreage, based on the input data, than include a &#8220;fudge factor&#8221; that in no way should be taken for gospel.</p>
<p>By the way, another thing that I do in terms of stating the error is truncate the number of significant digits in the acreage results.  If there is an error of &gt; 10%, you only get 2 significant digits; 1% &#8211; 10%, 3; 0.1% &#8211; 1%, 4; and &lt;0.1%, 5 significant digits.  This is just another kind of a &#8220;seat of the pants&#8221; error detection that I have included.  So if your tract doesn&#8217;t close by 20%, Tract Plotter is not going to tell you that it&#8217;s 42.385 acres.  It&#8217;s going to be 42, and even that is probably too generously precise, but I find less than 2 significant digits to be pretty worthless.  On the other end of the curve, more than 5 SD&#8217;s is probably better than any surveyor could ever trust his instruments.  But, as always, I leave the final decision up to you, as you can always see the full calculated value, out to as many SD&#8217;s as the computer can handle, by clicking on the &#8220;Show Full Precision&#8221; checkbox.</p>
<p>I definitely want to improve this significant digit algorithm in future versions, taking into account the precision of all entered data.  But, for now, I think it serves its purpose, and I hope that you find it useful.</p>
<p>**&lt;REDACTED&gt; refers to a leading provider of deed plotting software which, in my own personal opinion, cannot distinguish between legitimate criticism and libel.  In this blog posting, I have accurately described the behavior of &lt;REDACTED&gt; software, but they seem to think this constitutes libel.  In the interest of avoiding further legal hassles, I have removed their name from this blog entry.  However, I believe that my criticism stands.  Software should not provide surprise results.  A tract with sides of 200ft, 200ft, 200ft, and 205ft, all at 90-degree angles to each other, should not return an area greater than 40,000sf.  It should provide an area of 40,000ft exactly and let the user know that this might be wrong, preferably with a stated margin of error.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tractplotter.com/blog/?feed=rss2&amp;p=5</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Mineral Acres</title>
		<link>http://www.tractplotter.com/blog/?p=4</link>
		<comments>http://www.tractplotter.com/blog/?p=4#comments</comments>
		<pubDate>Fri, 01 Aug 2008 07:06:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.tractplotter.com/blog/?p=4</guid>
		<description><![CDATA[First off, I would like to thank everybody who has commented so far.  It is gratifying to see that the site is being put to good use.  Every comment is useful or thought-provoking in some way.  For example, now I am considering offering &#8220;lifetime memberships&#8221; or something like that that would be a one-time cost [...]]]></description>
			<content:encoded><![CDATA[<p>First off, I would like to thank everybody who has commented so far.  It is gratifying to see that the site is being put to good use.  Every comment is useful or thought-provoking in some way.  For example, now I am considering offering &#8220;lifetime memberships&#8221; or something like that that would be a one-time cost as if you had bought a piece of software.  As for making something available for download, I have considered that, but it would be beyond my technical capabilities, at least at this point.  Just a note, my main reason for starting this site in the first place was that I wanted to move entirely to the Macintosh platform instead of Windows, and deed plotting software was one place where I couldn&#8217;t see any alternatives on the Mac.  I had experience with PHP web programming before, so it was a natural step for me to put it on the Web.  Of course it has some limitations, but with things like the iPhone becoming more common, there are now more and more places where Tractplotter.com is usable.  Even if you&#8217;re standing in a courthouse in the middle of nowhere, chances are you will have cell phone reception and will thus be able to use your iPhone or other Web-enabled smartphone.</p>
<p>As for progress on the site: I am sad to say that there has not been much progress since the last blog entry.  My job, some out-of-town trips, and a family member in the hospital have kept me away from working on the site as much as I would have liked.  I am now setting an end-of-August target date for moving everything to the new server facility, and the rewrite for end-of-September.  Full &#8220;pay site&#8221; functionality will probably not happen before the end of the year.</p>
<p>Moving on to other topics&#8230;. Marty asked in comments for my insights on mineral acres.  Well, there really isn&#8217;t too much to say about mineral acres.  Usually you talk about mineral acres as being distinct from the actual acreage of a tract; i.e., we are talking about a partial mineral interest.  For example, maybe somebody owns a 50% mineral interest in a 10-acre tract.  This means that they have 5 net mineral acres, but the important thing is that those 5 net mineral acres are inseparable from the entire 10-acre tract.  It is like owning a half interest in a company; you can&#8217;t say that the inventory is yours and the physical plant and intellectual property is the other owner&#8217;s; you both own a 50% interest in the entire thing.  Or if you are a 20% partner in ownership of a racehorse, you cannot say that you own the head while the other partners own the rest of the body; you each have a 20% interest in the entire horse.</p>
<p>This is why we often see mineral interests referred to as &#8220;undivided&#8221; mineral interests.  To beat a dead horse, no pun intended, if you own the aforementioned 5 net mineral acres, you cannot point to any particular 5 acres of the 10-acre tract and say that you own those 5 mineral acres while somebody else owns the other 5.  If you wanted to, you could approach the other mineral owner(s) and negotiate to convey your 50% to them on 5 of the acres, and they would convey to you their 50% on the other 5 acres, and then you would have a 100% mineral interest in 5 acres and so would they (instead of each owning 50% of 10 acres).  Either way, it&#8217;s the same net mineral acreage, and this is probably not a terribly practical scenario for most people.  But, it could be done.  I&#8217;m only using it here to illustrate the concept of partial mineral ownership and how mineral acres are derived from the total acreage of the property.</p>
<p>Disclaimer: I am not a lawyer, and nothing that I write here or elsewhere should be construed as constituting legal, financial, or any other kind of advice.  My knowledge is limited to Texas, which takes a &#8220;bundle of rights&#8221; view of mineral ownership, and I know that all of the different states have their own take on mineral ownership.  Texas&#8217; body of oil and gas law is generally acknowledged to be the most established and complicated out of all the states&#8217;, as Texas was where the oil boom originally occurred, and oil and gas concerns have continued pretty consistently to the present day.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tractplotter.com/blog/?feed=rss2&amp;p=4</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Welcome!</title>
		<link>http://www.tractplotter.com/blog/?p=3</link>
		<comments>http://www.tractplotter.com/blog/?p=3#comments</comments>
		<pubDate>Sat, 31 May 2008 06:44:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.tractplotter.com/blog/?p=3</guid>
		<description><![CDATA[Welcome to the Tractplotter.com Development Blog.  I am the owner/developer/proprietor of TractPlotter.com.  I also have a &#8220;day job&#8221; as a landman in the Barnett Shale area of Texas.  This is what prompted me to write my own tract plotter, as the existing solutions all seemed to be lacking.
I would like to fill [...]]]></description>
			<content:encoded><![CDATA[<p>Welcome to the Tractplotter.com Development Blog.  I am the owner/developer/proprietor of TractPlotter.com.  I also have a &#8220;day job&#8221; as a landman in the Barnett Shale area of Texas.  This is what prompted me to write my own tract plotter, as the existing solutions all seemed to be lacking.</p>
<p>I would like to fill you all in on the plans for the site.  First off, the part that you see right now for free will always be there, for free.  It will even be improved somewhat, but it will always be a little watered down.  However, it will probably be sufficient for 90% of your tract plotting needs.  It is for me!  Most of the time I just want to know three things about a metes and bounds description: 1) Does it close?  2) Is the acreage correct?  3) What does it look like?  The existing free site that you see can do all three of those things pretty well.  I know I have a bug or two in the acreage calculations, but fortunately they don&#8217;t pop up in most tracts.</p>
<p>But I do want to eventually make money with this site.  So I will have a paid section as well.  You will be able to log in with your user name, and all of your plotted tracts will be there, organized in folders that you can arrange as you like.  You will be able to use arcs in your tracts.  You will be able to join multiple plots together, as many as you like, in an easy-to-use interface.  You will be able to alter the scale of any plot that you make, to match any scale you desire when you print it out.  You will be able to share your plots with other users that you work with.  I am even planning to allow overlays to Google Maps so that you can lay out your tracts on photographs of the actual terrain.  These are just some of the features that I&#8217;m planning to include in the final version.  Please comment below if you have a certain feature that you&#8217;d like to see, even if it&#8217;s one I already mentioned.  I&#8217;d like to get an idea of which features are most useful to other users.</p>
<p>When I do finally release the pay site, it will have a small monthly fee.  I am thinking $5 or $10.  Or maybe $5 and $10, if I can figure out some way of having two levels of service.  I think the monthly fee is the way to go.  All of the competing products that I know of are $150-$200, and they are standalone pieces of software.  They have to be installed on one computer, so they can&#8217;t be used on any computer with an internet connection.  They generally don&#8217;t include upgrades in the purchase price, so if you want the new version then you will have to pay again.  And they will not see the level of support that I will be able to provide.  Bug fixes, custom features, you name it, and it will be a lot easier for me to do than any of those other guys.  Of course I will offer a discount if you wish to pay yearly, and I will also offer multiple user discounts.</p>
<p>I am working right now on a full bottom-up rewrite of the site.  I have a &#8220;hidden&#8221;  area that I have used for my own personal needs for over a year now that has already implemented most of the features I listed above.  Unfortunately I have come to the realization that the current site&#8217;s acreage calculations are unreliable in a basic way (again &#8212; fortunately this occurs infrequently! but it is indicator of an underlying problem), and therefore almost the whole thing will need to be rewritten.  So I am in the middle of that right now.  I am also in the process of moving the server from a shared hosting solution to a dedicated, colocated server.  I have bought the physical server and rented the colocation space for it, but I still have yet to get the server fully configured and installed at the facility.  Hopefully I can get this done in the next month (by July) and have the site transition to the new server during that time.  The rewrite and availability of the pay site will take a little longer, but hopefully I will be able to fix the known calculation bugs in the free site within the same timeframe of the server installation.</p>
<p>So there you have it, that&#8217;s the current status of the site and a broad idea of the goal that I&#8217;m working toward.  Please feel free to comment with suggestions, problems, ideas, bugs, and anything else that you might want to say.  I realize that I have not been communicating effectively on the site status, and the whole site has been pretty mysterious to everyone up to this point.  I hope to change that with this blog, so at least you will know that yes, there is an actual person here, and yes, I am working on the site <img src='http://www.tractplotter.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks for reading!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tractplotter.com/blog/?feed=rss2&amp;p=3</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>
