Free and Open Source Software for Geospatial (FOSS4G) Conference Proceedings

No Thumbnail Available
ISSN
Publisher
Editor-in-Chief
Description
<p>This is a new platform being developed for the management of papers and posters submitted for review for the Free and Open Source for Geospatial (FOSS4G) conferences.
<magic ignore> <p>Add text for <macro publication.title> Aims &amp;amp; Scope page here.</p> </magic>
<!-- COMMENTED OUT BY SCHWEIK <h2><macro journal_styleguide_label></h2> <div id="styleguide"> <p>This document provides details on typesetting and layout requirements pertaining to final manuscript submission to <em><macro ir_journal.title encode='html'></em>.</p> <h3>Formatting Requirements</h3> <ul> <li>Do not include a title page or abstract. (Begin the document with the introduction; a title page, including the abstract, will be added to your paper by the editors.)</li> <li>Do not include page numbers, headers, or footers. These will be added by the editors.</li> <li>Write your article in English (unless the journal expressly permits non-English submissions).</li> <li>Submit your manuscript, including tables, figures, appendices, etc., as a single file (Word, <magic if test="my.AUTO_CONVERT_WORDPERFECT_FILE">WordPerfect, </magic><acronym title="Rich Text Format">RTF</acronym>, or <acronym title="Portable Document Format">PDF</acronym> files are accepted).</li> <li>Page size should be 8.5 x 11-inches.</li> <li>All margins (left, right, top and bottom) should be 1.5 inches (3.8 cm), including your tables and figures.</li> <li>Single space your text.</li> <li>Use a single column layout with both left and right margins justified.</li> <li>Font: <ol><li>Main Body&amp;#8212;12 pt. Times or the closest comparable font available</li> <li>Footnotes&amp;#8212;10 pt. Times or the closest comparable font available</li> </ol> </li> <li>If figures are included, use high-resolution figures, preferably encoded as encapsulated PostScript (eps).</li> <li>Copyedit your manuscript.</li> <li>When possible, there should be no pages where more than a quarter of the page is empty space.</li> </ul> <h3>Additional Recommendations</h3> <h4>Indenting, Line Spacing, and Justification</h4> <p><strong>Indent all paragraphs except those following a section heading.</strong> An indent should be at least 2 em-spaces.</p> <p>Do not insert extra space between paragraphs of text with the exception of long quotations, theorems, propositions, special remarks, etc. These should be set off from the surrounding text by additional space above and below. </p> <p>Don't "widow" or "orphan" text (i.e., ending a page with the first line of a paragraph or beginning a page with the last line of a paragraph).</p> <p>All text should be <strong>left-justified</strong> (i.e., flush with the left margin&amp;#8212;except where indented). Where possible, it should also be right-justified (i.e., flush with the right margin). "Where possible" refers to the quality of the justification. For example, <a href="http://www.latex-project.org" title="LaTeX project: LaTeX &amp;ndash; A document preparation system">LaTeX</a> and <a href="http://www.tug.org/" title="TeX Users Group (TUG) home page">TeX</a> do an excellent job of justifying text. Word does a reasonable job. But some word processors do a lousy job (e.g., they achieve right justification by inserting too much white space within and between words). We prefer flush right margins. However, it is better to have jagged right margins than to have flush right margins with awkward intra- and inter-word spacing. Make your decision on whichever looks best. </p> <h4>Language &amp;amp; Grammar</h4> <p>All submissions must be in English. Except for common foreign words and phrases, the use of foreign words and phrases should be avoided.</p> <p> Authors should use proper, standard English grammar. The <em>Elements of Style</em> by William Strunk, Jr. and E. B. White (now in its fourth edition) is the "standard" guide, but other excellent guides (e.g., <em>The Chicago Manual of Style</em>, University of Chicago Press) exist as well. </p> <h4>Article Length</h4> <p>Because this journal publishes electronically, page limits are not as relevant as they are in the world of print publications. We are happy, therefore, to let authors take advantage of this greater "bandwidth" to include material that they might otherwise have to cut to get into a print journal. This said, authors should exercise some discretion with respect to length.</p> <h4>Colored text</h4> <p>Set the <strong>font color to black</strong> for the majority of the text. We encourage authors to take advantage of the ability to use color in the production of figures, maps, etc., however, you need to appreciate that this will cause some of your readers problems when they print the document on a black &amp;amp; white printer. For this reason, you are advised to avoid the use of colors in situations where their translation to black and white would render the material illegible or incomprehensible.</p> <p>Please ensure that there are no colored mark-ups or comments in the final version, unless they are meant to be part of the final text. (You may need to "accept all changes" in track changes or set your document to "normal" in final markup.) </p> <h4>Emphasized text</h4> <p>Whenever possible use <em>italics</em> to indicate text you wish to emphasize rather than underlining it. The use of color to emphasize text is discouraged.</p> <h4>Font faces</h4><p>Except, possibly, where special symbols are needed, use Times or the closest comparable font available. If you desire a second font, for instance for headings, use a sans serif font (e.g., Arial or Computer Modern Sans Serif). </p> <h4>Font size</h4> <p>The main body of text should be set in 12pt. Avoid the use of fonts smaller than 6pt.</p> <h4>Foreign terms</h4> <p>Whenever possible, foreign terms should be set in <em>italics</em> rather than underlined.</p> <h4>Headings</h4> <p><strong>Headings</strong> (e.g., start of sections) should be distinguished from the main body text by their fonts or by using small caps. Use the same font face for all headings and indicate the hierarchy by reducing the font size. There should be space above and below headings.</p> <h4>Main text </h4> <p>The font for the <strong>main body</strong> of text must be black and, if at all possible, in Times or closest comparable font available. </p> <h4>Titles</h4> <p>Whenever possible, <strong>titles of books, movies, etc.</strong>, should be set in <em>italics</em> rather than underlined.</p> <h4>Footnotes</h4> <p><strong>Footnotes</strong> should appear at the bottom of the page on which they are referenced rather than at the end of the paper. Footnotes should be in 10 pt. Times or closest comparable font available, they should be single spaced, and there should be a footnote separator rule (line). Footnote numbers or symbols in the text must follow, rather than precede, punctuation. Excessively long footnotes are probably better handled in an appendix. All footnotes should be left and right-justified (i.e., flush with the right margin), unless this creates awkward spacing.</p> <h4>Tables and Figures</h4> <p>To the extent possible, <strong>tables and figures</strong> should appear in the document near where they are referenced in the text. Large tables or figures should be put on pages by themselves. Avoid the use of overly small type in tables. In no case should tables or figures be in a separate document or file. All tables and figures must fit within 1.5" margins on all sides (top, bottom, left and right) in both portrait and landscape view.</p> <h4>Mathematics</h4> <p><strong>Roman letters</strong> used in mathematical expressions as variables should be <em>italicized</em>. Roman letters used as part of multi-letter function names should not be italicized. Whenever possible, subscripts and superscripts should be a smaller font size than the main text. </p> <p><strong>Short mathematical expressions</strong> should be typed inline. <strong>Longer expressions</strong> should appear as display math. Also expressions using many different levels (e.g., such as the fractions) should be set as display math. Important definitions or concepts can also be set off as display math. </p> <p><strong>Equations</strong> should be numbered sequentially. Whether equation numbers are on the right or left is the choice of the author(s). However, you are expected to be consistent in this. </p> <p><strong>Symbols and notation</strong> in unusual fonts should be avoided. This will not only enhance the clarity of the manuscript, but it will also help insure that it displays correctly on the reader's screen and prints correctly on her printer. When proofing your document under <acronym title="Portable Document Format">PDF</acronym> pay particular attention to the rendering of the mathematics, especially symbols and notation drawn from other than standard fonts. </p> <h2 id="bibliography">References</h2> <p>It is the author's obligation to provide complete references with the necessary information. After the last sentence of your submission, please insert a line break&amp;#8212;not a page break&amp;#8212;and begin your references on the same page, if possible. References should appear right after the end of the document, beginning on the last page if possible. References should have margins that are both left and right- justified. You may choose not to right-justify the margin of one or more references if the spacing looks too awkward. Each reference should give the last names of all the authors, their first names or first initials, and, optionally, their middle initials. The hierarchy for ordering the references is:</p> <ol> <li> Last name of first author </li> <li> First name of first author <li> Last name of second author (if any). Co-authored work is listed after solo-authored work by the same first author (e.g., Edlin, Aaron S. would precede Edlin, Aaron S. and Stefan Reichelstein).</li> <li> First name of second author</li> <li> Publication date</li> <li> Order cited in text</li> </ol><p> The information to be given with each citation in the references is as follows:</p> <h4>Articles in traditional journals:</h4> <p><strong>Required:</strong> Author's (authors') name(s), title of article, name of journal, year of publication (or "n.d." if no date), volume number, page numbers. </p> <p><em>Optional (but desirable)</em>: issue number and month/season of publication. For forthcoming (in press) articles, put expected year of publication and substitute "forthcoming" for the volume and page numbers.</p> <p><em>Optional(but desirable)</em>: A hyperlink to the article.</p> <h4>Books:</h4> <p><strong>Required:</strong> Author's (authors') name(s), title of book, year of publication (or "n.d." if no date), publisher, publisher's address, edition (if not first). For forthcoming (in press) books, put expected year of publication and add "forthcoming."</p> <h4>Chapters in collections or anthologies:</h4> <p><strong>Required:</strong> Name(s) of author(s) of chapter, name(s) of editor(s) of book, title of chapter, title of book, year of publication (or "n.d." if no date), publisher, publisher's address, and edition (if not first). For forthcoming (in press) books, put expected year of publication and add "forthcoming."</p> <h4>Working papers:</h4> <p><strong>Required:</strong> Author's (authors') name(s), title of working paper, year (or "n.d." if no date), location (e.g., "Department of Economics Working Paper, University of California, Berkeley" or "Author's web site: http://www.someurl.edu/author." If the working paper is part of series, then the series name and the number of the working paper within the series must also be given.</p> <h4>Other works:</h4> <p><strong>Required:</strong> Author's (authors') name(s), title of work, year (or "n.d." if no date), and information about how the reader could obtain a copy.</p> <p>Within the references section, the citations can be formatted as you like, provided (i) the formatting is consistent and (ii) each citation begins with the last name of the first author. That is, the following would all be acceptable:</p> <div class="example"> <pre>Smith, Adam (1776) The Wealth of Nations, . . .</pre> <pre>Smith, A., The Wealth of Nations, . . . , 1776. </pre> <pre>Smith, Adam: The Wealth of Nations, 1776, . . .</pre> </div><div class="clear">&amp;nbsp;</div> <p>Use hanging indents for citations (i.e., the first line of the citation should be flush with the left margin and all other lines should be indented from the left margin by a set amount). Citations should be single-spaced with extra space between citations.</p> <p>When works by the same author are listed in a row, use &amp;#8212; instead of writing the name again. Hence, one might have</p> <div class="example"> <pre>Smith, Adam: The Wealth of Nations, . . .</pre> <pre>&amp;#8212;: The Theory of Moral Sentiments, . . . </pre></div><div class="clear">&amp;nbsp;</div> <p>Similarly, instead of repeating two names use</p> <div class="example"> <pre>"&amp;#8212; and &amp;#8212;."</pre></div> <p>For instance,</p> <div class="example"><pre>Edlin, A. and S. Reichelstein (1995) . . . &amp;#8212; and &amp;#8212; (1996) . . . </pre></div> <div class="clear">&amp;nbsp;</div> <p>Within the text of your manuscript, use the <strong>author-date</strong> method of citation. For instance, </p> <div class="example"> <pre>"As noted by Smith (1776)." </pre> </div><div class="clear">&amp;nbsp;</div> <p>When there are two authors, use both last names. For instance,</p> <div class="example"> <pre>"Edlin and Reichelstein (1996) claim . . . "</pre> </div> <div class="clear">&amp;nbsp;</div> <p>If there are three or more authors give the last name of the first author and append et al. For instance, a 1987 work by Abel, Baker, and Charley, would be cited as</p> <div class="example"> <pre>"Abel et al. (1987)." </pre> </div> <div class="clear">&amp;nbsp;</div> <p>If two or more cited works share the same authors and dates, use "a," "b," and so on to distinguish among them. For instance,</p> <div class="example"> <pre>"Jones (1994b) provides a more general analysis of the model introduced in Example 3 of Jones (1994a)."</pre></div> <div class="clear">&amp;nbsp;</div> <p>After the first cite in the text using the author-date method, subsequent cites can use just the last names if that would be unambiguous. For example, Edlin and Reichelstein (1996) can be followed by just Edlin and Reichelstein provided no other Edlin &amp;amp; Reichelstein article is referenced; if one is, then the date must always be attached.</p> <p>When citations appear within parentheses, use commas&amp;#8212;rather than parentheses or brackets&amp;#8212;to separate the date from the surrounding text. For instance, </p> <div class="example"> <pre>" ...(see Smith, 1776, for an early discussion of this)."</pre></div> <div class="clear">&amp;nbsp;</div> </div> -->

Search Results

Now showing 1 - 10 of 135
  • Publication
    Classification of land use/cover change in the Kanto region, Japan using FOSS4G and Open Data
    Iwasaki, Nobusuke; Spraguea, David; Onohara, Ayaka
    In this study, we classified land use/cover change from the 1880’s to 2010’s in the Kanto Region, Japan. First, we developed a 100m grid land use/cover database of the 1880’s with QGIS application and PostGIS database. The data were published through the GitHub Site as an Open Data (CC BY 4.0). We imported Japanese national Open Data about land use (1970’s and 2010’s) to the PostGIS database, and carried out a spatial join with land use/cover data of the 1880’s. A model-based clustering method was applied to the land use/cover change data that were summarized based on a 1 km by 1 km grid. The land use/cover change was classified into 29 categories, and we applied multi-dimensional scaling (MDS) analysis to categorize data. Based on MDS analysis, the categories were divided into 7 groups, and each land use/cover change category had a strong relation with distance and direction from central Tokyo and topographical features.
  • Publication
    GIS Investigation of Crime Prediction with an Operationalized Tweet Corpus
    Corso, Anthony J.; Alsudais, Abdulkareem
    Social media as the de facto communication channel is being used to disseminate one’s diurnal self-revelations. This profound discovery often contains double-talk, peculiar insights, or contextual information about real-world events. Natural language processing is regularly used to uncover both obvious and latent knowledge claims within disclosures published amid the complex environment. For example, a perpetrator with first-hand knowledge of their criminal incident uses social media to post critical information about it. A geographic information system (GIS) is capable of large-scale point data analysis and possesses methods that enable dataset processing, evaluation, and automatic spatial visualization. Such an artifact—fused with traditional environmental criminology theory and social media—erects guidelines, tools, and models for substantive construction and evaluation of GIS crime analysis solutions. Provided the social media stream is timely and correctly processed, corrective action can be taken. The construction of a natural language processing social media annotation pipe identifies latent indicators extracted from a social media corpus and is an integral part of societal mishap prediction. Spatial visualizations and regression analyses were used to describe and evaluate project artifacts. As a result, a social media corpus was operationalized, and subsequently used as a proxy for a traditional environmental criminology risk layer in construction of a social media GIS crime analysis artifact. Using such multi-domain collaboration, the artifact was able to increase the predictive crime incident outcome with an overall R-squared increase of 21.94%. This result is the state-of-the-art; there are no other results to compare it to.
  • Publication
    Gestural Interaction with Spatiotemporal Linked Open Data
    Bartoschek, Thomas; Pape, Gerald; Kray, Christian; Jones, Jim; Kauppinen, Tomi
    Exploring complex spatiotemporal data can be very challenging for non-experts. Recently, gestural interaction has emerged as a promising option, which has been successfully applied to various domains, including simple map control. In this paper, we investigate whether gestures can be used to enable non-experts to explore and understand complex spatiotemporal phenomena. In this case study we made use of large amounts of Linked Open Data about the deforestation of the Brazilian Amazon Rainforest and related ecological, economical and social factors. The results of our study indicate that people of all ages can easily learn gestures and successfully use them to explore the visualized and aggregated spatiotemporal data about the Brazilian Amazon Rainforest.
  • Publication
    An Evaluation of Open Source Geographic Information Systems Routing Tools in Vaccine Delivery in Kano State, Northern Nigeria
    Adewara, Kehinde A.
    The recent proliferation of online/desktop/mobile open source geographic information systems (GIS)routing tools such as qgis road graph plugin (QRG), open street routing machine (OSRM), google maps engine (GME), graphhopper (GH), and Osm And has led to the need to provide a method for comparatively evaluating the strength and weakness of these routing tools. This is crucial in view of its implication on the prospect and otherwise of routing related projects such as supply chain logistics, supply/delivery operations, and emergency services, among others. In this paper, comparative evaluation of these tools has been carried out using drive test survey and desktop routing estimation with respect to routine vaccine delivery in Kano, Nigeria. Kano state being one of the states in Nigeria with huge burden of health challenges with records of 3062 maternal death between 2005 – 2010(Ibrahim, 2014) . Thus vaccine delivery is one of such healthcare delivery programmes used to addressing some of these health challenges. The primary objective of this paper is to demonstrate comparative advantage of using open sourceGIS routing tools to optimize vaccine delivery process such that there would be significant reduction in logistics, manpower and cost associated with routine vaccine delivery. The capacity of the selected open source GIS routing tools was evaluated against this backdrop. Hence drive test survey was used to define the benchmark for determine the best rank among these desktop routing tools. The drive test survey was carried on selected number of delivery routes and the results were compared with values derived from desktop routing estimation using these tools. Two rounds of drive test survey were carried out for the delivery routes and an average was considered in order to minimum possible error associated with possible inconsistent in driving behavior. Significant discrepancies were observed in the outputs derived between desktop (QRG), online (OSRM, GME, GH) and mobile (Osm And) routing platforms. OSM vector base map was used across all the routing tools except GME.The overall outcome indicated QRG had the highest cumulative error margin of 67.52km while the lowest was reported for GraphHoper (46.17km) using same OSM base map. This is an indication that the routing algorithm used is not the same. When compared with GME that uses different base map, the cumulative error margin is very close (QRG – 67.52, GME – 55.99), an indication that similar routing algorithm has been used. Drive test outcome may not be sufficient to determine best or otherwise routing tool, it may be appropriate to consider other valuable criteria for the purpose of ranking these tools. Hence, those criteria were not limited to drive test/routing output error margin, others include capacity for multiple routing, base map completeness/content, support for traffic input, routing platform, and alternative routing option. With these considerations, QRG was ranked 1st. while OsmAnd (5) was least ranked. GME and GH had same ranking (2). QRG was ranked above other OSM based routing tools because it uses desktop platform and a capacity to integrate traffic input. It was ranked above GME majorly because of its robust OSM base map compared to google base map.
  • Publication
    Evaluating Flood Hazard Potential in Danang City, Vietnam Using FOSS4G
    Thi, An Tran; Raghavan, Venkatesh; Masumoto, Shinji; Nonogaki, Susumu; Nemoto, Tatsuya; Poliyapram, Vinayaraj; Yonezawa, Go
    Floodplain in the alluvial lowland coastal area in the south of Danang City is a part of Vu Gia - Thu Bon river basin where is affected by serious and repetitive flood hazard. The topography and geomorphology which directly related to flood hazard but such relationship are still poorly understood. This study aims to measure flood inundation during a flood event in 2007 and estimate the potential flood hazard areas. ALOS PALSAR imageries were used for observing flood inundation dynamics. A 5m resolution DEM of study area were generated using field survey elevation points data and BS-Horizon interpolation method (Nonogaki et al., 2012). The generated DEM and flood inundation map were used as input data to extract the geomorphologic features of the study area and investigate relations on flood hazards. The flood potential mapping based on the investigation of ALOS PALSAR interpretation, topographical analysis and the land cover classification was carried out. As the result, flood inundation map shows good correlation to field survey flood map in 2007 and potential flood hazard map also coincides with flood scenario assessment by the Danang City government.
  • Publication
    Facilitate Visualization and Distribution of NASA's Environmental Science Data through Open Standards and Open Source Software for Geospatial
    Wei, Yaxing; Wei, Zhaoying (Angie); SanthanaVannan, Suresh
    This paper introduces the utilization of open standards and open source software for visualization and distribution of geospatial environmental science data at the Oak Ridge National Laboratory Distributed Active Archive Center (ORNL DAAC). The ORNL DAAC is one of the NASA Earth Observing System Data and Information System (EOSDIS) data centers. A big challenge for the ORNL DAAC (https://daac.ornl.gov) is to efficiently manage over a thousand heterogeneous environmental data, collected through field campaigns, aircraft/satellite observations, and model simulations. ORNL DAAC also has to provide tools to easily find, visualize, and access the heterogeneous data. To address this challenge, the ORNL DAAC has leveraged Open Geospatial Consortium (OGC) standards and open source software to develop the Spatial Data Access Tool (SDAT, https://webmap.ornl.gov/ogc). SDAT is a suite of open standards-based web mapping, subsetting, and transformation services and applications that allow users to visualize and download geospatial data in customized spatial/temporal extents, formats, and projections. The open source MapServer/Geospatial Data Abstraction Library (GDAL) powers the backend OGC Web services of SDAT. Open source Javascript libraries, including OpenLayers, GeoExt, and proj4js, were used to create the SDAT Web User Interface and MapWidget, a light-weight Javascript library that allows SDAT visualization to be easily embedded on any webpage. SDAT also provides KML files to enable interactive data visualization in the popular Google Earth application or any KML-compatible client. SDAT provides a common framework and standard service interfaces for ORNL DAAC data holdings. SDAT user interface hides their heterogeneity from end users, and promotes their usage. SDAT facilitates integration of ORNL DAAC data resources with other related data systems. In 2016, SDAT served more than 2 million mapping requests and 72 thousand customized data downloads from over 2500 distinct data users.
  • Publication
    How to cross a square?
    Miksch, Jakob; Hahmann, Stefan
    The poster compares algorithms how squares can be integrated into a routing engine. A case study showed that most algorithms increase the processing time and the created count of edges significantly.
  • Publication
    Taarifa - Improving Public Service Provision in the Developing World Through a Crowd-sourced Location Based Reporting Application
    Iliffe, Mark; Sollazzo, Giuseppe; Morley, Jeremy; Houghton, Robert
    Public service provision in the developing world is challenged by a lack of coherence and consistency in the amount of resources local authorities have in their endowment. Especially where non-planned urban settlements (e.g. slums) are present, the frequent and constant change of the urban environment poses big challenges to the effective delivery of services. In this paper we report on our experiences with Taarifa: a location-based application built through community development that allows community reporting and managing of local issues.
  • Publication
    Development of a QGIS Plugin to Dasymetric Mapping
    Mileu, Nelson; Queirós, Margarida
    Demographic data is usually represented by choropleth map, where the statistical data is aggregated to areal units. This type of representation has several limitations associated with spatial analysis and distribution. A common alternative to display statistical data in meaningful spatial zones is the dasymetric mapping technique. Though dasymetric mapping has existed for many decades, the open source GIS tools to explore dasymetric mapping methods are scarce. In this paper, a Geographical Information System (GIS) open source application was developed in QGIS software that applies the dasymetric mapping method to the Portuguese Guimarães municipality 2011 Census block-group populations and using Corine Land Cover Data Set to redistribute the block-group populations into a 25-m grid. The application employs a simple centroid sampling approach (supported by the Addresses theme obtained in the INSPIRE ATOM Download Service from the Portuguese National Statistics Institute, INE) to acquire information on the population densities for different land use classes, and it uses the ratio of class densities to redistribute population to sub-source zone areas. Several tools available from QGIS and Geographic Resources Analysis Support System (GRASS) GIS were employed to generate a resident population dasymetric map. The application development was supported by Python 2.7 language and PyQt4 API. The plugin developed for the QGIS is an innovative tool that allows the population mapping to any case study that has statistical data and the Corine Land Cover layer. To test the results obtained from the tool, census block populations were compared with the dasymetric map. The results indicate that dasymetric mapping produce more accurate population distributions than the choropleth approach.
  • Publication
    Grassland Recognition with the Usage of Thermal Weights
    Mangafić, Alen; Mesner, Nika; Triglav Čekada, Mihaela
    In this paper we apply the usage of thermal weights, a new variable for geostatistical analysis and we present the method for their determination. In the case study we tested a data fusion between Sentinel-2 and Landsat 7/8 data, to incorporate also the thermal factor in the detection of land cover changes. The process distinguishes grasslands from other crops with similar vegetative appearance and offers us the possibility to create a new statistical sample with just grasslands. The data fusion is incorporated in the calculation of Land Surface Temperature (LSTFU) by combining the Sentinel-2 derived Normalized Difference Vegetation Index (NDVI), and from it derived land surface emissivity, with the Landsat 7/8 derived Top of Atmosphere Brightness Temperature (TOABT). The experimental LSTFU is modified into a normalized assessment variable by a time-series analysis. The result is a thermal weight layer which can help us in further object-based image analyses and classification. The thermal weight is calculated from Sentinel-2 and Landsat 7/8 datasets that has small acquisition time gaps between them. The accuracy assessment due to time gaps and sensor differences was evaluated with Cohens’s kappa (κ) and correlation matrix validation. The data fusion is made to test if a Sentinel-2 fusion approach could improve the Thermal Weight created just by Landsat imagery. The purpose was to evaluate the importance of thermal bands for LU/LC cover.