@article{2-s2.0-85051558824,

title = {The Mesoscale Convective Systems with bow echo radar signatures as an example of extremely severe and widespread geohazard in Poland},

author = { A. Widawski and W. Pilorz},

url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85051558824&doi=10.2478%2fenviron-2018-0002&partnerID=40&md5=6750ed13255916178117cce94c82d1fc},

doi = {10.2478/environ-2018-0002},

issn = {23540079},

year  = {2018},

date = {2018-01-01},

journal = {Environmental and Socio-Economic Studies},

volume = {6},

number = {1},

pages = {10-16},

publisher = {De Gruyter Open Ltd},

abstract = {In the last two decades we can notice a significant increase of severe anemological events, which are mostly connected with mesoscale convective systems and a cold front of a deep low-pressure system. One of them are very strong winds with speeds more than 25 m/s. They caused material damage and threatening people's lives. The most dangerous are winds generated by mesoscale convective systems where radar reflectivity signatures of bow echo/derecho appeared. In this paper the area of occurrence of such phenomenon in Poland are described and the features of bow echo signatures on radar images are presented and explained. Additionally one of the most severe event and still very weakly known episode of 11th August 2017 derecho in Poland is analysed. The damage data from European Severe Weather Database (ESWD) were analysed to confirm if the August 11th storm met derecho criteria. To identify the radar reflectivity signatures inside MCC the data from the Polish Institute of Meteorology and Water Management shared on the radar-opadow.pl site were used. The CAPPI 1 km data were very useful to determine the convective forms. After that the data from synoptic station were examined for presenting the running of selected meteorological elements. Finally, some information about material damage in infrastructures and forests are mentioned. © 2018 Artur Widawski et al., published by De Gruyter Open.},

note = {3},

keywords = {},

pubstate = {published},

tppubtype = {article}

}

@article{2-s2.0-17744407547,

title = {The analysis of the vegetation condition over Poland in 2000 in the light of the NOAA/AVHRR satellite information [Analiza stanu roślinności w Polsce w 2000 roku w świetle informacji satelitarnej NOAA/AVHRR]},

author = { P. Struzik and A. Widawski},

url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-17744407547&partnerID=40&md5=3e2067ecc18034a1472994a777d195fa},

issn = {01371983},

year  = {2000},

date = {2000-01-01},

journal = {Annales Universitatis Mariae Curie-Sklodowska. Sectio B},

number = {55-56},

pages = {309-319},

abstract = {Satellite AVHRR/NOAA information is very useful for agriculture needs: observation of state of crops, biomass amount evaluation using satellite derived NDVI parameter, determination of evapotranspiration and surface temperature. These parameters describing the Earth surface both qualitatively and quantitatively may be used as input parameters for hydrological and agricultural models of crop productivity. Specially interesting is the use of NOAA satellite data for land surface monitoring and different agriculture applications of this information. The AVHRR/NOAA information, which makes possible classification of land surface into different land-use classes: water, urbanised territory, coniferous forest, deciduous and mixed forest, pasture, cultivated area, cultivated area with predominance of corn fields, high mountain area according to the vegetation periods 2000 over Poland are presented on this paper. As input information for classification is the temporal and spatial profile of NDVI (Normalised Difference Vegetation Index) for each pixel of the Poland area during the vegetation season of the 2000 year. The length of a period necessary for amount of biomass determination is strictly connected with cloudiness. On the area of Poland usually period of 7-14 days is enough for cloud free image collection even for big areas.},

keywords = {},

pubstate = {published},

tppubtype = {article}

}