Latest Contributions by JoeBorgione

‎03-08-2012

Let's see if I can sort this out... When geocoding against street data, the geocoder "looks" for a corresponding street name with a range of addresses that will encompass the specific house number to be located. Typically, address ranges are assgined with respect to the 'FROM' and 'TO' nodes of a given segment; in other words, the smaller numbers are From while the larger numbers are To. So if we were to geocode an address of 101 S Main St, the locator looks for a segement with the components of S = PreDir, Main = Name and ST = Type. Then it looks for a segment with a range that 101 falls within. Lets' say it finds a segment that has 100-198 on the even side and 101-199 on the odd side for ranges. It then interploates a location based on the the length of the street segement, the range, and the given address. We would expect to see 101 S Main St located very close to the 'FROM' node. Whenever you use linear features like streets for geocoding, the location will be interpolated; this is not unique to Tiger files. Consider the same street but a different address: 150 S Main St. The locator will place the point right in the middle of the block on the even side of the street. The reality might be that house number 150 is actually located as the last house on the block and on odd side of the street. Geocoding against lines is accurate, but not truly precise. Again, typically, any addressing system is based on some sort of grid with a point of origin; that's not always an easily discovered fact and it's not alwyas easy to find the point of origin. For use in geocoding the streets should be oriented from the origin; from/to nodes should be all lined up segment to segment when 'traveling' in the same direction. In a perfect world, even numbers are on one side of the street, while odd numbers are on the other. Results obtained from geocoding are only as good as the data you match against. With respect to your question about getting location values of From/To nodes; yes, you can easily tease that information out of a street. You will need to add 4 attributes all as 'double' type. Name them something like FromXCoord, FromYcoord, ToXCoord, ToYCoord. Using the the Calculate Geometry tool, you can populate these fields accordingly. Hope this helps-

‎03-06-2012

A lesson in nomenclature: A true shape file is made up of at least three component files. <name>.shp, <name>.shx and <name>.dbf The .shp file is the spatial feature class in the form of points, lines, or polygons. The dbf holds the attribute data and the shx is the middle man that indexes the propr record (row) in the dbf with the proper feature. A lot of people use the term shape file like Kleenex and bandaid. There are other ways to store spatial data as feature classes in a geodatabase. There is a tendency to call these shape files when technically they are not. A mxd file is often times referred to as a map document. This document holds things like where feature classes are stored, how they are rendered, etc. My suggestion is to google 'what is GIS' or look at the arcgis help files to get a better perspective of the journey you are about to take. Please excuse any typos, I'm using an iPhone while riding a high speed commuter train to reply. Hope this helps.

‎03-06-2012

Arrgh! It might be time to hoist the white flag and give tec support a call. Maybe Brad from ESRI is lurking about out there to lend us a hand.

‎03-06-2012

It's in there; for whatever reason ESRI 'simplified' the choices in v10. Take a look at an earlier thread of mine. You may need to add some 'phony' fields...

‎03-05-2012

Just a shot in the dark Katherine, but is the dual range locator appropriate? Perhaps the US Streets would be a better choice? I'm not too familiar with the tiger street format.

‎03-03-2012

There is only one way to find out; try it...

‎03-02-2012

By large, I mean 3000 to 6000 hence why selecting each one is not an option. I am working with postcode centroids (points) inside postcode polygons. I create territories by entering delivery numbers into the polygons, then dissolving them based on that number. I then need to transfer the numbers to points inside the polygons. These points contain more detained address information which are then expored to a database. Thanks for the input though. Yep! 3K-6k qualifies as a large number! Even if there was a common field to relate to, calculating the values you are after would be an arduous chore... Maybe the spatial join option is looking better? Best of luck with this.

‎03-02-2012

How many is "a large number" ? You could iterively select each polygon, perform a spatial selection of the points based on the selected polygon and update the point attributes accordingly. I'm sure there is a way for Python to cursor through the same sort of process.

‎02-28-2012

Hello! We are trying to set up a multiuser geodatabase with a default version and a surrogate default version that folks are editing to. However, we have encountered a stupid problem. Once you create the surrogate version (which you just do in the version manager, correct?) how do you edit that version and not the default version? When we add the data to our map it just shows up as the default and when you start an edit session it doesn't give us an option of which to edit. In the help it said that it will look like you're replicating the GDB when you create another version but ours doesn't change. Any advice? thank you! Have you tried: Switch Version Setting the 'edit' version as the version to get through the connection dialog Making sde.default protected and edit-version public Hope this helps-

‎02-28-2012

Can someone provide an example that will work with a Personal Geodatabase? The above examples produce an error message when I use them. I have tried this syntax: ... AND Date_Site_Mod > GETDATE() -3 Google "datediff function access"...

‎02-28-2012

Can the near command work for your?

‎02-28-2012

Interesting Michelle- thanks for the update. Since this original post I've gained an appreciable amount of experience using 10.0 for locators. Painful at times, but in a good sort of way.... One of the things that I've gone to is creating locators in their own stand-alone directory. I used to keep them in the same geodatabase as the matching data, address list, and results. A nice tidy package, but it's been explained to me that keeping a locator in a geodatabase creates a bunch of un-needed over head. For distribution I publish them as suggested in Michelle's thread. Also noticed in the original post (several months old now) that Joe H was at sp2. My suggestion is to be sure SP3 is installed and there is a special Geocoding Patch for sp3 available. See an earlier post of mine for a link to the patch...

‎02-27-2012

That's the only way I know how to do it. Remember to use a different port than whatever you've used before; the default is 5151. I have the firewall guys open 5150-5160 so I can have mulitple instances; I create them in numeric order. If your clients are outside your firewall, they'll need to get the right ports opened on thier end as well.

‎02-21-2012

Not sure what you are asking, but when you replicate data, as I understand it you are acutally replicating the database. You don't have to replicate all the feature classes in a database but if you replicate one, you can certainly replicate more.

‎02-20-2012

Hi, I am trying to use python in order to convert a road center line into address points. Basically, I need to use the address ranges and create a point layer dispersed throughout the center line. Any ideas? Can't help you with the Python idea, but I do need to ask you a question: Why do you want to do this? You are going to end up with a gazzillion interpolated points along each segment of road that you have. If you want real address points, there are better ways to get them, like center points of parcels. Just a thought...

Online Status	Offline
Date Last Visited	Tuesday

My Ideas

Latest Contributions by JoeBorgione

Re: Geocoding - get street segment

Re: .shp versus .mxd

Re: Can't get geocoding to work without Zips

Re: Can't get geocoding to work without Zips

Re: Can't get geocoding to work without Zips

Re: update attribute data based on spatial location

Re: update attribute data based on spatial location

Re: update attribute data based on spatial location

Re: Editing the non default version, how?

Re: Help with Definition Query for Current Date minus 7 days

Re: How to calculate Automatically Distances to one fixed point

Re: Certain users can't Review/Rematch Addresses using SDE Locator

Re: Adding Addition Geodatabase to SDE/SQLserver

Re: Add layer to an existing replica.

Re: Convert road center line into address points

Topology in a Versioned GDB

Re: How do I edit metadata with Python?

Attribute Pane Properties

Re: Artificial Intelligence in GIS

Re: Data Scrubbing Addresses

Addressing

911 GIS