| aggCode | ATAG_6-M3338885R0 |
|---|---|
| repCode | AT_UWWTD_2019_1 |
| rptMStateKey | AT |
| uwwBeginLife | 12/31/06 00:00:00 |
| uwwBOD5Perf | P |
| uwwBODDischargeMeasured | 1 |
| uwwCapacity | 2660 |
| uwwCODDischargeMeasured | 3 |
| uwwCode | ATTP_6-M3338885R0 |
| uwwCODPerf | P |
| uwwCollectingSystem | ISCON |
| uwwLatitude | 47.168374743 |
| uwwLoadEnteringUWWTP | 2910 |
| uwwLongitude | 15.817348674 |
| uwwMethodWasteWaterTreated | M |
| uwwName | Pischelsdorf |
| uwwNRemoval | 1 |
| uwwNTotPerf | NR |
| uwwNUTS | AT224 |
| uwwOtherTreatment | 1 |
| uwwPRemoval | 1 |
| uwwPrimaryTreatment | 1 |
| uwwPTotPerf | NR |
| uwwRemarks | The higher load treated in contrast to the UWWTP capacity does not represent a drawback for reaching the required effluent concentrations and/ or required minimum percentage rates of reduction for BOD5 and COD. In case an UWWTP is operated technically sound, it is possible to reach the required treatment performance even in those cases, where the UWWTP – design capacity is temporarily exceeded (e.g. in touristic seasons). |
| uwwSecondaryTreatment | 1 |
| uwwState | 1 |
| uwwTSSPerf | NR |
| uwwWasteWaterTreated | 155125 |
| aucAggCode | ATAG_6-M3338885R0 | aucAggName | Pischelsdorf in der Steiermark |
|---|