I'm working with a set of feature classes saved in a file geodatabase (In Arc 10.1) that are numbered 1-4500. The naming convention is "VTR_XXXX_etc" - where XXXX stands for the number 1-4500. I have discovered that in the fGDB, the files are saved in an order like:
...Which I understand. The weird thing is that this convention is followed all the way up until tile VTR_450, at which point the convention stops and there are no more three digit values listed, until after VTR_4500. Then the three-digit number files are listed in number order, as in:
VTR_4500, VTR_451, VTR_452, VTR_453, ...and on.
I don't know what is going on here. Anyone have a comment or insider's knowledge? Are there bizarre nuances in how data is stored? Thanks for input.