[Live-demo] [eoxserver-dev] EOxServer - an Open Source WMS/WCS for Earth Observations & OSGeo-Live
Alex Mandel
tech_dev at wildintellect.com
Sun May 27 15:02:30 PDT 2012
Yes, there is a plan to do so (I've discussed it with the geonode devs)
but it will likely not be ready for 6.0. They have a custom auth code
which needs to be ported to the new plugin system in geoserver 2.2+. I'm
hoping it will be ready for 6.5.
Thanks,
Alex
On 05/27/2012 02:43 PM, Angelos Tzotsos wrote:
> I agree that Geonode would be a valuable addition to osgeo live. Is
> there a plan to merge custom Geoserver code to the mainstream version?
> Perhaps then it would be easier to include it in the disk.
>
> On 05/27/2012 09:48 PM, Alex Mandel wrote:
>> Along that same tangent is Geonode, which I haven't been pushing for
>> osgeo live yet because of some dependency issues (requires a custom
>> geoserver not the stock one).
>>
>> That's:
>> Geoext
>> Django
>> Geoserver
>> Geonetwork/Pycsw
>> Postgis
>>
>> It's primary goal is to let users upload data sets, fill out minimal
>> metadata, then allow it all to be remixed in web maps and shared out via
>> WMS, WFS, Tiles, etc.
>>
>> Geonode comes in large part from work by OpenGeo and some collaborators.
>> Will be interesting seeing how all these play out.
>>
>>
>> Thanks,
>> Alex
>>
>>
>> On 05/26/2012 06:14 AM, Angelos Tzotsos wrote:
>>> Stephan,
>>>
>>> I would suggest having a look at pycsw [1], that could be integrated in
>>> your django application and offer CSW (INSPIRE compliant) service.
>>>
>>> Best regards,
>>> Angelos
>>>
>>> [1] http://pycsw.org/
>>>
>>>
>>> On 05/26/2012 03:41 PM, Stephan Meißl wrote:
>>>> Cameron,
>>>>
>>>> up to now I was not aware of SISS as such although I heard of all the
>>>> individual projects. One could say that the idea of EOxServer
>>>> originates
>>>> from the C tribe where we're involved in MapServer for example
>>>> responsible for the WCS 2.0 implementation. On the other side the idea
>>>> was to have a lightweight metadata handling layer by using Python and
>>>> Django as framework. Thus the main software stack behind EOxServer is
>>>> build of Django, MapServer, GDAL, and SpatiaLite or PostGIS somehow
>>>> similar to SISS but using different software.
>>>>
>>>> One difference that I see is that we don't have a catalog as such but
>>>> rather use metadata in WCS and WMS directly via the EO extensions.
>>>>
>>>> I heard about HollowWorld and FullMoon in the frame of my OGC work when
>>>> it comes to data modeling e.g. in the specification of a new standard.
>>>> However, I've never used them but would be interested to better
>>>> understand them.
>>>>
>>>> In summary EOxServer is strongly focused on EO data (e.g. EO
>>>> metadata is
>>>> mandatory) and the server side of OGC 's WMS and WCS. As far as I
>>>> understand both SISS and EOxServer have their specialized areas and
>>>> strengths and could benefit from each other.
>>>>
>>>> cu
>>>> Stephan
>>>>
>>>>
>>>> On Sat, 2012-05-26 at 09:00 +1000, Cameron Shorter wrote:
>>>>> Some of the people involved in Australian/New Zealand Earth
>>>>> Observations
>>>>> (Andrew, RobA, Bruce, Jim, RobertG, David),
>>>>>
>>>>> As per below, Stephan has proposed that EOxServer be included in the
>>>>> OSGeo-Live DVD distribution, which will provide valuable marketing
>>>>> reach
>>>>> for EOxServer. I'm forwarding this on to each of you as I'm interested
>>>>> to understand whether the Australian Bureau of Meteorology (BOM) and
>>>>> CSIRO are aware of EOxServer. Have you considered using EOxServer?
>>>>> What have been your conclusions about such considerations?
>>>>> How does EOxServer compare against the SISS stack?
>>>>>
>>>>> Stephan,
>>>>> Note that BOM/CSIRO have been investing heavily in what they are
>>>>> calling
>>>>> the "Spatial Information Services Stack" (SISS), which consists of:
>>>>> PostGIS
>>>>> GeoServer
>>>>> GeoNetwork
>>>>> THREDDS
>>>>> HollowWorld
>>>>> FullMoon
>>>>> https://www.seegrid.csiro.au/wiki/Siss/SpatialInformationServicesStackHandbook
>>>>>
>>>>>
>>>>>
>>>>> Stephan,
>>>>> I'm interested to know whether participants in the EOxServer have been
>>>>> in touch with programs working on the SISS stack?
>>>>> Are there any areas for collaboration?
>>>>> What are the benefits of EOxServer over SISS?
>>>>>
>>>>>
>>>>> On 26/05/2012 1:21 AM, Stephan Meißl wrote:
>>>>>> On Mon, 2012-04-30 at 21:27 +1000, Cameron Shorter wrote:
>>>>>>> We are starting to build the 6.0 OSGeo-Live DVD which will be
>>>>>>> released
>>>>>>> in September 2012, ready for FOSS4G 2012 as well as many other
>>>>>>> spatial
>>>>>>> conferences. This upcoming version will be built upon the stable
>>>>>>> Xubuntu 12.04 Long Term Support (LTS) release. Documentation will be
>>>>>>> translated into eight languages, now also including Chinese and
>>>>>>> Catalan.
>>>>>>>
>>>>>>>
>>>>>>> Any new applications?
>>>>>>>
>>>>>>> We would like to hear from anyone wishing to add new projects to
>>>>>>> OSGeo-Live, anyone wishing to extend or add extra translations, or
>>>>>>> anyone who has ideas on how we should shape the upcoming release.
>>>>>>> ...
>>>>>> Hi Cameron,
>>>>>>
>>>>>> we'd like to propose the inclusion of the EOxServer [1] project in
>>>>>> OSGeo-Live. Three weeks ago we released our version 0.2.0 and even
>>>>>> though it has a rather low version number we think it would add some
>>>>>> value to OSGeo-Live. However, as this is a proposal and we're surely
>>>>>> not
>>>>>> aware of all policies we fully understand different opinions. It
>>>>>> would
>>>>>> be great to hear your advice.
>>>>>>
>>>>>> Here are the details about EOxServer following the wiki at [2]:
>>>>>>
>>>>>> Name: EOxServer
>>>>>> URL: http://eoxserver.org
>>>>>> License: MIT
>>>>>> Description and value added:
>>>>>>
>>>>>> EOxServer's mission is to provide an Open Source software
>>>>>> framework to
>>>>>> ease the online provision of big Earth Observation data archives via
>>>>>> Open Standard services for efficient exploitation by users.
>>>>>> * Open Source: MIT-style license
>>>>>> * software framework: Entirely based on Open Source (Python,
>>>>>> MapServer, Django, GDAL, etc.)
>>>>>> * ease online provision: Admin GUI and command line data
>>>>>> registration
>>>>>> * big Earth Observation data archives: Operators register
>>>>>> existing
>>>>>> raster data archives
>>>>>> * Open Standard services: Open in the sense of freely
>>>>>> available;
>>>>>> Open Geospatial Consortium (OGC); WMS, WCS, EO-WMS, EO-WCS
>>>>>> * efficient exploitation by users: User defined sub-setting;
>>>>>> view
>>>>>> and download
>>>>>>
>>>>>> OGC standards: WMS, WCS, EO-WMS, EO-WCS, WCS-T; All versions are
>>>>>> supported that are supported in MapServer. However, focus is on
>>>>>> WCS 2.0
>>>>>> and WMS 1.3 and their respective Earth Observation (EO) application
>>>>>> profiles.
>>>>>>
>>>>>> Language: Python and a small bit C
>>>>>>
>>>>>> Version: 0.2.0 (maybe 0.2.1 if we need to change something for
>>>>>> example
>>>>>> the packaging)
>>>>>>
>>>>>> Risk adverse organisations: EOxServer has been partly funded by the
>>>>>> European Space Agency (ESA) which is currently evaluating the
>>>>>> operational use. Also some European Commission supported projects are
>>>>>> evaluating the usage of EOxServer.
>>>>>>
>>>>>> User community: There is a user mailing list [3] but not yet much
>>>>>> traffic. According to the Python package index [4] there have been 96
>>>>>> downloads in the last three weeks and according to the website
>>>>>> statistics for eoxserver.org there have been around 3400 unique
>>>>>> visitors
>>>>>> with about 7800 visits in 2012.
>>>>>>
>>>>>> Developer community: Again we have a mailing list [3] with a bit more
>>>>>> traffic and nine committers. Please see ohloh [5] for more
>>>>>> statistics.
>>>>>>
>>>>>> Stable release: Our latest stable release is 0.2.0.
>>>>>>
>>>>>> Testing: We make extensive usage of Python's and Django's unit test
>>>>>> framework and have about 900 tests included in our autotest instance.
>>>>>> Additionally there are some selenium based tests of the web client
>>>>>> and
>>>>>> admin gui.
>>>>>>
>>>>>> Mature code: Again please see ohloh [5] for these statistics.
>>>>>>
>>>>>> User interface: In EOxServer we distinct between two user roles:
>>>>>> operators and users. Operators can register data and control the
>>>>>> server
>>>>>> via the command line and the Django provided admin gui. Users can
>>>>>> explore the available data via a simple web client based on
>>>>>> OpenLayers
>>>>>> and jQuery.
>>>>>>
>>>>>> Presentation at FOSS4G: There have been talks at the German speaking
>>>>>> FOSSGIS and the recent FOSS4G-CEE conference. Please see the
>>>>>> EOxServer
>>>>>> documentation [6] for a list of presentations.
>>>>>>
>>>>>> Volunteers for liaising: Stephan Meissl and Stephan Krause
>>>>>>
>>>>>> Application installation: Since EOxServer is a Python application the
>>>>>> recommended way of installation is using pip. However, since we're
>>>>>> using
>>>>>> setuptools we can easily provide .deb packages if needed.
>>>>>>
>>>>>> 512 Meg of RAM: Yes, EOxServer can be run in 512MB of memory.
>>>>>> However,
>>>>>> the image rendering will be limited to the capabilities of MapServer
>>>>>> and
>>>>>> GDAL.
>>>>>>
>>>>>> Disk space: The current base package extracts to 22MB but includes
>>>>>> 15MB
>>>>>> of documentation. Our autotest package which we'd propose for a
>>>>>> demonstration (see below) extracts to 130MB but 90MB of this are
>>>>>> expected results for the tests which can be safely ignored. If
>>>>>> needed I
>>>>>> believe we can shrink the test data to under 10MB to still provide a
>>>>>> meaningful demonstration. Usually we also copy the OGC schemas to
>>>>>> speed
>>>>>> up XML validation but this might not be necessary here. The packages
>>>>>> are
>>>>>> available here [7].
>>>>>>
>>>>>> Other dataset: We have to explore the already included demonstration
>>>>>> data but at a first glance we think we need to include some EO
>>>>>> data in
>>>>>> order to show off the capabilities of EOxServer.
>>>>>>
>>>>>> Project Overview and Quickstart: Will of course be produced and
>>>>>> provided.
>>>>>>
>>>>>> Windows and/or Mac installers: Not needed.
>>>>>>
>>>>>>
>>>>>> Thanks for your consideration,
>>>>>> Stephan on behalf of the EOxServer Team
>>>>>>
>>>>>> [1] http://eoxserver.org
>>>>>> [2] http://wiki.osgeo.org/wiki/Live_GIS_Disc_Apply
>>>>>> [3] http://eoxserver.org/doc/en/users/mailing_lists.html
>>>>>> [4] http://pypi.python.org/pypi/EOxServer/
>>>>>> [5] https://www.ohloh.net/p/eoxserver/
>>>>>> [6] http://eoxserver.org/doc_trunk/en/users/presentations.html
>>>>>> [7] http://eoxserver.org/wiki/Download
>>>>>>
>>>>>>
>>>>
>>>
>> _______________________________________________
>> Live-demo mailing list
>> Live-demo at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/live-demo
>> http://live.osgeo.org
>> http://wiki.osgeo.org/wiki/Live_GIS_Disc
>
>
More information about the Live-demo
mailing list