Using XY Mapped Fields in ArcLogistics Import and Geocode

Question

I would like some clarification.  I have a table of orders that I have an X and Y location (currently in CA State Plane coordinate value).  I have mapped the ArcLogistics X and Y fields using the X and Y values in both text and double data types.  In either case, I can get the locations to show up in an order box, but when I try to assign them to a truck, the data does not load.  the Geocoding field in the unassigned box all indicate Import XY.  To my understanding, this should be sufficient with ArcLogistics for routing and sequency, however, this does not seem to be the case.  If I leave off the X and Y fields and use only the address, then the data does get imported, the Geocode field indicates Address, City, State and then when I select some of them to assign to a truck, a route is produced.

Am I missing something?  Since I have high confidence in my XY location for my "address" location, I would like to take advantage of this if possible for routing purposes.  I know the current data does not show a city or a state, but they are all in Sacramento, CA.

Any insight is appreciated.
Thanks,
Nate

Nate_Test.zip

MargaretCrawford_0-1764096837257.png

BertYagrich · Answer

Typically, you'd just map the X/Y fields during import when importing from a file.  However, when reading a shapefile, this location is part of the imported information and you can't really override it.

You could export your shapefile to .csv or something and then import and map the X/Y fields but they really shouldn't be any more accurate than the shapefile.

Post up a sample shapefile or some addresses if you'd like us to take a look.

JamesJudge · Answer

I'm using ArcLogistics online 10 and when importing orders I'm only getting 90 percent geocoded. How can I set the preferences to read the X Y coordinate values in my stops shapefile?

BertYagrich · Answer

Basically, if I have a known location (XY, Lat/Long) in my table, can I use this directly during import so that I can generate routes. If I understand correctly, then it depends on the street network being used. If it is TeleAtlas, then my XY data needs to be in geographic. If my street network is in state Plane (i.e. a City street network), then the XY locations need to be in state plane.

Nate, your analysis above is correct and supports all the scenarios you listed above.  Are you planning on using Tele Atlas or some other custom dataset in State Plane with ArcLogistics?  Whichever you use, just make sure your XY order coordinates are in the same projection as the map and network dataset and it should work nicely.