Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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 Create points from lines.

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.

(As an aside, see Mapping points from total station data in Angle, Horizontal Distance, Vertical Distance for a related, though more general question)

share|improve this question

put on hold as unclear what you're asking by PolyGeo 17 hours ago

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.If this question can be reworded to fit the rules in the help center, please edit the question.

From your single paragraph text description I am having trouble absorbing the detail. Are you running this from a Python script that you could post? You mention several tools so are you able to include links to their help or download locations? Are you able to include a diagram of what you expected to see then what you observed? – PolyGeo Jun 14 '13 at 2:19
So people don't have to try and cross reference between your Question, 3 Comments and some web links can you hit the edit button and revise your question, please? Questions which are easy to read and comprehend tend to get the most and fastest attention. – PolyGeo Jun 14 '13 at 4:37
Thanks, I just edited the question. I'm new here so I appreciate your help, both with how to use the forum and on my content. Thank you! – awestriker Jun 14 '13 at 15:35
I've not previously looked at Bearing Distance To Line but it has quite a few parameters so it would be helpful to know what you are using for each, and also to be provided with two rows from your dBase file that include any fields referenced by the tool. I will be surprised if this does not come down to something to do with the units and the coordinate system. – PolyGeo Jun 14 '13 at 21:20
Has the conversion to dBase truncated the bearing values in some way? A screen shot of your table might help us identify the problem? – Hornbydd Jun 15 '13 at 13:40