Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
README.md
annotations.md
backend.ts
base.ts
frontend.ts
meshes.md
register_default.ts
segment_properties.md
sharded.md
skeletons.md
volume.md

README.md

The "precomputed" data source format is based on static collections of files served directly over HTTP; it therefore can be used without any special serving infrastructure. In particular, it can be used with data hosted by a cloud storage provider like Google Cloud Storage or Amazon S3. Note that it is necessary, however, to either host the Neuroglancer client from the same server or enable CORS access to the data.

Several types of data are supported:

HTTP Content-Encoding

The normal HTTP Content-Encoding mechanism may be used by the HTTP server to transmit data in compressed form; this is particularly useful for the JSON metadata files, unsharded "raw" or "compressed_segmentation" volume chunk data, unsharded skeleton data, and unsharded mesh manifests, which are likely to benefit from compression and do not support other forms of compression. Some HTTP servers can perform this compression on the fly, while others, like Google Cloud Storage, require that the data be compressed ahead of time. Note that with Google Cloud Storage (and any other system that requires ahead-of-time compression), the use of Content-Encoding is not compatible with HTTP Range requests that are needed for the sharded index and data files and unsharded multi-scale mesh fragment data files; therefore, ahead-of-time compression should not be used on such files.

You can’t perform that action at this time.