This is not ideal because I don’t want to manipulate the model each time I need to run viewsheds. If I open up the ‘Layer to KML’ tool and under “Extent to Export” I select the buffer layer, it does work for that entire feature class, BUT if I load a new feature class into the tool in a different part of the world, it keeps the Extent of the first feature class. When I connected the output of the buffer to the ‘Layer to KML’ tool and selected “Extent to Export”, it copied the file path into the coordinate boxes instead of the actual coordinates (See Picture Attachment). My last attempt I created a buffer of all the points using the observers maximum range. It keeps the same extent as the layer for Observer 1. This works for the first iteration (Observer 1), but once the tool starts to iterate over Observer 2, the Extent to Export does not change. I have also tried referencing the layer that is to be converted to a KML. I have tried using the ‘Default’ option, but it just returns null coordinates (See Picture Attachment). The next step is to convert the viewsheds into KMZs. I get an error on the ‘Extent to Export’ option of the ‘Layer to KML’ tool. The final output is 3 viewsheds (6ft, 10ft, 15ft) per point in the feature class. I created a model that iterates over points in a feature class and creates viewsheds observing different heights.
0 Comments
Leave a Reply. |