These views will exist in CTS_DATA. We are providing them for GIS integration as an ‘off-the-shelf’ solution. If you require different definitions or views, please contact Linko Technology at info@linkotechnology.com.
1) LinkoFOG FSE location table-view for GIS use
This SQL view is intended to be used by GIS for creating/updating a GIS Food Service Establishment (FSE) list with the currently active FSE locations. The view columns are listed below, with the native field name from the Linko table along with the field name that appears in LinkoFOG screens. Only Active (ActivePermit = True and PermitType = FOG) will appear in the view.
v_GIS_FSE_Locations – view of active FSE locations with site address and meta data
|
v_GIS_FSE_Locations –
populated by LinkoFOG (CTS_DATA SQL database) |
|
||
|
CTS_DATA Field |
Screen Reference |
Description |
ViewField |
|
t_PermitAccounts:PermitID |
n/a |
Auto-number ID for FSE, invisible to users |
FSE_ID |
|
t_PermitAccounts:PermitNo |
Facility No |
User assigned alphanumeric identifier for the FSE |
FSE_No |
|
t_PermitAccounts:Permittee |
Name |
user assigned name for the FSE |
FSE_Name |
|
t_Site:SiteAddr1 |
Address |
user assigned location Address line 1 |
FSE_AddrLine1 |
|
t_Site:SiteAddr2 |
Address 2 |
User assigned location Address line 2 |
FSE_AddrLine2 |
|
t_Site:SiteCity |
City |
User assigned City |
FSE_City |
|
t_Site:SiteState |
State |
User assigned State |
FSE_State |
|
t_Site:SiteZipCode |
Zip Code |
User assigned Zip Code |
FSE_Zip |
|
t_PermitAccounts.SewerAcctNo |
Sewer # |
Optional – User assigned billing account number |
FSE_AcctNo |
|
t_PermitOps.ClassCode |
Class Code |
Optional – User assigned FOG Program Identifier classification |
FSE_Class |
|
t_PermitOps.SecondClass |
Secondary Class |
Optional - more detailed class code value |
FSE_SecondaryClass |
|
t_PermitBaseSched.EffectiveDate |
Effective Date |
Optional – effective date of permit |
FSE_EffectiveDate |
|
t_PermitBaseSched.ExpirationDate |
Permit Event Due Date |
Optional – expiration date of permit |
FSE_ExpirationDate |
|
t_PermitBaseSched.LastInsp |
Inspection Event Complete Date |
Optional - Last Inspection Date |
FSE_LastInspection |
|
t_PermitBaseSched.NextInsp |
Inspection Event Due Date |
Optional - Pending Inspection Date |
FSE_NextInspection |
|
t_PermitBaseSched.LastPumpOut |
Pump Event Complete Date |
Optional - Last Pump Out Date |
FSE_LastPumpOut |
|
t_PermitBaseSched.NextPumpOut |
Pump Event Due Date |
Optional - Pending Pump Out Date |
FSE_NextPumpOut |
|
t_PermitAccounts:Permittee (via t_PermitAccounts:PumperID) |
Pumper |
Optional - Name of Hauling Company assigned to FSE |
FSE_HaulerCompany |
|
t_PermitOps.ActivePermit |
Active |
Optional – Is the FSE actively being regulated |
FSE_Active |
2)LinkoFOG FSE Extractors table-view for GIS use
v_GIS_FSE_Extractors view of active FSE grease abatement devices (GAD) (e.g. interceptors or traps) there could be zero to many extractors per FSE
|
v_GIS_FSE_Extractors –
populated by LinkoFOG (CTS_DATA SQL database) |
|
||
|
CTS_DATA Field |
Screen Reference |
Description |
View_Field |
|
t_PermitAccounts:PermitID |
n/a |
FK to FSE Locations |
FSE_ID |
|
tu_Extractors.ExtractorNo |
n/a |
Auto-number ID for extractor, invisible to users |
GAD_ID |
|
tu_Extractors.ExtractorID |
Extractor ID |
user assigned name for the FSE |
GAD_No |
|
tu_Extractors.ExtractorName |
Extractor Type |
Optional – type of device |
GAD_Type |
|
tu_Extractors.Manufacturer |
Manufacturer |
Optional – manufacturer of device |
GAD_MFG |
|
tu_Extractors.TrapSize |
Trap Size |
Optional – capacity of device |
GAD_Size |
|
tu_Extractors.Comments |
Comments |
Optional – comments relative to a device |
GAD_Comments |
|
tu_Extractors.CleaningFreq |
Cleaning Freq |
Optional – cleaning frequency |
GAD_CleanFreq |
|
tu_Extractors.TrapHeight |
Trap Depth |
Optional – depth of a device |
GAD_Depth |
|
tu_Extractors.TrapSizeUnits |
Units |
Optional – units relative to capacity, required if capacity is populated |
GAD_SizeUnit |
|
tu_Extractors.TrapHeightUnits |
Units |
Optional – units relative to depth, required if depth is populated |
GAD_DepthUnit |
|
tu_Extractors.ExtractorDesc |
Extractor Description |
Optional – location description or general description of a device |
GAD_Desc |
3) LinkoFOG FSE Violations table-view for GIS use
v_GIS_FSE_Violations view of historical violations relative to an FSE there could be zero to many violations per FSE
|
v_GIS_FSE_Violations – populated by LinkoFOG (CTS_DATA SQL database) |
|
||
|
CTS_DATA Field |
Screen Reference |
Description |
View_Field |
|
t_PermitAccounts:PermitID |
n/a |
FK to FSE Locations |
FSE_ID |
|
t_ViolEvents.EventID |
n/a |
Auto-number ID for violation, invisible to users |
Viol_ID |
|
tu_EventType.EventTypeAbbrv |
Violation Type |
Short Description of Violation Type |
Viol_Type |
|
tu_EventType.EventTypeDesc |
n/a |
Long Description of Violation Type |
Viol_Type_Desc |
|
t_Events.EventDesc |
Violation Description |
Optional – Description of the violation |
Viol_Desc |
|
t_Events.EventComments |
Internal Comments |
Optional – Internal Comments |
Viol_Comments |
|
t_ViolEvents.NCDate |
Date of NC |
Violation Date |
Viol_Date |
|
t_ViolEvents.MaxEnfDate |
Enforce Date |
Date of last enforcement action relative to the violation |
Viol_Enf_Date |
|
t_ViolEvents.CompleteDate |
In Compliance |
Date of violation was back in compliance |
Viol_InCompl_Date |
4) LinkoCTS IU location table-view for GIS use
This SQL view is intended to be used by GIS for creating/updating a GIS Industrial User list with the currently active IU locations. The view columns are listed below, with the native field name from the Linko table along with the field name that appears in LinkoCTS screens. Only Active (ActivePermit = True and PermitType = PTX) will appear in the view.
v_GIS_IU_Locations – view of IUlocations with site address and meta data
|
v_GIS_IU_Locations –
populated by LinkoCTS (CTS_DATA SQL
database) |
|
||
|
CTS_DATA Field |
Screen Reference |
Description |
ViewField |
|
t_PermitAccounts:PermitID |
n/a |
Auto-number ID for IU, invisible to users |
IU_ID |
|
t_PermitAccounts:PermitNo |
Facility No |
User assigned alphanumeric identifier for the FSE |
IU_No |
|
t_PermitAccounts:Permittee |
Name |
user assigned name for the FSE |
IU_Name |
|
t_Site:SiteAddr1 |
Address |
user assigned location Address line 1 |
IU_AddrLine1 |
|
t_Site:SiteAddr2 |
Address 2 |
User assigned location Address line 2 |
IU_AddrLine2 |
|
t_Site:SiteCity |
City |
User assigned City |
IU_City |
|
t_Site:SiteState |
State |
User assigned State |
IU_State |
|
t_Site:SiteZipCode |
Zip Code |
User assigned Zip Code |
IU_Zip |
|
t_PermitAccounts.SewerAcctNo |
Sewer # |
Optional – User assigned billing account number |
IU_AcctNo |
|
t_PermitAccounts.WaterAcctNo |
Meter # |
Optional – User assigned billing meter number |
IU_MeterNo |
|
t_PermitAccounts.DailyFlow |
Daily Flow |
Optional – Industry average daily flow |
IU_DailyFlow |
|
t_PermitOps.ClassCode |
Class Code |
Optional – User assigned IU Program Identifier classification |
IU_Class |
|
t_PermitOps.SecondClass |
Secondary Class |
Optional - more detailed class code value |
IU_SecondaryClass |
|
t_PermitBaseSched.EffectiveDate |
Effective Date |
Optional – effective date of permit |
IU_EffectiveDate |
|
t_PermitBaseSched.ExpirationDate |
Permit Event Due Date |
Optional – expiration date of permit |
IU_ExpirationDate |
|
t_PermitBaseSched.LastInsp |
Inspection Event Complete Date |
Optional - Last Inspection Date |
IU_LastInspection |
|
t_PermitBaseSched.NextInsp |
Inspection Event Due Date |
Optional - Pending Inspection Date |
IU_NextInspection |
|
t_PermitAccounts.TrunkLine |
Trunk Line |
Optional – Trunk Line of IU discharge |
IU_ TrunkLine |
|
t_PermitAccounts.ReceivingPlant |
Receiving Plant |
Optional – Receiving plant of IU discharge |
IU_ReceivingPlant |
|
t_PermitOps.ActivePermit |
Active Industry |
Optional – Is the IU actively being regulated |
IU_Active |
5) LinkoCTS IU Monitoring Point table-view for GIS use
v_GIS_IU_MonitoringPoints view of IU monitoring points; there could be zero to many monitoring points per IU
|
v_GIS_IU_ MonitoringPoints – populated by LinkoCTS (CTS_DATA SQL database) |
|
||
|
CTS_DATA Field |
Screen Reference |
Description |
View_Field |
|
t_PermitAccounts:PermitID |
n/a |
FK to IU Locations |
IU_ID |
|
t_MonPoints.MonPointID |
n/a |
Auto-number ID for monitoring point, invisible to users |
MP_ID |
|
t_MonPoints.MonPointAbbrv |
Monitoring Point |
user assigned abbrv. for the Monitoring Point |
MP_Abbrv |
|
t_MonPoints.MonPointDesc |
General Description |
Optional – Description of Monitoring Point |
MP_Desc |
|
t_MonPoints.TreatSysType |
Treatment System Type |
Optional – type of treatment system in use |
MP_TreatSysType |
|
t_MonPoints.WasteWaterType |
WasteWater Type |
Optional – type of wastewater discharged |
MP_WWType |
|
t_MonPoints.SampleNotes |
Sampling Notes |
Optional – notes to observe during sampling |
MP_SampleNotes |
|
t_MonPoints.SafetyNotes |
Safety Notes |
Optional – safety notes about monitoring point |
MP_SafetyNotes |
6) LinkoCTS IU Violations table-view for GIS use
v_GIS_IU_Violations view of historical violations relative to an IU; there could be zero to many violations per IU
|
v_GIS_IU_Violations – populated by LinkoCTS (CTS_DATA SQL database) |
|
||
|
CTS_DATA Field |
Screen Reference |
Description |
View_Field |
|
t_PermitAccounts:PermitID |
n/a |
FK to IU Locations |
FSE_ID |
|
t_ViolEvents.EventID |
n/a |
Auto-number ID for violation, invisible to users |
Viol_ID |
|
tu_EventType.EventTypeAbbrv |
Violation Type |
Short Description of Violation Type |
Viol_Type |
|
tu_EventType.EventTypeDesc |
n/a |
Long Description of Violation Type |
Viol_Type_Desc |
|
t_Events.EventDesc |
Violation Description |
Optional – Description of the violation |
Viol_Desc |
|
t_Events.EventComments |
Internal Comments |
Optional – Internal Comments |
Viol_Comments |
|
t_ViolEvents.NCDate |
Date of NC |
Violation Date |
Viol_Date |
|
t_ViolEvents.MaxEnfDate |
Enforce Date |
Date of last enforcement action relative to the violation |
Viol_Enf_Date |
|
t_ViolEvents.CompleteDate |
In Compliance |
Date of violation was back in compliance |
Viol_InCompl_Date |
Related Topics