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

Error when creating an archive for exporting referral vectors #388

Open
loicbaecher opened this issue Aug 11, 2022 · 5 comments
Open

Error when creating an archive for exporting referral vectors #388

loicbaecher opened this issue Aug 11, 2022 · 5 comments

Comments

@loicbaecher
Copy link

Current Behavior

When trying to create an archive for exporting referral vectors, an error occurs. The error occurs even if the maximum data size limit is increased. The error occurs not at the exporting step but at the archive creation step. The referral vectors are the only component in the archive.

Detailed Description

The error message is the following :

  time type msg
4999 2022-08-11@10_00_18 log The command:v.out.ogr --overwrite input=vReferralNetwork__ZMBref output=/tmp/RtmpkDhpNM/qiftotjcwqrgktmswtc/vector_referral_network_ZMBref output_layer=vector_referral_network_ZMBref format=ESRI_Shapefileproduced an error (1) during execution:Warning 1: 2GB file size limit reached for /tmp/RtmpkDhpNM/qiftotjcwqrgktmswtc/vector_referral_network_ZMBref/vector_referral_network_ZMBref.shp. Going on, but might cause compatibility issues with third party softwareERROR 1: Failed to write shape object. The maximum file size of 4294924780 has been reached. The current record of size 101944 cannot be added.ERROR: Failed to create OGR featureCallexecGRASS_orig(v.out.ogr, input = vReferralNetwork__ZMBref,output = /tmp/RtmpkDhpNM/qiftotjcwqrgktmswtc/vector_referral_network_ZMBref,output_layer = vector_referral_network_ZMBref, flags = overwrite,format = ESRI_Shapefile)
@fxi
Copy link
Collaborator

fxi commented Aug 11, 2022

Thanks for posting this.
This is an underlying limitation of shapefile export and OGR. [ I don't remember having ] reached this before.
The solution would be to export as sqlite or gpkg. We could let the user decides the format. It's about 1/2 day of work + testing. @nicolasray
Meanwhile, the data will be.. locked inside the DB. That's a bummer.
I can try to manually recover it, if required.

@loicbaecher
Copy link
Author

Understood.
Thank you for the proposition.
Yes please, I would very much like to see this shapefile (as well as another one for which I have a similar problem), if you have time to recover it (them).

@loicbaecher
Copy link
Author

Thanks for recovering the data. I wanted to mention that I have indeed noticed that some route vectors were not complete (even when exported as gpkg), as you mentionned. More especially, the vector is not drawn in its entirety but the travel time and distance values have been correctly calculated. I have tried relaunching a referral analysis to calculate an incomplete route which, this time, was drawn in its entirety.

@fxi
Copy link
Collaborator

fxi commented Aug 16, 2022

Ok. Did the analysis that produced the routes finish without error / warnings ?

@loicbaecher
Copy link
Author

As far as I remember, they were no errors or warnings.

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

No branches or pull requests

2 participants