...
This page deals with creating and configuring feeds in the yellow portal, not with how to publish them on your website. There is a separate page dealing just with that: https://avisec.atlassian.net/l/c/1WH0vJCv
General feed settings
Feeds have general settings like branding and contact options that are configured per camera rather than per feed individually. Read about these settings here: https://avisec.atlassian.net/wiki/x/CoAnuw
Creating and configuring feeds
...
Token: Each feed receives a randomly generated token that allows accessing the feed through feed.yellow.camera/<token>. The token is not configurable and will be generated once you save the feed. The token is guaranteed to be unique, and is guaranteed to always stay the same for a feed. In other words, you will not be able to change it.
Token alias: While the token is the most unambiguous identifier for a feed, it often doesn’t look pretty in a url. Also, you might decide to create another feed at some point to replace the current one, and still want to refer to it by the same name. So if you wishFor these reasons, you may specify an alias that will allow access to the feed as well, so you can for example link to your feed through
feed.yellow.camera/Plateau.MountLookitthat, instead of something less descriptive like feed.yellow.camera/IYRLNAEVNRYAUFTNCRAccessibility: There’s three accessibility levels: Web-Open, Public, and Private. Web-Open means that you are giving avisec implicit permission to use your feed in the promotion of yellow productspublish your feed, and allows search engine bots to index it. Public means the feed is accessible to anybody that knows the token or alias, and may not be re-published or indexed. Private means the feed is not accessible at all. Use it if there’s an issue and you need to take a feed offline temporarily, as deleting a feed may lead to issues because its replacement will almost certainly be assigned another token.
Latest image is public: If you check this checkboxbox, the latest image in the feed can be downloaded directly through api.yellow.camera/feed/<token>/latest.jpg. Sometimes this is useful, because it allows you to present the image in your own way if needed. Sometimes this is undesirable, because it might not be in your interest for 3rd parties to be able to access the image without your branding that comes with the feed.
Name: A name of for the feed , mostly intended to make the feed more easily identifiable by human users in the portalfor identification. It will be displayed in the feed list in the portal. It will not be visible in the feed itself.
Title: A title for the feed. The title will be displayed in the feed itself when configured in the cameras general branding options, and can be combined with a link.
Camera: The feed must reference a certain camera.
Table: The feed must point to a specific image table of the referenced camera. This is where all images visible in the feed will be taken from. Note that the camera and table cannot be altered once the feed is created.
Type: The type of feed you want to create. See next chapter. The type can only be selected once a camera has been chosen.
Description: Enter a text description that will be displayed in the feeds info popup. The text may contain links in the form of HTML <a> tags, but no other HTML elements are supported.
Error page URL: You may enter a link to a page that should be loaded if the feed currently has an error for whatever reason.
Show error page right now: Check this box to force the feed to display the error page instead. This can be helpful for hiding a feed on short notice should the need arise.
Types of feeds
There are different types of feeds, each with somewhat different configuration options and functionality. Currently, the following types of feeds are available.
...
The history feed publishes the ten latest images of your feed, for the times when you want to grant give people a wider bigger picture:
...
Archive feed
The archive feed is very similar to the history feed, but allows you to publish all images going back a configurable amount of days. It is recommended that you don’t configure a number of days larger than you consider absolutely necessary for your purposes. Publishing a long chronological selection of images makes it rather easy to accidentally violate GDPR-compliance.
...
You may better and more securely achieve what you intend by giving select persons a guest account for a specific camera table in the portal instead (you can easily do this using the invite feature in the cameras browse page).
If you just want to show progress over a longer time, a timelapse feed will demonstrate it more effectively.
You should never create a browsable feed on a table with original, high-resolution images.
Consider using the anonymiser to remove moving objects and persons from the images, as well as identity masks or overlays to hide areas in the image that may violate GDPR, like roads, surrounding buildings, etc.
While a feed token is an identifier, not a security measure, you it does provide some obscurity. You should never publically share a browsable feed's token and only make it known to persons that need to know and won’t publish it further. Do not publish a browsable feed or its token on a website, and do not give it an easy to guess alias!
...
Delay in days: Configure an amount of days the timelapses should lag behind the current state. Similar to the delay in the delayed feed, except it cannot be so granular, since timelapses are only rendered once each day.
Days: The amount of days backwards in time the timelapse should cover.
Length: The length the rendered video should have, in seconds. This can range from 10 seconds to 5 minutes. Note that the video is rendered at a fixed framerate. If there are not enough images in the day span you configured, it may be that the video ends up shorter than this. If there are more images in the configured range than can be fit in the videos length, the timelapse will still show the entire progress during those days, but will drop images at regular intervals to make the video fit the configured length.
Panning image feed
A panning image feed is an animated feed that will render your image using the full available height of the viewport and will pan from one end of the image to the other and back. Optionally it can also do an endless pan in the same direction for images that wrap around.
Panning speed: How many seconds the pan should take to move from one end of the image to the other.
Continuous pan: If checked, the feed will pan endlessly in one direction. This is intended to be used with 360 degree images that wrap around
Panning feed vs. Panofeed
The panning feed seems similar to the Panofeed (read more on it below), but is really not the same thing. A Panofeed provides a full, dynamic view of images potentially more than 100 megapixel in size. It can be panned manually and is zoomable, and can display hotspots in the image. A panning feed offers none of those features. It is intended for a preview-style publication of a much smaller image with a similar aspect ratio. With a properly sized image, a panning feed will load much faster than a Panofeed and is therefore more suited to publication in galeries or similar. On the other hand, a panning feed with a full-sized pano image will be a disaster that slows your website to a crawl, as it does not support any dynamic loading whatsoever.
Panofeed
The panofeed was especially developed for the yellow avisec panocam, to present arbitrarily large images fluently zoomable and panable in a web browser. Beyond that it has its own branding options, a 30 day archive, and the ability to place visual markers on top of the presented image to highlight points of interest. Despite being develped with 360 degree images in mind, it can be used to publish images that do not cover 360 degrees, and that originate from any camera. Do note however that unless you have a panocam, the panofeed is not included in the standard price and will incur additional costs.
For details on how to configure a panofeed, please refer to its own page.
Feed branding
Most feeds have the option to add branding to them, which is configured through the camera configuration. The idea here is to make it as simple as possible for all feeds of a camera to share a unified aesthetic, without configuring each individually.
Excluded from that are the timelapse feed, which currently doesn’t have any branding options, and the panofeed, which has completely different branding options.
The branding options for a cameras feed can be found on the camera configuration page:
...
Yellow Logo: If checked, the yellow logo will be displayed in the feed.
...
Partner Logo: If checked, the logo of the partner that delivered the camera will be displayed.
...
Customer Logo URL: If defined, the linked logo will be displayed in the feed as well, which will usually be the logo of the customer.
...
Logo Link: A link that is followed when the customer logo is clicked.
...
Show Title: If checked, the feeds title will be displayed. Add a title link if you want the title to become a clickeable link.
...
Show timestamp: If checked, the current images timestamp will be displayed.
...