Probably be the best way is to create a "topology dataset" with the rule "no overlaps". This will help you go through each digitizing error. The only downside is that it can take sometime..... so hopefully you have a smaller dataset

Here's an example of what I mean by that: -High NDVI values (0.6 to 1.0) is dense vegetation. -Medium NDVI values (0.2 to 0.6) is sparse vegetation. -Low NDVI values (-1 to 0.2) might be barren land, water, or areas with no vegetation.

Happy to help out!

You're correct. You won't be able to move levels up or down after converting to a graphic. That's one of the disadvantages of having a graphic. But yes, you'd have to explode the items in the graphic and move them up manually

I agree. Legends are not as intuitive as they were in ArcMap. But I've been using ArcGIS Pro so much that I know the exact settings that I always use... pretty much the same that I explain in this video

Would you be able to clarify "one" in this sentence - "what if that field you joined has more than one". It sounds like you might have to concatenate the two fields before and create a unique identifier.

@SpatialZone so I have a field called groveid in a feature layer and one in a standalone table, I want them to grab the matching one and give me the field labeled blk from the standalone that being said there is more than one matching groveid in the table and only brings over one in using your tutorial above

@@jodib9598 So you join "groveid" from your feature class and from your "standalone table". Basically, you'll create a new column in the feature class, and transfer the values from "blk" from the standalone table. But the problem, it sounds like you have more than one record in the standalone table (1:M relationship). For example, you might have in the feature class A1. Then, you might have in the standalone table multiple A1s. Is this correct? If I understand this correctly, this means that for every instance there is an A1 in the standalone table... then, you'd want there to be a record to be created in the feature class. So if you have 5 A1s in the standalone table, this means 5 overlapping points in the feature class. If I interpreted this correctly, I've had to do this in the past in ArcMap (not ArcGIS Pro). Follow the same steps as above. But try exporting it as a new feature class. I remember in ArcMap that the resulting feature class would have multiple points overlapping for each associated record in the standalone table. More information about cardinality and 1:M relationships here - gisgeography.com/relate-vs-join-attribute-tables-arcgis/

@SpatialZone thanks, I have done the one to many relate .

I find a lot is easier in ArcMap... lol

First, open up the Catalog pane. Create a new feature class. Follow the steps and make sure that it's a polygon feature class. Go into the Edit pane. Select "Create Features". Then you'll see the "rectangle" tool that you can digitize in your ArcGIS Pro session

I can guess, starting with a BA in geography, for a start .

you'he welcome

They are available for free on the USGS Earth Explorer. Here's a link to a KZbin video I made showing you how to download them

Is there imagery showing where the raster has null values? If that's the case, I am not sure to help you out. That's never happened to me before. Are you sure you don't have a basemap layer, or the old layer turned on underneath?

That's a good suggestion. DataCamp is pretty solid, especially for hands-on coding and learning the syntax. One area that they've struggled before was lacking projects... But they've kinda fixed this with their "projects" section. I still think this also is lacking a bit. A couple of other small complaints. They don't have anything on web development. I was searching for JavaScript tutorials and they don't have a single section on JavaScript. Not sure why, but it would come in handy for how much we use JavaScript in web mapping in GIS. Something else minor, but they are great at teaching basics. If you're just starting out, DataCamp is a great choice. But for those who are already knowledgeable in Python or R... I don't think it will benefit these types of learners compared to absolute beginners.