Nabble - PrimaGIS

Fwd: [geos-devel] 3.1 vs 3.2

2009-12-09T02:54:32Z

Can anybody confirm that Shapely reaps better performance with the
GEOS trunk?

Begin forwarded message:

> From: strk <strk@...>
> Date: December 9, 2009 9:59:04 AM CEST
> To: GEOS Development List <geos-devel@...>
> Subject: Re: [geos-devel] 3.1 vs 3.2
> Reply-To: GEOS Development List <geos-devel@...>
>
> On Tue, Dec 08, 2009 at 02:12:38PM -0800, Paul Ramsey wrote:
>> Not sure what this means, but:
>
>> ---- 3.1 ---- > ---- 3.2 ----
>>>
>> Files: 20 > Files: 58
>> Tests: 2216 > Tests: 3582
>> Failed: 0 > Failed: 0
>> Succeeded: 2216 > Succeeded: 3582
>> PASS: testrunner > PASS: testrunner
>>>
>> real 0m29.194s > real 0m11.558s
>> user 0m24.750s > user 0m10.630s
>> sys 0m1.489s > sys 0m0.230s
>
> Much more tests in less of half the time !
> It seems to mean 3.2.0 rocks :)
>
> --strk;
>
> Free GIS & Flash consultant/developer () ASCII Ribbon Campaign
> http://foo.keybit.net/~strk/services.html /\ Keep it simple!
> _______________________________________________
> geos-devel mailing list
> geos-devel@...
> http://lists.osgeo.org/mailman/listinfo/geos-devel

--
Sean

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: broken link

2009-12-09T02:02:31Z

Thanks.

On Dec 8, 2009, at 9:29 PM, Stefano Costa wrote:

> http://trac.gispython.org/lab/wiki/GeoJson has a broken link which
> should instead point to geojson.org, I think.
>
> Best regards,
> steko
>
> --
> Stefano Costa
> http://www.iosa.it/ Open Archaeology
> _______________________________________________
> Community mailing list
> Community@...
> http://lists.gispython.org/mailman/listinfo/community

--
Sean

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

broken link

2009-12-08T12:27:32Z

http://trac.gispython.org/lab/wiki/GeoJson has a broken link which
should instead point to geojson.org, I think.

Best regards,
steko

--
Stefano Costa
http://www.iosa.it/ Open Archaeology

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

signature.asc (205 bytes) Download Attachment

Re: rtree delete

2009-12-08T07:18:15Z

On Dec 2, 2009, at 10:12 AM, Andrew Byrd wrote:

> How about this... a little repetitive but I find it clearer.
>
> Original:
> :param coordinates: sequence or array
> This may be an object that satisfies the numpy array
> protocol, providing the index's dimension * 2 coordinate
> pairs representing the mink and maxk coordinates in
> each dimension defining the bounds of the query window.
>
> Proposed change:
> :param coordinates: sequence or array
> Dimension * 2 coordinate pairs, representing the min
> and max coordinates in each dimension of the item to be
> deleted from the index. Their ordering will depend on the
> index's :attr:`interleaved` data member.
> These are not the coordinates of a space containing the
> item, but those of the item itself. Together with the
> id parameter, they determine which item will be deleted.
> This may be an object that satisfies the numpy array protocol.

applied. http://trac.gispython.org/lab/changeset/1509 Thanks!

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: OWSLib - Access WMS attribution info

2009-12-07T00:46:16Z

Hi David,

Many thanks for the patch. I will look into putting this into the trunk.

re: the tests - yes they are broken... I'd better look into that. Actually I think in most cases the servers have changed their responses and the tests not updated to match.

Cheers,
Dom

-----Original Message-----
From: community-bounces@... on behalf of David Winslow
Sent: Fri 04/12/2009 18:45
To: community@...
Subject: Re: [Community] OWSLib - Access WMS attribution info

On 12/03/2009 12:20 PM, David Winslow wrote:

> Hi all,
>
> For a project I'm working on, I'd like to access the Attribution field
> on some layers in a WMS capabilities document. I'd love to use OWSLib
> (looks like it would be a lot easier to use than parsing the XML
> directly), but when I try to retrieve the Attribution I just get an
> empty string (or None if there is no attribution for the layer.) I
> was expecting an object with the title, logo URL, and link for the
> Attribution.
>
> Digging into the code a bit I see that Attribution is parsed in
> exactly the same way as Name and Title, so it will always be a
> string. Would it be reasonable to change this to an object or
> dictionary with the fields I mentioned above?
>
> I would be happy to put together a patch if there's interest.
>
> --
> David Winslow
> OpenGeo - http://opengeo.org/

Ignoring some test failures, here is a patch for the attribution
feature. Attribution is presented like so:

>>> wms['opengeo:poi'].attribution
{'url':
'http://svn.codehaus.org/geoserver/trunk/data/release/data/',
'logo_size': (353, 112), 'logo_url':
'http://geoserver.org/s/1518/25/0.1/_/download/resources/com.atlassian.confluence.themes.geoserver%3Ageoserver/chrome/geoserver-logo.png',
'title': 'GeoServer Sample Data'}

I am attaching the full patch.

--
David Winslow
OpenGeo - http://opengeo.org/

--
Scanned by iCritical.
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: OWSLib - Access WMS attribution info

2009-12-04T10:45:39Z

On 12/03/2009 12:20 PM, David Winslow wrote:

Ignoring some test failures, here is a patch for the attribution

feature. Attribution is presented like so:

>>> wms['opengeo:poi'].attribution
{'url':
'http://svn.codehaus.org/geoserver/trunk/data/release/data/',
'logo_size': (353, 112), 'logo_url':
'http://geoserver.org/s/1518/25/0.1/_/download/resources/com.atlassian.confluence.themes.geoserver%3Ageoserver/chrome/geoserver-logo.png',
'title': 'GeoServer Sample Data'}

I am attaching the full patch.

--
David Winslow
OpenGeo - http://opengeo.org/

Index: owslib/wms.py
===================================================================
--- owslib/wms.py (revision 1506)
+++ owslib/wms.py (working copy)
@@ -308,7 +308,7 @@
self.parent = parent
if elem.tag != 'Layer':
raise ValueError('%s should be a Layer' % (elem,))
- for key in ('Name', 'Title', 'Attribution'):
+ for key in ('Name', 'Title'):
val = elem.find(key)
if val is not None:
setattr(self, key.lower(), val.text.strip())
@@ -333,7 +333,23 @@
elif self.parent:
if hasattr(self.parent, 'boundingBox'):
self.boundingBox = self.parent.boundingBox
-
+
+ attribution = elem.find('Attribution')
+ if attribution is not None:
+ self.attribution = dict()
+ title = attribution.find('Title')
+ url = attribution.find('OnlineResource')
+ logo = attribution.find('LogoURL')
+ if title is not None:
+ self.attribution['title'] = title.text
+ if url is not None:
+ self.attribution['url'] = url.attrib['{http://www.w3.org/1999/xlink}href']
+ if logo is not None:
+ self.attribution['logo_size'] = (int(logo.attrib['width']), int(logo.attrib['height']))
+ self.attribution['logo_url'] = logo.find('OnlineResource').attrib['{http://www.w3.org/1999/xlink}href']
+
+
+
b = elem.find('LatLonBoundingBox')
if b is not None:
self.boundingBoxWGS84 = (
Index: tests/wms_GeoServerCapabilities.txt
===================================================================
--- tests/wms_GeoServerCapabilities.txt (revision 0)
+++ tests/wms_GeoServerCapabilities.txt (revision 0)
@@ -0,0 +1,92 @@
+Imports
+
+ >>> from owslib.wms import WebMapService
+
+Fake a request to a WMS Server using saved doc from GeoServer, using a subset
+of the sample data distributed with the installer.
+http://localhost:8080/geoserver/wms?request=GetCapabilities
+
+ >>> xml = open_file('geoserver-wms-cap.xml', 'r').read()
+ >>> wms = WebMapService('url', version='1.1.1', xml=xml)
+
+Test capabilities
+
+ >>> wms.identification.type
+ 'OGC:WMS'
+
+ >>> wms.identification.title
+ 'My GeoServer WMS'
+
+ >>> wms.identification.abstract
+ 'This is a description of your Web Map Server.'
+
+ >>> wms.provider.url
+ 'http://localhost:8080/geoserver/wms'
+
+ >>> wms.identification.keywords
+ ['WFS', 'WMS', 'GEOSERVER']
+
+ >>> p = wms.provider.contact
+ >>> p.name
+ >>> p.email
+
+Test available content layers
+
+ >>> wms.contents.keys()
+ [None, 'opengeo:poi']
+
+
+ >>> [wms[layer].title for layer in wms.contents]
+ ['My GeoServer WMS', 'Points of Interest']
+
+
+Test single item accessor
+
+ >>> wms['opengeo:poi'].title
+ 'Points of Interest'
+
+ >>> wms['opengeo:poi'].boundingBox
+ (-74.012, 40.707999999999998, -74.001999999999995, 40.719999999999999, 'EPSG:4326')
+
+ >>> wms['opengeo:poi'].boundingBoxWGS84
+ (-74.012, 40.707999999999998, -74.001999999999995, 40.719999999999999)
+
+ >>> wms['opengeo:poi'].crsOptions
+ ['EPSG:4326']
+
+ >>> wms['opengeo:poi'].attribution
+ {'url': 'http://svn.codehaus.org/geoserver/trunk/data/release/data/', 'logo_size': (353, 112), 'logo_url': 'http://geoserver.org/s/1518/25/0.1/_/download/resources/com.atlassian.confluence.themes.geoserver%3Ageoserver/chrome/geoserver-logo.png', 'title': 'GeoServer Sample Data'}
+
+ >>> wms['opengeo:poi'].styles
+ {'point': {'legend': 'http://localhost:8080/geoserver/wms?request=GetLegendGraphic&format=image%2Fpng&width=20&height=20&layer=poi', 'title': 'A boring default style'}}
+
+Expect a KeyError for invalid names
+
+ >>> wms['utterly bogus'].title
+ Traceback (most recent call last):
+ ...
+ KeyError: 'No content named utterly bogus'
+
+Test operations
+
+ >>> [op.name for op in wms.operations]
+ ['GetCapabilities', 'GetMap', 'GetFeatureInfo', 'DescribeLayer', 'GetLegendGraphic']
+
+ >>> wms.getOperationByName('GetMap').methods
+ {'Get': {'url': 'http://localhost:8080/geoserver/wms?SERVICE=WMS&'}}
+
+ >>> wms.getOperationByName('GetMap').formatOptions
+ ['image/png', 'application/atom xml', 'application/atom+xml', 'application/openlayers', 'application/pdf', 'application/rss xml', 'application/rss+xml', 'application/vnd.google-earth.kml', 'application/vnd.google-earth.kml xml', 'application/vnd.google-earth.kml+xml', 'application/vnd.google-earth.kmz', 'application/vnd.google-earth.kmz xml', 'application/vnd.google-earth.kmz+xml', 'atom', 'image/geotiff', 'image/geotiff8', 'image/gif', 'image/jpeg', 'image/png8', 'image/svg', 'image/svg xml', 'image/svg+xml', 'image/tiff', 'image/tiff8', 'kml', 'kmz', 'openlayers', 'rss']
+
+Test exceptions
+
+ >>> wms.exceptions
+ ['application/vnd.ogc.se_xml', 'application/vnd.ogc.se_inimage']
+
+Lastly, test the getcapabilities method
+
+# >>> wms = WebMapService('http://wms.telascience.org/cgi-bin/ngBM_wms?', version='1.1.1')
+# >>> xml = wms.getcapabilities().read()
+# >>> xml.find('<WMT_MS_Capabilities version="1.1.1">') > 0
+# True
+
Index: tests/geoserver-wms-cap.xml
===================================================================
--- tests/geoserver-wms-cap.xml (revision 0)
+++ tests/geoserver-wms-cap.xml (revision 0)
@@ -0,0 +1,174 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE WMT_MS_Capabilities SYSTEM "http://localhost:8080/geoserver/schemas/wms/1.1.1/WMS_MS_Capabilities.dtd">
+<WMT_MS_Capabilities version="1.1.1" updateSequence="0">
+ <Service>
+ <Name>OGC:WMS</Name>
+ <Title>My GeoServer WMS</Title>
+ <Abstract>This is a description of your Web Map Server.</Abstract>
+ <KeywordList>
+ <Keyword>WFS</Keyword>
+ <Keyword>WMS</Keyword>
+ <Keyword>GEOSERVER</Keyword>
+ </KeywordList>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms"/>
+ <ContactInformation>
+ <ContactPersonPrimary>
+ <ContactPerson/>
+ <ContactOrganization/>
+ </ContactPersonPrimary>
+ <ContactPosition/>
+ <ContactAddress>
+ <AddressType/>
+ <Address/>
+ <City/>
+ <StateOrProvince/>
+ <PostCode/>
+ <Country/>
+ </ContactAddress>
+ <ContactVoiceTelephone/>
+ <ContactFacsimileTelephone/>
+ <ContactElectronicMailAddress/>
+ </ContactInformation>
+ <Fees>NONE</Fees>
+ <AccessConstraints>NONE</AccessConstraints>
+ </Service>
+ <Capability>
+ <Request>
+ <GetCapabilities>
+ <Format>application/vnd.ogc.wms_xml</Format>
+ <DCPType>
+ <HTTP>
+ <Get>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?SERVICE=WMS&"/>
+ </Get>
+ <Post>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?SERVICE=WMS&"/>
+ </Post>
+ </HTTP>
+ </DCPType>
+ </GetCapabilities>
+ <GetMap>
+ <Format>image/png</Format>
+ <Format>application/atom xml</Format>
+ <Format>application/atom+xml</Format>
+ <Format>application/openlayers</Format>
+ <Format>application/pdf</Format>
+ <Format>application/rss xml</Format>
+ <Format>application/rss+xml</Format>
+ <Format>application/vnd.google-earth.kml</Format>
+ <Format>application/vnd.google-earth.kml xml</Format>
+ <Format>application/vnd.google-earth.kml+xml</Format>
+ <Format>application/vnd.google-earth.kmz</Format>
+ <Format>application/vnd.google-earth.kmz xml</Format>
+ <Format>application/vnd.google-earth.kmz+xml</Format>
+ <Format>atom</Format>
+ <Format>image/geotiff</Format>
+ <Format>image/geotiff8</Format>
+ <Format>image/gif</Format>
+ <Format>image/jpeg</Format>
+ <Format>image/png8</Format>
+ <Format>image/svg</Format>
+ <Format>image/svg xml</Format>
+ <Format>image/svg+xml</Format>
+ <Format>image/tiff</Format>
+ <Format>image/tiff8</Format>
+ <Format>kml</Format>
+ <Format>kmz</Format>
+ <Format>openlayers</Format>
+ <Format>rss</Format>
+ <DCPType>
+ <HTTP>
+ <Get>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?SERVICE=WMS&"/>
+ </Get>
+ </HTTP>
+ </DCPType>
+ </GetMap>
+ <GetFeatureInfo>
+ <Format>text/plain</Format>
+ <Format>text/html</Format>
+ <Format>application/vnd.ogc.gml</Format>
+ <DCPType>
+ <HTTP>
+ <Get>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?SERVICE=WMS&"/>
+ </Get>
+ <Post>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?SERVICE=WMS&"/>
+ </Post>
+ </HTTP>
+ </DCPType>
+ </GetFeatureInfo>
+ <DescribeLayer>
+ <Format>application/vnd.ogc.wms_xml</Format>
+ <DCPType>
+ <HTTP>
+ <Get>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?SERVICE=WMS&"/>
+ </Get>
+ </HTTP>
+ </DCPType>
+ </DescribeLayer>
+ <GetLegendGraphic>
+ <Format>image/png</Format>
+ <Format>image/jpeg</Format>
+ <Format>image/gif</Format>
+ <DCPType>
+ <HTTP>
+ <Get>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?SERVICE=WMS&"/>
+ </Get>
+ </HTTP>
+ </DCPType>
+ </GetLegendGraphic>
+ </Request>
+ <Exception>
+ <Format>application/vnd.ogc.se_xml</Format>
+ <Format>application/vnd.ogc.se_inimage</Format>
+ </Exception>
+ <UserDefinedSymbolization SupportSLD="1" UserLayer="1" UserStyle="1" RemoteWFS="1"/>
+ <Layer>
+ <Title>My GeoServer WMS</Title>
+ <Abstract>This is a description of your Web Map Server.</Abstract>
+ 
+ <SRS>EPSG:4326</SRS>
+ <LatLonBoundingBox minx="-74.012" miny="40.708" maxx="-74.002" maxy="40.72"/>
+ <Layer queryable="1">
+ <Name>opengeo:poi</Name>
+ <Title>Points of Interest</Title>
+ <Abstract>Points of Interest in New York City</Abstract>
+ <KeywordList/>
+ <SRS>EPSG:4326</SRS>
+ 
+ <LatLonBoundingBox minx="-74.012" miny="40.708" maxx="-74.002" maxy="40.72"/>
+ <BoundingBox SRS="EPSG:4326" minx="-74.012" miny="40.708" maxx="-74.002" maxy="40.72"/>
+ <Attribution>
+ <Title>GeoServer Sample Data</Title>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://svn.codehaus.org/geoserver/trunk/data/release/data/"/>
+ <LogoURL height="112" width="353">
+ <Format>image/png;charset=UTF-8</Format>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://geoserver.org/s/1518/25/0.1/_/download/resources/com.atlassian.confluence.themes.geoserver%3Ageoserver/chrome/geoserver-logo.png"/>
+ </LogoURL>
+ </Attribution>
+ <Style>
+ <Name>point</Name>
+ <Title>A boring default style</Title>
+ <Abstract>A sample style that just prints out a purple square</Abstract>
+ <LegendURL width="20" height="20">
+ <Format>image/png</Format>
+ <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?request=GetLegendGraphic&format=image%2Fpng&width=20&height=20&layer=poi"/>
+ </LegendURL>
+ </Style>
+ </Layer>
+ </Layer>
+ </Capability>
+</WMT_MS_Capabilities>

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: OWSLib - Access WMS attribution info

2009-12-04T08:12:22Z

On 12/03/2009 12:20 PM, David Winslow wrote:

Perhaps I am doing something wrong, but the test suite in trunk doesn't
seem to pass as-is. Is this the correct way to be running it?

cd tests/
python runalldoctests.py
# ... lots of text scrolls by
***Test Failed*** 6 failures.

I see an HTTP 401 error and such, so maybe the test suite is just out of
date? Is http://svn.gispython.org/svn/gispy/OWSLib/trunk the correct
repository?

This is on Fedora 12, running python 2.6. I'm using a virtualenv
sandbox for the tests.

--
David Winslow
OpenGeo - http://opengeo.org/
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: OWSLib - Access WMS attribution info

2009-12-04T01:26:49Z

Hi David,

I'd welcome a patch on this - that would be great.

It's worth noting that we're trying to keep the interfaces harmonized
across service types as much as possible - however I had a look at WCS
and WFS to see if there is anything similar and there isn't - so in
this case I think it's fine just to extend the WMS content metadata section.

I think it would be more in keeping with the rest of the library if it
was a dictionary at this level rather than another type of object - as
you can see here most things at the content metadata level are
lists/strings/dictionaries etc:
http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/interfaces.py#L139

Anyway a patch would be welcomed!
Also it would be good to work this into a test somewhere - if you have a
capabilities XML document that supports this we could use that as a
basis for testing.

Cheers,
Dominic

On 03/12/09 17:20, David Winslow wrote:

> Hi all,
>
> For a project I'm working on, I'd like to access the Attribution field
> on some layers in a WMS capabilities document. I'd love to use OWSLib
> (looks like it would be a lot easier to use than parsing the XML
> directly), but when I try to retrieve the Attribution I just get an
> empty string (or None if there is no attribution for the layer.) I was
> expecting an object with the title, logo URL, and link for the Attribution.
>
> Digging into the code a bit I see that Attribution is parsed in exactly
> the same way as Name and Title, so it will always be a string. Would it
> be reasonable to change this to an object or dictionary with the fields
> I mentioned above?
>
> I would be happy to put together a patch if there's interest.
>
> --
> David Winslow
> OpenGeo - http://opengeo.org/
> _______________________________________________
> Community mailing list
> Community@...
> http://lists.gispython.org/mailman/listinfo/community

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

OWSLib - Access WMS attribution info

2009-12-03T09:20:23Z

Hi all,

For a project I'm working on, I'd like to access the Attribution field
on some layers in a WMS capabilities document. I'd love to use OWSLib
(looks like it would be a lot easier to use than parsing the XML
directly), but when I try to retrieve the Attribution I just get an
empty string (or None if there is no attribution for the layer.) I was
expecting an object with the title, logo URL, and link for the Attribution.

Digging into the code a bit I see that Attribution is parsed in exactly
the same way as Name and Title, so it will always be a string. Would it
be reasonable to change this to an object or dictionary with the fields
I mentioned above?

I would be happy to put together a patch if there's interest.

--
David Winslow
OpenGeo - http://opengeo.org/
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: rtree delete

2009-12-02T08:12:42Z

Howard Butler wrote:
>> "... providing the index's dimension * 2 coordinate pairs representing
>> the mink and maxk coordinates in each dimension defining the bounds of
>> the query window."
>>
> Care to come up with some text that's not so confusing? I'll incorporate it before the next release.

How about this... a little repetitive but I find it clearer.

Original:
:param coordinates: sequence or array
This may be an object that satisfies the numpy array
protocol, providing the index's dimension * 2 coordinate
pairs representing the mink and maxk coordinates in
each dimension defining the bounds of the query window.

Proposed change:
:param coordinates: sequence or array
Dimension * 2 coordinate pairs, representing the min
and max coordinates in each dimension of the item to be
deleted from the index. Their ordering will depend on the
index's :attr:`interleaved` data member.
These are not the coordinates of a space containing the
item, but those of the item itself. Together with the
id parameter, they determine which item will be deleted.
This may be an object that satisfies the numpy array protocol.

> Excellent. Can you describe what you're using Rtree for? I'm really interested in how people are using it, and for what kind of data.

The Graphserver project (public transit route planning) is using Rtree
to find nodes in road and public transit systems that are close to one
another. I am experimenting with different strategies for deciding which
street is closest to a transit stop and creating new nodes when necessary.

Thanks again,
Andrew
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: Fwd: shapely multipolygon

2009-11-27T00:39:54Z

On Nov 26, 2009, at 11:35 PM, Jassin MEKNASSI wrote:

>>
>>>
>>>
>>> hi I want to union all the polygons in a list of elements and get
>>> all the distinct polygons at the end.
>>> union seems to produce a polygon if the 2 objects intersect and a
>>> multipolygon if not.
>>> If i Union all the elements in a polygon set i would get at the en
>>> only one multipolygon. (reduce +lambda + union)
>>> How can i get the distinct polygons objects from a multipolygon?
>>>
>>> Thanks
>>
>

Multipart geometries have a "geoms" attribute that you can use to
iterate over the parts.

Cheers,

--
Sean

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Fwd: shapely multipolygon

2009-11-26T14:35:15Z

hi I want to union all the polygons in a list of elements and get all the distinct polygons at the end.
union seems to produce a polygon if the 2 objects intersect and a multipolygon if not.
If i Union all the elements in a polygon set i would get at the en only one multipolygon. (reduce +lambda + union)
How can i get the distinct polygons objects from a multipolygon?

Thanks

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: describeCoverage

2009-11-25T03:51:21Z

I think I have solved the problem of getting coverage resolution (by
means of your help)... :

from owslib.wcs import WebCoverageService
wcs =
WebCoverageService('http://geoserver.irpi.cnr.it/geoserver/wcs',version='1.0.0')
wcs.contents
cvg=wcs['irpi:collazzone_2004']
cvg.grid.offsetvectors #I
[['15.0', '0.0'], ['0.0', '-15.0']]

thanks...

Ivan

Il giorno mar

, 24/11/2009 alle 18.03 +0100, ivan marchesini ha scritto:

> Hi Dominic,
> thanks for your answer...
>
> Il giorno mar, 24/11/2009 alle 09.26 +0000, dominic.lowe@... ha
> scritto:
> > #look at the coverage properties:
> > cvg.boundingBoxWGS84
> > cvg.timepositions
> > cvg.supportedCRS
> > cvg.supportedFormats
>
> yes.. many thanks.. but what I'm interested on is the resolution of the
> coverage, that in the describeCoverage call
>
> http://geoserver.irpi.cnr.it/geoserver/wcs?version=1.0.0&service=WCS&REQUEST=DescribeCoverage&COVERAGE=irpi:collazzone_2004
>
> is shown inside this part of the xml:
>
> <gml:RectifiedGrid dimension="2">
> <gml:limits>
> <gml:GridEnvelope>
> <gml:low>0 0 </gml:low>
> <gml:high>5358 5136 </gml:high>
> </gml:GridEnvelope>
> </gml:limits>
> <gml:axisName>GRAY_INDEX</gml:axisName>
> <gml:origin>
> <gml:pos>267740.22 4780537.966</gml:pos>
> </gml:origin>
> <gml:offsetVector>15.0 0.0</gml:offsetVector>
> <gml:offsetVector>0.0 -15.0</gml:offsetVector>
> </gml:RectifiedGrid>
>
>
> Ho can I store the resolution values (15) into a variable?
>
> many many thanks...
>
> ivan
>
>
>
>

Ti prego di cercare di non inviarmi files .dwg, .doc, .xls, .ppt.
Preferisco formati liberi.
Please try to avoid to send me .dwg, .doc, .xls, .ppt files.
I prefer free formats.
http://it.wikipedia.org/wiki/Formato_aperto
http://en.wikipedia.org/wiki/Open_format

Ivan Marchesini
Perugia (Italy)
Socio fondatore GFOSS "Geospatial Free and Open Source Software" http://www.gfoss.it
e-mail: marchesini@...
ivan.marchesini@...
fax (home): +39(0)5782830887
jabber: geoivan73@...
skype: geoivan73

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

signature.asc (205 bytes) Download Attachment

Re: Rtree pagesize error

2009-11-25T00:29:46Z

Thanks Howard,

I misunderstood the pagesize parameter. It's working fine with default pagesize. I tested with my road data (~1million) and the response is quite good.

Regards,
Gagan

On Tue, Nov 24, 2009 at 7:48 PM, Howard Butler <hobu.inc@...> wrote:

On Nov 24, 2009, at 5:26 AM, Gagan Bansal wrote:

> Hi,
>
> I was trying to use the 'pagesize' property as pagesize=1 while creating a index
> >>>idx = index.Index('road' , pagesize=1)
> and then I insert all my bbox to the index (idx)
> >>>del idx
>
> now next time I want to read the index from file (road.idx,road.dat)
> >>>idx = index.Index('road' , pagesize=1)
> or >>>idx = index.Index('road' )
> but I get error while reading i.e.
> rtree.core.RTreeError: Error in "Index_Create": Spatial Index Error: InvalidPageException: Unknown page id 1
>
> What could be the reason for this error?

I think this error has been fixed in trunk (requires trunk libspatialindex at this time too, unfortunately).

> My aim is to load the full index in single page for efficiency.

Remember that the pagesize is a value in bytes. A pagesize=1 will never contain the entire index. Also, ensure that your pagesize is large enough to hold any pickled data that you might be storing in the index as well. We have changed the pagesize to default to 4096, which is fairly reasonable. Any larger will waste disk space, and any smaller will mean creating lots of pages.

Howard
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: describeCoverage

2009-11-25T00:15:40Z

Hi Ivan,

try:
cvg.grid.offsetvectors
[['15.0', '0.0'], ['0.0', '-15.0']]

See also:
cvg.grid.axislabels
cvg.grid.dimension
cvg.grid.highlimits
cvg.grid.lowlimits
cvg.grid.origin

re the CRS issue - yes I think there's some work to do in owslib to differentiate request and response crs in WCS. API suggestions are welcome!

Cheers,
Dom

-----Original Message-----
From: ivan marchesini [mailto:ivan.marchesini@...]
Sent: Tue 24/11/2009 17:03
To: Lowe, Dominic (STFC,RAL,SSTD)
Cc: community@...
Subject: RE: [Community] describeCoverage

Hi Dominic,
thanks for your answer...

Il giorno mar, 24/11/2009 alle 09.26 +0000, dominic.lowe@... ha
scritto:
> #look at the coverage properties:
> cvg.boundingBoxWGS84
> cvg.timepositions
> cvg.supportedCRS
> cvg.supportedFormats

yes.. many thanks.. but what I'm interested on is the resolution of the
coverage, that in the describeCoverage call

http://geoserver.irpi.cnr.it/geoserver/wcs?version=1.0.0&service=WCS&REQUEST=DescribeCoverage&COVERAGE=irpi:collazzone_2004

is shown inside this part of the xml:

<gml:RectifiedGrid dimension="2">
<gml:limits>
<gml:GridEnvelope>
<gml:low>0 0 </gml:low>
<gml:high>5358 5136 </gml:high>
</gml:GridEnvelope>
</gml:limits>
<gml:axisName>GRAY_INDEX</gml:axisName>
<gml:origin>
<gml:pos>267740.22 4780537.966</gml:pos>
</gml:origin>
<gml:offsetVector>15.0 0.0</gml:offsetVector>
<gml:offsetVector>0.0 -15.0</gml:offsetVector>
</gml:RectifiedGrid>

Ho can I store the resolution values (15) into a variable?

many many thanks...

ivan

--
Ti prego di cercare di non inviarmi files .dwg, .doc, .xls, .ppt.
Preferisco formati liberi.
Please try to avoid to send me .dwg, .doc, .xls, .ppt files.
I prefer free formats.
http://it.wikipedia.org/wiki/Formato_aperto
http://en.wikipedia.org/wiki/Open_format

Ivan Marchesini
Perugia (Italy)
Socio fondatore GFOSS "Geospatial Free and Open Source Software" http://www.gfoss.it
e-mail: marchesini@...
ivan.marchesini@...
fax (home): +39(0)5782830887
jabber: geoivan73@...
skype: geoivan73

--
Scanned by iCritical.
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: rtree delete

2009-11-24T12:37:20Z

On Nov 24, 2009, at 12:33 PM, Andrew Byrd wrote:

>
> On 24 Nov 2009, at 18:50, Howard Butler wrote:
>>> The item is not removed from the index when the window specified in
>>> the delete method is larger that it, but only when the window exactly
>>> matches its bounding box.
>>>
>>> Is this the expected behavior, am I misunderstanding something?
>>
>> Expected, yes. "Uniqueness" in the sense of the rtree index is
>> really the bounding box that is inserted into it plus the id, not
>> merely the id. I put uniqueness in scare quotes because I think you
>> can actually have multiple id + bbox entries with the same value and
>> delete will delete both of them (not verified though).
>
> Thanks for your explanation, Howard. I was misinterpreting 'query
> window' in this comment in index.py:
> "... providing the index's dimension * 2 coordinate pairs representing
> the mink and maxk coordinates in each dimension defining the bounds of
> the query window."
>

Care to come up with some text that's not so confusing? I'll incorporate it before the next release.

>> I think you want something like a "range delete", which isn't
>> implemented in either libspatialindex or its C API. This would
>> allow a user to do it in one shot quite quickly. Right now, you can
>> cobble this up by doing a .intersection(objects=True) and inspecting
>> the resultant .id and .bbox elements of the results and *then*
>> issuing the delete with that.
>
> In fact, I wanted to delete a single item at a time, and was using
> results from intersection(objects=True) to find it. The problem was
> that I was calling delete with the item's bounds instead of its bbox,
> which is interleaved. It works perfectly with the coordinates in
> item.bbox.

Excellent. Can you describe what you're using Rtree for? I'm really interested in how people are using it, and for what kind of data.
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: rtree delete

2009-11-24T10:33:26Z

On 24 Nov 2009, at 18:50, Howard Butler wrote:

>> The item is not removed from the index when the window specified in
>> the delete method is larger that it, but only when the window exactly
>> matches its bounding box.
>>
>> Is this the expected behavior, am I misunderstanding something?
>
> Expected, yes. "Uniqueness" in the sense of the rtree index is
> really the bounding box that is inserted into it plus the id, not
> merely the id. I put uniqueness in scare quotes because I think you
> can actually have multiple id + bbox entries with the same value and
> delete will delete both of them (not verified though).

Thanks for your explanation, Howard. I was misinterpreting 'query
window' in this comment in index.py:
"... providing the index's dimension * 2 coordinate pairs representing
the mink and maxk coordinates in each dimension defining the bounds of
the query window."

> I think you want something like a "range delete", which isn't
> implemented in either libspatialindex or its C API. This would
> allow a user to do it in one shot quite quickly. Right now, you can
> cobble this up by doing a .intersection(objects=True) and inspecting
> the resultant .id and .bbox elements of the results and *then*
> issuing the delete with that.

In fact, I wanted to delete a single item at a time, and was using
results from intersection(objects=True) to find it. The problem was
that I was calling delete with the item's bounds instead of its bbox,
which is interleaved. It works perfectly with the coordinates in
item.bbox.

Thanks again for your help,
Andrew
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: rtree delete

2009-11-24T09:50:15Z

On Nov 24, 2009, at 11:23 AM, Andrew Byrd wrote:

> Hello,
>
> I'm trying to delete items that have been added to an rtree Index. I
> am finding that the items still exist after I thought they were
> deleted. I am using spatialindex and rtree freshly checked out from
> svn trunk, and compiled on OSX 10.5.6 with Python 2.6.
>
> The following test demonstrates my situation:
>
> $python
>>>> from rtree import Rtree
>>>> i = Rtree()
>>>> i.insert(1, (0,0,5,5))
>>>> i.insert(2, (1,1,6,6))
>>>> i.insert(3, (2,2,7,7))
>>>> i.intersection((3,3,4,4))
> [1L, 2L, 3L]
>>>> i.delete(2, (0,0,7,7))
>>>> i.intersection((3,3,4,4))
> [1L, 2L, 3L]
>>>> i.delete(2, (2,2,5,5))
>>>> i.intersection((3,3,4,4))
> [1L, 2L, 3L]
>>>> i.delete(2, (0.9,0.9,6.1,6.1))
>>>> i.intersection((3,3,4,4))
> [1L, 2L, 3L]
>>>> i.delete(2, (1,1,6,6))
>>>> i.intersection((3,3,4,4))
> [1L, 3L]
>>>>
>>>>
>
> The item is not removed from the index when the window specified in
> the delete method is larger that it, but only when the window exactly
> matches its bounding box.
>
> Is this the expected behavior, am I misunderstanding something?

Expected, yes. "Uniqueness" in the sense of the rtree index is really the bounding box that is inserted into it plus the id, not merely the id. I put uniqueness in scare quotes because I think you can actually have multiple id + bbox entries with the same value and delete will delete both of them (not verified though).

I think you want something like a "range delete", which isn't implemented in either libspatialindex or its C API. This would allow a user to do it in one shot quite quickly. Right now, you can cobble this up by doing a .intersection(objects=True) and inspecting the resultant .id and .bbox elements of the results and *then* issuing the delete with that.

Hope this helps,

Howard

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

rtree delete

2009-11-24T09:23:45Z

Hello,

I'm trying to delete items that have been added to an rtree Index. I
am finding that the items still exist after I thought they were
deleted. I am using spatialindex and rtree freshly checked out from
svn trunk, and compiled on OSX 10.5.6 with Python 2.6.

The following test demonstrates my situation:

$python
>>> from rtree import Rtree
>>> i = Rtree()
>>> i.insert(1, (0,0,5,5))
>>> i.insert(2, (1,1,6,6))
>>> i.insert(3, (2,2,7,7))
>>> i.intersection((3,3,4,4))
[1L, 2L, 3L]
>>> i.delete(2, (0,0,7,7))
>>> i.intersection((3,3,4,4))
[1L, 2L, 3L]
>>> i.delete(2, (2,2,5,5))
>>> i.intersection((3,3,4,4))
[1L, 2L, 3L]
>>> i.delete(2, (0.9,0.9,6.1,6.1))
>>> i.intersection((3,3,4,4))
[1L, 2L, 3L]
>>> i.delete(2, (1,1,6,6))
>>> i.intersection((3,3,4,4))
[1L, 3L]
>>>
>>>

The item is not removed from the index when the window specified in
the delete method is larger that it, but only when the window exactly
matches its bounding box.

Is this the expected behavior, am I misunderstanding something?

Thanks,
Andrew
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: describeCoverage

2009-11-24T09:19:42Z

Hi Dominic,
about the other problem, in the getCoverage call you asked a BBOX in
crs=32633 but the BBOX was expressed in crs=4326

> make get coverage request:
>
> u=wcs.getCoverage(identifier='irpi:collazzone_2004', bbox=
> (12.7, 42.5, 13, 43) , crs='EPSG:32633', format='PNG', width=100,
> height=100)
>
> u.read()
>
>
> Then you get a geoserver exception:
> '<?xml version="1.0" encoding="UTF-8"?><ServiceExceptionReport
> version="1.2.0" xmlns="http://www.opengis.net/ogc"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.opengis.net/ogc http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd"> <ServiceException code="problem with CoverageResults">\n org.vfny.geoserver.wcs.WcsException: The Intersection is null. Check the requested BBOX!\nThe Intersection is null. Check the requested BBOX!\n</ServiceException></ServiceExceptionReport>'
>
>
> This error response seems odd as the bounding box I requested is
> within your bounds...

in fact the exception is:
"The Intersection is null"

I have just added the support for 4326 to the coverage:
______________
from owslib.wcs import WebCoverageService
wcs =
WebCoverageService('http://geoserver.irpi.cnr.it/geoserver/wcs',version='1.0.0')
wcs.contents
cvg=wcs['irpi:collazzone_2004']

cvg.supportedCRS
['EPSG:32633', '', 'EPSG:4326', '', '']
_____________

but now, when I make the getCoverage call:

_______________
u=wcs.getCoverage(identifier='irpi:collazzone_2004', bbox=
(12.7, 42.5, 13, 43) , crs='EPSG:4326', format='PNG', width=100,
height=100)

u.read()
<?xml version="1.0" encoding="UTF-8"?><ServiceExceptionReport
version="1.2.0" xmlns="http://www.opengis.net/ogc"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.opengis.net/ogc
http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd">
<ServiceException code="problem with CoverageResults">\n
org.vfny.geoserver.wcs.WcsException: This Coverage does not support the
requested Response-CRS.\nThis Coverage does not support the requested
Response-CRS.\n</ServiceException></ServiceExceptionReport>'
_______________

the error is:
"This Coverage does not support the requested Response-CRS"

but cvg.supportedCRS said the opposite!!!! :-(

whats the problem??

Thanks....

Ivan

--
Ti prego di cercare di non inviarmi files .dwg, .doc, .xls, .ppt.
Preferisco formati liberi.
Please try to avoid to send me .dwg, .doc, .xls, .ppt files.
I prefer free formats.
http://it.wikipedia.org/wiki/Formato_aperto
http://en.wikipedia.org/wiki/Open_format

Ivan Marchesini
Perugia (Italy)
Socio fondatore GFOSS "Geospatial Free and Open Source Software" http://www.gfoss.it
e-mail: marchesini@...
ivan.marchesini@...
fax (home): +39(0)5782830887
jabber: geoivan73@...
skype: geoivan73

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

signature.asc (205 bytes) Download Attachment

Re: describeCoverage

2009-11-24T09:03:31Z

Hi Dominic,
thanks for your answer...

Il giorno mar, 24/11/2009 alle 09.26 +0000, dominic.lowe@... ha
scritto:
> #look at the coverage properties:
> cvg.boundingBoxWGS84
> cvg.timepositions
> cvg.supportedCRS
> cvg.supportedFormats

yes.. many thanks.. but what I'm interested on is the resolution of the
coverage, that in the describeCoverage call

http://geoserver.irpi.cnr.it/geoserver/wcs?version=1.0.0&service=WCS&REQUEST=DescribeCoverage&COVERAGE=irpi:collazzone_2004

is shown inside this part of the xml:

<gml:RectifiedGrid dimension="2">
<gml:limits>
<gml:GridEnvelope>
<gml:low>0 0 </gml:low>
<gml:high>5358 5136 </gml:high>
</gml:GridEnvelope>
</gml:limits>
<gml:axisName>GRAY_INDEX</gml:axisName>
<gml:origin>
<gml:pos>267740.22 4780537.966</gml:pos>
</gml:origin>
<gml:offsetVector>15.0 0.0</gml:offsetVector>
<gml:offsetVector>0.0 -15.0</gml:offsetVector>
</gml:RectifiedGrid>

Ho can I store the resolution values (15) into a variable?

many many thanks...

ivan

--
Ti prego di cercare di non inviarmi files .dwg, .doc, .xls, .ppt.
Preferisco formati liberi.
Please try to avoid to send me .dwg, .doc, .xls, .ppt files.
I prefer free formats.
http://it.wikipedia.org/wiki/Formato_aperto
http://en.wikipedia.org/wiki/Open_format

Ivan Marchesini
Perugia (Italy)
Socio fondatore GFOSS "Geospatial Free and Open Source Software" http://www.gfoss.it
e-mail: marchesini@...
ivan.marchesini@...
fax (home): +39(0)5782830887
jabber: geoivan73@...
skype: geoivan73

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

signature.asc (205 bytes) Download Attachment

Re: Rtree pagesize error

2009-11-24T06:18:30Z

On Nov 24, 2009, at 5:26 AM, Gagan Bansal wrote:

> Hi,
>
> I was trying to use the 'pagesize' property as pagesize=1 while creating a index
> >>>idx = index.Index('road' , pagesize=1)
> and then I insert all my bbox to the index (idx)
> >>>del idx
>
> now next time I want to read the index from file (road.idx,road.dat)
> >>>idx = index.Index('road' , pagesize=1)
> or >>>idx = index.Index('road' )
> but I get error while reading i.e.
> rtree.core.RTreeError: Error in "Index_Create": Spatial Index Error: InvalidPageException: Unknown page id 1
>
> What could be the reason for this error?

I think this error has been fixed in trunk (requires trunk libspatialindex at this time too, unfortunately).

> My aim is to load the full index in single page for efficiency.

Remember that the pagesize is a value in bytes. A pagesize=1 will never contain the entire index. Also, ensure that your pagesize is large enough to hold any pickled data that you might be storing in the index as well. We have changed the pagesize to default to 4096, which is fairly reasonable. Any larger will waste disk space, and any smaller will mean creating lots of pages.

Howard
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Rtree pagesize error

2009-11-24T03:26:34Z

Hi,

I was trying to use the 'pagesize' property as pagesize=1 while creating a index
>>>idx = index.Index('road' , pagesize=1)
and then I insert all my bbox to the index (idx)
>>>del idx

now next time I want to read the index from file (road.idx,road.dat)
>>>idx = index.Index('road' , pagesize=1)
or >>>idx = index.Index('road' )
but I get error while reading i.e.
rtree.core.RTreeError: Error in "Index_Create": Spatial Index Error: InvalidPageException: Unknown page id 1

What could be the reason for this error?
My aim is to load the full index in single page for efficiency.

Regards,
Gagan

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: describeCoverage

2009-11-24T01:26:31Z

Hi Ivan

getDescribeCoverage gets an ElementTree object, not the actual XML.

However you shouldn't need to do that actually - that method is just there as an 'extra'.

the way to do it is:

from owslib.wcs import WebCoverageService
wcs = WebCoverageService('http://geoserver.irpi.cnr.it/geoserver/wcs',version='1.0.0')
wcs.contents #prints available coverages
cvg=wcs['irpi:collazzone_2004'] #this gives you a coverage metadata object to interrogate

#look at the coverage properties:
cvg.boundingBoxWGS84
cvg.timepositions
cvg.supportedCRS
cvg.supportedFormats

make get coverage request:

u=wcs.getCoverage(identifier='irpi:collazzone_2004', bbox=
(12.7, 42.5, 13, 43) , crs='EPSG:32633', format='PNG', width=100, height=100)

u.read()

Then you get a geoserver exception:
'<?xml version="1.0" encoding="UTF-8"?><ServiceExceptionReport version="1.2.0" xmlns="http://www.opengis.net/ogc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/ogc http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd"> <ServiceException code="problem with CoverageResults">\n org.vfny.geoserver.wcs.WcsException: The Intersection is null. Check the requested BBOX!\nThe Intersection is null. Check the requested BBOX!\n</ServiceException></ServiceExceptionReport>'

This error response seems odd as the bounding box I requested is within your bounds...

Anyway, hope that helps.

Cheers,
Dom

-----Original Message-----
From: community-bounces@... on behalf of ivan marchesini
Sent: Mon 23/11/2009 22:16
To: henning.bredel@...
Cc: gispython.org community projects
Subject: Re: [Community] describeCoverage

I Henning...

many thanks for your answer...

> I tried to get the capabilities with
>
> http://geoserver.irpi.cnr.it/geoserver/wcs?request=GetCapabilties&service=WCS
>
> but it seems that the server has no capabilities set, yet.

I think adding the version parameter the getCapabilities works:

http://geoserver.irpi.cnr.it/geoserver/wcs?version=1.0.0&service=WCS&REQUEST=getcapabilities

but the problem is still:
___________
from owslib.wcs import WebCoverageService
wcs = WebCoverageService('http://geoserver.irpi.cnr.it/geoserver/wcs',
version='1.0.0')
description=wcs.getDescribeCoverage('irpi:collazzone_2004')
______________

from which I can't see anything inside "description".. :-(

many thanks...

ivan

> However,
> your request
>
> http://geoserver.irpi.cnr.it/geoserver/wcs?version=1.0.0&service=WCS&REQUEST=DescribeCoverage&COVERAGE=irpi:collazzone_2004
>
> works. I think, s/o has forgotten to set the (required) capabilities
> of the service. This should get fixed.
>
> Best
>
> Henning
>
>

Ti prego di cercare di non inviarmi files .dwg, .doc, .xls, .ppt.
Preferisco formati liberi.
Please try to avoid to send me .dwg, .doc, .xls, .ppt files.
I prefer free formats.
http://it.wikipedia.org/wiki/Formato_aperto
http://en.wikipedia.org/wiki/Open_format

Ivan Marchesini
Perugia (Italy)
Socio fondatore GFOSS "Geospatial Free and Open Source Software" http://www.gfoss.it
e-mail: marchesini@...
ivan.marchesini@...
fax (home): +39(0)5782830887
jabber: geoivan73@...
skype: geoivan73

--
Scanned by iCritical.

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

winmail.dat (5K) Download Attachment

Re: describeCoverage

2009-11-23T13:51:21Z

I Henning...

many thanks for your answer...

> I tried to get the capabilities with
>
> http://geoserver.irpi.cnr.it/geoserver/wcs?request=GetCapabilties&service=WCS
>
> but it seems that the server has no capabilities set, yet.

I think adding the version parameter the getCapabilities works:

http://geoserver.irpi.cnr.it/geoserver/wcs?version=1.0.0&service=WCS&REQUEST=getcapabilities

but the problem is still:
___________
from owslib.wcs import WebCoverageService
wcs = WebCoverageService('http://geoserver.irpi.cnr.it/geoserver/wcs',
version='1.0.0')
description=wcs.getDescribeCoverage('irpi:collazzone_2004')
______________

from which I can't see anything inside "description".. :-(

many thanks...

ivan

signature.asc (205 bytes) Download Attachment

Re: describeCoverage

2009-11-23T12:49:43Z

ivan marchesini wrote:

> now I suppose I must use
>
> description=wcs.getDescribeCoverage('irpi:collazzone_2004')
>
> but it seems that the created object is empty or, probably, I'm not able
> to read the output.

Ivan,

I tried to get the capabilities with

http://geoserver.irpi.cnr.it/geoserver/wcs?request=GetCapabilties&service=WCS

but it seems that the server has no capabilities set, yet. However,
your request

http://geoserver.irpi.cnr.it/geoserver/wcs?version=1.0.0&service=WCS&REQUEST=DescribeCoverage&COVERAGE=irpi:collazzone_2004

works. I think, s/o has forgotten to set the (required) capabilities
of the service. This should get fixed.

Best

Henning

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

signature.asc (268 bytes) Download Attachment

describeCoverage

2009-11-23T12:46:50Z

Dear al python-gis users..

I'm starting to use python and owslib... so I have my first
questions... :-)

This is

http://geoserver.irpi.cnr.it/geoserver/wcs?version=1.0.0&service=WCS&REQUEST=DescribeCoverage&COVERAGE=irpi:collazzone_2004

the ows request I would like to replicate by means of owslib...

I would like to store the xml result into a python object.

I have loaded the modules and defined the url:

from owslib.wcs import WebCoverageService
wcs = WebCoverageService('http://geoserver.irpi.cnr.it/geoserver/wcs',
version='1.0.0')

now I suppose I must use

description=wcs.getDescribeCoverage('irpi:collazzone_2004')

but it seems that the created object is empty or, probably, I'm not able
to read the output.

How can I obtain what I need?
Moreover, I need to extract the resolution from the describecoverage
call... which is, in your opinion, the best way to obtain these values?

many thanks...

Ivan

--
Ti prego di cercare di non inviarmi files .dwg, .doc, .xls, .ppt.
Preferisco formati liberi.
Please try to avoid to send me .dwg, .doc, .xls, .ppt files.
I prefer free formats.
http://it.wikipedia.org/wiki/Formato_aperto
http://en.wikipedia.org/wiki/Open_format

Ivan Marchesini
Perugia (Italy)
Socio fondatore GFOSS "Geospatial Free and Open Source Software" http://www.gfoss.it
e-mail: marchesini@...
ivan.marchesini@...
fax (home): +39(0)5782830887
jabber: geoivan73@...
skype: geoivan73

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

signature.asc (205 bytes) Download Attachment

Re: rtree thread safe

2009-11-18T20:27:04Z

Thanks Sean,
I'll look into this.
Regards
Gagan

On Wed, Nov 18, 2009 at 8:17 PM, Sean Gillies <sean.gillies@...> wrote:

On Nov 18, 2009, at 4:41 AM, Gagan Bansal wrote:

> Hi,
>
> Now I have achieved this by thread lock acquire and release.
> <snip>
> threadlock=thread.allocate_lock()
> global threadlock
>
> threadlock.acquire()
>
> # find intersection or nearest here
>
> threadlock.release()
> </snip>
>
> Thanks,
> Gagan

FWIW, I'm serializing access to my rtree with an HTTP server.

Tangent: David Beazley's presentation on performance-killing
interactions between the GIL and threads is really interesting:

http://www.dabeaz.com/python/GIL.pdf
Google preview: http://tinyurl.com/y9gdtau

--
Sean Gillies
Programmer
Institute for the Study of the Ancient World
New York University

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: rtree thread safe

2009-11-18T06:47:18Z

On Nov 18, 2009, at 4:41 AM, Gagan Bansal wrote:

> Hi,
>
> Now I have achieved this by thread lock acquire and release.
> <snip>
> threadlock=thread.allocate_lock()
> global threadlock
>
> threadlock.acquire()
>
> # find intersection or nearest here
>
> threadlock.release()
> </snip>
>
> Thanks,
> Gagan

FWIW, I'm serializing access to my rtree with an HTTP server.

Tangent: David Beazley's presentation on performance-killing
interactions between the GIL and threads is really interesting:

http://www.dabeaz.com/python/GIL.pdf
Google preview: http://tinyurl.com/y9gdtau

--
Sean Gillies
Programmer
Institute for the Study of the Ancient World
New York University

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

rtree thread safe

2009-11-18T01:41:48Z

Hi,

Now I have achieved this by thread lock acquire and release.
<snip>
threadlock=thread.allocate_lock()
global threadlock

threadlock.acquire()

# find intersection or nearest here

threadlock.release()
</snip>

Thanks,
Gagan

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: rtree thread safe

2009-11-17T09:12:01Z

I haven't needed this yet, but was going to shortly. The read-only model is very interesting to me too. Has anyone scoped the pain of supporting read-only concurrent access in development time? Days, weeks, ...?

-----Original Message-----
From: community-bounces@... [mailto:community-bounces@...] On Behalf Of Brent Pedersen
Sent: Tuesday, November 17, 2009 8:12 AM
To: gispython.org community projects
Subject: Re: [Community] rtree thread safe

On Tue, Nov 17, 2009 at 5:58 AM, Howard Butler <hobu.inc@...> wrote:

>
> On Nov 17, 2009, at 5:05 AM, Gagan Bansal wrote:
>
>> Hi,
>>
>> I am using rtree to find the nearest roads from my road data set ( around 1 million road segments) and its working superb. But when I am testing it for user concurrency more than one, the error is thrown 'resource lock'. What could be the reason?
>>
>> I am loading the bounding box of roads initially from a file. Then I use the index to find the nearest. There is no insertion of the b-box later. Is there any option to freeze the index or read only ?
>
> rtree is not quite thread safe at this time (assuming you're using 0.5 or trunk). There is some capacity for thread safety and multi-threaded access within libspatialindex, but there are some areas of the code that have not been locked up yet. Brent Pedersen has done some work in this area, and he could provide more details. Basically, the answer is we need some work libspatialindex and possibly the Rtree bindings as well. Short term, employ the Big Ass Lock (TM) pattern ;)
>
> Howard
>
> _______________________________________________
> Community mailing list
> Community@...
> http://lists.gispython.org/mailman/listinfo/community
>

yeah, i just did a work-around, forcing a web-app to be single threaded.
i created a ticket to track this:
http://trac.gispython.org/lab/ticket/195
-b
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community
_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

Re: rtree thread safe

2009-11-17T08:11:49Z

On Tue, Nov 17, 2009 at 5:58 AM, Howard Butler <hobu.inc@...> wrote:

Re: rtree thread safe

2009-11-17T05:58:47Z

On Nov 17, 2009, at 5:05 AM, Gagan Bansal wrote:

> Hi,
>
> I am using rtree to find the nearest roads from my road data set ( around 1 million road segments) and its working superb. But when I am testing it for user concurrency more than one, the error is thrown 'resource lock'. What could be the reason?
>
> I am loading the bounding box of roads initially from a file. Then I use the index to find the nearest. There is no insertion of the b-box later. Is there any option to freeze the index or read only ?

rtree is not quite thread safe at this time (assuming you're using 0.5 or trunk). There is some capacity for thread safety and multi-threaded access within libspatialindex, but there are some areas of the code that have not been locked up yet. Brent Pedersen has done some work in this area, and he could provide more details. Basically, the answer is we need some work libspatialindex and possibly the Rtree bindings as well. Short term, employ the Big Ass Lock (TM) pattern ;)

Howard

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

rtree thread safe

2009-11-17T03:05:06Z

Hi,

I am using rtree to find the nearest roads from my road data set ( around 1 million road segments) and its working superb. But when I am testing it for user concurrency more than one, the error is thrown 'resource lock'. What could be the reason?

I am loading the bounding box of roads initially from a file. Then I use the index to find the nearest. There is no insertion of the b-box later. Is there any option to freeze the index or read only ?

Thanks,
Gagan

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community