Journal

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

ISSN
Publisher
Editor-in-Chief
Collections
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
  • PublicationOpen Access
    Exploring the Relationship Between Climate and Forest Conditions in Forest Classee De La Mondah (GABON) using Remote Sensing Data
    MBOUMBA, Mariano
    This study aims to examine the relationship between temperature and precipitation as climatic factors and the vegetation characteristics in Forêt Classée de la Mondah (Gabon). A pixel based spatial analysis procedure with QGIS was used to extract vegetation characteristics from MODIS on Terra, NDVI band, data from February 2000 to December 2015, while temperature and precipitation were monitored from January 1980 to December 2015 to highlight climate fluctuations in the study area. Two regression analyses were conducted : one between temperature and NDVI and the other one between precipitation and NDVI. Results showed that temperature and precipitation did not vary significantly and the overall linear correlation between climate factors and NDVI was not significant. However, a close to medium correlation was found between temperature and NDVI during the long dry season. The authors are conducting a similar study in a broader scale (at country level), based on polygon as a spatial analysis procedure to extract MODIS data, in order to obtain further information about the relationship between climate and vegetation in this region and highlight the fact that vegetation may respond differently to climate effects depending on different micro climate.
  • PublicationOpen Access
    Development of Environment Spatial Information Service Utilizing Mobile Location-Based Technology
    Yoon, Jeongho
    Rapid implementation of mobile devices and significant development of communication technology lead diverse changes over the society at large. Especially, Location-Based Technology of mobile devices is recognized as an important tool to improve task efficiency of tasks that requires on-site investigation and management. The research develops the way to improve environmental administrative work by utilizing Location-Based Technology of mobile devices and environmental geographic information towards tasks for both instruction and inspection of environmental pollutant discharge industries. In addition, it defines function and improvement direction of environment monitoring tasks via test bed implementation to developed mobile application and spatial information database.
  • PublicationOpen Access
    Spatial Data Infrastructure of the Plurinational State of Bolivia - A free and democratic SDI
    Molina Rodriguez, Raul Fernando; Lesage, Sylvain
    The Vice Presidency of the State, with the help of the GeoBolivia project, is building the Spatial Data Infrastructure of the Plurinational State of Bolivia (IDEEPB by its Spanish initials). The first phase of the project has already been completed. It consisted in implementing an infrastructure and a geoportal that nowadays gives access to the reference geographic information of Bolivia, through WMS, WFS, WCS and CSW services. The project is currently in its second phase dedicated to decentralizing the structure of IDE-EPB and promoting its use throughout the Bolivian State. The whole platform uses free software and open standards. As a complement, an on-line training module was developed to undertake the transfer of the knowledge the project generated. The main software components used in the SDI are: gvSIG, QGis, uDig as GIS desktop clients; Post-GreSQL and PostGIS as geographic database management system; geOrchestra as a framework containing the GeoServer map server, the GeoNetwork catalog server and the OpenLayers and Mapfish GIS webclient; MapServer as a map server for generating OpenStreetMap tiles; Debian as operating system; Apache and Tomcat as web servers.
  • PublicationOpen Access
    Identification of SAR Detected Targets on Sea in Near Real Time Applications for Maritime Surveillance
    Voinov, Sergey; Schwarz, Egbert; Krause, Detmar; Berg, Matthias
    Remote sensing technologies are widely used in maritime surveillance applications. Nowadays, spaceborne Synthetic Aperture Radar (SAR) systems provide outstanding capabilities for target detection at sea for large areas independently from the weather conditions. The generated value added target detection product is composed by complementary information from the Automatic Identification System (AIS). Resulting information layers provides a more reliable picture on the maritime situation awareness. This paper describes the approach of SAR-AIS data fusion and its visualization means developed for Near Real Time (NRT) Applications for Maritime Situational Awareness by the Maritime Security Lab at the Ground Station in Neustrelitz, part DLR’s German Remote Sensing Data Center (DFD). Presented implementation is based on combination of many open source geospatial libraries and frameworks (e.g., GDAL/OGR, Geoserver, PostgresSQL) and shows their effectiveness in the context of complex automated data processing in the frame of NRT requirements.
  • PublicationOpen Access
    Analysing the Performance of NoSQL vs SQL Databases with Respect to Routing Algorithms
    agarwal, sarthak; Rajan, KS
    With the increased shift towards GeoSpatial Web Services on both the Web and mobile platforms especially in the usercentric services, there is a need to improve the query response time. The traditional routing algorithm requires server to process the query and send the results to a client but here we are focussing on query processing within the client itself. This paper attempts to evaluate the performance of an existing NoSQL database and SQL database with respect to routing algorithm and evaluate whether or not we can deploy the computations on the client system only. While SQL databases face the challenges of scalability and agility and are unable to take the advantage of the abundant memory and processing power available these days, NoSQL databases are able to use some of these features to their advantage. The nonrelational databases are more suited for handling the dynamic rise in the data storage and the increased frequency of data accessibility. For this comparative study, MongoDB is the NoSQL engine while the PostgreSQL is the chosen SQL engine. The dataset is a synthetic dataset of road network with several nodes and we find the distance between source and destination using various algorithms. As a part of paper The implementation we are planning on using pgRouting for the analysis which currently uses PostgreSQL at the backend and implements almost all the routing algorithms essential in practical scenarios. We have currently analyzed the performance of NoSQL databases for various spatial queries and have extended that work to routing. Initial results suggest that MongoDB performs faster by an average factor of 15x which increases exponentially as the path length and network data size increases in both indexed and nonindexed operations. This implies that nonrelational databases are more suited to the multiuser query systems and has the potential to be implemented in servers with limited computational power. Further studies are required to identify its appropriateness and incorporate a range of spatial algorithms within nonrelational databases.
  • PublicationOpen Access
    GRASS in the Desert? Developing FOSS tools for monitoring desertification
    Zanchetta, Anna
    The use of Change Vector Analysis (CVA) combined with the Tasselled Cap tranform (TCT) is a powerful remote sensing tool to monitor forests and vegetated areas, but its application to arid and semiarid environment is not straightforward. This question is tackled through the calculation of a new set of TCT coefficients using R and GRASS-GIS for SPOT and Landsat satellites, then applied and tested in change detection analysis on a short (seasonal) and a long (decades) temporal scale. Results show that the combined procedure is an effective method to detect changes in desert environment. Furthermore, the new TCT allows the use of this combined procedure for studies in arid and semi-arid regions, eliminating the doubts on its compatibility with the area of study. Further development is the creation of a new GRASS-GIS module to performe CVA, thus enabling the simple usage of this technique, until now not available in most common software.
  • PublicationOpen Access
    Hydraulic modeling for the assessment of flood hazard using the Iber software in the Amarante urban center
    Martins, Márcia; Gomes, Alberto; Pinto Santos, Pedro
    Recently, there is an availability increase of hydraulic modeling software that allows the analysis and definition of several hydraulic variables, namely water depth and flow velocity, which are important parameters for the assessment and management of flood-prone areas. The growing use of this software is related with the fact of being Free and Open Source Software (FOSS), making possible the understanding of different approaches and providing most reliable and accurate results of flood-prone areas according different return periods. In this study it was used the freely hydraulic software Iber, a tool for two-dimensional modeling of water flow in rivers and estuaries that provides the hydraulic variables (water depth and velocity) required for the definition of flooded areas. The main objective of this work was the analysis of flood hazard at the city of Amarante (North of Portugal), a place frequently affected by these extreme events. Due to the huge concentration of activities and services along the flood-prone area, economic and social damages caused by floods in the historical and urban center of Amarante are very important. Therefore, hydraulic modeling of the flooded area was performed for different return periods (10, 100 and 500 years) using the Iber software. The main results shows the maximum extent of the flood, the water depth and the flow velocity for a specific return period and also, a flood hazard map for the return period of 100 years. This case study aims to contribute for a better management of flood risk, which is a challenge for competent authorities, namely the local civil protection, fireman's and municipality services.
  • PublicationOpen Access
    OPENSENSEMAP - A Citizen Science Platform For Publishing And Exploring Sensor Data as Open Data
    Pfeil, Matthias; Bartoschek, Thomas; Wirwahn, Jan Alexander
    A plethora of citizen science sensor platforms for dierent use-cases already exist. They provide cheap, precongured, plug and playable hardware and software solutions. Using data from multiple platforms and resources can be a challenging task in respect of discovering, exploring, downloading and converting. This work aims to implement a one-stop-shop for sensor data that tries to tackle these problems. Therefore a basic data schema capable of metadata is established that allows publishing generic sensor platforms and sensor data. For exploration a web platform is implemented based on common web standards. This work describes the requirements, design and implementation of the OpenSenseMap. OpenSenseMap is following the clientserver model and its complete application stack is implemented in JavaScript. It describes the basic components and the underlying data model. All components are using open-source technology and are published under an opensource license too. The RESTful service is the heart of OpenSenseMap and implements the data publish and data retrieval functions. Developers may use it to build custom applications around OpenSenseMap or integrate OpenSenseMap into existing projects. The NodeJS application runs its own web server and implements the different HTTP request types. The OpenSenseMap concept is being evaluated with a technical and a user survey.
  • PublicationOpen Access
    The Construction of Open Data Portal using DKAN for Integrate to Multiple Japanese Local Government Open Data
    Seto, Toshikazu; Sekimoto, Yoshihide
    In recent years, the Code for Japan, a civic tech community in Japan, has focused on the context of the FOSS4G. Consequently, the Japanese have published open data in more than 150 local governments, but these data are almost simply provided as a file on their website. And also CKAN portal are used less than 20 cities. In this study, we built open data platform that uses DKAN for integrated open data distribution of Japanese local governments.
  • PublicationOpen Access
    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.