Search results

Jump to navigation Jump to search
  • Update: (2015-07-24) A Project Steering Committee has been formed. Management decisions a In early 2015, OTB set up an official Project Steering committee (PSC) to provide high le
    8 KB (1,191 words) - 07:08, 7 April 2017
  • ...r of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code A ...o evaluate the projects based on the timeline provided. By means of weekly reports, we keep track of their progress, and let the students adjust the timeline
    8 KB (1,199 words) - 17:03, 22 January 2018
  • ...r of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code A ...o evaluate the projects based on the timeline provided. By means of weekly reports, we keep track of their progress, and let the students adjust the timeline
    8 KB (1,214 words) - 03:37, 6 February 2019
  • ...mapserver and Geonetwork which provided public access to research data and reports. ...mapserver and Geonetwork which provided public access to research data and reports.
    5 KB (759 words) - 18:06, 25 January 2017
  • |+ '''PDX-OSGEO Meetings, third Wednesdays, for 2015, 6:00-7:30 PM''' ...o/posts/2015/01/20/anatomy-of-a-travel-map/ | http://justinmiller.io/posts/2015/01/20/anatomy-of-a-travel-map/ ]]
    9 KB (1,311 words) - 17:50, 26 January 2018
  • * Past conference reports are detailed at [[Past FOSS4G Reports]] ...er:Maria | Maria Brovelli]] - member since March 2016 (Chair FOSS4G Europe 2015)
    13 KB (1,871 words) - 04:24, 25 March 2024
  • '''SOTM - OSGeo CoC Implementation BoF Session - 5 June 2015 - Checklists to create: (1) reporting guidelines (2) incident reports
    3 KB (498 words) - 15:39, 5 August 2015
  • :* Bug reports for other OSGEO software ...esentation/foss4geu2015.html#/ spoke about open data at FOSS4GE in Como in 2015], has attended the Danish "Kortdage"-conference since 2008 (with [http://ww
    4 KB (542 words) - 01:28, 17 October 2017
  • ...r of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code A ...entioned, we keep track of the project's progress by evaluating the weekly reports. Based on this, the students can adjust the timeline and their weekly commi
    10 KB (1,449 words) - 23:41, 15 May 2020
  • OSGeo participated in Google Summer of Code 2015 with 13 projects, all successful: * GRASS GIS - Matej Krejci: [https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata Improved Metadata for GRASS GIS]
    20 KB (2,988 words) - 11:29, 11 February 2016
  • ...s, apps, publications. All software developed is FOSS4G (checked November 2015) ...n tracking system for lynx, wolverine, brown bear and wolf (checked August 2015)
    10 KB (1,480 words) - 05:13, 4 August 2016
  • ...r of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code A ...entioned, we keep track of the project's progress by evaluating the weekly reports. Based on this, the students can adjust the timeline and their weekly commi
    11 KB (1,554 words) - 11:52, 15 February 2022
  • *We'll explore the possibility of hosing FOSS4G 2015 in Korea with other GIS related society like KSIS(Korean Spatial Informatio [[Category: Reports 2011]]
    3 KB (497 words) - 02:49, 11 August 2014
  • ...r of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code A ...e Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly c
    11 KB (1,617 words) - 08:03, 15 March 2022
  • ...r of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code A ...e Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly c
    11 KB (1,622 words) - 09:00, 25 February 2023
  • ...r of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code A ...e Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly c
    11 KB (1,627 words) - 05:32, 25 February 2024
  • ...page to jot down and develop any good idea for the [[Google Summer of Code 2015]] program with gvSIG project. Please, use the gvSIG mailing lists for discu ...nd the capabilities of Jython scripting in gvSIG Desktop as geoprocessing, reports,...
    4 KB (536 words) - 02:11, 27 March 2015
  • Date: May 2015 ...sed, there was extensive [https://lists.osgeo.org/pipermail/conference_dev/2015-June/003048.html debate] in the OSGeo community as to whether a slide with
    16 KB (2,421 words) - 15:52, 16 October 2015
  • ...considering telecommunication data from "Telecom Italia Big Data Challenge 2015". My idea is to create first the visualization environment and further impo == Weekly Reports ==
    12 KB (2,016 words) - 01:07, 10 September 2016
  • ...(camera ready). Charlie has the template. He modified the one from FOSS4G-2015. ** Venka suggested we send a remainder to all project PSC to submit their reports by end of Oct. 2017 and include their budget request for 2018 in the report
    5 KB (817 words) - 15:01, 30 October 2017

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)