You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for amazing flatgeobuf. Seems we finally have something after decades of dealing with shapefiles. Can't wait for adoption by mainstream GIS. I am getting occasional GET http://localhost/some.fgb net::ERR_CACHE_OPERATION_NOT_SUPPORTED with flatgeobuf-geojson.min.js. Not sure if I am doing something wrong. I am getting this error in both Chrome and Edge. The frequency of this error might be correlating with number of features being fetched but I do get it anywhere between fetching a couple hundred to tens of thousands.
Uncaught (in promise) TypeError: Failed to fetch
at pt.getRange (flatgeobuf-geojson.min.js:15:20070)
at ft.getRange (flatgeobuf-geojson.min.js:15:19425)
at dt.readFeature (flatgeobuf-geojson.min.js:15:18667)
at dt.readFeatureBatch (flatgeobuf-geojson.min.js:15:18536)
at readFeatureBatch.next ()
at Function. (flatgeobuf-geojson.min.js:15:10825)
at flatgeobuf-geojson.min.js:15:1510
at Object.next (flatgeobuf-geojson.min.js:15:1615)
at flatgeobuf-geojson.min.js:15:552
at new Promise ()
The text was updated successfully, but these errors were encountered:
I've not seen this issue. Sure it's not an issue with your local webserver?
Thank you for quick reply. Might be my misunderstanding of what cache this error talks about. I thought it is about browser cache. I will do some more testing including AWS servers after I deploy from local to dev and come back with findings.
Thank you for amazing flatgeobuf. Seems we finally have something after decades of dealing with shapefiles. Can't wait for adoption by mainstream GIS. I am getting occasional GET http://localhost/some.fgb net::ERR_CACHE_OPERATION_NOT_SUPPORTED with flatgeobuf-geojson.min.js. Not sure if I am doing something wrong. I am getting this error in both Chrome and Edge. The frequency of this error might be correlating with number of features being fetched but I do get it anywhere between fetching a couple hundred to tens of thousands.
The text was updated successfully, but these errors were encountered: