Thanks for your reply. I'm familiar with the "Make NetCDF Raster" Tool, but when I try and run it, even after defining the projection, ModelBuilder says that there is no spatial reference. I tried both Define Projection and Project (although, by convention, the original NetCDF file should be in WGS 84). And it's mostly after applying that tool that the process becomes a bit more murky for me, in the separating out the individual years and months of interest (namely, 4 specific years and 4 months of each year, one representing each season), and individual jurisdictions of interest. We're looking at 4 particular years and 4 particular months of each year, but the NetCDF files contain data for each month of each year, not annual data. So, in theory, I suppose one must generate an individual raster for each month of each year of interest, then use the Raster Calculator to combine said months into one raster representing the year as a whole. The data also has to be clipped, considering the original raster generated is national in scope and we are looking more regional and local. But I'm very uncertain about the procedure after applying the aforementioned tool. The spatial reference error generally kicks in around where the Clip tool is applied (current flowpath for each month in question is Make NetCDF Raster (month of interest selected under Dimension Values)-->Define Projection (WGS 84)-->Project (MD State Plane NAD 83)-->Clip (Somerset County, MD, MD SP NAD83)-->Raster Calculator (combined with other months, divided by 12)-->Representative Annual Raster for Year. There are preconditions in place to ensure the sequence for each month completes before the subsequent month runs and to ensure all monthly rasters generate before the Raster Calculator runs.)
I've also tried removing the Define Projection, as well as shuffling the flowpath order, flipping the order of the Clip and Project, shifting the clip features into WGS 84 first to run the Clip, then projecting the clipped jurisdiction into the State Plane system afterward. It always results in the same error regarding the spatial reference.