I can't find a good amount of information on creating a grid within a set boundary and using the intersection points as points for data. I work in the archaeology field and we dig shovel tests on a 50 foot grid. I am trying to figure out a way of creating a grid before entering the field, where each intersection point already has a distinct GPS point, and data can be entered via a database app in reference to each one of these points. Can anyone help me through this process?
I understand the fishnet tool, but not sure how to use the intersections and create points for each, and additional attributes to be filled in later. And how could I label each point based off of that grid system of x, y? For example, transect 1, shovel test 1.
That may make things easier. But wondering how the grid would be numbered then? Or if there is a way to choose on which side of the baseline the grid is drawn?
Hi Brian.
Yes, I'm unfamiliar with GitHub. Can you explain how I would load these tools to arcmap? I've added the toolbox but there is some kind of error when I run the tool.
This is what can happen when the result from a previous run are still in the TOC of ArcMap. ArcMap will probably create an exclusive lock on those featureclasses and fail to delete them. So, remove
C:\Users\ericv\Documents\ArcGIS\Web Maps\Mechanicsville, Virginia\Features.gdb\grid_point
and
C:\Users\ericv\Documents\ArcGIS\Web Maps\Mechanicsville, Virginia\Features.gdb\grid_poly
...and try again.
Another question:
Do you have a folder called "Mechanicsville, Virginia" with a comma and a space"? If so, it is better to avoid using large names, spaces and special characters in folder names.
If you search this forum for "schema lock" you will find hundreds of messages.
In my experiences, as with many things in ArcMap and ArcCatalog, quitting and restarting is the most reliable (and time consuming) way to deal with schema locks. There does not seem to be any consistent pattern to it that I have ever seen.
I find that if I try to keep ArcMap open and to run the tools in ArcCatalog it's worst - I have to close ArcMap to clear the lock before I can work in ArcCatalog. If the feature class or sometimes just the geodatabase is open in ArcMap it can get locked. I would think that it would only create locks when I start editing but that's not always true.
I have the best luck when working exclusively in ArcMap but even that's often problematic.
I will try to write up something on github for GIS people soon.
I updated the README in the github project, and added sample MXD and GDB.
Also I added a few words on github but my intention is to write a blog post about using it, perhaps once ESRI fixes the codesharing.arcgis.com support for github.
Hi Brian,
Found this thread many years after you wrote it, but I'd love to know the code/workflow for how made your "shovel test" grid. I work in an archaeological lab and we're trying to do a similar thing.