Thanks for the offers of help. I did attempt to create an altname table and I thought I had it figured out to some extent, but it fails when it tries to create the locator.I have a centerlines file with a streets with many segments. I created a JOINID field on each segment. For example, segment JOINID 36 is called FAYETTEVILLE RD, but it's also known as US 401 HWY.So I have a matching ALTNAME table with JOINID 36 and it's street name is US 401.STREET_ID DIR_PRE STNAME STYPE DIR_SUF joinid465 US 401 HWY 36The ALTNAMES table I'm creating is a DBF file. The centerlines file table I used was also a DBF table. Is that what I should be doing?
Your streets need to be in the form of a feature class, not a file. When you geocode, you are turning an address that you and I recognize into a pair of X,Y coordinates that the GIS recognizes; the coordinate system of your street feature class is the basis of those x-y pairs.
I'm not familiar with geodatabases and feature classes yet. I have worked almost exclusively in shapefiles. I see a tool for featureclass to shapefile, but not the other way around.I opened the centerlines shapefile dbf table and added the JOINID field. I was not working with just a dbf of street names, if that matters.I felt like I was following all the steps, but when it tries to build the locator, it would fail with a very general error.
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.