Latest Contributions by GeorgeNewbury

Thought I'd share my experience with topic. I'm reading a CSV file, making a feature layer from it, and performing transformations on the geometry.  In the end I'm updating the feature class's fields with the geometry, e.g. Point.X, .Y, and .Z going into 'Easting', 'Northing', and 'Altitude' fields.  At first I used the 'Calculate Field' tool for each field. Of course to do this I had to use the tool three times, one for each field.  Next I tried using one update cursor and thus doing all three updates in one loop through the feature class. I found it shaved off 3-4 seconds.  If you need to go through and calculate multiple fields then you may want to consider using the Update Cursor instead of the 'Calculate Field' tool. It could save you a lot of time. ... View more

For the identify parameters layerOption, you can choose from: 'LAYER_OPTION_ALL', 'LAYER_OPTION_TOP', 'LAYER_OPTION_VISIBLE' These options query against the default service visibilities and layer orders, correct? I was putting together the the identify sample with the toggle layer example, and even though I turned a layer off, I would still get an identify result if I clicked on a feature. For example, turn off lakes, click where a lake is, and I'd get the lake even though it wasn't visible. Thanks, George ... View more

I am playing around with Line Barrier - Scaled Costs based on an external set of geometry.  I have the base road data with costs in minutes and the barrier I am adding is scenic byways (road that are fun to drive on). I loaded byway data via 'Load Locations' and use the Geometry as the 'Location Position'.  I expected that it would snap to the street data but it doesn't. Therefore because the byway data isn't coincident with the street data the route analysis essentially ignores it. I am able to select roads from the street data (ones that are on scenic byways) and the load those into the line barriers and get expected results.  I can also add a buffer of the byway data and use that as a polygon barrier and get expected results. Any ideas on the simplest way to do this? I think buffer is straight forward, and probably most accurately reflects the physical phenomena. It would tag some side roads, but I would expect those roads to be somewhat scenic also. Does the polygon come at a much higher computational cost? Thanks, George ... View more

I created a table, and then started editing it, however when I select a record, the record doesn't show up in the Attribute Window (from the Editor Toolbar).  I discovered this because I'm trying to populate an attributed relationship class between tables. I made a feature class out of the table (geocoded addresses) and the attributes window is populated correctly and I can create attributed relationships. Am I missing something here? I'm running ArcGIS 10, with Service Pack, and the tables are in a File Geodatabase. Thanks, George ---Update I found that if I had as Origin-Destination: Feature Class A - Table A (Fa - Ta) Table A - Table B (Ta-Tb) That I could add relationships in Ta-Tb if I got to the origin key in Ta via Fa-Ta.  But that I couldn't add relationships in Ta-Tb directly. ... View more

Currently Time Is placed in the attribute field, making it associated with all of the geometry of the object. In the case of a single point, this is ok, but for more complex geometry, mulitpoint, polyline, polygon, it is not.  We should be integrating time into the geometry of each node.  Each node should have X, Y, Z, M, B, D and where B and D represent the time of Birth and Death (Or start/end time) of that vertex. Where would this be useful? My immediate requirement is for georeferencing video. I currently put time (or a derivative of it like a frame number) in the M column, but when the video stops at one place (vehicle stopped), then there is a problem. Since the video didn't move, it should't move spatially, only temporally. So the M value should change.. But I wouldn't want to be storing multiple points at the same location (besides in some cases it is difficult because of XYZ and M tolerance). Thus if we add the Birth and Death of the Vertices then I can have a temporally correct representation of the location of the video. We have video represented as a line, because it makes it made an efficient way for figuring out where to start the video based on a user click (reverse geocode). If we are going to model the physical world, then we should strive to embed the fundamentals of that world in the models that we create. Time complements space, and so incorporating it at the most fundamental level would lead to additional capabilites for the analysts building the next GIS. ... View more