I am using the Bearing Distance To Line tool to draw geodesic lines to points defined by a bearing and distance.
This is an aside, but I will then use the Feature Vertices To Points tool to convert the lines to points.
I have a dBase file (because my Excel and CSV tables were failing for some unknown reason which may become the subject of another question) with the bearings in decimal degrees and the distances in meters.
All of the X and Y points from which the lines are drawn are the same because the bearings and distances were all taken with a total station from a single datum point. So the X and Y fields of my table are the same value for each entry.
The problem arises when I run the tool -- I only get a single output line drawn when there should be 113 individual lines with different bearings and distances from the same start X,Y coordinate.
Has anyone encountered this issue before or have an idea how to resolve it? Does it have something to do with the start X and start Y being the same value for each table entry? It shouldn't be the case, but am I missing something?
I am not running a custom Python script, just using ArcMap 10.0. I added the dBASE file from ArcCatalog and ran the Bearing Distance to Line tool with the dBASE file as my input file. I am expecting to see something similar to the top graphic in this post.
To work around the problem of the Bearing distance to line tool, I found and used this script from Susan Jones which did work with a feature class created from the data in the dBASE file.
However, I'd still like to be able to figure out the Bearing Distance to Line problem. Thanks!
(As an aside, see my other question for a related, though more general question)