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
    FOSS4G 2016 Proceedings: Academic Program - selected papers and posters
    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. Like in previous FOSS4G conferences on national and international level the academic papers and posters cover an extensive wide range of topics reflecting the contribution of the academia to this field by the development of open source software components, in the design of open standards, in the proliferation of web-based solutions, in the dissemination of the open principles important in science and education, or in the collection and the hosting of freely available geo-data.
  • Publication
    Analysis of Spatial Density Utilizing The Big Data of Floating Population of Seoul City
    Kim, Hailin
    The goal of this research is to support spatial decision that deals with foreign tourists’ inconveniences in Seoul City—associated with place—by using data mining technology. The analysis of domestic mobile phone records of foreign tourists not only produces the number of floating population demonstrated in the aspect of its nationality and time period, but also conducts the spatiotemporal localization of foreign visitors. R-Studio, a statistical computing software, is used to analyze the spatial density from the call traffic; QGIS, an open-source Geographic Information System(GIS) software, is useful in displaying the data on a map. As a result, fourteen areas, where foreign floating population’s mobility patterns are noticeable, are selected: Gyeongbok Palace, Namsan Hanok Village, Deoksu Palace, Insa-dong, Myeong-dong, Namdaemun Market, Dongdaemun Market, Garosu-gil, Apgujeong-dong, Itaewon, Hongik University, Gangnam Station, COEX, and Lotte World. Further this research introduces the application to alleviate the inconveniences regarding the signposts, bus route, and insufficient tourist information centers; it suggests to add more foreign languages on the signposts at certain locations, modify the current route of the city tour bus, and position additional tourist information centers at the area where floating population of foreign tourists turns out to be dense. Likewise, the connection between big data and GIS technology in this research poses a significant impact on enhancing the efficiency of spatial decision.
  • Publication
    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.
  • Publication
    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.
  • Publication
    Performance Analysis of MongoDB Vs. PostGIS/PostGreSQL Databases For Line Intersection and Point Containment Spatial Queries
    agarwal, sarthak; Rajan, KS
    Relational databases have been around for a long time and Spatial databases have exploited this feature for close to two decades. The recent past has seen the development of NoSQL non-relational databases, which are now being adopted for spatial object storage and handling too. And this is gaining ground in the context of increased shift towards GeoSpatial Web Services on both the Web and mobile platforms especially in the usercentric services, where there is a need to improve the query response time. While SQL databases face scalability and agility challenges and fail to take the advantage of the cheap memory and processing power available these days, NoSQL databases can handle the rise in the data storage and frequency at which it is accessed and processed - which are essential features needed in geospatial scenarios, which do not deal with a fixed schema(geometry) and fixed data size. This paper attempts to evaluate the performance of an existing NoSQL database 'MongoDB' with its inbuilt spatial functions with that of a SQL database with spatial extension 'PostGIS' for two primitive spatial problems - LineIntersection and Point Containment problem, across a range of datasets, with varying features counts. For LineIntersection function, the dataset consisted of two independent layers of horizontal lines and vertical lines with incremental lengths and their size varied from ten lines to million lines in each layer and another dataset with two layers, one of random lines of variable size and shape and another layer of a single line which is intersecting many lines of layer1. For Point Containment problem, the dataset consists of two layers, one of polygons in space of different shape and size and another layer of random points in the space, some inside the polygons and some outside. All the data in the analysis was processed In-memory and no secondary memory was used. Initial results suggest that MongoDB performs better by an average factor of 25x for Line Intersection Problem and 10x for Point Containment Problem which increases exponentially as the data size increases in both indexed and nonindexed operations. Given these results NoSQL databases may be better suited for simultaneous multiple-user query systems including Web-GIS and mobile-GIS. Further studies are required to understand the full potential of NoSQL databases across various geometries and spatial query types.
  • Publication
    Towards OSGeo Best Practices for Scientific Software Citation: Integration Options for Persistent Identifiers fn OSGeo Project Repositories
    Löwe, Peter; Neteler, Markus; Goebel, Jan; Tullney, Marco
    As a contribution to the currently ongoing larger effort to establish Open Science as best practices in academia, this article focuses on the Open Source and Open Access tiers of the Open Science triad and community software projects. The current situation of research software development and the need to recognize it as a significant contribution to science is introduced in relation to Open Science. The adoption of the Open Science paradigms occurs at different speeds and on different levels within the various fields of science and crosscutting software communities. This is paralleled by the emerging of an underlying futuresafe technical infrastructure based on open standards to enable proper recognition for published articles, data, and software. Currently the number of journal publications about research software remains low in comparison to the amount of research code published on various software repositories in the WWW. Because common standards for the citation of software projects (containers) and versions of software are lacking, the FORCE11 group and the CodeMeta project recommending to establish Persistent Identifiers (PIDs), together with suitable metadata setss to reliably cite research software. This approach is compared to the best practices implemented by the OSGeo Foundation for geospatial community software projects. For GRASS GIS, a OSGeo project and one of the oldest geospatial open source community projects, the external requirements for DOI-based software citation are compared with the projects software documentation standards. Based on this status assessment, application scenarios are derived, how OSGeo projects can approach DOI-based software citation, both as a standalone option and also as a means to foster open access journal publications as part of reproducible Open Science.
  • Publication
    Volume Introduction Letter
    Köbben, Barend
    This Conference Proceedings is a collection of outstanding papers submitted to the Academic Program of the International Conference for Free and Open Source Software for Geospatial (FOSS4G), 17th to 21st September 2013 in Nottingham, U.K.
  • Publication
    Evaluation Of An Open-Source Collaborative WebGIS Prototype In Risk Management With Students
    Aye, Zar Chi; Charrière, Marie; Olyazadeh, Roya; Derron, Marc-Henri; Jaboyedoff, Michel
    Over the past decades, advancements in web services and web-based geospatial technologies have led to increasing delivery, access and analysis of rich spatial information over the web. With the use of open access data and open-source technology, it has become possible to make better, transparent and informed decisions for policy and decision makers. Under the framework of the European Marie Curie CHANGES project, a prototype web-based collaborative decision support platform was developed for the evaluation and selection of risk management strategies, mainly targeting flood and landslide hazards. The design of the conceptual framework was based on the initial feedback and observations obtained from field visits and stakeholder meetings of the case study areas of the project. A three-tier client-server architecture backed up by Boundless (OpenGeo) was applied with its client side development environment for rapid prototyping. The developed prototype was tested with university students to obtain feedback on the conceptual and technical aspects of the platform as well as to analyze how the application of interactive tools in the exercise could assist students in studying and understanding risk management. During the exercise, different roles (authorities, technicians, community) were assigned to each group of students for identification and selection of risk mitigation measures in the study area: Cucco village located in MalborghettoValbruna commune of North- Eastern Italy. Data were collected by means of written feedback forms on specific aspects of the platform and the exercise. A subsequent analysis of the feedback reveals that students with previous experience in GIS (Geographical Information Systems) responded positively and showed interests in performing exercises with such kinds of interactive tools for learning, compared to the ones with fewer or no GIS experience. These results also show that the prototype is useful and supportive as a decision support tool in risk management while userfriendliness, interactivity and practical aspects of the platform could be further improved.
  • Publication
    WebGIS-based Natural Disaster Information System of China
    Du, Jia; Yang, Yaping; Yue, Xiafang; Jing, Wenlong
    We have constructed China natural disaster information system utilizing open source WebGIS framework. Through comparisons and researches on different WebGIS system structures, implementation patterns, spatial database management patterns and several popular software, open source WebGIS platform MapServer, PostgreSQL+PostGIS (spatial database and spatial data engine), client-side browser framework openLayer were used. This system have basic function of web information publishing, spatial data storage and management, and it collects natural disaster information that have been publishing on the internet through grabing internet information, and based on the analysis to the text information, different kinds of natural disaster information databases were constructed. Additionally, locations of the disaster occurred were combined to provide map services, and the system is able to meet multi-user access issues, and have functions of thematic mapping, query and statistics, charting and output, et.al.
  • Publication
    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.