Latest Contributions by MervynLotter

You can also use the Topographical Positional Index (TPI) to determine position along a slope. If you are using ArcMap, then there is a really useful add-on that was developed by Jenness Enterprises that will easily calculate and categorise this for you. The add-on is free and part of the Land Facet Corridor designer tool. See Jenness Enterprises - ArcGIS Tools; Land Facet Corridor Designer  The Slope Position 3-category output may give you what you are looking for.  The documentation is really good and will help with the installation and setting some of the parameters.  If you are using ArcGIS Pro, then you can more-or-less accomplish the same thing using Focal Statistics and Raster Calculator, you will just need to categorise the output yourself afterwards.  ... View more

Hi Dan No. I was actually thinking in terms of the geoprocessing history as recorded in the Catalog pane history tab. See my screen-grab. All processing recorded here. And as an example of the geoprocessing  history recorded in the metadata. ... View more

Perhaps it would be a good idea to check your geoprocessing history to see whether the edits were logged, and if so, to the same feature class you expected? Edits are also recorded in the file metadata. You may want to check these in Catalog view. ... View more

Hi Jason You are correct, I meant that it records an average for 30 locations instead of seconds.  I do not recall what I set the streaming interval to (probably the default value) or the location accuracy to (I suspect I had set this to 4-5 meters) as I am now testing the new Aurora Collector app but which has not yet implemented the GPS averaging functionality in the current beta version. I noticed it is implemented for the iOS platform.  The Extract Values to Points requires the Spatial Analyst extension. Under the Extraction toolset. Good luck ... View more

Hi Kenta I see what you mean regarding the problem with the output from the Point to Line feature class.  I replicated this issue using my own GPX file. The workaround would be to work with the point feature class that was an output from the GPX conversion tool.  There is a nifty tool called Collect Events that will take your point feature class as an input and provide an output of point features with a count of the number of times that points overlapped. But the point geometry has to be identical for them to be counted as such. Try this and check the results, but you may first want to run another tool before this one where you can specify that all points within, for example, 20 meters are considered to be the spatially identical and then these points are snapped to one another. This is the Integrate tool but be very careful to work on a copy of your original feature class as this tool changes the geometry of your existing points.  ... View more

I had another look at editing my data with unique symbology applied and I cant replicate the problem you describe, although I am using Pro 2.3 Beta. ... View more

I can only comment on the symbology issue and it sounds like the software is behaving as expected. If the symbology is linked to an attribute through Unique Values, and you change the attribute value through editing, then Pro wont know how to render the new attribute item and it will automatically be assigned to the "All other" category. This is expected. To render the new attribute values is easy though, you need to click on the large + plus sign to "Add unlisted values" and the list of unrendered attribute values will be provided to you. Select the value or values to include then click on OK.  They will then be added to your symbology options. ... View more

The workflow I described does not include any points, just the line feature layer you created from your points. From your post I could not tell whether you actually ran the Intersect tool on your line feature (as the only input)? This is an important step to break up your line segments wherever they overlaps with one another. As your results did not show any overlaps using join count, either (1) there are no overlapping features if you zoom in close enough (i.e. the lines may be adjacent to one another like on either side of a highway), or (2) I did not properly explain the process of Intersecting and running the Spatial Join tools. Lets call your overlapping polyline C20181224data_GPX4. I created a simple polyline with 3 features that partially overlap to explain the below process. The process I would follow: a) Run the Intersect tool with only the C20181224data_GPX4 as your input feature. See screenshot. The result will only include areas where the lines overlap. But to determine how many lines overlap, proceed to b). b) Then run the Spatial Join tool using the result from a) as both the Target Feature and Join Features. I forgot to mention previously that you need to change the Match Option to something like "Are identical to" or "Within" (Within may be useful as you can set a search radius if the roads do not quite touch - but I have not tested this). c) Open the output of the attribute table and there should be a Join_Count field with a count of the overlap. Lastly, as a completely different approach, to simply try simply visualize the overlap if there is a lot of it, try setting the transparency to something like 80% and the areas where they overlap will be darker in color. ... View more

You could try first running the Intersect tool using your line feature as input only. This will create unique line sections where they overlap. Then run the Spatial Join tool with the result of the Intersect as both the* Target Features* and Join Features as inputs to the tool. The output will provide many attributes but the *Join_Count *field will identify the overlap and provide a count of the number of times that the lines overlapped. ... View more

I also find the free Tile Package Kreator very easy to use for this workflow Introducing Tile Package Kreator (Esri Labs) and https://marketplace.arcgis.com/listing.html?id=9c9ddae83e5549bb88a2c22e87a18ba1     ... View more

I am using Collector with my Samsung Galaxy S8 phone, with no external receivers. That's why I need use the averaging function to try and improve the accuracy. The error is probably between 1 and 6 meters based and a few comparisons with basemap imagery. I also carry with me a set of A4 white boards (each with a large black cross) that I place across my study area and use to record my ground control points. ... View more

Hi Jason Just to add that for my needs I have had good results using Collector with GPS averaging set to 30 seconds for each point captured. In ArcGIS Online there is a easy way to create a new feature class with the right attributes names using their Ground Control feature template.  The vertical resolution can still be off so I do update the altitude values by running the Extract Values to Points GP tool using the Terrain image service from the Living Atlas. This at least puts my 3D mesh nicely on the ground.  ... View more

Do you know whether the resolution of your feature class or shapefile can handle that number of decimals (resolution)? The reason I ask is that when you create a new feature class, one is prompted to provide a  resolution value for the xy coordinates. The finer the scale, the greater the accuracy, although there is an increase in the size of the feature class.  I sometimes use the opposite to reduce the size of large feature classes where I do not require that level of accuracy. So in the below example, I have the option for setting the resolution to a finer scale than the default value. Do take a look at this help page, it explains it in more detail. The properties of a spatial reference—Geodatabases | ArcGIS Desktop  It is possible that your edited feature layer cannot store that many decimal values.  ... View more

The only place I have encountered the setting of pixel tolerance is with snapping settings (Edit tab > Snapping group > Snapping Settings). This kind-of functions the same as grabbing (snapping to) features during an edit session. Is this what you were looking for? ... View more