15 results have been found
Guide to Detector Ingestion API
/en/node/2704
The Detector Ingestion API provides an endpoint to submit raw detector measurements for a PTV Flow product instance. The submitted measurements are validated, archived, and forwarded for …
Use Case
/en/node/2717
Partial batch acceptance: valid and invalid items A System Integrator (SI) submits a batch where some measurements are valid and some are not (for example, a detector code that does not exist, or a reserved field set to a non-null value). The service …
Use Case
/en/node/2714
Partial batch acceptance: high volume ingestion A System Integrator (SI) submits a batch of 20.000 measurements. Due to the volume of the batch and the limit of the architectiure, the processing budget is exceeded after validating 14.000 items. The …
Limitations
/en/node/2744
For architectural reasons, you can ingest up to 14.000 measurements in one only batch operation. If you want to load: One measurement for every detector, you can load 14.000 measurement joined to 14.000 detectors. Two measurements for every detector, you …
Relevant Terms
/en/node/2708
The Detector Ingestion API service is connected to Detectors API service. For this reason is relevant to take a look to Detectors API Relevant terms section. Gzip Gzip (GNU Zip) is a widely used file format and software utility for lossless data …
API Reference
/en/node/2715
{ "openapi": "3.0.3", "info": { "title": "Data Provider Detector Ingestion API", "description": "The *Data Provider Detector Ingestion API* provides an endpoint to submit raw detector measurements\nfor a product instance. Submitted measurements are …
Quick Start - Detector Ingestion API
/en/node/2709
You can use the Detector Ingestion service to implement standard batch ingestion of the measurements associated with the detectors in your Flows instance. A typical scenario is a client application (for example, a telemetry system) that provides a …
Use Case
/en/node/2557
Add two detectors to a count location associated to a count site The System Integrator (SI) creates a sensors network. First step In one only payload the SI can build the entire hierarchy of count sites, count locations and detectors. In this use case, in …
Payload sizing
/en/node/2626
A count site represents a logical object (like an intersection or a parking facility) where speeds, flows, counts, etc. are measured with different technologies (for example, loops and cameras). It is a logical aggregation of many types of hardware …
Relevant Terms
/en/node/2445
Count site A count site represents a logical object (like an intersection or a parking facility) where speeds, flows, counts, etc. are measured with different technologies (for example, loops and cameras). It is a logical aggregation of many type of …
Quick Start - Detectors API
/en/node/2447
With the Detectors service you can get several types of measurements from the field of your instance. Follow the steps on this page to get started with Detectors …
Use Case
/en/node/2560
Add a vehicle type The System Integrator (SI) needs to add a new vehicle type. First step As starting point, it is necessary to check which vehicle types are associated to your instance. GET …
API Reference
/en/node/2432
{ "openapi": "3.1.1", "info": { "title": "Data Provider Registry API", "description": "The *PTV Flows Detector API* provides endpoints to access detector data of your product instance. It offers functionalities such as:\n* management interfaces for *count …
Guide to Detectors API
/en/node/2433
The Detectors API can be used to build a count site capable to register several types of real-time data. A count site represents a logical object (such as an intersection or a parking facility) where speeds, flows, counts, etc. are measured using …