Latest Contributions by JoeBorgione

You could use a composite locator that steps through the individual feature classes as references.  In 9.3 SDE did not support composites, but in 10.x it appears that it does. Hope this helps- ... View more

You are talking about is reverse geocoding; there is a developers code here.  I take it your parcels don't have addresses and you are just trying to get them addressed?  If the parcels already have addresses, you could spatially join your GPS points to the parcels and get the parcel address on the points. Hope this helps- ... View more

Would it make sense to create a composite locator?  I'm not at all familiar with Tiger data any more (and I thank my lucky stars ) but from what you describe, it sounds like you have in one feature class, StreetName, StreetRange, AltName, AltRange, where StreetName and StreetRange go together and then AltName and AltRange go together.  If you create Street-Locator and Alt-Locator, referencing the the appropriate feilds and then composite them together, would that do the trick for you? ... View more

I am trying to geocode using One address locator. Somehow I have never come across this problem. I have about 20% of the addresses I tried to geocode showing up in the yellow Tied category. I checked the box for "match if tied" however they're still showing up in the yellow with the status of "Tied" but would like to see them in Green! I noticed that say for example "1 Pond View" there are two candidates that match 100 percent so I believe the program does not know which 100 percent match address to pick. This is the case for all 2,000 addresses that went into the Tied category. I'm relatively new with this and need some help or ideas, has anyone else ever encountered this? How do I tell the program to pick either one of the 100 percent matches as they are correct? Thanks! A tie means there are at least two choices in your spatial data that your address list can match against: It's up to you to go through and pick which one you want it to match against. For me, ties are a data quality test. More ties means less data integrity and accuracy. ... View more

And, to be clear, I'm not trying to create the locator inside a feature dataset.  I'm just trying to create a locator for a geocoding source, which IS within a feature dataset.  Can't be done according to my version of ArcEditor 10. Must be a new feature of 10.x.  I can do it at 9.3... ... View more

I've never tried to build a locator within a feature dataset, but yep, you're right.  It can't be done. ... View more

Sounds like the original data is in text/character format, and if I take your use of the term 'loading' literally, it sounds like you are using the simple data loader to get the original data into another table.  Is that correct?  Long story short, your text/character leading zeros are being translated into an integer format.  Whatever your process is, keep your original text format, and you should be good to go. Hope this helps- ... View more

You might give one of the US Streets locators a try; I have very good luck them.  I really can't think of a good reason why the interactive method works but the file method won't. [edited a few moments after post] I just ran an address interactlvely on one of my US Streets locator;  I have to provide a full Pre_Dir, Street_Name StreetType, SufDir in order for it to work with an intersection. So: State St & 4500 S did not work but S State St & E 4500 S did. I wonder if you trye that with your file of intersections if that might do it for you.... ... View more

Try using a Single Field type of locator, and use the Parcel Address or what ever it's called as the key field.  I've found that type of locator to work pretty well with the parcels I use. If you are still having a problem, email me: FirstIntitialLastName at the CompanyName dot com in my signiture block below. ... View more

Why not perform a spatial join of your points into the block group polygons.  Then you could summarize the resulting feature class attribute table by block group name; after that, join or relate the summary table back to the original block group via the block group value and colorize or dot density on the count value from the summary table. ... View more

Hi - I am really thinking this should not be so difficult 😞  I'm simply trying to create an address locator off of a parcels layer. I have a geocoded table that was created off a roads layer but the points are so offset it's basically useless. (Parcels are offset from the road due to buffers, etc.) 1. Created an address locator from parcels layer using US One Address 2. Geocode my table which has data ex: 100 S 200 E for address, all in the same city - city and state are in other columns. 3. I am mapping both the address and street to the 'parcel address' column since it is one feature per address. 4. The output only geocodes a couple of points and I can clearly see in the tables the data "100 S 200 E" looks the exact same. I can't figure out why it will not recognize the data when I can clearly see the address is the same... PS - it's all in the same geodb too. Please help! Sounds like you are geocoding in Utah.  I suggest you take a look at parcel data and make sure the Parcel Address or whatever field you are hitting against is properly formatted to accept #### E #### S etc.  My guess is the parcels are using South or So or East or whatever, and that's what's goofing on you.  Single point address locators can be very unforgiving and the spelling needs to be exact to make a match; this includes leading and/or trailing spaces in the address of the parcel.  (Haven't seen any of those since the last time I matched against parcels...) Keep in mind that once you get the parcel thing straightened out, the points geocoded along the streets will have a different location than the ones matched against the parcels for two reasons: 1. Street matching is interpolated, so on a street between 100 E and 200 E, the interpolation would put the address 150 E in the middle of the block, and that may or may not be the case. 2. Unless you are using something special to match against with your parcels, the point generated from a positive geocoded match will assume the location of the parcel polygon centroid. Good luck- ... View more

Personally, I cheat and round them off.  They occupy the exact x,y location as the whole number, so I don't see the difference. ... View more

I suggest that you vote for this functionality on the ESRI Ideas.com site. Hey Derek- your link sends me to a place called salesforce.com; is this where we need to go and then sign up for a free 30 day trial?  Seems kind of odd... ... View more

You'll need to parse out the apartment number of suite number of your address field. That's pretty typical when geocoding; getting the address data into a form your locator needs. As far as getting a polygon as a result; never heard of that.  Geocoding is the process that takes non-spatial tabular data and  creates a discrete x,y location (point feature) by virtue of interpolating an address against some sort of spatial reference, be it a street, parcel, or address point. ... View more