Latest Contributions by JimCousins

Perhaps a spatial join of the points to the lines? You could leave it at that, export the result to a new file, or add a field to the original file, and calculate it based on the field in the joined dataset. Regards, Jim ... View more

You could load your data, and perform a spatial adjustment. Your could edit your points, and use "Move" to offset them. If you have some experience with arcpy, here is a snippet of code that may help you: Regards,  Jim Shifting features Posted on November 15, 2012 by ArcGIS Python Recipes Shifting (or moving) features is a snap using the arcpy.da module’s UpdateCursor. By modifying the SHAPE@XY token, it modifies the centroid of the feature and shifts the rest of the feature to match. This approach will hold for point, polyline or polygon features. To modify only a single or subset of features in a feature layer, apply a selection to that layer and pass the layer in as the input to shift_features. Word of caution, this is using UpdateCursor, so features will be permanently modified. So, back up your data if you may potentially want to reverse the updates. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 import arcpy   def shift_features(in_features, x_shift = None , y_shift = None ):      """      Shifts features by an x and/or y value. The shift values are in      the units of the in_features coordinate system.        Parameters:      in_features: string          An existing feature class or feature layer.  If using a          feature layer with a selection, only the selected features          will be modified.        x_shift: float          The distance the x coordinates will be shifted.        y_shift: float          The distance the y coordinates will be shifted.      """        with arcpy.da.UpdateCursor(in_features, [ 'SHAPE@XY' ]) as cursor:          for row in cursor:              cursor.updateRow([[row[ 0 ][ 0 ] + (x_shift or 0 ),                                 row[ 0 ][ 1 ] + (y_shift or 0 )]])        return ... View more

Apologies, I neglected to say that I would trust the results of the point distance analysis over the buffer analysis. Jim ... View more

Preface: I am by no means an expert in this process. The first step is to post your point data and evaluate if you have constraints along the edges. If you do not, your plume will be pushed outward larger than is realistic because it will use the mean beyond your data. Your options in this case are to use quantile kriging, logarithmic (this one typically creates a plume smaller than the actual, but you work with the data you have), or to put in constraining data points (control points) based on your knowledge of the site, transmissivity, hydraulic head, etc. I look to see if the resulting plume makes sense in terms of the data set used to create the plume. I know I have not responded to your specific question, but I feel that the parameters you are looking at are secondary to reviewing the data to see if the results make sense. Best Regards, Jim ... View more

In order of likelihood: Buffer will look to do an intersect, and rasterizes the features. So, dependent on the cell size used, you may miss points, or erroneously include points.  Another consideration is the projection you are using - does it preserve distance? The last item I can think of is the buffer parameter for METHOD - Euclidean vs Geodesic. This will only effect you if your coordinate system is not planar.  More information is available in the ArcGIS help under Buffer Analysis. Best Regards, Jim ... View more

I do not have the license for Topology, but there is a tool called Align Edge which should do what you want. Regards, Jim ... View more

I have not viewed the tutorial, but you could use 3D Analyst Tools >> Functional Surface >> Interpolate Shape to add z information from a surface. The default sampling distance is your raster cell size, or you could set it to 1/2 your cell size. As and aside, you can set an offset of 1 (or more) map units to bring your dataset above your other data. Best Regards, Jim ... View more

From the Help under Layer>>Labels>>Expression: Building label expressions Function FindLabel ([NAME], [POPULATION]) if (cLng([POPULATION]) >= 250000) then FindLabel = "<CLR red='255'><FNT size = '14'>" + [NAME] + "</FNT></CLR>" else FindLabel = [NAME] end if End Function You will need to modify the fields/variables to match your needs. The formatting tag for bold is <BOL> followed by </BOL> This information is available under "Using Formatting Tags" in the help. Best Regards, Jim ... View more

Information is out there. Here are 2 links to Blogs regarding education and GIS: https://community.esri.com/community/education/blog/2019/03/04/hands-on-gis-workshops-on-analysis-data-and-society  This contains contact information for teachers who wish to mentor or be mentored by other teachers. Probably a very good place to start. https://community.esri.com/community/education/blog/2019/03/03/fun-with-gis-243-t3g-2019  ... View more

Under the Data Managment Tools toolbox: Fields >> Add Field, right click on it and choose Batch Regards, Jim ... View more

I have had some issues with this in the past. My workaround is to select all the symbols first, and then use the right click (on the Symbol tab at the top) and choose "properties for selected symbols". Best Regards, Jim ... View more

It looks like you have terrain turned on in google earth, and your data is only above the ground surface where you can see it. Even that line is spotty as it cuts through the ground surface. Try turning off GE terrain, or look into "Clamped Features to ground" option during conversion of the layer to KML. Regards, Jim ... View more

This would depend on: Your needs -  do you need to portray accurate area or distance / direction.  Your other data - are your other data layers in x/y coords? it is good practice to try keeping all layers in 1 coord sys Your extents - continental scale is inappropriate for UTM/State Plane, as you will span multiple zones and create distortion.  That said, We work within state plane zones, or UTM zones most frequently, but I am focused on continental US and specific sites / areas within it, and our analyses and model output / input are in feet or meters, and therefore put us into x,y coords and not geographic lat/long. I am sure that the user community will have additional input to this open ended question.... Best Regards, Jim ... View more