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

Max file size? #8

Open
cristianmad opened this issue Aug 19, 2020 · 1 comment
Open

Max file size? #8

cristianmad opened this issue Aug 19, 2020 · 1 comment
Labels
question Further information is requested

Comments

@cristianmad
Copy link

cristianmad commented Aug 19, 2020

Hi,
When using large .geojson files (in my case >1.6GB), I noticed that the provider is throwing an error.
{"message":"Error parsing file ....geojson: Cannot create a string longer than 0x3fffffe7 characters","level":"error"}

When going through the source code I noticed that it seems to load the entire file content in memory and then parse it. Is this correct? Would it make sense to read one entry at a time (or maybe a buffer), process it and then add each processed item/batch to the result? (unless there is a limit on the result as well).

Thanks!

PS: I'm new to koop so maybe a silly idea :)

@rgwozdz
Copy link
Member

rgwozdz commented Aug 20, 2020

I think you could try, though at some point increasing file sizes will produce some noticeable latency. Once your data is all processed it will get sent on to other Koop dependencies that handle any filtering, sorting, reprojection, etc, that is defined by the request.

Also if you are using the feature server output, it will limit the number for features returned to a max amount (it expects large datasets to be paged).

@rgwozdz rgwozdz added the question Further information is requested label Aug 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants