1. Creating Non-Managed Decoded Soils Layer Companywide
Credit to Dave Zoufal for initial workflow and query with Microsoft Access
Process:
1. ConvertDave’sQueryfromAccessto utilize inSQL
2. Isolate the necessaryfieldsinqueryresult
3. Exportquery resultfromSQL to Access
a. Initiallywouldnotworkcopy/ paste queryresults
b. ExportedresultsasCSV intoexcel
4. BringCompanySoilsLayerintoArcGIS
5. BringQueryResultsintoArcGIS
6. Jointable tolayer
7. Isolate byOrg or Org groupsfrom soil legendIDindatabase
8. Exportby Org or area
9. Addreginal resultstoregional SharedfoldersonQdrive
Soils Layer FMS (Workaround)
Dave’sWork around:
 separate Floridaoutof the SoilslayerinFMS
 builta queryinAccess
 linkedthe table tothe layerinArc
 createdthe FMSSoilsInfoshapefile
 createda layerfile inFMS thatshowsSMG/SMGDesc as a theme.
Since soilsisa fairlystaticlayer(atleastuntil the holesare filled),thisshouldbe goodforalongtime.

2. Questions:
1. How didyouseparate Floridaoutof Soilslayer in FMS (nocliptool)
2. What was yourquery(Idon’tknow access but I wouldtryitin SQL)
3. Didyou use a simple “Join”inArcto add the table to the Floridashapefile
Answers:
1. I justusedthe Lasso selecttool inFMS and copiedthemtoa new layer. Nogood wayto select
inthe layersince there isnofieldrelatedtoorg. There isa fieldinthe dbo_vtMasterSoilCode
table that I usedinthe qry below thatlimitsthe qryresultstoFlorida/Chattahoochee orgs –
fieldissoillegendID. The SoilLegendIDhasitsownvt table calleddbo_vtSoilLegend,thisID has
orgs grouped. If youwere goingto dosomethingforthe entire soil layeryouwouldneedto
remove the 12 criteria(see highlightedpartof code). Ionlydecodedacouple of fields(most
used) – coulddo othersif theyare needed.
2. Here is the SQL language forthe Accessqry.
SELECT dbo_Soil.SoilID,dbo_vtMasterSoilCode.MasterSoilCodeID,
dbo_vtMasterSoilCode.SoilCode,dbo_vtMasterSoilCode.SoilLegendID,
dbo_vtSoilLegend.SoilLegendCode,dbo_vtSoilLegend.SoilLegendDesc,
dbo_vtSoilGroup.SoilGroupCode,dbo_vtSoilGroup.SoilGroupDesc,
dbo_vtMasterSoilCode.SoilGroupID,dbo_vtDrainageClass.DrainageClassDesc,
dbo_vtMasterSoilCode.DrainageClassID,dbo_vtMasterSoilCode.SubSoilDepthID,
dbo_vtMasterSoilCode.SurfaceTextureID,dbo_vtMasterSoilCode.SurfaceGravelID,
dbo_vtMasterSoilCode.SubSurfaceTextureID,dbo_vtMasterSoilCode.SubSurfaceGravelID,
dbo_vtMasterSoilCode.ProductivityClassID,dbo_vtMasterSoilCode.LandscapePositionID,
dbo_vtMasterSoilCode.GeologyID,dbo_vtMasterSoilCode.SoilModifier1ID,
dbo_vtMasterSoilCode.SoilModifier2ID,dbo_vtMasterSoilCode.SoilModifier3ID,
dbo_vtMasterSoilCode.SoilManagementGroupID,
dbo_vtMasterSoilCode.HarvestAreaErosionHazardID,
dbo_vtMasterSoilCode.TrailsErosionHazardID,dbo_vtMasterSoilCode.RuttingHazardID,
dbo_vtMasterSoilCode.HarvestOperabilityHazardID,
dbo_vtMasterSoilCode.LogDeckLandingHazardID,dbo_vtMasterSoilCode.HaulRoadHazardID,
dbo_vtMasterSoilCode.RoadConstructionHazardID,
dbo_vtMasterSoilCode.RoadFillMaterialHazardID,
dbo_vtMasterSoilCode.MechSitePrepSurfaceHazardID,
dbo_vtMasterSoilCode.MechSitePrepSubSurfaceHazardID,
dbo_vtMasterSoilCode.MechPlantingHazardID,dbo_vtMasterSoilCode.BurningHazardID,
dbo_vtMasterSoilCode.SeedlingMortalityHazardIDINTOFloridaSoilInfo
FROM(((dbo_Soil INNERJOIN dbo_vtMasterSoilCodeON dbo_Soil.MasterSoilCodeID=
dbo_vtMasterSoilCode.MasterSoilCodeID) INNERJOIN dbo_vtSoilLegendON
dbo_vtMasterSoilCode.SoilLegendID=dbo_vtSoilLegend.SoilLegendID) INNERJOIN
dbo_vtSoilGroupON (dbo_vtMasterSoilCode.SoilLegendID=dbo_vtSoilGroup.SoilLegendID)
AND(dbo_vtMasterSoilCode.SoilGroupID=dbo_vtSoilGroup.SoilGroupID))INNERJOIN
dbo_vtDrainageClassON (dbo_vtMasterSoilCode.SoilLegendID=
dbo_vtDrainageClass.SoilLegendID) AND(dbo_vtMasterSoilCode.DrainageClassID=
dbo_vtDrainageClass.DrainageClassID)
WHERE (((dbo_vtMasterSoilCode.SoilLegendID)=12));_+
3. Yes usedthe joinonthe SoilIDfield.

3. Query convertedfor SQL Server:
SELECT Soil.SoilID, vtMasterSoilCode.MasterSoilCodeID, vtMasterSoilCode.SoilCode,
vtMasterSoilCode.SoilLegendID, vtSoilLegend.SoilLegendCode, vtSoilLegend.SoilLegendDesc,
vtSoilGroup.SoilGroupCode, vtSoilGroup.SoilGroupDesc, vtMasterSoilCode.SoilGroupID,
vtDrainageClass.DrainageClassDesc, vtMasterSoilCode.DrainageClassID,
vtMasterSoilCode.SubSoilDepthID, vtMasterSoilCode.SurfaceTextureID,
vtMasterSoilCode.SurfaceGravelID, vtMasterSoilCode.SubSurfaceTextureID,
vtMasterSoilCode.SubSurfaceGravelID, vtMasterSoilCode.ProductivityClassID,
vtMasterSoilCode.LandscapePositionID, vtMasterSoilCode.GeologyID,
vtMasterSoilCode.SoilModifier1ID, vtMasterSoilCode.SoilModifier2ID,
vtMasterSoilCode.SoilModifier3ID, vtMasterSoilCode.SoilManagementGroupID,
vtMasterSoilCode.HarvestAreaErosionHazardID, vtMasterSoilCode.TrailsErosionHazardID,
vtMasterSoilCode.RuttingHazardID, vtMasterSoilCode.HarvestOperabilityHazardID,
vtMasterSoilCode.LogDeckLandingHazardID, vtMasterSoilCode.HaulRoadHazardID,
vtMasterSoilCode.RoadConstructionHazardID, vtMasterSoilCode.RoadFillMaterialHazardID,
vtMasterSoilCode.MechSitePrepSurfaceHazardID,
vtMasterSoilCode.MechSitePrepSubSurfaceHazardID, vtMasterSoilCode.MechPlantingHazardID,
vtMasterSoilCode.BurningHazardID, vtMasterSoilCode.SeedlingMortalityHazardID
FROM (((Soil INNER JOIN vtMasterSoilCode ON Soil.MasterSoilCodeID =
vtMasterSoilCode.MasterSoilCodeID) INNER JOIN vtSoilLegend ON
vtMasterSoilCode.SoilLegendID = vtSoilLegend.SoilLegendID) INNER JOIN vtSoilGroup ON
(vtMasterSoilCode.SoilLegendID = vtSoilGroup.SoilLegendID) AND
(vtMasterSoilCode.SoilGroupID = vtSoilGroup.SoilGroupID)) INNER JOIN vtDrainageClass ON
(vtMasterSoilCode.SoilLegendID = vtDrainageClass.SoilLegendID) AND
(vtMasterSoilCode.DrainageClassID = vtDrainageClass.DrainageClassID)
Non Managed Decoded Soils
1. File AddOtherData inFMS and navigate tosharedfolderinyourregionandselectthe Shapefile
to add to FMS

4. 2. Once the layeris addedtothe TOC,openthe Layer Properties>Symbologytab
a. Here you can theme the layerbasedoncategories

5. b. Or importthe layersymbology“FMSSoilsInfo”fromthe Q drive