AnsweredAssumed Answered

Relating returned order of 'Stops' back to input data

Question asked by jgamble-esri-ca-esridist on Jan 15, 2013
Latest reply on Jan 22, 2013 by jgamble-esri-ca-esridist

Like • Show 0 Likes0
Comment • 3

Hi,

I am trying to build on the Esri Silverlight route example, using the ESRI_Route_NA service. I am successfully submitting and displaying the calculated route data.

I have a GraphicsLayer that contains a listing of stops (or point attributes) that I am using for the input RouteParameters.Stops.

I want to be able to identify the sorted order of Stops that was determined by the routing service. From what I have read, the 'SourceOID' field in the returned Stops object should contain the ID of the original stop. In my testing, this is not the case.

Can anyone tell me how I can map this SourceOID field from my input? The output SourceOID looks like contains a unique value identifying the stop, but it is a number that has no relation to my input attributes (that I can find). I have tried renaming my input attributes to be 'SourceOID' or 'SOID' without any luck on the output.

Any help is much appreciated.
Thanks
Jon

pstevens-esristaff

Jan 17, 2013 6:42 AM

Correct Answer

Hello, Jon!

The SourceOID field is one of four fields that are used to identify where along the network the stop is located. The other three fields are SourceID, SideOfEdge, and PosAlong.

You see, each stop has two locations. The first location is the actual x/y of the shape. This is where the stop is located geographically. The second location is where along the streets the stop is considered to be. Imagine a square block of streets with your stop x/y located somewhere in the middle. Network Analyst needs to determine which of the surrounding streets you mean to use as the place to arrive at or depart from the stop.

The four location fields are:

SourceOID - the object ID of the street feature that the stop is located along
SourceID - the ID of the street feature class
SideOfEdge - is the stop considered to be on the right or left side of the feature at its position
PosAlong - from 0.0 to 1.0, where along the feature is the stop located.

I hope this helped,

Patrick

See the reply in context

No one else had this question

Outcomes

jgamble-esri-ca-esridist Jan 16, 2013 9:14 AM

After some testing I've found that the 'stops' are being returned in the same order as they are sent to the web service, and the order for which they *should* be in is identified in the 'Sequence' attribute of the stops object.

I am still stumped on the purpose of the SourceOID field names. What I have done to ensure that I am looking at the correct objectIDs, is to store the objectIDs in the 'Name' attribute when submitting my stops to the web service. I can then retrieve my original objectIDs by looking in the 'Name' attribute of the returned routeResult.stops object and resort my original data using the defined Sequence.

Cheers.
Jon.

jgamble-esri-ca-esridist Jan 22, 2013 6:12 AM

Hey Patrick,

Thanks for the info - Yes, thing makes a lot more sense now!

My confusion was around those 4 fields. I was thinking they referred to the stop it self, where as what they are actually referring to is the data within the network dataset.

Cheers!
Jon

Actions

3 Replies

jgamble-esri-ca-esridist Jan 16, 2013 9:14 AM
Mark Correct
Correct Answer
After some testing I've found that the 'stops' are being returned in the same order as they are sent to the web service, and the order for which they *should* be in is identified in the 'Sequence' attribute of the stops object.

I am still stumped on the purpose of the SourceOID field names. What I have done to ensure that I am looking at the correct objectIDs, is to store the objectIDs in the 'Name' attribute when submitting my stops to the web service. I can then retrieve my original objectIDs by looking in the 'Name' attribute of the returned routeResult.stops object and resort my original data using the defined Sequence.

Cheers.
Jon.
Like • Show 0 Likes0
Actions
pstevens-esristaff Jan 17, 2013 6:42 AM
Unmark Correct
Correct Answer
Hello, Jon!

The SourceOID field is one of four fields that are used to identify where along the network the stop is located. The other three fields are SourceID, SideOfEdge, and PosAlong.

You see, each stop has two locations. The first location is the actual x/y of the shape. This is where the stop is located geographically. The second location is where along the streets the stop is considered to be. Imagine a square block of streets with your stop x/y located somewhere in the middle. Network Analyst needs to determine which of the surrounding streets you mean to use as the place to arrive at or depart from the stop.

The four location fields are:

SourceOID - the object ID of the street feature that the stop is located along
SourceID - the ID of the street feature class
SideOfEdge - is the stop considered to be on the right or left side of the feature at its position
PosAlong - from 0.0 to 1.0, where along the feature is the stop located.

I hope this helped,

Patrick
Like • Show 0 Likes0
Actions
jgamble-esri-ca-esridist Jan 22, 2013 6:12 AM
Mark Correct
Correct Answer
Hey Patrick,

Thanks for the info - Yes, thing makes a lot more sense now!

My confusion was around those 4 fields. I was thinking they referred to the stop it self, where as what they are actually referring to is the data within the network dataset.

Cheers!
Jon
Like • Show 0 Likes0
Actions

GeoNet

The Esri Community

Relating returned order of 'Stops' back to input data

Outcomes

Related Content

Recommended Content