While testing out the process I found that the even when the Census Tract ID Column is selected and the test data CSV with a tract id column is uploaded, the process fails with a message indicating that it is still looking for Lat/Long columns.
BTW it is very good to have this test data to work with, though I noticed that this tracts2010.csv has lat/long columns, which I think should be removed just for the sake of clarity and simplicity (these column values also have a lot of leading spaces which is strange).
While testing out the process I found that the even when the Census Tract ID Column is selected and the test data CSV with a tract id column is uploaded, the process fails with a message indicating that it is still looking for Lat/Long columns.
BTW it is very good to have this test data to work with, though I noticed that this
tracts2010.csv
has lat/long columns, which I think should be removed just for the sake of clarity and simplicity (these column values also have a lot of leading spaces which is strange).To complete: