An SDF is Autodesk's version of a geodatabase. It's easy to learn, especially if you already have a geospatial background. It can handle multiclasses, it's editable and unlike ESRI, it's just a single file so it's highly portable.
The problem with SDFs is its popularity. Aside from diehard Map3D users, its never used. Its not an extension that others can export for AutoCAD users to use and if others receive an SDF file they can't open them unless they run Map3D, Civil3D or Infraworks. It's the smart freckled-face-buck-toothed-clumsy-kid that no one wants on their dodgeball team. Too bad. Make friends with freckle face and he'll probably let you copy his answers on the next math test.
Most, if not all, SDFs are homegrown, meaning someone,someplace has tried their hand at compiling a geospatial file probably because they don't know how to, or aren't cofortable doing it as a shapefile. I know, I know, it should be just as easy either way but dabblers will be dabblers. BTW, I've never seen an online site offering a download in SDF format.
I doesn't look like your problem is with AutoCAD and your workflow looks good so far. If you can connect to the data and it shows up on your Task Pane then that's half the battle. The other half is assigning an appropriate coordinate system so your data plops down where it's suppose to. Do your parcels appear in modelspace? If you turn on Bing Hybrid do the parcels look like they belong in the neighborhood? How about uploading another screenshot?
Intuition tells me something is in that SDF that shouldn't be and that screwwed things up. Or maybe
something that should be there isn't. I'd take a careful look at the ingredients that making up the data. After that, I'd take a look at the recipe because the instructions weren't followed.
Chicagolooper
