08/01/2012
brent.duncan
Other
spike and dip
FIX; noise points can be classified to class 7.
Please Fix; Thanks!
good
Spike and dip combination.  My NAIP imagery does not show anything on the surface like trees.  It appears to be a field on the imagery.
FIX; noise can be classified to class 7.
Spike and dip combination. Because this one is like the previous I believe it is a wet area.
Spike and dip combination.  This is most likely due to saturated soils like the previous two examples.
Spike and dip combination.  No figure is included.  Please refer to previous figures.
Spike and dip combination.  No figure is included.  Please see previous examples.
Spike and dip combination.  No figure included.  Please see previous figures for reference.
Unusual_please_review
Unusual Z-value clusters.  Trees showing up in LiDAR are not showing up in the NAIP imagery.  The trees are approx 44 ft tall and could not have grown this fast since the time of imagery acquisition.
Dip example similar to previous examples.
FIX; noise points can be classified as class 7.
Missing trees on NAIP and dip.  Please refer to previous figures for examples.
08/02/2012
Spike
FIX; noise points can be placed on class 7.
Spike and dip example.  No figure was created.  Please refer to previous examples.
Dips are present in this tile, 15_07294036. No figure is provided.
.  No figure provided.
All low points appear to be on class 7.
OK, no action required
spike
FIX; high points can be classified to class 7.
Extreme spikes and dips.
Spikes and a dip near a house.  Also notice that in the 3D profile that the dip is starting way above the dip z-vaule.
07/27/2012
charlotte.odom
Other HFB
Should there be HFB on this channel/ditch?
Segement is below spec.
HFB-appear- unnecessary 15_07324036 when compared with NAIP.
Intensity shows water in the LiDAR.
HFB needed 1pt5acre_pond missing HFB 15_07324036
FIX; pond can be collected.
One of two 3+ acre pons Missing HFB 15_07264033
Two of two 3+ acre pons Missing HFB 15_07264033
HFB missing - 6 acre_pond_15_07264032
HFB 2-acre pond no HFB 15_07334030
Pond is mostly dry in the LiDAR.
HFB inconsistant use - 1-ac pond 15_07364021 no HFB, but pond next to it 1/3-ac. has HFB
Features do not meet size spec; 1/3 acre pond should not have been collected.
Classification_errors
HFB appear unnecessary on the plowed field.
Completely filled with water in the LiDAR
HFB added to what appears to be a plowed field on 15_07053000
Feature is correctly collected as a pond.
HFB seem unnecessary on this terraced field 15_06993991
Filled with water in the LiDAR.
HFB seem unnecessary on this field 15_069913991
HFB missing on 6-ac pond 15_07123982
FIX; pond should be collected.
HFB  seem unnecessary on these fields 15_07474042
Completely filled with water in the LiDAR.
HFB seen unnecessary on these fields 15_07244033 & 35
Both are filled with water in LiDAR and Google Earth.
HFB missing on 3-ac pond 15_07304033
08/08/2012
Classification_errors HFB
HFB not needed on irrigated field 15_07294039
FIX; feature can be removed.
HFB continuation/connection may be needed 15_07304042 07324042
FIX; feature can be extended.
Please use your judgement
HFB appear unecessary 15_07364044
Pond is legitimate.
HFB seem unnecessary in this area of woods on 15_07474053
This feature is a pond.
HFB continuation appear needed for this waterway on 15_07184023
FIX; segment can be collected.
HFB appear unnecessary 15_07354020 Please evaluate
Feature is a lake; breakline definitely necessary.
HFB seem unnecessary 15_07274020
LiDAR shows open water.
HFB appear to be needed 15_07174011
Area does not require breaklines.
HFB seem unnecessary in this field. 15_07054000
FIX; feature can be deleted.
HFB do not seem necessary on this terraced field 15_06963978
HFB seem unnecessary on this field. 15_07053975
FIX; breakline can be deleted.
HFB seem unnecessary on this flooded field. 15_06913960
Feature is filled with water in LiDAR.
HFB seem unnecessary on this field 15_06853975
FIX; breakline can be removed.
HFB seem unnecessary on this field 15_06843961
HFB seem unnecessary on this field 15_06853958
HFB seem unnecessary on this field 15_06823975
HFB seem unnecessary here 15_06843957
HFB seem unnecessary on this field 15_06873955
HFB seem unnecessary on this field 15_06823954
Should this segment of the creek have HFB? 15_06793949
Not enough water showing in LiDAR to warrant collection.
Should this segment of Long Creek have HFB? 15_06793948-06793949
Should this segment of Long Creek have HFB? 15_06793948
HFB seen unnecessary in this wooded area  15_06813948
HFB seem unnecessary 15_06573847-06583847
Imagery shows dry fields; LiDAR shows water. Judgement call.
HFB seem unnecessary 15_06583849
HFB seem unnecessary 15_06603849
HFB seem unnecessary 15_06603847
08/09/2012
HFB missing on 1-ac pond 15_0744034 next to smaller ponds that HAVE HFB
FIX; pond can be classified.
07/23/2012
Other - HFB need further eval
AR Cache 262-ac need-evaluate Need HFB?
FIX; features should be collected.
AR Cache 8-ac_15_06723960-06733960 need-evaluate for HFB
Feature shows as mostly dry in the LiDAR.
AR Cache 25-ac 15_06763995 need-evaluate for HFB
Feature does not have enough water present or meet size specs for collection.
AR Cache 3-ac 15_06783952  need-evaluate for HFB
This is just a muddy field with small amounts of water.
AR Cache 20-ac 15_06813952 water treatment ponds  need-evaluate for HFB
The two ponds in question are dry in the LiDAR.
AR Cache 15_06793952 water treatment ponds  need-evaluate for HFB
These ponds are dry in the LiDAR and/or not 1 acre in size.
AR Cache 6-ac 15_06793951stream/ponds  need-evaluate for HFB
FIX; breakline could be collected here.
inconsistant-use-of-hfb 15-06763945 has .8-ac pond with HFB, but adjacent 15-06763943 same size pond, does not have HFB
FIX; 0.8 acre pond can be deleted.
AR Cache eval area for HFB 15-06753943
None of these featuers meet size specifications for collection.
AR Cache 15_06703943 eval for HFB needed
AR Cache need eval water or void 15_06723942
AR Cache 2pt5 acre eval for HFB 15_06863940
Not a pond; feature is a freshly paved driveway or small runway.
AR Cache 1pt2 acre pond or void 15_06873937
This is a building, not a pond.
AR Cache 3pt5 acre pond NO HFB 15_06843937
FIX Pond can be collected.
AR Cache 2-acre treatment pond no HFB 15_06703936
These two ponds were dry in the LiDAR and were therefore not collected.
AR Cache 4-acre treatment pond no HFB 15_06703936
AR Cache 2pt5 -acre pond/drainage  no HFB 15_06663934
AR Cache 12-acre pond no HFB 15_06823934-36
07/26/2012
AR Cache HFB does not follow river 12_06523841
Breakline matches the LiDAR.
AR Cache HFB seem misplaced (shoot off in area with no drainage, truncate at tile index, and do not join or cover the rest of the stream.
FIX Breakline can be exteded.
AR_cache_15-0652384_2ac-pond-no-HFB
Pond does not measure greater than 2 acres in the LiDAR.
HFB appears truncated and incomplete
HFB none on approx. 2 acre pond 15_06523846
Waterway snaking through woods seems large enough to need HFB?
Channel is not defined enough to collect; looks to be a swamp.
HFB appear needed here 15_06963991
Muddy, we area; no breakline required.
Should this area have HFB? 15_07124011
HAS HFB,make sure not simply a LAS data void 15_07124011
Correctly shown as a pond
HFB seem unnecessary. Please evaluate 07064009, 07084009, 07064008
FIX; Breaklines can be removed
HFB seem unnecessary in this field. 15_07084009
HFB seem unnecessary in this field. 15_07084008
HFB seem unnecessary 15_06974005
HFB seem unnecessary . Please evaluate 15_07123999
Breakline is collected on a valid pond.
HFB seem unnecessary, please evaluate 15_07023985
Breaklines collected on valid features.
Other - HFB missing
HFB missing - 5.4 ac standing water
Muddy, wet field does not warrant collection.
AR Cache 4-ac water-treatment-pond_no-HFB
08/16/2012
HFB seems inappropriate here. Please Evaluate 15_07384029
Feature is a pond and requires a breakline.
Should HFB have been continued here on 15_07414027-15_07424027? (appears tree canopy disguises water for part of water course)
These channels are dry and well under spec.
Should HFB been continued here on the 'South Fork'?
HFB seem unnecessary here. Please Evaluate 15_07184012
Area shows standing water.
HFB seem unnecessary here. Please Evaluate 15_07054008
LiDAR shows ponded water here.
HFB seem unnecessary/inappropriate here. Please Evaluate 15_07064008
HFB seem unnecessary/inappropriate here. Please Evaluate 15_07084008
HFB seem unnecessary/inappropriate here. Please Evaluate 15_07034005
Pond features are collected correctly.
HFB seem unnecessary/inappropriate here. Please Evaluate 15_07004005-0704003
Feature is filled with water in the LiDAR.
Features are collected accurately.
It seems that HFB would be more appropriate continuing on this drainage rather than where currently placed.  Please Evaluate 15_07004005-0704003
AR_Cache_2011 BeaverDamDitch is shown on DRGs and ArWaterOrg MajorStreamsDRG_does not have HFB. Please evaluate.
FIX?; Can be collected but does not meet USGS size specs.
Data Void Concern
Possible Data VOID. DLG shows RIDGE  where this 1-ac area has  HFB on 15_07064011. Please Evaluate
Not a void; standing water
08/17/2012
Cache_Lot3_HFB_Dbl_line_Drain_Island. 15_06963991 HFB needed here?
Island collected correctly.
Cache_Lot2_HFB_Dbl_line_Drain_Island. 15_06823969 HFB needed here?
AR Cache 2011 called Double Line Drain Island 15_06963991 please evaluate
AR Cache 2011 called Double Line Drain Island 15_06823969 please evaluate
AR Cache 2011 called Double Line Drain Island 15_06963993-91 please evaluate
AR_Cache_2011 shows on NED_DRG_AR_Water_Org_no HFB please evaluate
FIX; breakline can be extended.