From @eneemann and has been sitting in my email for far too long
After sifting through the Locate data some more (and the bbecon databases Scott sent me), I have a few recommendations to remove data from the "bbecon-static" database and instead pull from SGID layers:
-
Golf Courses: Perform Feature to Point analysis with 'inside' option to convert polygons from the SGID layer into points. This will result in points that are nearly identical to what is in the 'GolfCourse_pts' layer of the static database. Drive times are not calculated on this this layer, so the points don't have to be close to roads.
-
Ski Resorts: Just use the 'SkiAreaLocations' SGID layer. All points are located close to roads and within a few meters of the points in the static database layer. The only exception is Canyons, where the SGID layer is closer to the mountain base by about 1/2 mile, whereas in the static layer it's at the roundabout. The SGID point is still right on the roads data, so drive time calculation should be okay. Obviously, this change would need to be tested to verify all of the drive times work.
-
Major Roads 1 Mile Buffer: Create from SGID layer with buffer analysis. I can't tell if this is currently created from SGID (looks like it from 'ironing_board' script) or pulled from the static database, which has a 'MajorRoads_Buffer1mile' layer. If not being done already, I recommend using the SGID data to create the roads buffer.
-
Business Resource Centers, Workforce Service Centers, Procurement Technical Assistance Centers: Recommend adding these three layers to SGID as part of ECONOMY or SOCIETY groups. Then data could be pulled from the SGID instead of the static database. These layers still appear current based on my review of the business.utah.gov web pages. If there's a reason not to add these layers to SGID, then they should probably just stay in the static database.
From @eneemann and has been sitting in my email for far too long
After sifting through the Locate data some more (and the bbecon databases Scott sent me), I have a few recommendations to remove data from the "bbecon-static" database and instead pull from SGID layers:
Golf Courses: Perform Feature to Point analysis with 'inside' option to convert polygons from the SGID layer into points. This will result in points that are nearly identical to what is in the 'GolfCourse_pts' layer of the static database. Drive times are not calculated on this this layer, so the points don't have to be close to roads.
Ski Resorts: Just use the 'SkiAreaLocations' SGID layer. All points are located close to roads and within a few meters of the points in the static database layer. The only exception is Canyons, where the SGID layer is closer to the mountain base by about 1/2 mile, whereas in the static layer it's at the roundabout. The SGID point is still right on the roads data, so drive time calculation should be okay. Obviously, this change would need to be tested to verify all of the drive times work.
Major Roads 1 Mile Buffer: Create from SGID layer with buffer analysis. I can't tell if this is currently created from SGID (looks like it from 'ironing_board' script) or pulled from the static database, which has a 'MajorRoads_Buffer1mile' layer. If not being done already, I recommend using the SGID data to create the roads buffer.
Business Resource Centers, Workforce Service Centers, Procurement Technical Assistance Centers: Recommend adding these three layers to SGID as part of ECONOMY or SOCIETY groups. Then data could be pulled from the SGID instead of the static database. These layers still appear current based on my review of the business.utah.gov web pages. If there's a reason not to add these layers to SGID, then they should probably just stay in the static database.