I have two feature classes.

  1. Point feature of hand-sampled GPS locations
  2. Line feature of terrace walls digitized from aerial photograph.

sample points and terrace walls

Because of the less than perfect ways I generated these features, I need to allocate each GPS point to the nearest terrace wall from which I sampled it.

I defined the Input as the Point Feature, and the near feture as the terrace lines.

near tool

But the process fails to generate results. If it's a Near Table, then it's an empty one, and when I use the Near Tool itself on the point feature, it adds two fields with -1 in them.

Point feature with -1

When I run the tool on the features in an opposite way, it does generate results, and for every terrace walls gives me the nearest point - obviously, not what I'm looking for.

Any idea why the process fails?

  • Are the projections defined and the same for both layers? – JeremyFon Jun 6 '13 at 15:03
  • Yes they are. Like I said, doing it the other way round worked fine. – HDunn Jun 6 '13 at 16:40

I can see that you have tried the Near tool but what is not clear is the search radius that you have used.

Expand the tool dialog by dragging its corner (or use the scroll bar) to see what it is defaulting to and then try increasing it because:

The values for NEAR_FID and NEAR_DIST will be -1 if no feature is found within the search radius.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.