TUW Hundstage #2 | TU Wien Skip to content (Accesskey: 1) Skip to navigation (Accesskey: 2) Skip to search (Accesskey: 7) Close page navigation Login DE Open page navigation Search Start search TU Wien Overview News About TU Wien Organisation Corona A university for all Working at TUW TUW Community Campus Contact Studies Overview News Studies Admission Studying at TU Wien Student support services Teaching at TU Wien Continuing Education Helping Ukraine International Research Overview News Events Profile Facilities Successes TUW Doctoral School RTI support Funding opportunities Databases Partnerships Overview Industry Relations Technology Offers Inventions, Patents, Commercialization Start-ups Center for Technology and Society , opens an external URL in a new window University Alliances EULIST TU Austria , opens an external URL in a new window Fundraising Services Overview Newsletter Events Media Library Campus services Digitalisation IT-Services TUW-Jobportal , opens an external URL in a new window TISS , opens an external URL in a new window TUW alumni club , opens an external URL in a new window TUW Career Center , opens an external URL in a new window Continuing Education Internal News articles TU Wien / News / News articles / 29. July 2021 TUW Hundstage #2 An alternative to industrial water treatment. The mobile desalination plant is cost-effective and conserves resources. Enlarge image mobile Desalination Unit https://www.tuwien.at/tu-wien/aktuelles/news/news/mit-dem-fahrrad-zum-trinkwasser, opens an external URL in a new window Worldwide, 2 billion people have no or insufficient access to drinking water. Although saltwater is already treated in industrial plants in areas with low freshwater levels, this process is cost-intensive and resource-intensive. As a result, only a fraction of those with no or limited access to drinking water have benefited from this technology to date. In order to make salt and brackish water treatment more efficient, Prof. Dr. Margit Gföhler and Prof. Dr. Michael Harasek from the Vienna University of Technology developed a mobile desalination plant that is operated entirely without electricity. Technically, the scientists use the principle of reverse osmosis, i.e. the pressure of natural osmosis is reversed and the salt is removed from the salt water. Combined with a piston pump with pressure energy recovery, which is operated by a bicycle pedal drive, seawater or brackish water can finally be treated. One of these mobile desalination plants is already sufficient to cover the daily water needs of a family. Furthermore, the low maintenance costs provide financial relief for the users. Skip to footer TU Wien News About TU Wien Organisation Sustainability Corona A university for all Working at TUW TUW Community Campus Contact Studies News Studies Admission Studying at TU Wien Student support services Teaching at TU Wien Continuing Education Helping Ukraine International Research News Events Profile Facilities Successes Networks TUW Doctoral School RTI support Funding opportunities Databases Partnerships Industry Relations Technology Offers Inventions, Patents, Commercialization Start-ups Center for Technology and Society, opens an external URL in a new window University Alliances EULIST TU Austria, opens an external URL in a new window Fundraising Services Newsletter Events Media Library Campus services Digitalisation IT-Services TUW-Jobportal, opens an external URL in a new window TISS, opens an external URL in a new window TUW alumni club, opens an external URL in a new window TUW Career Center, opens an external URL in a new window Continuing Education Internal © TU Wien # 1502 Legal notice Accessibility Declaration Data Protection Declaration (PDF) Cookie settings Top menu level TU Wien Back: list subpages of parent page "News" Back to: News News articles Facebook Twitter LinkedIn YouTube Instagram issuu About Cookies and other techniques × Our website uses cookies an integrates content from third-party providers to ensure you get the best experience on our website, for analytical purposes, to provide social media features, and for targeted advertising. This it is necessary in order to pass information on to respective service providers. If you would like additional information about cookies and content from third-party providers on this website, please see our Data protection declaration. Settings Mandatory Allow mandatory cookies These cookies are required to help our website run smoothly. Name Purpose Lifetime Type Provider CookieConsent Saves your settings for the use of cookies on this website. 1 year HTML Homepage TU Wien SimpleSAML This is needed to distinguish between the sessions of the logged-in users. session HTTP Login TU Wien SimpleSAMLAuthToken This is needed to distinguish between the sessions of the logged-in users. session HTTP Login TU Wien fe_typo_user Is needed so that in case of a Typo3 frontend login the session ID is recognized to grant access to protected areas. session HTTP Homepage TU Wien staticfilecache Is needed to optimize the delivery time of the website. session HTTP Homepage TU Wien Web statistics Allow statistic cookies These cookies help us to continuously improve our services and adapt our website to your needs. We statistically evaluate the pseudonymized data collected from our website. Name Purpose Lifetime Type Provider _pk_id Used to store a few details about the user such as the unique visitor ID. 13 months HTML Matomo TU Wien _pk_ref Is used to store the information of the users home website. 6 months HTML Matomo TU Wien _pk_ses Is needed to store temporary data of the visit. 30 minutes HTML Matomo TU Wien nmstat Is used to record the behaviour on the website. It is used to collect statistics about website usage, such as when the visitor last visited the website. The cookie does not contain any personal data and is only used for website analysis. 1000 days HTML Siteimprove siteimproveses Is used to track the sequence of pages that a visitor views during his/her visit to the website. The cookie does not contain any personal data and is used solely for website analysis. session HTTP Siteimprove AWSELB Always occurs in pairs with siteimproveses (for load balancing on the provider server) session HTTP Siteimprove Marketing Allow marketing cookies With the help of these cookies and third-party content we strive to improve our offer for our users. By means of anonymized data of website users we can optimize the user flow. This enables us to improve ads and website content. Name Purpose Lifetime Type Provider _ga Is needed to distinguish the sessions of the users from each other. persistent HTTP Google Analytics _gali Is needed to determine which links are clicked on a page. expires immediately HTTP Google Analytics _gat This is a function-related cookie, whose tasks may differ. 2 years HTTP Google Analytics _gid Is needed to distinguish users and create statistics. 24 hours HTTP Google Analytics _gads Required to enable websites to display advertising from Google, including personalized advertising. 13 months HTTP Google Analytics _gac_ Required by advertisers to measure user activity and the performance of their advertising campaigns. 90 days HTTP Google Analytics _gcl_ Required by advertisers to determine how often users who click on their ads end up taking an action on their website. 90 days HTTP Google Analytics _gcl_au Contains a randomly generated user ID. 90 days HTTP Google _gcl_aw Is set when users click on a Google ad on the website and contains information about which ad was clicked. 90 days HTTP Google __utma Is used to record visits and visitors. 2 years HTTP Google Analytics __utmb Is used to detect new visits. 30 minutes HTTP Google Analytics __utmc Is used in connection with __utmb to determine whether it is a new (recent) visit. session HTTP Google Analytics __utmd Is used to store and track visitor journeys through the site and classifies them into groups (marketing/tracking). 1 second HTTP Google Analytics __utmt Is needed to limit the query rate on Google Analytics. 10 minutes HTTP Google Analytics __utmz Is needed to determine from which source/campaign visitors come. 6 months HTTP Google Analytics __utmvc Is needed to collect information about user behavior on multiple websites. This information is used to optimize the relevance of advertising on the website. 24 hours HTTP Google AdSense utm_source Is needed to tag URLs with parameters to identify the campaigns that forward traffic. expires immediately HTTP Google Analytics __utm.gif Is needed to save browser details. session HTTP Google Analytics gtag Is needed to perform remarketing. 30 days HTTP Google AdSense id Is needed to perform remarketing. 2 years HTTP Google AdWords 1P_JAR Is needed to optimize advertising, provide ads that are relevant to users, improve campaign performance reports, or prevent users from seeing the same ads more than once. 2 years HTTP Google AID Is needed to activate targeted advertising. 2 years HTTP Google Analytics ANID Is needed to display Google ads on non-Google websites. 2 years HTTP Google AdSense APISID Unknown functionality 2 years HTTP Google Ads Optimization AR Is needed to profile visitors' interests and display relevant ads on other websites. This cookie works by uniquely identifying your browser and device. 2 years HTTP Google AdSense CONSENT Is needed to store the preferences of visitors and personalize advertising. persistent HTTP Google DSID Is needed by DoubleClick for advertising displayed in various places on the web and used to store the preferences of users. 2 years HTTP Doubleclick DV Is needed to store user preferences and other information. This includes, in particular, the preferred language, the number of search results to be displayed on the page, and the decision whether or not to activate the Google SafeSearch filter. 2 years HTTP Google HSID Contains the Google account ID and the last login time of the user. 2 years HTTP Google IDE Is needed by DoubleClick to record and report the actions of users on the website after viewing or clicking on one of the provider's ads, with the purpose of measuring the effectiveness of an advertisement and displaying targeted advertisements to users. 2 years HTTP Doubleclick LOGIN_INFO Is used to store the credentials of users of Google services. 2 years HTTP Google NID Is used to store information about user settings. 6 months HTTP Google OTZ Is needed to link activities of visitors with other devices that are previously logged in via the Google account. In this way, advertising is tailored to different devices. 1 month HTTP Google RUL Is needed by DoubleClick to determine whether advertising has been displayed correctly in order to make marketing activities more efficient. 1 year HTTP Doubleclick SAPISID Is needed by YouTube to store user settings and to calculate user bandwidth. persistent HTTP Google SEARCH_SAMESITE Enables servers to mitigate the risk of CSRF and information leakage attacks by specifying that a particular cookie may only be sent on requests originating from the same registerable domain. 6 months HTTP Google SID Contains the Google account ID and the last login time of the user. 2 years HTTP Google SIDCC Is needed to store information about user settings and information for Google Maps. 3 months HTTP Google SSID Is needed to collect visitor information for videos hosted by YouTube on Google Maps integrated maps. persistent HTTP Google __SECURE-1PAPISID Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP Google __SECURE-1PSID Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP Google __SECURE-3PAPISID Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP Google __SECURE-3PSID Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP Google __SECURE-3PSIDCC Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP Google __SECURE-APISID Is needed to profile the interests of website visitors in order to display relevant and personalized advertising through retargeting. 8 months HTTP Google __SECURE-HSID Is needed to secure digitally signed and encrypted data from the unique Google ID and to store the last login time that Google uses to identify visitors, prevent fraudulent use of login data, and protect visitor data from unauthorized parties. This may also be used for targeting purposes to display relevant and personalized advertising content. 8 months HTTP Google __SECURE-SSID Is needed to store information about how visitors use the site and about the ads they may have seen before visiting the site. Also used to customize ads on Google domains. 8 months HTTP Google test_cookie Is set as a test to check whether the browser allows cookies to be set. Does not contain any identification features. 15 minutes HTTP Google VISITOR_INFO1_LIVE Is needed by YouTube to store user settings and to calculate user bandwidth. 6 months HTTP Youtube facebook Is used to Enable ad delivery or retargeting 90 days HTTP Meta (Facebook) __fb_chat_plugin Is needed to store and track interactions (marketing/tracking). persistent HTTP Meta (Facebook) _js_datr Is needed to save user settings. 2 years HTTP Meta (Facebook) _fbc Is needed to save the last visit (marketing/tracking). 2 years HTTP Meta (Facebook) fbm Is needed to store account data (marketing/tracking). 1 year HTTP Meta (Facebook) xs Is needed to store a unique session ID (marketing/tracking). 1 year HTTP Meta (Facebook) wd Is needed to log the screen resolution. 1 week HTTP Meta (Facebook) fr Is needed to serve ads and measure and improve their relevance. 3 months HTTP Meta (Facebook) act Is needed to store logged in users (marketing/tracking). 90 days HTTP Meta (Facebook) _fbp Is needed to store and track visits to various websites (marketing/tracking). 3 months HTTP Meta (Facebook) datr Is needed to identify the browser for security and website integrity purposes, including account recovery and identification of potentially compromised accounts. 2 years HTTP Meta (Facebook) dpr Is used for analysis purposes. Technical parameters are logged (e.g. aspect ratio and dimensions of the screen) so that Facebook apps can be displayed correctly. 1 week HTTP Meta (Facebook) sb Is needed to store browser details and security information of the Facebook account. 2 years HTTP Meta (Facebook) dbln Is needed to store browser details and security information of the Facebook account. 2 years HTTP Meta (Facebook) spin Is needed for promotional purposes and social campaign reporting. session HTTP Meta (Facebook) presence Contains the "chat" status of logged in users. 1 month HTTP Meta (Facebook) cppo Is needed for statistical purposes. 90 days HTTP Meta (Facebook) locale Is needed to save the language settings. session HTTP Meta (Facebook) pl Required for Facebook Pixel. 2 years HTTP Meta (Facebook) lu Required for Facebook Pixel. 2 years HTTP Meta (Facebook) c_user Required for Facebook Pixel. 3 months HTTP Meta (Facebook) bcookie Is needed to store browser data (marketing/tracking). 2 years HTTP LinkedIn li_oatml Is needed to identify LinkedIn members outside of LinkedIn for advertising and analytics purposes. 1 month HTTP LinkedIn BizographicsOptOut Is needed to save privacy settings. 10 years HTTP LinkedIn li_sugr Is needed to store browser data (marketing/tracking). 3 months HTTP LinkedIn UserMatchHistory Is needed to provide advertising or retargeting (marketing/tracking). 30 days HTTP LinkedIn linkedin_oauth_ Is needed to provide cross-page functionality. session HTTP LinkedIn lidc Is needed to store performed actions on the website (marketing/tracking). 1 day HTTP LinkedIn bscookie Is needed to store performed actions on the website (marketing/tracking). 2 years HTTP LinkedIn X-LI-IDC Is needed to provide cross-page functionality (marketing/tracking). session HTTP LinkedIn AnalyticsSyncHistory Stores the time when the user was synchronized with the "lms_analytics" cookie. 30 days HTTP LinkedIn lms_ads Is needed to identify LinkedIn members outside of LinkedIn. 30 days HTTP LinkedIn lms_analytics Is needed to identify LinkedIn members for analytics purposes. 30 days HTTP LinkedIn li_fat_id Required for indirect member identification used for conversion tracking, retargeting and analytics. 30 days HTTP LinkedIn U Is needed to identify the browser. 3 months HTTP LinkedIn _guid Is needed to identify a LinkedIn member for advertising via Google Ads. 90 days HTTP LinkedIn Save Accept all cookies