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
    Object-Based Building Boundary Extraction from Lidar Data
    Shao, You; Lim, Samsung
    Lidar is a remote sensing technology that uses laser beams to generate high-accuracy, three-dimensional (3D) information of the Earth. As urban areas are developing and expanding rapidly, lidar applications such as 3D building modelling and city mapping are of increasing importance. Hence building boundary extraction is one of the main applications of lidar in civil engineering and urban planning projects. In this paper, three boundary extraction algorithms including an alpha-shape algorithm, a modified concave hull algorithm and a grid-based algorithm are tested to assess their object-by-object accuracy. The alpha-shape algorithm generates reliable boundaries for most of sample buildings, while the grid-based algorithm shows less consistency in some cases. The concave hull algorithm performs moderately with a few limitations. Advantages and disadvantages of each algorithm are identified and addressed in this paper.
  • Publication
    Open Source and Open Learning
    Beare, Ryan; Goti, Vidhi; Trojacek, Seth
    We are the Geospatial Information Systems Club from Texas A&M University - Commerce in Commerce, TX. Over the past year, we have cultivated an incredible community of researchers, data analysts, programmers, and writers to make our club one of the top academic clubs on our campus. Our first project even won a first place award. How did we do it? We used Foss4G software. As beginners, we came together as a community of close friends, learned QGIS and undertook a project that highlighted and celebrated the rich 125 year history of our university. Together we continue to use QGIS to study such topics as gentrification, education scarcity, cattle migration, movement of our alumni over time, and many others. We take a different educational approach to learning. Rather than setting tight deadlines for large projects, we come together, we collaborate to solve problems. In addition to our use of QGIS, we have developed our own open source software, and we only use open source software when completing our projects. We want to show how learning GIS looks outside of the classroom, and how beneficial the community of problem solvers we've created has been to our university.
  • Publication
    GIS Oriented Service Optimization Tool For Fecal Sludge Collection
    Hossain, Mohammad Dalower; Ninsawat, Sarawut; Sharma, Shulaxan; Koottatep, Thammarat; Sarathai, Yuttachai
    In developing countries most of the urban dwellers don’t have access to sewer system. People are mostly using “onsite” systems such as septic tanks or pit latrines that need to be emptied periodically, as the densely built urban environment won’t allow new pits to be dug every time they fill up. In the conventional fecal sludge collection systems, authorities are collecting the sludge from house to house and dump on the plant. Fecal sludge collection system is different from traditional vehicle routing and even from solid waste collection system in terms of dynamic collection points, urgency of getting the service and diversity of demand. Due to those vibrant factors authorities are facing proper networking and management problems. This research describes algorithms that can accommodate constraints and prioritized customers who need immediate service. The GPS log data of the fecal sludge collection truck that maintained by Nonthaburi Municipality, Thailand has been considered as the base data during the development of this application. Spatial analysis has been done using Geographic Information Systems (GIS).Tabu Search has been implemented in order to optimize. Basically two algorithms were produced for assisting fecal sludge collection systems. First algorithm was able to produce multiple trip for each vehicle if required considering all the customers having equal priority, time window. The second one was able to perform optimization that can accommodate priority along with the first one. Input for the algorithms were very simple; distance matrix having distance between each customers and plant, customer order with latitude, longitude, order unit, time window, priority and vehicles with capacity. Algorithms were able to produce better result than the actual operation or even from shortest path algorithm in term of distance. After optimization, efficiency of the algorithms were tested with the actual travelling distance. Travelling distance were reduced to half compare to actual cost and it ensured maximum utilization of vehicle capacity by allocating maximum number of customers in each route.
  • Publication
    QKan - Management of drainage system data with QGIS
    Höttges, Jörg
    Based on QGIS a database structure and a set of plugins have been developed to improve the workflow for the hydraulic design of urban drainage systems for consulting engineers. The main goal is pre- and postprocessing in combination with various commercial hydraulic simulation software packages. The plugins provide import and export functionalities, simulation result viewing and generation of longitudinal cross sections in a CAD program. All modules make intensive use of SQL based spatial functions instead of functions implemented in QGIS, because of their stability, higher flexibility and speed due to the indexing functionality. On the other hand the database structure is kept simple to make it possible for engineers as a typical user to work directly with the data in the database.
  • 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
    The Development of Web3D-based Open-pit Mine Monitoring System
    Kim, Se-Yul; Lee, Dong-Gook; Lee, Jung-Bin; Jang, Byung-Jin; You, Ji-Ho; Lee, Hyun-Jik,
    Large-scale open-pit mines are critical infrastructure for acquiring natural resources. However, this type of mine can experience environmental and safety problems during operations and thus requires continuous monitoring. In this study, a web three-dimensional(3D)-based monitoring system is constructed using geospatial information open platform and open-source geospatial information software which targets open-pit mines in Gangwon-do, Korea. The purpose is to develop a monitoring system of open-pit mines that enables any person to monitor the topographic and environmental changes caused by mine operations and to develop and restore the area’s ecology. Open-pit mines were classified into active or inactive mines and monitoring items and methodologies were established for each type of mine. Cesium which is a WebGL-based open-source platform was chosen as it supports dynamic data visualization and hardware-accelerated graphics related to elapsed time which is the essential factor in the monitoring. The open-pit mine monitoring system was developed based on the geospatial database which contains information required for mine monitoring as time elapses, and by developing the open-source-based system software. The geospatial information database for monitoring consists of digital imagery and terrain data and also includes vector data and the restoration plan datas. The basic geospatial information used in the monitoring includes high resolution ortho image(GSD 0.5 m or above) for all areas of the mines. This is acquired by periodically using an airborne laser scanning system and a LiDAR DEM (grid size 1m × 1 m). In addition, geospatial information data were acquired by using an UAV and terrestrial LiDAR for small-scale areas; these tools are frequently used for rapid and irregular data acquisition. The geospatial information acquired for the monitoring of the open-pit mines represents various spatial resolutions and different terrain data. The database was constructed by converging this geospatial information with the Cesium-based geospatial information open platform of the ESRI World Imagery map and with SDK World Terrain meshes. The problems that resulted from the process of fusing aerial imagery and terrain data were solved in the Cesium-based open source environment. The prototype menu for the monitoring system was designed according to the monitoring item which was determined by the type of mine. The scene of the mine and changes in terrain were controlled and analyzed using the raster function of PostGIS according to the elapsed time. Using the GeoServer, the aerial imagery, terrain and restoration information for each period were serviced using the web standard interface, and the monitoring system was completed by visualizing these elements in Cesium in 3D format according to the elapsed time. This study has established a monitoring methodology for open-pit mines according to the type of mine and proposes a method for upgrading the imagery and terrain data required for monitoring. The study also showed the possibility of developing a Web3D-based open-pit mine monitoring system that is applicable to a wide range of mashup service developments.
  • Publication
    Urban Multi-scale Environmental Predictor - an extensive tool for climate services in urban areas
    Lindberg, Fredrik; Grimmond, Sue; Gabey, Andrew; Huang, Bei; Kent, Christoph W; Sun, Ting; Theeuwes, Natalie E; Järvi, Leena; Ward, Helen; Capel-Timms, Izzy; Chang, YY; Jonsson, Per; Krave, Niklas; Liu, Dongwei; Meyer, D; Olofson, K Frans G; Tan, Jian-Guo; Wästberg, Dag; Xue, Lingbo; Zhang, Zhe
    The city based climate service tool UMEP (Urban Multi-scale Environmental Predictor) is a coupled modelling system that combines models essential for urban climate processes and is developed as an extensive QGIS plugin. An application is presented to illustrate its potential, specifically of the identification of heat waves and cold waves in cities. The tool has broad utility for applications related to outdoor thermal comfort, urban energy consumption, climate change mitigation etc. It includes tools to: enable users to input atmospheric and surface data from multiple sources, prepare meteorological data for use in urban areas, undertake simulations and consider scenarios, and compare and visualize different combinations of climate indicators.
  • Publication
    Volume Introduction Letter
    Behr, Franz-Josef
    This Conference Proceedings is a collection of selected papers and posters submitted to the Academic Program of the International Conference for Free and Open Source Software for Geospatial (FOSS4G 2016), 24th to 26th August 2016 in Bonn, Germany. Again geospatial open source software was the focus of a well-attended international conference flanked by presentations on open standards and the open data movement, a meeting place for open communities.
  • 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
    AEGIS - A state-of-the art component based spatio-temporal framework for education and research
    Giachetta, Roberto
    In past years, geoinformation has gained a significant role in information technology due to the spread of GPS localization, navigation systems and the publication of geographical data via Internet. The inclusion of semantic information and temporal alteration has also become increasingly important in GIS. The overwhelming amount of spatial and spatiotemporal data resulted in increased research effort on processing algorithms and efficient data management solutions. This article presents the AEGIS framework, a currently developed spatio-temporal data management system at the Eötvös Loránd University, Faculty of Informatics (ELTE IK). This framework will serve as the future platform of GIS education and research at ELTE IK. It aims to introduce a data model for the uniform representation of raster and vector data with temporal references; to enable efficient data management using specialized indexing; and to support internal revision control management of editing operations. The framework offers a data processing engine that automatically transforms operations for distributed execution using GPGPUs, allows fast operations even with large datasets and high scalability with regard to new methods. To demonstrate the usage of the system two prototype applications – segment-based image classification and agent-based traffic simulation – are also presented.