[Osgeo4w-trac] Re: [osgeo4w] #179: Add Python RTree to OSGEO4W

David Fawcett david.fawcett at gmail.com
Wed Sep 22 13:08:07 EDT 2010


Howard,

Thanks for the fast reply.  I understand your concern about keeping
the version current in OSGEO4W.

My goal is to have a relatively simple way to install Shapely and
Rtree in a way that they can be used with the gdal module.

It has been a few months since I attempted this, but as I remember it,
the problem with the Windows installer for Rtree was that it doesn't
give you an option for which Python install to use.  In the case of my
work machine, there is the primary Python 2.5 install and the Python
that is part of OSGEO4W.  The Rtree installer put rtree into the
primary Python install, which made it difficult to use gdal from the
OSGEO4W install to read in WKB features from an external data source.

It sounds like easy_install could be a way to get around the issues
with the installer.

I am OK with not including Rtree in OSGEO4W if I can document a way to
use Rtree and Shapely with the Python modules in OSGEO4W.  I would be
happy to write up the recipe on a wiki some place if I can get it to
work.

David

On Wed, Sep 22, 2010 at 9:05 AM, OSGeo4W <trac_osgeo4w at osgeo.org> wrote:
> #179: Add Python RTree to OSGEO4W
> -------------------------+--------------------------------------------------
> Reporter:  davidfawcett  |       Owner:  osgeo4w-dev@…
>    Type:  enhancement   |      Status:  new
> Priority:  minor         |   Component:  Package
>  Version:                |    Keywords:  Rtree
> -------------------------+--------------------------------------------------
>
> Comment(by hobu):
>
>  David,
>
>  I think it would be more productive to make the Rtree distribution on PyPI
>  easy_install'able instead of putting a copy on osgeo4w that very likely is
>  going to get out of date.  What would you think of that?
>
>  Alternatively, I could put a windows Rtree egg on PyPI that users could
>  download to their home directories and then point at with PYTHONPATH.  I
>  know neither of these solutions is overly convienent for someone trying to
>  have consistent software to teach a lab,  but I'm concerned that after a
>  single release, I'll totally forget to update osgeo4w again.  If we modify
>  the distribution stuff to push what's needed to PyPI it will always be up-
>  to-date.
>
>  Howard
>
> --
> Ticket URL: <http://trac.osgeo.org/osgeo4w/ticket/179#comment:1>
> OSGeo4W <http://trac.osgeo.org/osgeo4w>
> OSGeo4W is the Windows installer for the OSGeo stack.
>


More information about the Osgeo4w-trac mailing list