Different C:N ratio approaches in biofloc system for Pacific white shrimp

Open data API in a single place

Provided by Zenodo

Get early access to Different C:N ratio approaches in biofloc system for Pacific white shrimp API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2023.03.14 00:00
Created
2023.01.01
Available languages
English
Keywords
Shrimp, nitrification, water quality
Quality scoring

Dataset description

We evaluated two C:N ratio in this experiment. The first one, was an heterotrophic system with C:N ratio of 15:1. Three days before stocking, water was fertilized with feed and white sugar at carbon/nitrogen ratio (C:N) of 15:1 in order to reach 200 mg L-1 of total suspended solids (TSS) at the beginning of the rearing period. During the experiment, when total ammonia nitrogen (TAN) surpassed 1 mg·L-1, extra sugar was added to the system at a ratio of 20 g of sugar per each gram of TAN. For the second one, we use a C:N ratio of 8,9, with inoculation of water from a mature tank. The experimental tanks of the mature biofloc treatment (n = 4) were by mixing 90 L of water from a biofloc tank stocked with shrimp (30%; matrix tank) and 210 L of seawater. The matrix tank was a 9 m3 circular tank stocked with 300 adult shrimp m-3 (weight = 21.3 ± 0.52 g). Water quality parameters of matrix tank were as follows: salinity 37 g L-1, TAN 0.21 mg L-1, alkalinity 136 mg L-1, pH 8.01, TSS 450 mg L-1, orthophosphate 1.2 ± 0.08 mg L-1, nitrite 0.12 mg L-1 and nitrate 41.7 mg L-1, indicating that the process of nitrification had occurred. The results of the trial indicated that the C:N of 8.9 with inoculation of water from a mature tank is enough to maintain the water quality and shrimp growth performance. 
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks