Latest Contributions by JoeBorgione

Thank you very much Brad for the input. Sure, end users prefer to see geocoded address in the precise place. [ATTACH=CONFIG]32897[/ATTACH] Do you mean that the Google database of addresses, for example, is collected at the level of each building as the found addresses match the precise location of the target? [ATTACH=CONFIG]32898[/ATTACH] It boils down to what your use is and what your budget is, and how they balance each other:  As has been described, anytime you interpolate an address based on a linear feature, you accuracy is okay, but your precision suffers.  That's just the name of the beast.  Lets say you have a street that is ranged from 100-198 and 101-199 on the even and odd sides respectively.  That locator will interpolate house number 150 right in the middle of the block on the even side; the reality might be that its really on the odd side and at the 199 end of the block.  If block level accuracy is 'good enough' then your are good to go.  However, if you need better precision than that (like the actual location of house #150) you'll need different data with which to match.  Accuracy might cost you $X, while Precision might cost you $X * 5.  However, what is the result of an accurate location versus a precise location?  That's something only you can answer. ... View more

You might take a look at US One Range locator type. http://resources.arcgis.com/en/help/main/10.2/index.html#/Commonly_used_address_locator_styles/00250000000v000000/ ... View more

Hey Vince- will the current approach work with versioned feature classes?  And will your new approach work for one? ... View more

When it comes to making front end edits to a sql database that is accessed via SDE, my thoughts are buyer beware.  You've got another thread on a similar topic, and I think the answer provided to the OP is a good one. IMHO you would be better served by updating your SDE data via ArcGIS. I use SDE to manage an enterprise database that includes a street centerline feature class. However, I replicate the SDE feature class(es) to a production file geodatabase that several published services point to, including geocoding services used in 9-1-1 dispatch.  For me and my application, separating the edit data (field data) from the production (consumed) data works quite nicely. With respect to your question about interrupting services that view the data: in order for those services to see any changes, you'll need to refresh the data by restarting the service.  In my case, I have two different services; when one is hot, the other is not.  That is, at any given time only one service directory is being accessed and the data therein consumed.  This way I can shut down the 'cold' service, do my replication process, and rebuild any locators or map services without interrupting the users.  Then I restart the cold service and point my users to it, so now it's hot and the other is not; repeat the rebuild process for the now-cold services so both are current. ... View more

Hi Joe, The 99.6% is not the same concept of "match rate" in geocoding. What I mean here is that we geocoded the dataset once and validated the results by geocoding the same dataset on another computer again (same geocoding options and same address locator). We followed the procedures below and expected to have the same X and Y coordinates for all addresses from the two runs. 1. Import the .dbf tables into SAS 2. Keep only uniqueid, x, y 3. In one of the datasets, rename x = x1 and y = y1 4. Merge the two datasets by uniqueid 5. Find the difference between the x�??s and y�??s (diffx = x1 - x and diffy = y1 - y) 6. Run a frequency on diffx and diffy to see if there are records that had different values for x or y However, only 99.6% of the cases have the same values of X and Y coordinates from the two runs. Around a thousand geocoded addresses vary in their X and Y coordinates. And when I checked the X and Y coordinates of each address from the two separate runs, the distance between the two points are several hundred feet apart or even closer. Feel free to ask questions if you need further clarification. Thanks! Still seems a little fuzzy but for the sake if argument, let's assume it just me... 1.These are the dbf tables from your gecoding results?  Why do you need to import them to SAS? 2-6....  Personally, I'd out put the geocoding results to some flavor of geodatabse; Shapefiles are so 1995.  I would JOIN the two TABLES not the point features via the UniqueID.  Your temporary output table from the join should then have: UniqueID, X,Y, X1,Y1 Then select where x<> x1 OR y <> y1.  Or make a selection where x<>x1 AND y<>y1.  You could then do your diff analysis there.  The only thing I can think of is how each computer actually computes the x,y pairs; that or the .dbfs are the root of the problem. ... View more

Hi All, I geocoded a dataset with around 500,000 addresses on my computer, and my team member validated the geocoding results using the same address locator and geocoding options on her computer. A small number of the addresses (0.4% among all addresses) in the dataset have unmatched X and Y coordinates from the two separate runs. Most of the unmatched geocoded X and Y coordinates are several hundred feet apart or even closer. The address locator that we use comes from the ESRI StreetMap Premium. Does anybody have an idea about why this happened? Thanks! Not sure I understand your question.  You say that you've geocoded 500K records with a 99.6% hit rate.  That's pretty awesome. But here's where you lose me: most of the unmatched geocoded X and Y coordinates are several hundred feet apart or even closer. Closer to what? If they are unmatched, how do you know they are 'several hundred feet apart or closer'?    If my math is right, at a hit-rate of 99.6%, you've got 498K records geocoded, and you're wondering why the other two thousand did not?  Perhaps you could clarify. ... View more

Hello, I must be missing something.  I have a buildings layer with address (house number, street name, street type, etc.) all in one field named "Address".  City and zip are in separate fields.  I am trying to create a Address locator using 'US Address - Single House', but when I do so it seems to want to have the address separated in multiple fields (e.g. House Number, Street Name, etc.).  I dont want to try to parse my data out.  I tried specifying the single 'Address' field for all these related fields, but that does not seem to work. How do I create an Address Locator based on a single 'Address' field? Thanks Neal I think you'll want to use the "General -  Single Field" type of locator.  It asks for a single Keyfield and you can store your address there or the building name. ... View more

FeatureDatasets in SDE spell trouble for me. I wonder if somebody is using the data within the featuredataset within the fgdb and that's the cause of your error.  Is it published?  I really suggest re-thinking using anything within a featuredataset in SDE.  The problem with locks and permissions make them a problem child. ... View more

Hello - I'm trying to copy/paste a File Geodatabase into an Oracle SDE Instance running in Windows 7.  There are 61 classes in the FGDB.  When it hits about the 6th class I get the error: Failed to paste <dataset> Underlying DBMS error From there I'm trying to find out what kind of error was encountered.  I've looked in the Windows Event Viewer but can't find anything there.   Is there another location where I could find more details about the error? Thanks, Ed Copying and pasting a FGDB into SDE seems like a lot to ask.  My suggestion is  to import your feature classes from the FGDB into SDE with the import multiple feature classes utility. ... View more

Personally, I'd never use windows authentication for a SQl server db.  I add my editors to a  group called (drum roll) editors, and everybody else gets read only by default.  All my editors also share the same schema as well.  Nobody owns a schema, that way its easier to drop them when the go to greener pastures. ... View more

I'v read through the docs and want to make sure I'm reading this right. Can only 1 user create and own a feature class? Is that why when I right click a feature class in catalog to manage it. All items are grayed out in the menu, unless its the user that created it? Thanks for any info. Are talking about in a SDE geodatabase?  Yes, it can only have one owner, the user that created it; however, you could set permissions to other users to edit and I suppose delete it.  I suppose the same would be true in a FGDB on a shared network drive.  You would need to set permissions accordingly. ... View more

I'm having a problem geocoding roundabout intersections in my Streets dataset.  I think the reason could be that the two roads actually intersect twice because of the way the roundabout is drawn. Has anyone come into contact with this? Is there a better way to portray a roundabout intersection that will allow a geolocator to find it? [ATTACH=CONFIG]32157[/ATTACH] Round abouts are pain in the back side for geocoding; my guess is your doing this for a public safety agency for traffic stops or traffic accidents, right? Here are a couple of suggestions.  1.  Don't sweat the small stuff:  you are getting a 100% tie on all sides of the round about.  pick one and go with it. 2.  Drop or rename the street name of all but one the segments of the round about.  That way when the intersection is used, it'll hit: MyStreet & MyStreet Roundabout  (where MyStreetRoundabout is the only segment of roundabout that is named that way.) 3.  Create a point feature class of your round abouts and geocode to them 4.  Create an additional feature class of 'streets' that looks like this at a roundabout:   _|_ 5.  If you go with 3 or 4, add them with your main streets to a composite locator, and make them the first to look at 6.  Have fun... ... View more

How about: 1.  Add two floating fields to your polygon attribute table: CentroidX, CentroidY 2.  Use calculate geometry accordingly 3.  Export the attribute table as a stand alone table 4.  Add the new table to arcmap and add xy data 5.  Convert that to a point feature class 6.  All your polygon data is now on a point feature ... View more

Good afternoon. I've searched the question in this blog. Maybe I don't use the right words but anyway my problem is not present in any post so I'll try to explain my question by opening a new one. I have a polygon shape (eg states). I calculated the centroids and the function saved them in an another file. Now I have point and polygon shape (centroids and polygons). I need a unique shape but functions Merge and Union (as I understand it from what I've read) can only be made between shape with the same feature class (point-point, line-line, polygon-polygon). How can I do to combine different geometry types into the same feature class? Is there a way to get the results I need? Or a procedure to get the centroids of the polygons on the same shape? I hope I explained thanks Tsunanya How can I do to combine different geometry types into the same feature class? You can't.  Geometry is what defines a feature class. There is no Polygon/Point hybrid. Perhaps you could try to explain what your objective is. ... View more