I increased the size of

client_max_body_size 500M

in geonode.kartoza.nginx.conf

Hi @timlinux and mas @lucernae

I try to upload the training data to the geonode.inasafe.org, but some data failed to upload. Failed because entity too large.

This totally size of building data 71.1 MB

And, then I find failed upload when I try to upload the raster population.

I check to the layer but there is no raster population layer has been uploaded. This totally size of raster population data are 149 MB

increased the size of
client_max_body_size 500M
in geonode.kartoza.nginx.conf

this max size also support to the geonode.inasafe.org or not?

• If yes, why the data that under 500M size can not upload properly?
• If no, please make it happy 😄

Hi @felix-yew
The one that @lucernae changed is the one for geonode.kartoza. It's different instance of geonode, and has different setting. I will see if I can set it to 500 MB also for geonode.inasafe.org.

It's this one:
https://github.com/kartoza/docker-geosafe/blob/develop/deployment/docker-nginx/nginx.conf#L49
If you have any nginx reverse, modify accordingly.

Also, this issue is not related with this repo, I think.
Can you move this issue somewhere @ismailsunni and close it once it's done.
Perhaps to docker-geosafe, and make PR there.

Let's chunk the files during upload to avoid this problem.

@cchristelis @euclidian how is progress with chunking (using AT approach?)

Will this be applied to raster and vector uploads?

@gubuntu, yeah, the same approach. @euclidian seems to be having some difficulty finding his feet with the JS.

@NyakudyaA didn't you test demo.geonode.org and it doesn't fail with large file uploads? Did you come to any conclusions?

@gubuntu I tested the demo site and they have issues with uploading big datasets as well. I saw on the geonode list the geonode guys have it on their to-do list as well.