Latest Contributions by curtvprice

Hi @JoeBorgione - just a digression about "fat" tables with many fields - with shapefiles and (gasp) coverages, empty string fields take up a lot of space and slow things down, as the physical space (eg a 255 byte string field) is used whether there are data in the field or not. However, in the world of geodatabases (which live in highly indexed data structures behind the scenes) empty fields and short string fields do not actually take up space. Also shapefiles don't store null, just ' ' or 0 for string fields. Back in the day (1980s, 1990s) we would make tables as skinny as possible by normalizing data (lookup tables) and joins to speed things up - not so much a concern with geodatabases. In geodatabase design you are often better off with fewer, indexed, "fat" tables to keep schemae as simple as possible. ... View more

This can be done in Python (either script, command line, Notebook, or using the Calculate Value tool in Model Builder),  with the arcpy.da.UpdateCursor method The Calculate Field tool can only update one field at a time.   with arcpy.da.UpdateCursor(tbl, ["FLD1", "FLD2"]) as rows: for row in rows: row = (" ", " ") # or (None, None) (None and blank are not the same) rows.updateRow()         ... View more

The AGOL platform can't see local files (ie your M drive). The only way to make this work is to upload your excel data to a table in Google Sheets or as a csv to ArcGIS Online. The latter task could be done on the Windows side using a python script that uses the gis module. Here is a learn.arcgis.com  tutorial to update a feature service, try that, if you get it working you can use the same procedure to update your .csv. Another possibility is copying your excel sheet to a web accessible folder so you can provide an https address to read the excel file, but I am unsure that would work. ... View more

UPDATE: looked at the screen shot and the output path is: C:\Users\jami\Documents\Capstone_20minCity\Tempe_20minCityGDB\ModelOutput2021.gdb\BikeAll\BikeAll_Grocery_Stores Are you sure that both the geodatabase ModelOutput2021.gdb exists and the BikeAll feature dataset exists within it?   ... View more

I strongly encourage you to keep any installation media in any other folder than on OneDrive. Just doing that may solve your problem. Even when using GIS, you should turn off OneDrive synch while you work on those folders (I avoid it). ... View more

This does sound like an appropriate use of subtypes, but a complex data design is not without cost. I do recommend you do data design from scratch and then load data into the new data model, much easier than trying to retrofit a data model in-place. Another thing to consider if the main use case for the domains is field data collection is Survey123 with XLSForms, this allows a lot of flexibility for a complex data collection task, for example if you choose a certain type of object, you can make fields that are not needed disappear from the form experience so they aren't in the way. The XLSForms programming is not trivial but if you get it working it makes the data collection user experience really easy and simple. ... View more

This can vary a lot depending on which country you are in and what your license requirements are. For example, if you are a student you may be able to get it for free from your university. Or, if you are a student or want to use the software for non commercial use, you may have access to ArcGIS for Personal Use (small yearly subscription). This is a question for Esri as they can get you set up with what you need. ... View more

Basemaps are tiled image services - they are a picture (just for backdrop) they are not elevation data. I think what you want are ArcGIS Online imagery layers, these are raster data you can work with directly. There is a nice imagery layer in the ArcGIS Online Portal called Terrain that allows you to download elevation, slope, etc. If you create a local raster you must save it locally (for example as a .tif) or as a file geodatabase raster. ... View more

I don't think there is a very efficient way to do this, as you would need to remove the domains from all the fields they refer to, add new fields, and create new domains of the correct type referring to the new fields. Are you extremely sure you need to create subtypes? They are a very specialized thing and are only really appropriate when you have a single feature class than has all the same fields but different domains and defaults (and maybe different topology rules) for different groups. The example I use when teaching is water pipes, where some are trunks, some are mains, some are laterals, they all have the same fields and can be one feature class but each may have a default type and size and maybe different domains as well. If you have 75 (!) domains i wouldn't do anything in a hurry because it seems to me you have a major geodatabase design challenge on your hands.  ... View more

Seems to me like a job for XLSForms. It's a pretty flexible programming language to modify the survey based on input as you go. ... View more

To speed things up for many wells there are two approaches you may want to consider: 1. Make use of the memory workspace - this avoids the slowdown of disk IO 2. If you have a maximum buffer size (or maybe select to groups so you have a group of smaller buffers) you can do the clip in non-overlapping groups. I wrote a tool in the NAWQA toolbox that weeds points years ago to do this (similar problem as yours calculating land use around thousands of wells). ... View more

Assuming the points (buffers) and red lines all share a well ID, you can process these one at a time. This could be done in ModelBuilder using an iterator, on each run  you would select layer by attribute to pick each line and its buffer in turn and clip. Name the clip outputs uniquely with the well-ID or %n% and then append them at the end after the iterator is done (ie outside the iterating model). This would take a while if you have thousands of points. Hope this helps you out! ... View more

It may be help if you explain exactly what you are trying to do here. It looks like you are trying calculate table values back into a table. If that is what you are doing, why not just use the table? ... View more

There are two approaches to extracting values from a table of values into ModelBuilder variables that I know. 1. Create a table view and then use Select Layer By Attribute (or Iterate Row Selection if you want to dig into an iterator) to select each row, and then use the Get Field Value tool to get the data into model variables. This would probably be done best in a sub model, as we're talking about a lot of tools. 2. Use the Calculate Value tool to read the table in Python and do whatever you are doing in Python using Python variables, not ModelBuilder.  (This requires Python knowledge.) ... View more