Skip to content

OSGeo Live Application

Jump to bottom Edit New page
Levi John Wolf edited this page Jul 24, 2015 · 1 revision

  1. Please describe your application.

    • What is its name?

      PySAL, the Python Spatial Analysis Library.

    • What is the home page URL?

      https://pysal.github.io

    • Which OSI approved Open Source Licence is used?

      PySAL is licensed under the BSD 3-Clause license

    • What does the application do and how does it add value to the GeoSpatial stack of software?

      PySAL is an open source cross-platform library of spatial analysis functions written in Python. It is intended to support the development of high level applications for spatial analysis. It is primarily concerned with spatial analysis of vector data, and offers a wide variety of analytical techniques. It currently fills an uncontested niche in spatial analytics of vector data.

    • Does the application make use of OGC standards? Which versions of the standards? Client or server? You may wish to add comments about how standards are used.

    • What language is it written in?

      Python 2.*

    • Which version of the application should be included in the next OSGeo-Live release?

      Pysal 1.10

  2. Stability is very important to us on OSGeo-Live. If a new user finds a bug in one application, it will tarnish the reputation of all other OSGeo-Live applications as well. (We pay most attention to the following answers):

    • If risk adverse organisations have deployed your application into production, it would imply that these organisations have verified the stability of your software. Has the application been rolled out to production into risk (ideally risk adverse) organisations? Please mention some of these organisations?

    • Open HUB provides metrics to help assess the health of a project. Eg: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html Could you please ensure that your project is registered with Open HUB, and Open HUB has been updated to reference the correct code repository(s) for your project. What is the Open HUB URL for your project?

      Yes, PySAL has been on OpenHub for a while.

    • What is the size of the user community? You can often answer this by mentioning downloads, or describing a healthy, busy email list?

    • What is the size of your developer community?

      There are 20 contributors.

    • Do you have a bug free, stable release?

      No software anywhere is bug free. But, our tracking is fast and time to close issues is rather low.

    • Please discuss the level of testing that your project has gone through.

      We use continuous integration through TravisCI and have 86% test coverage in PySAL 1.10.

    • How long has the project has had mature code.

      Since version 1.0.

  3. OSGeo-Live is targeted at applications that people can use rather than libraries.

    • Does the application have a user interface (possibly a command line interface) that a user can interact with?

      Yes. The library has a rather well developed python CLI.

  4. If your project is involved with OSGeo Incubation, or has been selected to be presented at FOSS4G, then please mention this.

  5. Who will serve as liaison between OSGeo-Live and PySAL?

  6. OSGeo is Ubuntu-based. How will you install the package?

    The package is pip-installable, as well as being in the Anaconda Scientific Python Distribution. Pip is probably the preferred method of installing PySAL for this use case.

  7. What are the system requirements?

    • OSGeo-Live is memory and disk constrained. Can the application run in 512 Meg of RAM?

      Yes.

    • How much disk space will be required to install the application and a suitable example application?

    • We aim to reduce disk space by having all applications make use of a common dataset. We encourage applications to make use of the example datasets already installed

      PySAL uses significant amounts of example datasets in its doctests. The example datasets provided by the OSGeo-Live distribution are very nice, but are sadly not quite within the scope of the package's functionality. Including a subset of examples from PySAL's standard examples would be simple.

    • Each OSGeo-Live application requires a Project Overview available under a CC By and a Quickstart available under a CC By-SA license. (You may release under a second license as well). Will you produce this?

    • In past releases, we have included Windows and Mac installers for some applications. It is likely we won't have space for these in future releases. However, if there is room, would you be wishing to include Windows and/or Mac installers?

      We currently rely on pip for installation, but did implement builds for specific operating systems in the past. So, we would have to see if Appveyor or a similar release framework for OSX would be feasible.

Add a custom sidebar
Clone this wiki locally