Latest Contributions by RichardFairhurst

Press Control Z I should have thought of that.  It does the same thing as the Delete Vertex context menu option when that option is applied to the last vertex, only it is faster.  Ctrl-Z is limited to removing the last vertex one vertex at a time, while the context menu Delete Vertex can delete any vertex in the sketch by right clicking on top of the chosen vertex. ... View more

Hi, Does anyone know how to delete vertices (i.e. back up) in ArcMap 10 while drawing in freehand in the construction tools?  I was just curious if there was a way to do this without having to go ahead and complete the polygon and then go back and edit the vertices post completion. Thanks! Matthew You should be able to right click directly on top of the last vertex placed in your editing sketch and delete it using the context menu.  The Delete Vertex context menu can delete a vertex at the beginning or middle of your sketch as well as the last vertex of the sketch.  (Correction from my prior statement that the context menu only worked on the last vertex, it actually works on any vertex). ... View more

Greetings, As the title of this post indicates, I have two questions pertaining to drawing curves using the editor functions for cadastral mapping purposes. 1.) I have been unable to find adequate tutorials or examples of how to draw curves from surveyors data, such as arc length, radius, or delta angle. I am hoping to input that information into editor to produce the lines. Any idea on how to do this? 2.) In some instance, no surveyor data is provided for the arc, but I am able to discern that based on other information. My question is, if an arc is 500 ft long, what is the simplest way to measure certain distances along the arc to place nodes at those locations? To get an idea of what I'm talking about, I attached a sample block key card with a curve containing parcels every 51.9 feet along the curve. I need to be able to break the curve into 51.9 ft segments. Thanks, Rob M For your first question tha answer is COGO:  Start with the help here and follow the section it is in to see your tools and workflow options:  An overview of COGO ... View more

Hi, Forum! Im running into some issues when trying to display Route events (Points with length data) within a river catchment. Here`s the point of departure and the way I tried it: I got 51 fish sampling points evenly distributed over the Austrian river network. For each of these points I do have data on the length of the fished stretch (between 200 and 6500 meters for each point) and whether the sampling was conducted upstream or downstream of a point. In order to get a polyline imprint ffor each of those 51 sampling points, I was trying the "locate features along routes"-tool to get their location at the river network (units in meter). Curiously, after providing the tool with the correct Route identifiers, the measured distance (meas field output in the attribute table) for each point is way too short (always somewhat between 0 and 600 m) although a river route may be greater than 1500 meters in length. Still, although those numbers are to small, their location seems to follow a correct ratio (e.g. if i got 2 fish points in a row, one would show me 150 m and the upstream one 180m) However, next I was using the meas data and the fished length data on the "display route events" option. For upstream lengths, i calculated "meas + fished length" and vice versa for the downstream fished lengths ("meas - fished length"). The result is a polyline shapefile where every single length is  overestimated at large scale (sometimes more, sometimes less). I hope you can help me with this, thanks in advance Wolf The logical explanation is that the measures of your route are not in meters, since all of your results are consistent with that condition.  Although what unit of measure it is using is unclear from what you have described.  Route measures can be in any conceivable unit length, including random lengths, depending on how they were built. On your routes, go to the properties and apply hatching of your measures to see what is actually stored on your route lines.  Then use the measure tool to determine the length between several pairs of known hatches to see if there is an obvious unit ratio difference that consistently defines your route measure system.  There are ways to have the Routes remeasure themselves based on lengths (unit conversion multiplication with the Route editing tools, rerunning the Create Routes tool, etc), but which is best for your situation depends on how many routes you have, whether the current routes have a consistent unit differential to meters, the amount of route branching and looping, etc. ... View more

Thanks a lot. The syntax that works in model builder is as follows: !SHAPE!.extent.ymin Obviously the shape field needs to be capitalized and surprisingly the xmin field need not be. The expression above works in the Desktop environment and so does my expression (I tested both).  But apparently only one syntax is supported by the geoprocessing environment.  Whatever works is all that matters in the end.  But the syntax support should be consistent between Desktop and ModelBuilder.  ModelBuilder should add support for the alternate syntax and not drop the alternate from Desktop, since Desktop gets used so much more often than the ModelBuilder tool. Differences like this definitely can and do exist between Desktop and ModelBuilder tools.  It is annoying, since it is confusing when something works in one and not the other. ... View more

Thanks, Below is the result: Executing (Add Field): AddField Geo_Index_All_test test DOUBLE # # # # NULLABLE NON_REQUIRED # Start Time: Mon May 20 12:00:04 2013 Adding test to Geo_Index_All_test... Succeeded at Mon May 20 12:00:05 2013 (Elapsed Time: 1.00 seconds) Executing (Calculate Field): CalculateField Geo_Index_All_test test !TEST.Extent.XMin! PYTHON # Start Time: Mon May 20 12:00:05 2013 ERROR 000539: Invalid field TEST.Extent.XMin Failed to execute (Calculate Field). Failed at Mon May 20 12:00:05 2013 (Elapsed Time: 0.00 seconds) However, Below are the results when with different expression (runs - but all NULL) Geo_Index_All_test test DOUBLE # # # # NULLABLE NON_REQUIRED # Start Time: Mon May 20 12:02:19 2013 Adding test to Geo_Index_All_test... Succeeded at Mon May 20 12:02:20 2013 (Elapsed Time: 1.00 seconds) Executing (Calculate Field): CalculateField Geo_Index_All_test test !TEST!.Extent.XMin PYTHON # Start Time: Mon May 20 12:02:20 2013 Succeeded at Mon May 20 12:03:22 2013 (Elapsed Time: 1 minutes 2 seconds) Test is not the name of a shape field and no field you have created can be used in the field calculator expression to do this type of calculation (Test could be the name of an output field only, but not part of the calculation expression).  The shape field is a built in field for a feature class or shapefile and would always contain the word Shape in the name, so your expression tests above are meaningless. Copy and paste the exact expression below into the field calculator (don't change anything) and run it so that it outputs to your test field or whatever field you have set up as a double for the calculation output: !SHAPE.Extent.XMin! ... View more

Thanks. I am getting the same error. however when I use the expression: !test!extent.XMin It runs but no values are added to the field. All are NULL No my syntax is essentially correct, since I just tested it, but perhaps the capitalization is wrong (Python at 10.1 is case sensitive).  First double click the Shape field in the pick list so that it has the exact same capitalization and name spelling for your shape field as you see in the table and then capitalize .Extent.XMin exactly like that.  For my successful calculation my shape field is in all caps, so my expression read: !SHAPE.Extent.XMin! ... View more

Hi,  Thanks for the reply. The error is that it can't find the address locator. I don't understand why this is occuring since I checked that I got the correct file path. One odd thing is that it seems to be reading the file in incorrectly. Consider the following code and error:  >>> open(r'GIS Servers\arcgis on tasks.arcgisonline.com\Locators\TA_Address_NA_10.GeocodeServer') Runtime error <type 'exceptions.IOError'>: [Errno 2] No such file or directory: 'GIS Servers\\arcgis on tasks.arcgisonline.com\\Locators\\TA_Address_NA_10.GeocodeServer' It seems to read in too many back slashes. I have also tried to open other files on my computer in python in arcgis and it doesn't work. Could there be a problem with python in arcgis where it doesn't allow me to open other files?  Thanks,  Julian The number of backslashes shown is correct, since backslash is an escape character to python and in order for python to resolve it as an actual character it either must be preceeded with the raw qualifier (the r in front of the quoted string) or each literal backslash character must be preceeded by an escape backslash character. I don't know how your servers are set up, but in my system I would have expected two backslashes would preceed the server name if this is a dfs setup, i.e., open(r'\\GIS Servers\arcgis on tasks.arcgisonline.com\Locators\TA_Address_NA_10.GeocodeServer') ... View more

Hello All, I have polygons in a geo-databases - WGS84 I want to calculate the extent (XMin, ...) I have added a field XMin_Test (double) In the field calculator I added the Python expression !extent.XMin! I am getting the following error: ERROR 000539: Invalid field extent.XMin Failed to execute (Calculate Field). I have tried the field as text, changed the expression to !extent.shape.YMin! Same error. The syntax in the Field Calculator should !Shape.extent.XMin! The name of shape field in the feature class has to come first in the expression before accessing the properties of the shape field with the dot property operator. ... View more

Hi all, I'm trying to use python to geocode a set of files, but it returns the above error after a few minutes of running the code every time. I've read that I might need to convert my files into a .dbf format, but I'm not sure. I've put my code below. #Julian Katz-Samuels #May 1, 2013 #Geocode addresses import arcpy arcpy.env.workplace="X:\ebruch\shared" parts=range(10) parts.remove(0) parts=map(str, parts) years=["2000", "2001", "2002", "2003", "2004", "2005", "2006", "2007", "2008", "2009"] Geocoder = r"GIS Servers\arcgis on tasks.arcgisonline.com\Locators\TA_Address_NA_10.geocodeServer" for i in years:     for j in parts:         address_table= r"X:\ebruch\shared\HistoryFile" + i + "_part" + j +".csv"         geocode_result= r"X:\ebruch\shared\GeocodedHistoryFiles\GeocodedHistoryFile" + i + "_part" + j         arcpy.GeocodeAddresses_geocoding(address_table, Geocoder, "Address SRmailSTREETNAME VISIBLE NONE;City SRmailCITY VISIBLE NONE;State SRmailSTATE VISIBLE NONE;Zip SRmailZIP VISIBLE NONE", geocode_result, "STATIC") print "Done!" Best, Julian Did you look that error up to see if it has explanations about potential causes?  The text of the error you have written is very generic.  That could be the nature of the error, but the help sometimes gives details that narrow down what caused the error better than the error message. Since the error is so generic, I would add a file exists test to verify a file with the input name you are feeding to the tool actually exists.  Not sure how good error messaging is when an input does not actually exist, but even a single character difference in a file name (a leading zero inconsistency for example) or a missing file name in the series would be the first error possibility I would eliminate. You also have not set the geocode process flag that overwrites prior outputs.  If you ran this and an output continues to exist from a prior run I would expect a failure.  The tool you are using also may not support overwriting a prior output even if that flag is set.  In any case, it is possible the tool would only fail when it is nearly complete and actually attempting to overwrite a prior output.  Be sure to clean out all prior outputs before rerunning the code (or adjust the code to start at a point that will not impact the prior outputs).  Of course if no output has ever been generated by this code ever, that would be an important piece of information to help narrow down the cause of the error. Other error possibilities exist, but these two are errors that commonly crop up when working through a series of files and attempting to rerun tools after a prior failure. ... View more

Deal member, I am a new user of ArcGIS. I wanted to export one shape file to coverage using ArcGIS 10.  However, it fails to do with an error message, 'Feature class to converge'. Can any one suggest as to how can I overcome this problem? DVK Nageswara Rao Not sure why it failed, but export functions will fail if the source feature class is open in an edit session and some fail if the source file is not exclusively controlled by the export tool (i.e., it cannot be open or locked elsewhere, either by you in a different ArcMap application, or by others). Screen shot the error message or write out what it actually says.  Some error messages are overly generic and not much help, but others give vital information about what actually went wrong so that you can correct the problem. Out of curiosity, why do you need to work with this shapefile as a coverage? ... View more

Thanks a lot for your generous reply. But I am looking for the surface created in the image attached not symbology. That elevated surface where the values are high and less elevated where values are low. Well it will involve one or more of the 3D Analyst tools at some point, but I do not know what data type the original layer is showing, so I cannot propose a workflow without more information.  If that is a raster then conversion should be pretty straight forward. ... View more

Do I need to make a copy of the feature class before doing this? Is there a chance I will mess the file up and can't go back? Thanks for the help. Yes, it is wise to have a back up, especially when first testing out and learning how topology behaves.  Corruption is not so much of a problem as much as failing to realize how your choices using the topology tools affect your features, because you are not used to them.  Topology will permanently alter your data, but it does it within an edit session.  As long as you catch problems before saving and exiting the edit session you can undo them or prevent them from becoming permanent, but if you missed a problem after committing the edits you cannot go back without some kind of backup.  Once you have everything working well and understand the topology workflow options and the critical quality check steps you need to do, you could choose to delete all back ups and work with the topology controlled feature class alone. ... View more

Thank you soooo much for an answer. It helped a lot with dissolve. You probably figured this out, but you do not have to limit yourself to the line and polygon FID fields.  You could choose all of the fields of your intersected feature set in the unique case field (the fields from the original lines and the fields from the original polygons) as long as you do not include the new ObjectID field of the currently Intersected feature set.  As long as the unique field values you choose do not prevent lines from combining that you want combined this method can be used to retain the full set of attributes from your original Intersect inputs in the final Dissolve output. Also, please add a point or an answer check on the right side of my post if it helped you.  Those votes are the best way to help others find answers more quickly. ... View more