Coastal Vulnerability Model (v3.7): WindowsError: exception: access violation reading 0x00000000

coastal-vulnerability
#1

I’m running the new version of the Coastal Vulnerability model and getting an error:
WindowsError: exception: access violation reading 0x00000000

InVEST-Coastal-Vulnerability-log-2019-05-13–12_48_46.txt (3.5 KB)

#2

Hi Monica, thanks for testing the new model! Would you mind sending me your data so that I can reproduce this error? davefisher@stanford.edu

Thanks!

#3

Hi Dave, Here are the inputs I’ve been using. If the google drive thing doesn’t work, here’s the link: https://drive.google.com/file/d/1s5WYQL3qtDCq_9CMX854Zp0G7E9xGHiA/view?usp=sharing
CoastalVulnerability_Inputs_VicData_v37.zip

#4

Thanks for sharing your data. The issue here is with the WaveWatchIII dataset. It looks like you chose to project the global dataset to match your AOI’s projection. That’s totally sensible, but since the original data includes points all over the globe, not all of the lon/lat coordinates transformed to the local projection you’re working with. Instead the transformation left some point features with no geometry, or maybe something undefined. The model crashed when trying to index those points.

Solutions:
Either use the WaveWatchIII.shp that is included with the InVEST sample data, which is unprojected (the model will handle the projecting appropriately). Or, select a subset of the points near your AOI and project only those. I tried both options with your data.

#5

Thanks for getting back to me so quickly! That’s really interesting. I’ll switch to using the unprotected WaveWatchIII dataset.