Hi all, I am trying to join observations of the speed limit data captured by the car's GPS (>16k rows) to road segments (543 rows). I tried to use the spatial join tool and besides the "Closest" Match Option, which shows quite okay results, all the other options gave me data. Is there any other function I could use to join (map-matching) observations of the speed limit to the roads segment? Should I first set the projected coordinate system in order to perform this kind of features join?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Spatial Join (observations to line segment)

AgnieszkaLisonek

Hi all,

I am trying to join observations of the speed limit data captured by the car's GPS (>16k rows) to road segments (543 rows).

I tried to use the spatial join tool and besides the "Closest" Match Option, which shows quite okay results, all the other options gave me <Null> data.

Is there any other function I could use to join (map-matching) observations of the speed limit to the roads segment?

Should I first set the projected coordinate system in order to perform this kind of features join?

Vind meer berichten getagd met

Analysis

Desktop

Accepted answers

danretired

That is what the second link I posted covers.

If a location is equally close to two features, one is chosen at random.

Your option would be manually editing.

The Near tool also uses the same algorithm, so it is constrained by the data quality.

what percentage of your data produces what you call "errors"

All comments

AgnieszkaLisonek

Thank you very much for your help!

danretired

That is what the second link I posted covers.

If a location is equally close to two features, one is chosen at random.

Your option would be manually editing.

The Near tool also uses the same algorithm, so it is constrained by the data quality.

what percentage of your data produces what you call "errors"

AgnieszkaLisonek

I also thought that "CLOSEST" will be the best solution but sometimes it can generate error such as assign the speed limit sign to the wrong road segment, especially when close to the intersections.

I was wondering if there is any other method to get rid of such as mistakes.

danretired

From here

Spatial Join (Analysis)—ArcGIS Pro | Documentation

and here

How proximity tools calculate distance—ArcGIS Pro | Documentation

it is best to use a projected coordinate system (except Web Mercator, which is useless), to get the best results.

JayantaPoddar

Since all the GPS points don't intersect with the Road segments, "CLOSEST" seems to be the best match. Had there been intersection between the road segments and GPS Points, "INTERSECT" would have been the better choice then.

Do you have any concern with the "CLOSEST" relationship?

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.