Latest Contributions by JoeBorgione

Becky-  I couldn't find the 2010 all line files, but I stumbled upon 2008. (Can Census make it a little more cumbersome to navigate the site?!) Anyway, I downloaded the roads for Anderson County.  In this county there are a total of 39874 road segments.  37,672 do not have ranges in the data.  When I select those and relate them to the _addr table, nothing gets selected in the related table.  There are only 3899 records in the entire related table. When I switch the selected edges to those that have at least partial (one side or the other) ranges and choose related tables, all of the 3899 get selected.  This whole thing is pretty murky for me; if the edge record has ranges, the _addr file seems to confirm them.  But if the edge record hs no range information, the _addr file doesn't provide anything. Let me know one of the counties you are working on and I'll see what it does for me or if I can make sense of it.  If Anderson is one of them, I'm more than dissapointed with the data census provides. [edited a few minutes later] :  Just for fun I downloaded the all lines data for Salt Lake County, Utah.  I personally maintain this data for 9-1-1 response.  For the most part the geomtries are okay.  I did notice however that randomly identifying my streets against the census streets that census will flip rf-rt, lf-lt and even lf with rf and lt with rt.  Not sure what's up with that. ... View more

You might try ArcGIS online.  Perhaps a google search for data.  It's probably going to be tough.  I've often wondered how to geocode a neighborhood that looks like the attached image. Best of luck!  Let us know how it works out for you. ... View more

I am trying to create an address locator for the state of Texas (it can be split into 11 regions).  I read over the PDF on relationships on the Census Bureau's website(http://www.census.gov/geo/www/tiger/tgrshp2010/TGRSHP10SF1CH6.pdf).  They recommend using the All Lines shapefiles which also require the Address Ranges Relationship files for all of the address data.  I have downloaded several county All Lines shapefiles and the Address Ranges Relationship files for these counties.  I merged the shapefiles for the counties and the tables and now have one shapefile and one table.  The Census Bureau says to link these two files using the TLID field.  However, it is a one (shapefile) to many (table) relationship since each line segment has multiple address rnages associated with it.  I have not created an address locator before, but I understand it needs to be a single file.  How can I join these to use them as intended - to create an address locator? I'm not too familiar with Census data, but the way I'd do it is county by county, rather than one big merged shapefile and table.  See if at a single county level you can join the street segments (shapefile records) to thier respective table records via the TLID.  If you are still getting a one to many (one segment to many range records) I don't know how they expect you to use thier data. ... View more

Glad it worked out for you Ashley! ... View more

Hi there, I went ahead and added/connected to the service, in ArcCatalog by adding a GIS Server. (I added the "main page"/"service directory" http:// link,  and I can see the services in my ArcCatalog - Catalog Tree, including the geocoding service I want to use.  (Note this is not hosted locally, it's on a local government website somewhere). In ArcMap, I went to use the "Geocode Addresses" Tool, and for Input Address Locator, I navigated to GIS Servers\ArcGIS ............\..... GeocodeServer When I did so, I recieved the "000732 : <value>: Dataset <value> does not exist or is not supported" error. Does this make sense?  Could it be that I am looking at the service both in ArcCatalog & ArcMap and I should close one (that's my go to solution 🙂 ) I think I'm missing the "Add Locator" step, but I'm a little lost as to how to do that...Suggestions? Thanks! Ashley The only thing I can think of is the tool may be goofing on you.  I don't have a 10.x version in front of me so I don't know if this has changed.  In 9.3.1 or earlier, click on the tools menu, pull down to geocoding, and select Address Locator Manager.  In the dialog box presented, click ADD and navigate to your service.  That's how I've always done it, and that's the method I used for the screen shots in my last post. Hope this helps! ... View more

I'm going to assume the title of your thread is what you mean, not whats in the body of it. My guess is you want to export just the x/y fields (and perhaps some others) from the resulting feature class you created by geocoding into a table. Short answer: Yes! In ArcMap double click your geocoded_results feature class and go to properties.  In the fields listing, turn off all the but the fields you want.   Then open the feature class attribute table.  It should be displaying just those one you left checked.  Go to options on the bottom of the table window, select data and export. Hope this helps- ... View more

There are no common fields between Parcels and Street Signs.  So i can't do a join. My next step is to try a composite address locator built using a street centerline file and a parcel polygon. After that it's an intern 😉 Emphasis on SPATIAL JOIN. GIS 101; point in polygon. That's how you'll get the polygon address onto the point location. ... View more

If you can add the [published] locator to an arcmap or arccatalog session you'll be able to use it just like a local locator; it may be a little slower depending on connection speeds and the server it's actually on.  You'll need a connection through 'GIS Servers' in acrcatalog estblished; simply 'add address locator'. See attached image; back to front, adding a published locator from a server I maintain. Hope this helps- ... View more

What if you performed a spatial join of your points into the parcel polygons. No doubt you'll get multiple joins but from what you describe that's okay. Hope this helps. ... View more

I've been researching the match score for geocoding, and can't find how ESRI defines accuracy, especially when the default is 80% as opposed to 100%. Does anyone know how ESRI decides this and how reliable 80% is? I use it for research and want to be as accurate as possible, but also have as many matched addresses as possible. Thanks! I don't know the actual stats, perhaps someone can from ESRI chime in; I've found it often depends on the type of locator you are using.  Certain elements of the address are weighted differently, like prefix & suffix direction, type etc. Here in Utah we use a grid system where the actual address is a point on a grid.  For example, 4104 S 3305 E is 41 blocks south and 33 blocks east of the 0,0, point downtown. Consider the evil twin of this address; 4104 S 3305 W.  In terms of geocoding with a US streets locator the two addresses are almost the same, yet if the evil twin existed, they would in actuality be miles apart.  I can't remember what the percentage of hit is between these two, but it's pretty close;  in a 9-1-1 response situation, it would be up to the lawyers to sort it all out in the end.  For a coupon mailer it's just another one that goes into a black hole. So, when you ask how 'reliable' is an 80% hit, you have to ask yourself; What's at stake with an 80% hit?  Everyone wants to be as accurate as possible whether you are dispatching 9-1-1 calls, mailing coupons, or in your case doing research.  However, IMHO accuracy in geocoding is mostly a function of the data you are matching against as well as the data you are matching. Another discussion is accuracy versus precision.  When geocding against streets, you can only hope to be accurate; that is the address falls on the correct block.  Lets say you street has a range of 100-200 on the even side and 101-199 on the odd side.  Logically the address 150 would be half-way along the block on the even side.  That's accuracy. The reality might be that the house with 150 painted on the curb is at the end of the block on the odd side of the road.  If you need precision results your street data isn't going to provide it.  Maybe parcel data/point matching would be the way to go. Hope this helps! ... View more

Each agency manages its own speed limits without state or federal oversite so a database like that can't exist. Oh, it can exist, but it probably does not.  Give me enought money and I'll give you a database of whatever you want! :rolleyes: ... View more

You can, the data just needs to be in a form that is consistent with the intersection that your locator uses.  Typically "&" "and" are the defaults.  So if your data looks like 'Elm St & 2nd Ave' or '33rd and 3rd' you will be good to go.  If your data is set up a little differently like 'Main St - Center St', you have two choices; change your address data to match your locator or change your locator to match your data. ... View more

Hyphens are not special characters in French. They are part of the official names and I need the user to see the official names in the match_addr when using the locator.  Any other suggestions? Thank you Sophie Sorry Sophie- I didn't realize they were as important as they are;  we can get away with my solution here in the states.... ... View more

My guess is that the feature dataset is your problem.  Is there a compelling reason why your featureclass(es) need to be n a feature dataset? You might try to put the feature class in a geodatabase with out it being a member of a feature dataset and see if it works.  Another trick I've recently learned (after geocoding gazillions of addresses) is to put the actual locator in a folder rather than have it stored in a geodatabase. Hope this helps- ... View more

I suggest you get rid of all the special characters in your data.  They are problematic for a number of reasons, geocoding not withstanding. ... View more