Latest Contributions by JoeBorgione

The fastest way to do this would be to recreate the replica: 1.  Unregister the replica from each geodatabase 2.  Delete the feature class in the child geodatabase 3.  Replicate the data from the parent to the child geodatabase again But won't step #2 delete the features added to the child by the field walker? Before you delete the child feature class, may I suggest you make a comparison of the parent to the child.  Make a spatial selection of everything in the child that is the same in parent;  then switch the selection of the child, and you should have just the field walker additions.  Write those to a feature class so you can load them or otherwise get them into the parent. Hope this helps- ... View more

I'm a bit of GIS beginner, I'd appreciate any and all advice. I'm using ArcGIS 10.  I'm trying to geocode a set of data I have only using zip codes in Mexico City. I was able to find data that had zip codes in Mexico City listing their lat/long, it was an excel doc and I've converted it into a shape file. Basically, how do I geocode this? I've been reading tutorials, but am having trouble because most of them are based on geocoding of US addresss.  When creating an address locator, what style should I be using, the general-single field? What about reference data, the shape file I made? If anyone can point to any tutorials or offer me advice on where to go or where I'm goin wrong, I would highly appreciate it.  Thank you Kelly- geocoding is a process that converts locations, addresses, etc that we as humans recognize into a xy pair that a GIS can display.  So, you and I understand 1234 Elm St and geocoding matches that address to a feature class and subsequently derives an xy pair based on the the matching data.  Street center line data with address ranges are by far the most popular data to match addresses to. Is your Zip Code data in the form of  points or polygons?  My guess is you had a list of Zip Codes and in which the centroid of the zip code polygon is provided as an ay pair, and you have converted it to a point feature class.  I'm and old hand with versions of ArcGIS 9.3.1 and earlier, and I'm fumbling about with the geocoding process in 10.0.  However, you may want to take a peak at the desktop help under Professional Library - Guide Books - Geocoding - Preparing For Geocoding you'll find a listing locator styles.  There are several available that will work with points or polygons, including  US Address-Zip 5-Digit that will probably be just what you are looking for. You'll find a geocoding tutorial in that same Geocoding Guide Book. Hope this helps- ... View more

I'm having problems with a database that I imported. I converted an SPSS database into an excel database, and my latitude/longitude variables have 13 decimal places. Everything translated correctly from SPSS to Excel. When I import and open up the Excel database in Arc 10, the decimal places are chopped to six. If I select the latitude variable and adjust the number of decimal places under "field properties" and "number format" to 13, then only nine of the decimal places actually show up on the screen. What happened to the rest of the decimals? How do I get them back? I want the latitude/longitude variables to be that precise because a given location may fall in the incorrect census tract if it is not. Thanks! Wow.  0.0000000000001 degrees.  Using excel to do the math, and using the figure of 49 miles per degree in a mid-latitude location   that calculates to 0.0000000258720 feet. I'll let you do the math to figure out how many fractions of an inch that is, but I'm guessing it's somewhere on the level of a neutron. Think about it; are your census tracts that spatially precise?  I like to provide answers and try not to give advice, but I will here; life is short.  Nine decimal places will provide more than enough precision. All the best! ... View more

Thanks Vince; I used a direct connect internally which worked fine.  The remote users are not using a direct connect. I'll be back on site Monday and see what we can figure out. ... View more

I've found that FGDBs don't like the 'LIKE' statement;  In a pgdb you can use Name like '[0-9]*'  to find those that start with a number.  I don't know if that is a VB only type of query or not, so your mileage may vary in version 10.  If that works for you, so will Name like '[A-Z]*'  .  For a SDE GDB with a SQL Server back end you'll need to use % instead of *. Hope this helps. ... View more

Just to add my $00.02...  If you want to design your own attributes, you can do so in an empty feature class and then use the simple data loader.  Just a suggestion.... ... View more

Unless I'm missing something, the project function is what you need ... View more

Hello, I am working with the NA Location-Allocation. Every Time the Analysis Options offer me to choose between Drive Length and Drive Time as Impedance. When I build the NetworkDataset I just type a cost attribute referencing the shape length but none for drive times. So, why can I chose driveTime impedance? Where does it come from? Where does NA get the values from? What happens when I implement a time attribute also before building the dataset? will then my attribut be used for drive time? thanks for quick help You'll need to create one of two things; either an actual attribute of 'drive time' in the street feature class or evaluate for it when you set up your network dataset.  I choose the latter, since I have a speed limit attribute in my street data. My speed limit is in MPH and my shape length units are Feet, so with a little algebra I can get a relative drive time to traverse each street segment. Hope this helps- ... View more

Hi there - My GIS work is tied to a multi-agency public safety dispatch system. Due to the software the dispatch system uses, I am limited to 3 alias fields in the road centerline layer. I am trying to figure out a way to fit more than 3 aliases into this layer, while maintaining only 3 actual alias fields. Any suggestions? Thank you so much! You can create an additional table that is related to your roads data via some unique-id. Do not use ObjectID; it will give you trouble. I have had this same discussion with one of my 9-1-1 center clients; they want a gazillion aliases for a street.  I don't go more than 2 deep; that is the real street name and two aliases.  After that it becomes a maintenance nightmare, a database performance issue, and somewhere along the line you lose the sense of the actual street name.  Just something to think about. ... View more

You don't have access to ArcGIS Desktop, just SDE?  I think you'll want to get a copy of ArcGIS desktop installed and you can then create a composite locator through ArcCatalog. ... View more

I guess I have a little too much time on my hands today as I'm looking over past posts of mine. The VGI tool I've been using seems to have settled down on it's own.  One thing you need to be aware of is to turn off your virus ware before you make the run.  Since my intitial post I've run VGI no less that 1,000 times or so it seems. If you have any specific questions about it, I'll do my best to answer them.  Sorry I haven't been more active with this thread. You can email me if you like; jborgione at alpine geographic dot com  (all one word....) ... View more

Could you post up the full, unparsed street names as well as the feild names and values of them parsed?  I'd be happy to take a look it. ... View more

It's there, but hidden under the relationship files - I had to look for a bit.  I was able to use this file to successfully geocode one county in my dataset today with 85% accuracy, and that low rate is probably due to errors in my dataset.  I did not have to download any additional files to create the address locator.  So, I guess the take away is not to use the instructions they provide as they are confusing, and it appears, unnecessary. You've got more patience than me; I'm still fumbling around looking for the relationship files.  I did take a look at the Salt Lake County Utah data.  Wow.  Pretty weird to me. See attached map:  I selected one short segment and this is what was returned.... Glad it worked for you! [edited moment s later: ]  oohhh; there are the relationship files!  Just had to scroll down on the original picklist....  And, the feature class that I downloaded to create the image apparently is the 'wrong' one.  I found the address range feature class; like I said earlier, can they make it more difficult to get what you want? ... View more

I submitted a question to the census bureau as well and below is what I heard back today.  I am still waiting to find out if I still need to link this shapefile to a table though their description doesn't sound like I will have to.  I will test it out this week, even if I don't hear back, and post the results here. "The 2011 TIGER/Line Shapefiles were released yesterday.  This set of shapefiles contains a new shapefile, address range - feature shapefile, which has better geocoding results than the all lines shapefile.  The Address Range-Feature (ADDRFEAT.shp) shapefile contains a record for each address range to street name combination.  Address ranges associated to more than one street name are also represented by multiple coincident address range feature edge records.  This shapefile includes all unsuppressed address ranges and will have better geocoding address match rates compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge.  The TIGER/Line Files contain potential address ranges, not individual addresses.  Potential ranges include the full range of possible structure numbers even though the actual structures may not exist. " So it sounds like the address range feature shapefile is the one you want.  I've worked with streets where the data-maintainer has put the 'exact' range, that is the range of the structures along the street.  Personally, I don't see the point in that.  When geocoding against a linear feature you are interpolating the location of the address.  Since my primary use of geocoding is for 9-1-1 response my feeling is this: Streets and addresses are typically based on a grid.  Use it.  Address through intersections. If you want precise locations, use point data; don't massage linear data into a false positive.  But that's just me.... Would you mind posting a link to the 2011 data?  I'd like to see what they are publishing... ... View more