Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception struck: 10588 #8

Closed
vincentcau opened this issue Jul 21, 2014 · 7 comments
Closed

Exception struck: 10588 #8

vincentcau opened this issue Jul 21, 2014 · 7 comments

Comments

@vincentcau
Copy link

hello,

I try to use Contour but i have the error Exception struck: 10588.

Can you help me please?
Thanx !

@ccrook
Copy link
Owner

ccrook commented Jul 21, 2014

Not without more information :-)

If you can provide a test data set and the options you are using for contouring then I can look at it.

Cheers
Chris


From: Vince [notifications@github.com]
Sent: 22 July 2014 04:21
To: ccrook/QGIS-Contour-Plugin
Subject: [QGIS-Contour-Plugin] Exception struck: 10588 (#8)

hello,

I try to use Contour but i have the error Exception struck: 10588.

Can you help me please?
Thanx !


Reply to this email directly or view it on GitHubhttps://github.com//issues/8.

This message contains information, which may be in confidence and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or info@linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank You.

@vincentcau
Copy link
Author

I use the plugin with QGIS 2.4.

The data are an Array of points, results of PostgreSQL request with pgRouting's methods.
results are 263 412 entities
Each points are a node with cost, exemple:
Points = {node : 123, cost : 0.2345643}

Contour configuration :
Input
Vector layer : may_layer
data field : cost
Contouring
contour lines
number: 5
Min: 0.0000
Max: 0.8300
Extend: neither
Method: equal

Layer name : Contour
Label precision 4

I try a lots of config but i have the same error.

@ccrook
Copy link
Owner

ccrook commented Jul 21, 2014

Hi Vince

253,412 points is a lot of points! I suspect the problems is just that your data set is too big for the matplotlib contouring algorithm.

Do you know if the contouring plugin works for you on (much) smaller data sets. I'd just like to confirm that the problem comes from the data set rather than from your set up.

If the problem is the number of points then you may need to use some other approach. For example you could resample down to a smaller data set. I haven't tried doing this, but it looks like some of the processing algorithms may be able to do this (GDAL analysis Grid methods look like good candidates)

Chris

From: Vince [mailto:notifications@github.com]
Sent: Tuesday, 22 July 2014 6:59 a.m.
To: ccrook/QGIS-Contour-Plugin
Cc: Chris Crook
Subject: Re: [QGIS-Contour-Plugin] Exception struck: 10588 (#8)

I use the plugin with QGIS 2.4.

The data are an Array of points, results of PostgreSQL request with pgRouting's methods.
results are 263 412 entities
Each points are a node with cost, exemple:
Points = {node : 123, cost : 0.2345643}

Contour configuration :
Input
Vector layer : may_layer
data field : cost
Contouring
contour lines
number: 5
Min: 0.0000
Max: 0.8300
Extend: neither
Method: equal

Layer name : Contour
Label precision 4

I try a lots of config but i have the same error.


Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-49649508.


This message contains information, which may be in confidence and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or info@linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank You.

@vincentcau
Copy link
Author

Hello Chris,
In fact the problem is my data set contains too many points.
I test with a data set of 10 000 points and the plugin work very well !

i'll change my approach and modify my request, but i would lose i precision.
Thank for your quick response.

Best regards.
Vince

@chadw17
Copy link

chadw17 commented Jul 25, 2014

I still have trouble with this plugin. I am using data with about 20,000
points. I have to delete them until I have only about 500 points before I
stop getting the exception struck error. Going to try again today with a
new set of data points and see what happens.
On Jul 22, 2014 2:07 AM, "Vince" notifications@github.com wrote:

Hello Chris,
In fact the problem is my data set contains too many points.
I test with a data set of 10 000 points and the plugin work very well !

i'll change my approach and modify my request, but i would lose i
precision.
Thank for your quick response.

Best regards.
Vince


Reply to this email directly or view it on GitHub
#8 (comment)
.

@ccrook
Copy link
Owner

ccrook commented Jul 27, 2014

Just further to this - I've recently used the plugin with a grid of data that contained over 700,000 points. (Not quick - but it worked). I think that the exceptions that are being struck are generally to do with the configuration of the points. I've released a new version of the plugin that implements an optional (and very crude) point thinning algorithm to help bypass this issue...

@chadw17
Copy link

chadw17 commented Aug 3, 2014

Sounds great. I have a set of data points I am going to try this week will
let you know how it goes. All of the data points I use come from a depth
finder on a boat.
On Jul 27, 2014 4:03 PM, "Chris Crook" notifications@github.com wrote:

Just further to this - I've recently used the plugin with a grid of data
that contained over 700,000 points. (Not quick - but it worked). I think
that the exceptions that are being struck are generally to do with the
configuration of the points. I've released a new version of the plugin that
implements an optional (and very crude) point thinning algorithm to help
bypass this issue...


Reply to this email directly or view it on GitHub
#8 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants