camera.jpg

CVE Operation

Return current raw camera image. The returned image is lossy and compressed for best bandwidth usage. For monitoring, use monitor.jpg instead of camera.jpg, since the former provides more information.

• Example: http://firepick:8080/firerest/cv/1/gray/camera.jpg

HTTP GET

• MIME: image/jpeg
• status 404: Camera not available

HTTP POST (recommended)

Support for HTTP POST enables additional use cases such as external image acquistion and camera-less computer vision testing. For example, this capability was added to FireFUSE in order to leverage existing raspistill software for camera image acquisition. Adding the capability to FireFUSE automatically provides it to FireREST/CV via NodeJS. The FireREST/CV utility of HTTP POST for camera.jpg will probably be limited to system testing, since it is now possible at the FireREST/CV level with mock images. Additional use cases may evolve.

• MIME: image/jpeg
• status 404: Camera not available

Synchronous, Blocking Requests

By default, FireREST requests use cached results and do not block. If your application requires and is willing to wait for the latest camera image, use the synchronous, blocking form of the URL. Blocking requests monopolize FireREST resources, so use them only when needed.

• Example: http://firepick:8080/firerest/sync/cv/1/gray/camera.jpg

See Also

• FireREST-CV
• FireREST-CV-PnP
• camera.jpg
• output.jpg
• monitor.jpg
• Synchronous-Requests