We are trying to use GeoEvent server to pull in updated data from an external system using the "Watch a Folder for new GeoJSON Files" input connector.
Right now, the set-up is that the server machine housing GeoEvent calls an external URL to download a GeoJSON each hour and saves it in a folder on the machine. Then GeoEvent watches that folder for new GeoJSONs. This process was working as expected with the initial GeoJSON pull that it was tried with. We then realized there was a different GeoJSON we should be pulling, and updated the call on the server machine to pull that GeoJSON. The only difference between these GeoJSONs is their size (due to an increase in features included) - the original pull was about 3.5 MB and the new one is about 25.5 MB.
Is there a limit for the size of a GeoJSON that GeoEvent can handle? Or is there something additional we should look at?
Seems like you've done everything right. Two things to check:
The first is the filename. GeoEvent may ignore a file it thinks it has already processed, so try to append a datetime to the end of the filename as it is saved.
For the second, please see the following blog on wathching folders for files. Sometimes the file is large enough that the file system takes some time to write the file; if GeoEvent tries to grab the file while it is still being written, it can cause issues.