I've come to be pretty dependent on both Geometry and Geography storage types, given that I can do significantly more automated data management and processing with them both. Knowing that I'm taking a performance hit by using them, there are a lot of tuning options available, which I've managed to get Geography performing as well, if not faster in some cases, than binary. The biggest gain comes from tweaking the spatial index, but there are other gains from adding other non-clustered indexes and or statistics based on specific use.
As for view performance, one can force indexes on a view at creation with schemabinding:
CREATE VIEW [dbo].[ELKOFFTAKE_VIEW_LOCATIONS]
WITH SCHEMABINDING
AS
SELECT
OBJECTID, VERROR, MAPSOURCE, SOURCEDATE, EDITDATE, MAPMETHOD,
QUADNAME, UNITNAME, HERROR, COUNTY, STATE, X_COORD, Y_COORD, LAT, LON,
WATERSHED, STREAMNAME, ELEVATION, YR, NOTES, COORD_UNITS, COORD_SYSTEM,
DATUM, UTM_ZONE, MANAGEMENTZONE, PARKDISTRICT, EDITBY, CREATEBY, CREATEDATE,
UNITCODE, RESTRICTION, VEG_CLASS, LANDFORM, GlobalID AS 'LOC_ID', LOC_NAME, TRAIL, ROAD, VALID_RESULT
FROM [dbo].[WILD_ELK_OFFTAKE_LOC_PT]
GO
Then
CREATE UNIQUE CLUSTERED INDEX IDX_WILD_ELK_OFFTAKE_LOC_PT
ON ELKOFFTAKE_VIEW_LOCATIONS (LOC_ID);
