Latest Contributions by JoeBorgione

No need to keep them in a file geodatabase either.  In fact I suggest not to.  I keep all my locators in a shared drive folder called (wait for it...)  Locators.  And yes you can point them to your sde data.  Just remember, that any edits will not be reflected in the locators until you rebuild the locators.  If you publish any of them, that means stopping the service first. In my particular situation, the published locators are used by 9-1-1 dispatchers, so I have an A and B set of locators.  At any given time, one is 'hot' and the other 'not'.  That means the dispatchers are using the hot one.  I shut down the not one, rebuild the locator(s) and then toggle the users from what they have been using to the one with fresh data.  So what was hot is now not and vice versa.  I then go the the rebuild process again so I'm always up to date on both... ... View more

Are you storing your locators as an object in your SDE database? If so, perhaps that's the issue given the version differences.   I keep all my locators in a shared drive directory instead of in any flavor geodatabase.  Much less overhead that way... ... View more

Have you tried the counties themselves? ... View more

One more item you might consider: Before you perform your intersection, add a field of type Double called Length_Original (or something to that effect). Calc it to equal (wait for it...) Shape Length. Then once you follow either Dan's or Xander's suggestion, you can figure out what percentage of the road will be under water.... ... View more

Gina-  I can get the model to run on a small set of address points. The bummer is only 39 of the 220 points match up with the correct street.  So it works....  Sort of. When I look at the points that are mismatched and the correct street is right there!  Typically adjacent to the the one it selects. I'll keep poking and prodding. Thanks and Happy New Year! ... View more

Hey Gina-  I just downloaded the iterate near tool box.  I have a feature class of address points that has a common field with a feature class of street centerlines.  I need another attribute from the centerlines to appear correctly on the points. I figured out the Near By Group model easily enough (I think), with respect to filling in the feature class names etc, but I'm a bit stymied with the sub model.   I'm assuming that the first Parameters of Input Features and Group Field(s) are passed to it from the Near by Group model.  Is that correct?  And for that matter are all the other Parameters passed into the sub model from the main model? Where then should I put the street centerlines feature class?  In the Near Tool itself?  I'll keep hacking at this and see if I can get it to go. Thanks in advance! ... View more

Are you creating shapefiles or features of feature class in a geodatabase?  If the former, do yourself a favor and go with the latter.   Do you "Stop Editing" as well?  I don't think you can exit out of an ArcMap session without being asked to stop the edit session, but maybe you are missing that? the polylines disappear from the Attributes Table, What is really happening (I think) is the records of the attributes are simply turning off from the table view. May I suggest you create one feature in an edit session, fill in all the attribute values you need, save your edits and then stop editing.  Using the information tool (the i icon) click on your new polygon and see if the attribute values are there as intended.  If all goes well, start your edit session back up and add more polygons and populate the attributes for each.  Save often. ... View more

The problem is the variability in contents.  Even if you pop() the last two elements (Zip and State) you are still left with a variable length list. You might want to try filtering the data through a query or queries.  One such query might be [ADDRESS_FIELD] not like 'PO BOX %'.  Maybe look for street types as well.  These might give you an idea of what you need to do to tease out  the data you're after.  You need to get acquainted with the data to be able to do such filtering.  After all that you'll still have a ton of error trapping the figure out.  Sorry, not a lot of help... ... View more

And when you add the XY data as shown, your telling ArcMap what units they are, correct? ... View more

What XY units are assigned to your data?  Are any of the empty?  To me it sounds like your map is zooming out to a full extent that covers everything; including those that are in error. ... View more

The tool is available here:  http://www.arcgis.com/home/item.html?id=9ac78cd092b640b3b69c6093e1be40bf It has worked great for me; it's been a while since I used it last, but as long as I have the dimensions of the sectors, it works like a charm. ... View more

You might want to search the help documentation on Geocoding. Geocoding is a process by which you translate an address that we humans understand, think 1234 Main St, into a pair of xy coordinates that the GIS understands.  Your locator is based on some sort of feature class,  often road centerlines that has address data that you match your address table to. The help docs have a tutorial as I recall.  Give it a go, and let us know if you get stuck along the way. ... View more

Seems like a number of extra clicks just to get back to the old style right click on the field. But if that works for you, it's cool with me... ... View more

It should retain python within a session, That's what I figured, but for whatever reason, the script stays intact, but the radio button goes back to VB: it craps out in a hurry... ... View more