20131213
15564600
1.0
North American Profile of ISO19115 2003
FALSE
CalculateStatistics "Database Connections\SCD_GDBA@SCD_GIS_PROD@sql2012-sql127GIS.sde\SCD_GIS_PROD.SCD_GDBA.SNOCO__SNOWLOAD__per6ftPixelValue" 1 1 # OVERWRITE "Feature Set"
ChangePrivileges \\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.JURISDICTION__land_use_jurisdiction;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__CAPITALFACILITIES__fire_protection_distircts;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__CAPITALFACILITIES__general_county_facilities;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__CAPITALFACILITIES__monitored_landfills;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__CAPITALFACILITIES__sewage_treatment_facilities;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__CAPITALFACILITIES__solidwaste_facilities;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__CAPITALFACILITIES__water_system_facilities;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__FLU__agriculture;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__FLU__futurelanduse;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__FLU__minerals;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__FLU__municipalurbangrowth;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__FLU__municipalurbangrowth_shoreline;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__FLU__rural_urban;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__FLU__urbangrowth;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__FLU__urbangrowth_muni;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__land_use_jurisdiction;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__PERMIT__building_inspection_areas;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__PERMIT__BUILDING_INSPECTION_AREAS_EDIT;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__PERMIT__community_groups;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__PERMIT__snowload;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__PERMIT__snowload_per6ftPixelValue;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__PERMIT__snowload_per10ftPixelValue;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__PRESERVATION__conservationfutures;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__Subarea_Boundary;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.PLANNING__TDR__transferofdevelopmentrights;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD__LbsPerSqFtPixelValue;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD__per6ftPixelValue;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD__per10ft;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO_SNOWLOAD_per10ftPixelValue_floatpt;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SWIFD_All;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SWIFD_BullTrout;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SWIFD_Chinook;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SWIFD_Steelhead;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_airparks;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_approach_and_transitional_surfaces;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_approach_surfaces;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_boundaries;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_buildings;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_compatibility_areas;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_FAA7460_buffer_20k;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_influence_areas;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_runway_protection_zone;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_runways;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_runways_centerlines;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_structures;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_taxiways;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__airport_transitional_surfaces;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__hwymrkrsymb;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__ILA;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__interstate_adjco;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__sr_adjco;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__TES_arterial_circulation;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__TES_bicycle_facility_systems;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRANSPORTATION__wsdot_LOS;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRIBAL__quil_ceda_village_bndy;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRIBAL__sauk_suiattle_reservation;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRIBAL__stillaguamish_bndy;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.TRIBAL__tribal_jurisdiction_parcelbase;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.UTILITIES__DISTRICTS__sewer;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.UTILITIES__DISTRICTS__sewermoratoriums;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.UTILITIES__DISTRICTS__water;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.UTILITIES__EASEMENT__Everett_Transmission_25ft_Buffer;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.UTILITIES__EASEMENT__Everett_Transmissionline;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.UTILITIES__NETWORK__pipelines;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.UTILITIES__NETWORK__sewerlines;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.UTILITIES__NETWORK__waterlines;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.WUI;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__CURRENT__zoning_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__CURRENT__zoning_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__CURRENT__zoningdissolve_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__CURRENT__zoningozmap_anno;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__AgriDesig_Bndy_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__AgriDesig_Notice_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__AgriDesig_Notice_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__Airpark_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__Airpark_Notice_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__Airpark_Notice_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__Airpark_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__CFandLF_Notice_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__CFandLF_Notice_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__CFFTA_Dissolve_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__FandR_ORV_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__FandR_ORV_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__FHA_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__IsoStreetBlocksDivBy4_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__IsoStreetBlocksWhole_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__LotStatus_Easement_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__LotStatus_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__MasterPageGrid;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__MinLotSize_10ac_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__MRO_Dissolve_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__MRO_Notice_line;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__MRO_Notice_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__SCC30dot23_Multifamily_TDR_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__Shortplat_Easement_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__Shortplat_poly;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__Shortplat_pt;\\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.ZONING__OZMAP__Tulalip_Res_Bndy "SNOCO\SNOCO_All Hands" "Grant view privileges" "Do not change edit privileges"
Resample \\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD__per6ftPixelValue \\snoco\gis\plng\carto\SCDJ2L\dev\AMANDA_prop_info\ZonalStat_TEST.gdb\SNOCO__SNOWLOAD_per36ftPixel "36 36" Bilinear
CopyRaster SNOCO__SNOWLOAD_per36ftPixel \\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD_per36ftPixel # # # NONE NONE # NONE NONE "Esri Grid format" NONE CURRENT_SLICE NO_TRANSPOSE
Rename \\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD_per36ftPixel \\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD__per36ftPixel RasterDataset
Rename \\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD__per36ftPixel \\snoco\gis\plng\GDB_connections_PAG\SCD_GDBA\SCD_GDBA@SCD_GIS_PUBLISH.sde\SCD_GDBA.SNOCO__SNOWLOAD__per36ftPixelValue RasterDataset
SCD_GDBA.SNOCO__SNOWLOAD_per36ftPixel
1244714.006022
1622426.006022
284276.073984
477596.073984
1
Server=PAG-GISDept; Service=sde:sqlserver:PAG-GISDept; Database=SCD_GIS_PUBLISH; User=scd_gdba; Version=sde.DEFAULT
ArcSDE Connection
001
Projected
GCS_North_American_1983
Linear Unit: Foot_US (0.304801)
NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.3.0'><WKT>PROJCS["NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1640416.666666667],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-120.8333333333333],PARAMETER["Standard_Parallel_1",47.5],PARAMETER["Standard_Parallel_2",48.73333333333333],PARAMETER["Latitude_Of_Origin",47.0],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2285]]</WKT><XOrigin>-117104300</XOrigin><YOrigin>-99539600</YOrigin><XYScale>37926742.22403606</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>2</ZTolerance><MTolerance>2</MTolerance><HighPrecision>true</HighPrecision><WKID>102748</WKID><LatestWKID>2285</LatestWKID></ProjectedCoordinateSystem>
20241018
13522400
20241018
13522400
ISO19139
500000
5000
dataset
external
891a2fc69f67382c4319a3159f6fd14cd48f01e6
PDS-GIS Administrator
Snohomish County Planning and Development Services (PDS)
Team Lead/Principal
3000 Rockefeller Ave, MS 604
Everett
WA
98201
PDSGISTeam@snoco.org
US
https://gismaps.snoco.org/Html5Viewer/Index.html?viewer=pdsmapportal
425.388.3311
1) Online downloads available via the Snohomish County Open Data Portal, "https://snohomish-county-open-data-portal-snoco-gis.hub.arcgis.com/";
2) Online MapServer/REST Services available at, https://gis.snoco.org/host/rest/services; and https://gis.snoco.org/img/rest/services;
3) Online PDS Map Portal {Web Map Viewer} , "https://gismaps.snoco.org/Html5Viewer/Index.html?viewer=pdsmapportal"; 4) Request relating to Planning, Future Lane-Use, or Zoning geo-datasets are handled by PDS;
5) All other request for geo-datasets are handled by the Snohomish County Department of Information Technology,
also refer to "https://snohomishcountywa.gov/1402/Maps-GIS".
https://gis.snoco.org/img/rest/services; https://gis.snoco.org/img/rest/services
ArcGIS REST Services
Snohomish County geo-datasets available as ArcGIS REST Services. Viewable via ArcGIS Online Map Viewer. If need be, Esri offers a free account (www.arcgis.com).
True
PDS-GIS Administrator
20241018
Enterprise Geodatabase Raster Dataset
Esri
Esri ArcGIS 13.3.0.52636
pds_snowload
2000-02-10T00:00:00
external
891a2fc69f67382c4319a3159f6fd14cd48f01e6
PDS-GIS Administrator
Snohomish County Planning and Development Services (PDS)
Team Lead/Principal
3000 Rockefeller Ave, MS 604
Everett
WA
98201
PDSGISTeam@snoco.org
US
https://gismaps.snoco.org/Html5Viewer/Index.html?viewer=pdsmapportal
425.388.3311
1) Online downloads available via the Snohomish County Open Data Portal, "https://snohomish-county-open-data-portal-snoco-gis.hub.arcgis.com/";
2) Online MapServer/REST Services available at, https://gis.snoco.org/host/rest/services; and https://gis.snoco.org/img/rest/services;
3) Online PDS Map Portal {Web Map Viewer} , "https://gismaps.snoco.org/Html5Viewer/Index.html?viewer=pdsmapportal"; 4) Request relating to Planning, Future Lane-Use, or Zoning geo-datasets are handled by PDS;
5) All other request for geo-datasets are handled by the Snohomish County Department of Information Technology,
also refer to "https://snohomishcountywa.gov/1402/Maps-GIS".
https://gis.snoco.org/img/rest/services; https://gis.snoco.org/img/rest/services
ArcGIS REST Services
Snohomish County geo-datasets available as ArcGIS REST Services. Viewable via ArcGIS Online Map Viewer. If need be, Esri offers a free account (www.arcgis.com).
True
PDS-GIS Administrator
1
-122.459131
-120.906506
48.309271
47.767990
A pre-fabricated raster with pixel-values representative of the actual Snow Load for building structures (lbs. / sq. ft. or psf) within the proximity of a 6-feet cell size.
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>For Snohomish County, the roof snow load may be greater than or equal to 25 pounds per square foot (psf) depending on the elevation of the site location. Applicants for building permits must account for the ground snow load calculations, as verified by the Plans Examiner. Map algebra and raster calculations derived the Snow Load by multiplying the elevation times the Snow Load factor. These pixel-values represent the actual Snow Load calculation in psf at that spot.</SPAN></P><P><SPAN>[ Snow Load Calculation {psf} = (Snow Load Factor {pixel-value}) x (Elevation {ft.}) ]</SPAN></P><P><SPAN>As the American Society of Civil Engineers states that "in civil engineering, design loads are defined as the maximum amount that a structure can handle". Since the International Code Council (ICC), as with the historical Universal Building Codes (UBC), indicates in section 1608.2 that "Ground snow loads" for the area of Snohomish County falls under a Case Study (CS). The Washington Association of Building Officials (WABO) and Structural Engineers Association of Washington (SEAW) organizations have a White Paper which provides more detailed information. During the early 2000's, PDS Engineers and Plans Examiners decided on the iso-lines for the Snow Load factor. Further interpolations and vector-to-raster transformations occurred. In 2007, the Snohomish County Code (SCC) 30.52F.300TableR 301.2(1) was amended in to establish a Minimum Roof Snow Load of 25 psf. In 2015, the PDS created a web application (PDS Map Portal) that allows users to find Snow Loads at any given location as compiled in a PDS Property Report. </SPAN></P></DIV></DIV></DIV>
PDS; ICC; ASCE; WABO; SEAW.
Snow Load
SCC 30.52F.300TableR 301.2(1)
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Use of any data acquired from this site is subject to the following limitations: All maps, data, and information set forth herein (“Data”), are for illustrative purposes only and are not to be considered an official citation to, or representation of, the Snohomish County Code. Amendments and updates to the Data, together with other applicable County Code provisions, may apply which are not depicted herein. Snohomish County makes no representation or warranty concerning the content, accuracy, currency, completeness or quality of the Data contained herein and expressly disclaims any warranty of merchantability or fitness for any particular purpose. All persons accessing or otherwise using this Data assume all responsibility for use thereof and agree to hold Snohomish County harmless from and against any damages, loss, claim or liability arising out of any error, defect or omission contained within said Data. Washington State Law, RCW 42.56.070(8) prohibits state and local agencies from providing access to lists of individuals intended for use for commercial purposes. A commercial purpose includes any business activity intended to generate profits. By proceeding and accessing this data, you agree and represent that you will not use any lists of individuals, or data from which such lists may be compiled, for any commercial purpose.</SPAN></P></DIV></DIV></DIV>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Snohomish County Code, Table R301.2(1) - Climatic and Geographic Design Criteria:
30.52F.300Table R 301.2(1) – amended.
Minimum Roof Snow Load (PSF) = 25; May increase**
** Footnotes:
a. The roof snow load may be greater than 25 psf depending on site location. Verify the ground snow load with a Plans Examiner prior to design. Ground snow load will vary according to site and shall be applied as the
roof snow load when prescriptive structural design under the International Residential Code is used. The roof snow load may be reduced by a Washington State licensed design professional with a structural analysis.
The roof snow load used in design is not permitted to be less than 25 psf.
Source: https://snohomishcountywa.gov/DocumentCenter/View/10905/Minimum-Submittal-Requirements-for-Structural-Plans?bidId=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- International Code Council (ICC):
Source:
https://codes.iccsafe.org/s/IBC2018/chapter-16-structural-design/IBC2018-Ch16-Sec1608.2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- American Society of Civil Engineers (ASCE):
GUIDES OFFER PRACTICAL HELP WITH LOAD PROVISIONS OF ASCE 7-16:
In civil engineering, design loads are defined as the maximum amount that a structure can handle. ASCE’s standard, Minimum Design Loads and Associated Criteria for Buildings and Other Structures, ASCE/SEI 7-16, describes the means for determining design loads, as well as how to assess load combinations. To assist practicing engineers, ASCE has developed supporting guides that provide detailed descriptions of the wind, seismic, tsunami, snow, and rain load provisions in ASCE 7-16.
Source:
https://www.asce.org/publications-and-news/civil-engineering-source/article/2021/03/02/guides-offer-practical-help-with-load-provisions-of-asce-7-16#:~:text=ASCE's%20standard%2C%20Minimum%20Design%20Loads,how%20to%20assess%20load%20combinations.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- WABO/SEAW - WHITE PAPER, SNOW LOAD REGULATIONS AND ENGINEERING PRACTICES, WASHINGTON STATE, August 2000
- WABO = Washington Association of Building Officials
- SEAW = Structural Engineers Association of Washington
BACKGROUND:
In 1996, the Structural Engineers Association of Washington (SEAW) presented a seminar on snow load design at
three locations in the State. The main purpose of the seminar was to introduce a new edition of the SEAW Snow
Load Analysis for Washington to engineers and regulators. The first edition was published in 1975.
At the late 1996 seminar in SeaTac, an ad-hoc committee of members of the Seattle Chapter of SEAW conducted a
panel discussion of issues related to the seminar, including snow load regulation. Much of the discussion focused on
the lower elevation regions of the Puget Sound area. As a result of the panel discussion, it was recommended that
SEAW and the Washington Association of Building Officials (WABO) attempt to bring more consistency to the
design and review process relating to snow loads. A joint WABO-SEAW Ad Hoc Snow Load Committee (see
Appendix III) was subsequently formed to consider snow load issues and to facilitate consistency of design and
enforcement. CURRENT REGULATIONS:
The Uniform Building Code (UBC) is the adopted model code in the State of Washington. In general, the provisions
of the UBC (1994 Section 1605.4, 1997 Section 1614) require local jurisdictions to establish snow loads used in the
design of structures constructed in the local community.
THE SEAW SNOW LOAD ANALYSIS FOR WASHINGTON:
There have been several publications developed over the last 30 years that address the statistical determination of
snow loads for the design of buildings. These publications include the 1970 National Building Code of Canada, and
manuals by Structural Engineers Associations in Oregon, Colorado, Idaho, and Washington. The latest version of
the SEAW Snow Load Analysis for Washington incorporates many concepts from these previous publications.
Precipitation and snow depth data used in the SEAW Snow Load Analysis for Washington are based on
measurements from the Soil Conservation Service and the National Weather Service. Density relationships have
been developed in the various documents mentioned above. The Snow Load Analysis uses the Rocky Mountain
Conversion Density relationship from a 1986 University of Idaho study. Basically, the relationship provides lower
density at lesser snow depths and higher density at greater snow depths to account for accumulation effects. Snow
depths are based on a Mean Recurrence Interval of 50 years with a Log Pearson Type III distribution.
SEAW’s Snow Load Analysis for Washington provides a method to calculate basic ground snow load throughout the
state from mapped information and elevations. Using the ground snow load and formulas found in UBC Appendix
Chapter 16, one can then calculate the roof snow load, which for most buildings is less than the ground snow load.
The Snow Load Analysis also contains a table in Appendix A of that document that provides a recommended
ground snow load for various jurisdictions (see Appendix I this document). These recommended loads are
appropriately higher than what one could calculate from known elevations and the isolines.
Source:
https://www.seaw.org/codeswhite-papers
https://static1.squarespace.com/static/5c3faa364eddecdc367bedc5/t/5c50814a562fa7296ef9c419/1548779850480/WABO-SEAW+Snow+Load+White+Paper.pdf
https://wabo.memberclicks.net/assets/SEAWPapers/WABO%20SEAW%20WP%208%20Snow%20Loads%20-%20Final%20-%209.14.2020.pdf
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- WABO, WHITE PAPER 8-2021:
I. INTRODUCTION:
The requirements for snow loading are specified in the International Building Code (IBC) and the
accompanying ASCE 7, “Minimum Design Loads for Buildings and Other Structures” which has a table
with Ground Snow Loads for Selected Locations in Washington. The SEAW “Snow Load Analysis for
Washington,” second edition 1995 (SEAW Analysis), provides ground snow loads for additional
locations in Washington as well as a method for determining ground snow loads in locations not listed in
ASCE 7 or Appendix A of the SEAW Analysis.
The SEAW Analysis is based on data from the National Weather Service and the Soil Conservation
Service and provides methods to determine basic ground snow load throughout the state. It has been used
successfully by design professionals including building officials for many years. The first edition was
published in 1975.
WABO/SEAW
Liaison Committee
Washington Association of
Building Officials &
Structural Engineers Association
of Washington
This white paper is intended to coordinate the various codes and standards and to be a guideline for
establishing a uniform approach to determining minimum ground snow loads, pg, and roof snow loads, pf,
snow drift considerations in low-lying areas and other roof design considerations.
Source: https://wabo.memberclicks.net/assets/SEAWPapers/WABO%20SEAW%20WP%208%20Snow%20Loads%20-%20Final%20-%209.14.2020.pdf
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Army Corps of Engineers:
Site-Specific Case Studies for Determining
Ground Snow Loads in the United States
Cold Regions Research
and Engineering Laboratory
James Buska, Alan Greatorex, and Wayne Tobiasson July 2020
https://apps.dtic.mil/sti/pdfs/AD1105146.pdf
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
external
891a2fc69f67382c4319a3159f6fd14cd48f01e6
PDS-GIS Administrator
Snohomish County Planning and Development Services (PDS)
Team Lead/Principal
3000 Rockefeller Ave, MS 604
Everett
WA
98201
PDSGISTeam@snoco.org
US
https://gismaps.snoco.org/Html5Viewer/Index.html?viewer=pdsmapportal
425.388.3311
1) Online downloads available via the Snohomish County Open Data Portal, "https://snohomish-county-open-data-portal-snoco-gis.hub.arcgis.com/";
2) Online MapServer/REST Services available at, https://gis.snoco.org/host/rest/services; and https://gis.snoco.org/img/rest/services;
3) Online PDS Map Portal {Web Map Viewer} , "https://gismaps.snoco.org/Html5Viewer/Index.html?viewer=pdsmapportal"; 4) Request relating to Planning, Future Lane-Use, or Zoning geo-datasets are handled by PDS;
5) All other request for geo-datasets are handled by the Snohomish County Department of Information Technology,
also refer to "https://snohomishcountywa.gov/1402/Maps-GIS".
https://gis.snoco.org/img/rest/services; https://gis.snoco.org/img/rest/services
ArcGIS REST Services
Snohomish County geo-datasets available as ArcGIS REST Services. Viewable via ArcGIS Online Map Viewer. If need be, Esri offers a free account (www.arcgis.com).
True
PDS-GIS Administrator
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>All maps, data, and information set forth herein (“Data”), are for illustrative purposes only and are not to be considered an official citation to, or representation of, the Snohomish County Code. Amendments and updates to the Data, together with other applicable County Code provisions, may apply which are not depicted herein. Snohomish County makes no representation or warranty concerning the content, accuracy, currency, completeness or quality of the Data contained herein and expressly disclaims any warranty of merchantability or fitness for any particular purpose. All persons accessing or otherwise using this Data assume all responsibility for use thereof and agree to hold Snohomish County harmless from and against any damages, loss, claim or liability arising out of any error, defect or omission contained within said Data. Washington State Law, Ch. 42.56 RCW, prohibits state and local agencies from providing access to lists of individuals intended for use for commercial purposes and, thus, no commercial use may be made of any Data comprising lists of individuals contained herein.</SPAN></P></DIV></DIV></DIV>
During the early 2000's, PDS Engineers and Plans Examiners decided on the iso-lines for the Snow Load factor. Further interpolations and vector-to-raster transformations occurred.
[sft_i]
10
EPSG
5.3(9.0.0)
Stretch.Pixel Value
Snow Load
PDS
Table
979
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
Value
Value
Integer
4
10
0
Count_
Count_
Double
8
38
8
Pixel
5370
10492
36.000000
36.000000
16
1
Upper Left
FALSE
LZ77
1
pixel codes
SDR
TRUE
row and column
36.000000
36.000000