Latest Contributions by HardolphWasteneys

Jeroen, I'm using Win 7 64 bit with 9.3.  Generalize will work on multiple selected features.  Try an offset of 0.001 for your case; it is scale dependent.  There may be some limit to the number of vertices governed by your AdvancedArcMapSettings file, but it does work.  Just work up from there on the offset or down on the number of selected ellipses if it bonks. Hardolph ... View more

Rob, the methods John and Joshua suggested will work fine if you know the X-Y offset.  However, if it is really a direction-distance move then you need a reference vector and use Spatial Adjustment.  Bit more complicated, here's how: 1. create a 2 point polyline corresponding to the direction - distance (right click after starting to draw) you want to move points (i.e. a vector). 2. use the copy features tool in advanced editing and replicate and separate the lines so you have 3 parallel "vectors" 3. set SNAPPING on the endpoints of the "vector" line feature class 4. switch editing to the points and select the points you want to move 5. in Spatial Adjustment leave Adjust Data as selected features and adjustment method as affine 6.  snap the spatial adjustment link tool in sequence on each of the 3 "vectors" in the direction you want the move (an affine transformation needs a minimum of 3 links) 7. hit adjust in Spatial Adjustment with the vectors set up you could always move the points exactly back by reversing the links. If that is too complicated use trig and calculate the X-Y offset and do it with Move. Hardolph ... View more

Cliff, Essentially the COGO description window allows you to specify 2 aspects of how to get to the next point and the type of line:  You specify curve in the first pull down at the top, then pull down chord and enter the chord direction and length and then radius of the arc and then left or right of the curve.  There are several alternate ways to describe a curve so that's why the pull downs. (caveat; I don't use COGO, but the geometry is pretty straightforward). If you were drawing this without COGO you would use the curve tool in advanced editing with snapping set to vertices and having already placed the start and end point using a right-click with the sketch tool from the start point and then direction-distance to mark the end points of the chord.  (No need to consider a tangent curve) here's the help description [ATTACH=CONFIG]22066[/ATTACH] Hardolph ... View more

Hi everyone, I'm still relatively new to using the Traverse tool and while putting in a long description I came across this and I don't know how to enter it - help please! �?�thence along an arc with a radius of 350 feet and a 114.26 foot chord distance bearing N27-35-22E, 114.77 feet�?� Your help and explanations would be greatly appreciated! Thanks, Cliff Cliff, ... means that from the point you are at define a point 114.77 feet on the bearing 27 deg 35' 22" and establish a circular curve with radius 350 feet probably tangent to the start point and stopping at the new point.  Start by assuming tangency since they have not defined which side of the chord the curve is on and you can draw the curve without defining the azimuth of the chord, but if that is not correct then draw the chord first and then draw the curve between the start and end points.  (All right click and select functions I presume you are familiar with). Hardolph ... View more

Jeroen,  Marco, Densify is an Arc 10 function and that should work if you're there.  In 9.3 some combination of SMOOTH and GENERALIZE will accomplish what you need to convert a parametric curve into a series of vertices. Generalize should work for circles and ellipses, which as parametric curves are defined by only a few vertices and some code.  To get the density of points that is suitable for your purpose, start with a low number like 1 or 0.1 and work up, or undo the edit and try a lower number.     What I meant about empty geometry refers to the scaling or coordinate system you are in and therefore what offset value you use with generalize. If too big a number it interprets the feature as empty. Seems a bit odd that this is happening to your ellipses anyway since exporting a circle or ellipse in Arc9.3 automatically triggers conversion to a series of vertices that approximate the true curve.  There is no direct ellipse feature drawing in 9.3 only graphic so I converted a graphic ellipse to a gdb feature which retained the parametric curve definition, then exported to shp. Since gdb parametric-feature to vertice-defined shp conversion works without intervention in 9.3; I'd suspect you have a problem in 10 with your installation, perhaps as a result of some Windows update, which has been a suspected plague with some gdb functions for me recently. Some added thoughts:  sounds like you are exporting or copy-pasting into an existing SHP. Try instead exporting the layer to a new shapefile i.e. right click on the layer in the TOC and export data if that is how it looks in 10.   There may also be a new setting in 10s version of AdvancedArcMapSettings that is too big that defines the number of vertices on export.  Hardolph ... View more

Anri, must be the same layer, but multiple intersecting features. Also check that you haven't set up symbology that leaves the new feature blank. Hardolph ... View more

Hi all, I work with ArcMap 10 desktop, basic. I need to convert a polygon feature class from an esri file geodatabase into an esri shapefile. The feature class contains ellipses! So when converted into a shapefile these ellipses transform into squares, diamonds or stripes. Is there a solution to this problem? Greetings and thanks in advance for any comments on this topic! Jeroen Jeroen, you may need to significantly increase the number of vertices by using the generalize tool in advanced editing.  Essentially, in the geodatabase your polygon edge is being defined as a mathematical shape or curve rather than a close spaced series of vertices. As loing as the generalize tool doesn't interpret empty geometry it should work. Try playing with the parameters of the Generalize tool until you get something smooth enough before exporting to shapefile. Hardolph ... View more

Hello, I see the confusion in this map and unfortunately no direct way of solving it except to understand what the hatched lines and numbers represent and at least be able to visualize what I would interpret as as a shallow pit though there are dumps east of the highway on the right.  The map shows a slope with contours between 1500 and 1800 (presumably feet) with superimposed hatched lines representing the crest or edges of mining benches I see cut into the hillside judging from the way contours are chopped.  The numbers represent the height of the bench:  -ves referring to the drop from the crest to the bench below.  The one at the very left/top -57) is on the left side of the line away from the hatches as are all the other -ve.  The +ve number is at the base of a cut and represents the rise to the crest. As you can see the series of numbers through the middle of the benches add up to about the slope difference of the contours or 300 feet (or meters) so they are the same units.  The problem is that the bench heights are variable along their length as shown by the changes in numbers so cannot be treated as contour lines although some connect directly to a contour.  This is most evident and expected ones are at the top and bottom of the pit and in between less so (e.g. the -57 line runs to lower numbers to the south.   If it could be simplified to assume that the crests at least in the middle of the pit were contours then the contours above could simply be crowded close together into the hatched area.  The other test is to compare how the crest heights intersect contours on the north side and south side of the pit and see how close they are.  They are chopped in the image so I can't tell.  The crest elevations can be expected to be fairly even and on contour, but all depends on the era in which the mining was done and hence the survey control. What I would suggest is pick a few benches where the crest height looks even in the middle of the pit, check their north and south contour intersections and draw from there assuming even elevations.  If the crest changes in elevation then you lines are going to cross the crests and that is harder to draw your contours, but at least you can visualize it. good luck Hardolph ... View more

Kemal, not quite sure what you are doing, but to explicitely shift a polygon by changing the coordinates of vertices you should use Spatial Adjustment. Many options to move just the one selected polygon or selected polygons OR the whole shapefile OR any number of other shapefiles in the current editing session workspace. (as an aside this should work for Feature classes or shapefiles, but I recently noticed a bug in my system that prevents it from working on file geodatabase feature classes; probably some darn windows update effect on the FGDB engine) The coordinates of each link are displayed in a table (activated by the pulldown list) as you create them as well as the destination coordinates. Usually one does this graphically by connecting the links to some other spot and then hitting "adjust" after you have enough connections for the Transformation you are using (e.g. affine needs 3). In your case I would just make preliminary links by "snapping" (i.e. set snapping to vertices in your feature) to a vertex then randomly completing the link and then go to the link table and EDIT the coordinates of the destination. Finally after completing you links hit adjust and save your edits. Hardolph ... View more

First you need to clean up the line work making sure the polylines close as John mentioned.  Sloppy line work is a curse for this kind of thing. Then in ArcView try this: http://forums.arcgis.com/threads/6786-polyline-to-polygon You can form polygons from as many closed line shapes and from as many layers as you want in one go just by copying them all and merging them then running the procedure I outlined in the numerous previous posts on the subject using the "Auto-Complete Polygon" Task.  No need to use any out side tools; it was just never documented in 9.x, but also works in 10 and I'm not sure if it was documented there either. Hardolph ... View more

Jeff, your points are appearing at the geographic origin i.e. near 0 N, 0 W, in the Bight of Benin because you have not used the "edit" button in the add X-Y data tool to enter the geographic coordinate system of your data so when it gets plotted on the map, as shown, it is assumed by ArcMap that your coordinates are in Web Mercator Auxiliary Sphere which is measured in meters.  Hence your points are plotting a few meters north of the equator and west of Greenwich.  Had you started with some other basemap (say one that was in geographic coordinates) your data might have plotted correctly.  Wayne and Lucas may also be correct about you data, that is a common problem.  I usually import the data from xls format into a geodatabase table to make sure it gets read as numeric and sometimes copy the data into new columns in the spreadsheet if the original read of the data caused it to be interpreted as text. Hardolph ... View more

Michal, I split the polygons into 4 shapefiles manually:  I simply selected first one non-overlapping set covering as much of the original 'lines" file as possible right click copied the selection, deleted them and pasted them into another shapefile using create features and Target: the second shapefile, then repeat the process with the remaining outlines and a new shapefile until the remainder was a non-overlapping set.    I then copied and pasted and merged each set in a scratch file and ran the "Autocomplete Polygons" process on each merged set with the Target being a Polygon shapefile..  Actually, the other polyline shapefiles were not strictly necessary except to make it easy to see that I had 4 non-overlapping sets or if one used the Copy Features tool to preserve attributes. I am not familiar with the ET geowizards Polyline to Polygon tool, but I expect it would works the same as "Autocomplete Polygons" and the new functions in ArcGIS 10 that produce polygons from all the intersecting outlined areas rather than one per record. Hardolph ... View more

Matt, did you use the "Set Adjust Data" parameters to select the point layer file as well as the polygon layer?   By default selected features would be adjusted, but you might have better luck with the "All features in these layers" parameter and select the files specifically. Hardolph ... View more

Michal, Interesting problem; as you say there is no automatic way of creating ONLY a single polygon from each polyline outline when they overlap others.  Ideally, the polygon creation would go record by record or you could have a tool to sort the set into non-overlapping files. For this I just manually split the set up into 4 non-overlapping shapefiles, which was kind of amusing, and ran each to create polygons in a common target polygon shapefile.  Worked fine and I symbolized them by area as shown in the figure.  Use the "Copy Features" tool to create the new files and maintain the attributes.  I just did a select, right-click copy, r-c delete, r-c paste to a Target shapefile and then copied and merged the polylines in a scratch shapefile  (see http://forums.arcgis.com/threads/6786-polyline-to-polygon) Hardolph [ATTACH=CONFIG]18217[/ATTACH] p.s. in Arc10.1 you might be able to use modelbuilder and the iterate over records function http://resources.arcgis.com/en/help/main/10.1/0040/00400000000n000000.htm ... View more