Video surveillance system

Abstract

A video management system (VMS) 300 for use in, for example, surveillance system 10 applications, comprises: a recording server 320, a user interface (UI) client 400, and a processing unit . The recor

Description

TECHNICAL FIELD The present disclosure generally relates to video surveillance systems and 5 optionally computer-implemented video management methods for video surveillance systems. BACKGROUND Modern video surveillance systems have evolved into highly complex and often 10 heterogeneous systems comprising a large number of different peripheral devices and computer hardware elements that are tied together via a networked infrastructure, and controlled by means of advanced management software. One important component of modern video surveillance systems is a video recording and processing system that allows video streams from one or more video 15 cameras to be received, stored and processed. A video management system (VMS), also known as video management software or a video management server, is a component or sub-system of a video surveillance system. The VMS typically provides various video management services, such as one or more of the following: collecting one or more video 20 streams from one or more video cameras, storing the received one or more video streams to a storage device and providing an interface to view the received one or more live video streams and / or to access one or more stored video streams. Further, a VMS may be configured to also handle other types of data besides video streams such as, but not limited to, audio streams, data from monitoring 25 services such as motion detectors, fire alarms, etc. Moreover, it is generally desirable that surveillance systems and, in particular, VMSs are versatile and can be used in different types of applications which may impose different demands or requirements to processing and displaying received video streams supplied by the one or more video cameras. Moreover, the 30 demands and requirements imposed in a surveillance system may change over time. 31 03 25 A particular challenge to video surveillance systems and the VMS subsystem is to handle video streams supplied by moving or movable, i.e. non-stationary, video cameras during normal operation of video surveillance system. The movable video camera or cameras may move or travel through a geographical 5 surveillance area and / or facilities like office buildings etc. A further challenge for video surveillance VMS subsystems is to present data to a user / operator in a way that facilitates the user’s comprehension of the data and thereby the user’s decision-making. 10 SUMMARY It is an object of at least some aspect described in the present disclosure to solve one or more of the problems identified above and / or other problems associated with existing video surveillance systems, or at least to provide an alternative to known systems. 15 In an aspect there is disclosed a video management system (VMS) according to claim 1. Optional features of the aspect may be according to claims 2 to 9. The metadata stream associated with each video stream may comprise timestamps, i.e. a digital record of time, together with corresponding FOV data associated with the video camera in question. This allows for time 20 synchronization of the video streams and metadata streams received at the VMS. Timestamps associated with metadata “frames” and timestamps associated with video frames may be separate such that a time synchronization is necessary in order to relate the frames to each other. For example, so as to be able to determine the FOV of the selected camera at a time associated with a displayed 25 video frame. During time synchronization a given frame is related to a relevant frame from the other stream, i.e. for a given video frame a relevant metadata frame is coupled to it or for a given metadata frame a relevant video frame is coupled to it. The relevant video frame may be the one having a timestamp at or before the timestamp of a given metadata frame. Likewise, the relevant metadata 30 frame may be the one having a timestamp at or before the timestamp of a given video frame. In some instances, the relevant frame is more appropriately chosen 31 03 25 as the frame having a timestamp that is later than the timestamp of the given frame. Thus, the relevant frame may not be the frame having a timestamp closest to the timestamp of the given frame from the other stream. For example, it may be more suitable in a given scenario to relate a given frame from one stream to a 5 frame from another stream having a timestamp at or before the timestamp of the given frame even though the frame that is closest in time is one having a later time stamp compared to that of the given frame. In some cases, the timestamps of the frames in the metadata stream match the timestamps of the frames in the video stream exactly. This may occur when the 10 metadata is generated based on an analysis as is well known to a skilled person. It may also occur when the metadata and video originate from the same source. However, when the video streams and the metadata streams originate from independent, although associated, sources, the frames will have entirely independent timestamps, e.g. a GPS device associated with a video camera may 15 only be providing the position each second, whereas the associated video camera may be providing 25 video frames per second. Each video camera may further be associated with multiple metadata streams, which may each originate from an independent, but associated, source such that the associated metadata streams may comprise multiple sets of timestamps. 20 Thus, the FOV of a selected camera at a time associated with a displayed video frame from the selected camera may be determined following a time synchronization. Metadata may be obtained from different sources. Field-of-view (FOV) data is also metadata, i.e. data that describes and gives information about other data. 25 The FOV data used in the determination of an adjusted FOV may for example be obtained from a driver, or from a setting, such as a default setting, or as metadata in a metadata stream associated with a video stream. The adjusted FOV may for example be determined using a default setting of the lens and / or using image sensor information obtained from a driver. In some embodiments, the FOV data 30 is obtained, entirely or partially, by the VMS as a metadata stream supplied by, or associated with, the video camera from which the respective video stream was acquired. The position of a respective camera may be obtained from a camera-associated GPS unit or device. 31 03 25 The determined adjusted FOV may be added to the metadata stream for the respective camera, and may be stored as part of the metadata stream. The determined adjusted FOV may be stored in a metadata stream of its own. Each video camera in the plurality of video cameras may be associated with multiple 5 metadata streams. In some embodiments, the recording server is further configured for receiving and storing the plurality of video streams with which the plurality of metadata streams is associated, respectively. The processing unit may be configured to store the plurality of video streams and respective metadata streams in a video data 10 repository and in a metadata repository, respectively, and to retrieve the plurality of video streams and respective metadata streams from the video data repository and metadata repository, respectively, as discussed in further detail below with reference to the appended drawings. The plurality of video cameras may comprise at least one movable video camera 15 and optionally one or more stationary video cameras. In some embodiments, the plurality of video cameras comprises a plurality of movable video cameras. The movable video cameras may each travel along a path or trail within an area via mounting to any suitable support structure of a vehicle, for example motorized vehicles like cars, trucks, busses, trains, motorcycles etc. The movable video 20 cameras may be moved or transported along the path or trail of the area by way of mounting on, or worn by, a person via a suitable support like a belt etc. The one or more optional stationary video cameras may be mounted on, or fixed to, various kinds of stationary structures like factory or office buildings, train stations, support structures, etc. and may be arranged at traffic roads or junctions or the 25 like. Metadata on the position and orientation of a camera together with metadata on the image sensor and lens information of the camera allows for the calculation of a theoretical FOV of the respective camera, i.e. the extent of the area within which the camera can observe the world at any given moment. 30 The image sensor and lens characteristics will provide information on the width and depth covered by the camera. While the image sensor and some characteristics of the lens of the camera usually does not change over time, the 31 03 25 lens information will comprise both physical, i.e. fixed, characteristics of the lens, and the current, i.e. dynamic, zoom level. Thus, these characteristics provide the shape of the FOV of the camera. The position and orientation of the camera will provide the information needed to 5 determine where the camera is viewing from and in which direction. In some embodiments, the metadata for the orientation of each camera comprises one or more of: compass direction, relative pan, and relative tilt. A geo-map is a map of a geographical area. An icon representative of the selected camera may be displayed on the geo-map at a camera map position, 10 where the camera map position is a geographical position in the shown map. The camera map position may be the last known position of the selected camera, or the camera map position may be based on the reported position of the respective selected camera at a given time. The III client may continuously update the geo-map such that the extent of the 15 selected camera’s FOV is comprised in the geo-map, i.e. such that the geographical area within the camera’s FOV is comprised within the geo-map. The geo-map is updated when the camera position or FOV data changes, such as when the camera position or FOV data changes more than a pre-determined threshold. Alternatively, or additionally, the geo-map may be updated at pre- 20 determined time intervals. Thus, the geo-map will follow the camera FOV to always show the user of the VMS the area, which the selected camera is in. Such a dynamic update means that the geo-map will show an area that is updated each time the FOV and / or position of the selected camera changes. This improves the user’s awareness of the location and other features in the same 25 area as the selected camera. The III client may be configured to display, on the geo-map, a pre-determined area extent in addition to the FOV of the selected camera and dynamically zoom in and out on the geo-map as the FOV of the selected camera changes, e.g. as the zoom of the selected camera increases, the geo-map will zoom out, and as the zoom of the selected camera decreases, 30 the geo-map will zoom in. The pre-determined area extent may be selected by a user. 31 03 25 The III client may be configured to centre the geo-map, for example to centre the geo-map relative to the FOV of the selected camera and / or such that the camera map position of the selected camera is always centered, for example at least along the horizontal axis of the geo-map. A plurality of centering options may be 5 available for a user to choose from. An option may be to have the camera map position of the selected camera centered both horizontally and vertically. This centering option may work well with a geo-map display, where north in the map is always pointing up, i.e. towards the top of the display on which the GUI with the geo-map is running. Alternatively, the geo-map displayed may orient itself such 10 that the central line-of-sight of the camera is pointing up, i.e. such that the bearing of the geo-map changes according to the orientation of the camera. Such a centering option may work well in a situation where the GUI is also showing the video stream in a frame at the same time as the geo-map is being shown, since this will provide a user with directions in the video and geo-map displays that are, 15 to most users, well connected visually, i.e. left and right in the video are the same as in the geo-map, while forward and backward in the video are up and down, respectively, in the geo-map. Another option is to make the bearing of the geomap dependent on the orientation of the camera, while also taking into consideration the dimensions of the geo-map layout. For example, if the layout of 20 the geo-map view is a long and thin rectangle, e.g. with ratio 1:3, having the camera map position close to a side of the view, i.e. close to one of the shorter sides of the rectangle, with the camera oriented towards the opposite side may allow for the better view of what lies in the FOV in the area shown in the geomap. In some embodiments, the geo-map is centred in the FOV of the selected 25 camera, e.g. positioned at half of the width at half of the depth of the FOV of the selected camera. In some embodiments, the UI client is further configured to display, on the geomap, a graphical representation of the FOV of the selected camera. As the FOV of the selected camera changes, the graphical representation of the FOV on the 30 geo-map is updated to reflect the change. In some embodiments, the processing unit is further configured to: - determine the subset of the plurality of video cameras for which the position of the video camera is within the geographical area 31 03 25 displayed in the geo-map and / or for which the FOV of the video camera is at least partially within the geographical area displayed in the geo-map; and wherein the III client is further configured to: 5 - display an icon on the geo-map representative of each camera in the subset at a respective camera map position. Thus, the geo-map may be configured to have icons representing a geographical position of other cameras, i.e. cameras other than the selected camera, within the geographical area displayed in the geo-map. Additionally, the geo-map may also 10 have icons representing the geographical position of other cameras having a FOV that lies at least partially within the geographical area displayed in the geomap. Thus, the geo-map may provide information on other cameras that are positioned outside the area shown in the geo-map, but for which the FOV extends into the area. The icon of such cameras positioned outside the area of 15 the geo-map may be positioned e.g. on the edge of the geo-map that is closest to what would be the camera map position of that camera. Alternatively, or additionally, the icon representing a camera positioned outside the area of the geo-map may have an arrow, or other indicator, pointing towards the camera map position of that camera. 20 In some embodiments, the III client is further configured to display, on the geomap, a graphical representation of the FOV within the geo-map of each of the cameras in the subset of the plurality of video cameras. The selected camera may be selected by e.g. a process or a user. For example, the III client may be configured to receive user input provided by a user, the user 25 input comprising a selected one of the plurality of video cameras. A process that selects a camera may be a process responding to an incident, for example a process that responds to an alarm being triggered, or a process that is part of a search. In some embodiments, the III client is further configured to display, on the geo-map, a user-activatable button associated with each of the cameras in 30 the subset of the plurality of video cameras, wherein activating a button selects the associated camera in the subset, and wherein, optionally, the user-activatable button is comprised in the icon 31 03 25 representative of the respective camera in the subset at the camera map position of the respective camera. In some embodiments, the processing unit is further configured to: - receive Geographic Information System (GIS) data associated 5 with the position of the selected camera; - determine an adjusted FOV associated with the video stream of the selected camera, the determination being based on the FOV data and on the GIS data, where the adjusted FOV indicates unobscured FOV and / or limited-visibility FOV, 10 wherein the FOV of the selected camera utilized in the displaying of the geo-map is the adjusted FOV. The GIS data may be a dataset stored in a suitable manner in a component within the VMS, for example in a GIS repository, or the GIS data may be obtained from a database external to the VMS. 15 In the determination of the adjusted FOV, structures described in the GIS data for the area covered by the FOV may be used to remove obstructed parts of the FOV of the camera, or mark parts of the FOV of the camera as having limited visibility. That is, the part(s) of the FOV of the camera for which the line of sight is interrupted by one or more structures described in the GIS data can be 20 accounted for by the FOV being adjusted to not include the areas beyond the interrupted line of sight or to mark one or more areas as having limited visibility. The determination of the adjusted FOV may be done using geometric intersection calculations to account for the structures described in the GIS for the area covered by the FOV. 25 The processing unit is further configured to: - determine the direction of movement of the selected camera at the associated time, - determine a projected FOV area, which is an estimate of an area covered by the FOV of the selected camera at a later time, where 30 the projected FOV area is based on the direction of movement of the selected camera, 31 03 25 wherein the III client is further configured to: - display, on the geo-map, a geographical area that additionally comprises at least the extent of the projected FOV area of the selected camera. 5 Thus, the geo-map additionally shows at least the extent of an area ahead of the FOV in the direction of movement of the camera, i.e. a part of the geographical area that the camera view is moving towards, and possibly into unless a change of direction is made. If the camera is moving straightforward, the projected FOV area will be further in front of the camera, whereas if the camera is turning, and 10 its movement is sideways, the projected FOV area will be to the side of the FOV towards which the camera is turning. The direction of movement of the selected camera may be determined from the FOV data, e.g. from the position of the camera at different times. In some embodiments, the processing unit is further configured to display, on the 15 geo-map: - a graphical representation of the projected FOV area, or - a graphical representation of at least the part of the projected FOV area, which is not part of the graphical representation of the FOV of the selected camera. 20 Thus, the geo-map may display a graphical representation, such as an outline, of the entire projected FOV area, or it may show a graphical representation only the projected FOV area that does not overlap with a graphical representation of the FOV. In some embodiments, the geo-map is centred in the combined area covered by 25 the FOV of the selected camera and the projected FOV area. In another aspect is disclosed a video surveillance system comprising: a plurality of video cameras arranged in a surveillance area and configured to generate respective video streams, wherein each camera of the plurality of video cameras comprise, or is associated with, a position detecting 30 device and an orientation detecting device configured to add position metadata and orientation metadata, respectively, to each of the respective video streams; 31 03 25 and a video management system (VMS) as disclosed herein. The plurality of video cameras may comprise at least one movable video camera and optionally one or more stationary video cameras according to one 5 embodiment of the video surveillance system. In some embodiments, the plurality of video cameras comprises a plurality of movable video cameras. The movable video camera(s) may each travel along a path or trail within the surveillance area via mounting to any suitable support structure of a vehicle for example motorized vehicles like cars, trucks, busses, trains, motorcycles etc. The movable video 10 camera(s) may be moved or transported along the path or trail of the surveillance area by way of mounting on, or worn by, a person via a suitable support like a belt etc. The one or more stationary video cameras may be mounted on, or fixed to, various kinds of stationary structures like factory or office buildings, train stations, support structures, etc. and may be arranged at traffic roads or junctions 15 or the like. In another aspect there is disclosed a computer-implemented video management method according to claim 10.. Optional features may be according to claims 11 to 16. The computer-implemented video management method may further comprise 20 steps of: determine a subset of the plurality of video cameras for which the position of the video camera is within the geographical area displayed in the geomap and / or for which the FOV of the video camera is at least partially within the geographical area displayed in the geo-map; 25 display an icon on the geo-map representative of each camera in the subset at a respective camera map position. The computer-implemented video management method may further comprise steps of: display, on the geo-map, a graphical representation of the FOV within the 30 geo-map of each of the cameras in the subset of the plurality of video cameras. 31 03 25 The computer-implemented video management method may further comprise steps of: display, on the geo-map, a user-activatable button associated with each of the cameras in the subset of the plurality of video cameras, 5 where activating a button selects the associated camera in the subset, and wherein, optionally, the user-activatable button is comprised in the icon representative of the respective camera in the subset at the camera map position of the respective camera. The computer-implemented video management method may further comprise 10 steps of: Display, one the geo-map, a graphical representation of the projected FOV area, or display, on the geo-map, a graphical representation of at least the part of the projected FOV area, which is not part of the graphical representation of the FOV of the selected camera. 15 The computer-implemented video management method may further comprise steps of: receive GIS data associated with the position of the selected camera; determine an adjusted FOV associated with the video stream of the 20 selected camera, the determination being based on the FOV data and on the GIS data, where the adjusted FOV indicates unobscured FOV and / or limited-visibility FOV, and wherein the FOV of the selected camera utilized in the displaying of the geo-map is the adjusted FOV. 25 In another aspect there is disclosed a video management system (VMS) according to claim 17. In the aspects disclosed herein, terms and features relate to the terms and features having the same name in the other aspects and therefore the descriptions and explanations of terms and features given in one aspect apply, 30 with appropriate changes, to the other aspects. Additional aspects, embodiments, 31 03 25 features and advantages will be made apparent from the following detailed description of embodiments and with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS 5 The above and other aspects will be apparent and elucidated from the embodiments described in the following with reference to the drawings in which: FIG. 1 is a schematic block diagram of an exemplary video surveillance system in accordance with the invention; FIGS. 2-9 illustrate in schematic form exemplary graphical user interfaces (GUIs) 10 of a VMS according to some embodiments; FIGS. 10-11 show flow diagrams of a computer-implemented video management method according to some embodiments; FIGS. 12A and 12B show swim lane diagrams of a computer-implemented video management method according to some embodiments; 15 DETAILED DESCRIPTION FIG. 1 is a schematic block diagram of an exemplary video surveillance system 10. The video surveillance system 10 comprises a plurality of video cameras 100a, 100b, 100c communicatively connected to a video management system 20 (VMS) 300 via respective wired or wireless communication links or connections 200. Some embodiments of the video surveillance system 10 may comprise a mix of movable video cameras and stationary video cameras for example at least one movable video camera 100c and one or more stationary video cameras 100a, 25 100b. Other embodiments may exclusively comprise one or more movable video camera(s) and no stationary video cameras while yet other embodiments exclusively comprise stationary video cameras. The stationary video cameras 100a, 100b are, when present, typically distributed across a predetermined area or space where surveillance is desired. The number and position / location of the 30 stationary video cameras 100a, 100b of the video surveillance system 10 as well as the type of video camera comprised therein may be selected based on factors 31 03 25 such as a level of surveillance desired, a size of the surveillance area or facility and / or the complexity of the layout of the surveillance area or facility. The movable video camera(s) 100c has a Field of view (FOV) and the stationary video cameras 100a, 100b have respective FOVs (not shown). The FOV is the 5 open, observable area of the camera in question as schematically illustrated by a pie-shaped outline 110c. The skilled person will appreciate that different types of video cameras may have different FOVs for example caused by different optical properties of camera lenses. In the present specification, the term “movable” as a property of a video camera 10 means the camera can be moved, i.e. is geographically dynamic, while carrying out video recording and / or live video streaming. The video recording and / or live video streaming is often carried out during active operation of the video surveillance system 10. The movable video camera is for example displaced along a certain path or trail of the surveillance area. A stationary video camera is 15 typically fixed to a stationary, like a building wall or a pole in the surveillance area. The movable video camera 100c may travel along a path or trail of the surveillance area via mounting to any suitable support structure of various types of vehicles for example motorized vehicles like cars, trucks, busses, trains, 20 motorcycles etc. The movable video camera 100c may be moved along the path or trail of the surveillance area by being mounted on, or worn by, a person via a suitable support like a belt etc. The person may for example be a police officer, bus driver, fireman etc. In the latter situation the movable video camera 100c travels through the surveillance area when the person walks or runs. 25 Alternatively, the movable video camera 100c may be transported or moved via the vehicle’s travel when the person wearing the movable video camera 100c is a driver or passenger of the vehicle. The stationary video cameras 100a, 100b may be mounted on, or fixed to, various kinds of stationary structures like factory or office buildings, train stations, support structures arranged at traffic roads or 30 junctions etc. The movable video camera(s) may be conventional portable video camera(s) known as such in the art of video surveillance. It will be appreciated that the video surveillance system 10 typically includes a plurality of movable video cameras of 31 03 25 the same type and / or different types. Different types of movable video cameras of the video surveillance system 10 may for example be tailored to specific operation schemes and placements, e.g. fixed to a truck or on-person fixations. The movable video cameras of different types may be configured to supply video 5 streams of different resolution, in different formats or outputting additional metadata associated with the video stream. Examples of functions of the movable video cameras may include one or more of the following: video streaming, in particular live streaming, and / or video recording and audio streaming and / or audio recording. The video streaming and / or video recording 10 may be carried out in visible wavelength ranges and / or in infrared wavelength ranges, such as near-infrared wavelength ranges. The moveable video camera(s) and stationary video cameras may comprise various control functions such as pan or zoom, image processing capabilities, motion detection, etc. The respective video streams supplied by the stationary video cameras 100a, 15 100b as well as those of the one or more movable video cameras 100c are associated respective metadata streams. The metadata stream may be separate stream from the associated video stream but originating from either the same video camera or another device mounted on the same person or vehicle as the video camera. The metadata stream associated with each video stream 20 preferably includes time stamps together with corresponding position data associated with the video camera in question. This property allows time synchronization of the video streams and metadata streams at the VMS. The respective geolocations of the stationary video cameras 100a, 100b and those of the one or more movable video cameras 100c may be derived from the position 25 data supplied by a camera associated GPS unit or device. The associated GPS unit or device of a movable or stationary video camera may be built into the video camera as schematically illustrated by GPS device 102c of the movable video camera 100c, or May fixed to a vehicle or person carrying the movable video camera in question. 30 The stationary video cameras 100a, 100b as well as the one or more movable video cameras 100c are often communicatively connected to the video management system (VMS) 300 as mentioned above for example connected via a local area network 200 or in any other suitable manner, e.g. via point-to-point 31 03 25 wired and / or wireless connections, or the like. For example, the stationary video cameras 100a, 100b may be connected to the VMS via an Ethernet connection. The one or more movable video cameras 100c may often be wirelessly connected to the VMS 300 for example through a wireless network like Wi-Fi, a 5 4G and / or 5G network. However, one or more movable video cameras 100c may alternatively be configured to record the video stream during active operation where the video camera moves in or through the surveillance area. In the latter scenario, the recorded video stream may be transferred to, or off-loaded at, a media repository 350 of the VMS 300 at the time of return to an associated 10 station. In the latter use case, the video stream may be offloaded at regular time intervals for example when a camera user or cameral vehicle such as a bus driver or police officer returns to the station. The skilled person will understand that some exemplary video surveillance systems may include additional sensors providing sensor signals and / or media 15 streams different from video streams, such as audio signals, radar signals, Lidar signals, etc. The VMS 300 is preferably configured to store the received video streams in the media repository 350. The VMS 300 provides an interface 360 for accessing live video streams as well as the previously discussed added metadata, and to 20 access video streams with respective metadata stored in the media repository 350. The interface 360 may implement different types of interfaces. For example, the interface may provide an application interface, e.g. in the form of a software development kit and / or one or more communication protocols, such as a suitable messaging protocol, e.g. SOAP, XML, etc. Accordingly, the interface may operate 25 as a gateway to different types of systems. The VMS may be configured to implement various types of processing of received live video streams and / or recorded and retrieved video streams for example object detection, object recognition, motion detection etc. The media repository 350 may comprise a media database or other suitable 30 storage device for storing media content. The VMS may include a user interface client (UI client) 400, for example configured to provide a graphical user interface, displayed on a suitable user screen or screens of the VMS 300. The graphical user interface enables users to view live video streams and / or stored video 31 03 25 streams and / or to control operation of one or more of the stationary video cameras 100a, 100b and / or control operation of the one or more movable video cameras 100c. The content and structure of data items displayed through the user interface may be configurable by the operator via control buttons etc. The 5 user interface comprises a map component integrated in VMS. The map component is utilized to build or provide a geo-map of at least a part of the surveillance area for presentation on the user screen. The map component may be configure to provide a geo-map overview of the respective positions of the plurality of video cameras. 10 The VMS 300 may be embodied as one or more software program(s) comprising respective computer executable instructions configured for execution on a suitable data processing system, e.g. by one or more server computers. The data processing system implementing the VMS is typically arranged remote from the one or more movable video cameras 100c as the latter often travel over a large 15 geographical area for example through a route or trail comprising various streets, roads and facilities. The route or trail may cover a city neighbourhood or even an entire city. The video streams from the movable video camera(s) may be transmitted to the VMS 300 over wireless public or other wireless communications networks. Alternatively, the movable video camera(s) 100c of 20 the video surveillance system 10 may move in relative proximity to a locally arranged on-site VMS 300 for example in a manufacturing facility, residential or office buildings, shopping centre etc... The VMS 300 may comprise one or more camera drivers 310 for providing interfaces to respective types of stationary and movable video cameras. Different 25 types of these video cameras may provide their respective video streams in different formats, e.g. using different encoding schemes and / or different network protocols. Similarly, different cameras may provide different interfaces for camera control such as zoom, or pan. Accordingly, the VMS 300 may include a plurality of different camera drivers 310 configured to cooperate with respective camera 30 types. In particular, the camera drivers 310 may implement one or more suitable network protocols and / or other communications standards for transmitting data between movable and stationary video cameras and / or other peripheral devices and data processing systems. Examples of such protocols and standards include 31 03 25 the Open Network Video Interface Forum (ONVIF) standard and the Real Time Streaming Protocol (RTSP). The camera drivers 310 may further configured to add one time stamp to each frame of the received video streams 101 so as to ensure that the video streams, 5 which are stored and subsequently supplied by the VMS 300, include a uniform time stamp. The added time stamp will also be referred to as a canonical time stamp. The canonical time stamp is indicative of the time of receipt, by the VMS 300, of the respective video streams from the respective stationary and movable video cameras. The camera drivers thus provide uniformly time-stamped input 10 video streams 311, each time-stamped input video stream 311 corresponding to a respective one of the received video streams. The VMS 300 comprises a recording server 320. The recording server may be embodied as a software program module executed by a suitable data processing system, e.g. by one or more server computers. The recording server receives the 15 inputted video streams 311 originating from the respective stationary and movable video cameras through the corresponding camera drivers 310. The recording server stores the received inputted video streams in a suitable media storage device, such as a suitable media database. It will be appreciated that the media repository 350 may be part of the VMS 300 or it may be separate from, but 20 communicatively coupled to the VMS. The media repository 350 may be implemented as any suitable mass storage device, such as one or more hard disks or the like. The storing of the received input video streams is also referred to as recording the received input video streams. The recording server may receive additional data such as the previously discussed metadata stream. 25 The VMS 300 may store the generated metadata in a suitable metadata repository 340, such as a suitable metadata database, which may be separate from or integrated into the media repository 350. To this end, the VMS 300 may include an index server 330. The index server may be embodied as a software program module executed by a suitable data processing system, e.g. by one or 30 more server computers. The index server may receive metadata and store the received metadata in the metadata repository 340. The index server may further index the stored metadata so as to allow faster subsequent search and retrieval of stored metadata. 31 03 25 FIG. 2 illustrates in schematic form an exemplary graphical user interface (GUIs) of a VMS according to some embodiments. The GUI 700 comprises a number of frames 715, 720, 730, wherein visual 5 information is presented to a user. A control and information frame 715 may provide the user with information, e.g. information relating to a video stream being displayed, or information relating to the geo-map shown in the geo-map frame 730. The control and information frame 715 may further provide the user with ways to communicate instructions to the 10 VMS and / or other control systems. For example, the user may be provided with one or more buttons, sliders, text fields, etc., and / or with one or more input fields, wherein the user may input text, such as a search string. Inputted text may then be transmitted to the VMS via a User Interface (UI) client in a suitable form. A video stream frame 720 is configured to show the video stream, for example 15 the video stream from a selected camera may be shown in the frame. The video stream is shown frame-by-frame with each frame being associated with a time, for example by the frame having a timestamp. Such a timestamp may be shown in the control and information frame 715 together with controls for the user to select a different frame and / or a different timestamp. 20 Additionally, the GUI 700 presents the user with a geo-map frame 730 showing a map of a geographical area. Icons, graphics, and other information may be displayed in the geo-map as well, e.g. as overlays on the map. An icon representative of the selected camera is displayed on the geo-map at a camera map position, where the camera map position is a geographical position in the 25 shown map. The camera map position may be the last known position of the camera, or the camera map position may be based on the reported position of the respective camera at a given time. A processing unit within the VMS determines the FOV of the selected camera at a time associated with the displayed video frame, and the geo-map is 30 continuously updated in accordance with the determined FOV such that the geomap comprises at least the extent of the FOV of the selected camera. 31 03 25 Thus, advantageously, the GUI 700 may display a coordinated video stream and geo-map display, where a user watching a video stream, possibly paused at a single frame, can see the geographical area the camera was / is in at the time of recording the video. This provides the user with an increased awareness of the 5 location seen in the video stream and may assist in the interpretation of what is seen in the video stream / frame. The camera map position corresponds to a geographical position and is different from the relative position of the icon within the geo-map display. A number of options for the centring of the geo-map, and thereby of the positioning of the 10 selected camera icon within the geo-map frame 730 as well as the bearing of the geo-map, are possible. In FIG. 2 the centre C of the geo-map is roughly at the centre of the FOV 738 of the selected camera, i.e. positioned at roughly half of the width at roughly half of the depth of the FOV of the selected camera. When the area shown in the geo-map comprises the extent of the FOV, possibly 15 with an additional area extent, the geo-map will dynamically zoom in and out on the geo-map as the FOV of the selected camera changes, e.g. as the zoom of the selected camera increases, the geo-map will zoom out, and as the zoom of the selected camera decreases, the geo-map will zoom in. A distance scale 705 shown in the geo-map frame provides scale for the shown map. A pre- 20 determined area extent may be selected by a user or may be a predefined setting. The GUI 700 may allow the user to select a degree of zoom of the geomap, perhaps to see a larger geographical area or to see more detail in the map, while the video stream plays and the geo-map updates to illustrate the movement of the camera in the area. 25 A compass 702 on the map shows the bearing. The geo-map shown in FIG. 1 is oriented such that the central line-of-sight of the camera is pointing up, which means that the bearing of the geo-map changes according to the orientation of the camera. Such a centering option may work well in a situation where the GUI is also showing the video stream in a frame at the same time as the geo-map is 30 being shown, since this will provide a user with directions in the video and geo map displays that are, to most user’s, well connected visually, i.e. left and right in the video are the same as in the geo-map, while forward and backward in the video are up and down, respectively, in the geo-map. 31 03 25 Also shown in the geo-map frame 720 of the GUI 700 is a graphical representation of the FOV 738 of the selected camera. The FOV 738 is shown as a dashed outline, but may be illustrated for the user in other suited ways such as with a different type of outline, in colour, as a shading, etc. As the FOV of the 5 selected camera changes, the graphical representation of the FOV 738 on the geo-map is updated to reflect the change providing the user with a direct display of the FOV on the geo-map. This gives a user a fast and intuitive overview of the area viewed by the selected camera to aid the user in understanding what is seen in the video stream, which reduces the cognitive load on the user. 10 FIG. 3 illustrates in schematic form an exemplary graphical user interface (GUIs) of a VMS according to some embodiments. The GUI 700 in FIG. 3 is similar to the one shown in FIG. 2. Additionally, the GUI 700 in FIG. 3 shows a representative icon 737 of another known cameras, a second camera, positioned 15 within the geographical area shown in the geo-map and a representative icon 737’ of a third camera for which its FOV is at least partially within the geographical area shown in the geo-map. The icon representing the second camera 737 positioned within the geographical area is shown at the respective camera map position like that of the selected camera, while the icon representing 20 the third camera 737’, which is positioned outside of the area shown on the geomap is positioned on the edge of the geo-map that is closest to what would be the camera map position of that camera. Also shown in the geo-map frame 720 of the GUI 700 is a graphical representation of the FOV 739 of the second camera 737, and a graphical 25 representation of the partially seen FOV 739’ of the third camera 737’. Thus, a user is able to quickly assess whether other cameras in the geographical area of the selected camera might have footage, which is of interest to the user. As the number of video cameras and available video footage is ever increasing, being able to find the right footage in the many available streams is of great 30 value. The icons representing the second 737 and third 737’ camera shown in the geomap may have activatable buttons, which allow a user to select another camera, 31 03 25 i.e. to choose another camera, which is the selected camera. This allows the user to switch the view to another camera and view the video stream from that camera. 5 FIG. 4 illustrates in schematic form an exemplary graphical user interface (GUIs) of a VMS according to some embodiments. The GUI 700 in FIG. 3 is similar to the one shown in FIG. 2 except that the geo-map further shows a projected FOV area 740, which is an estimate of the area that the camera is moving towards. From the direction of movement of the selected camera at the associated time, 10 shown by the arrow 736, which may also be shown on the geo-map for the user, the projected FOV area 740 is determined as an estimate of an area covered by the FOV of the selected camera at a later time. A processing unit within the VMS determines the projected FOV area for the selected camera and the geo-map is continuously updated in accordance with both the determined FOV and the 15 projected FOV 740 area such that the geo-map comprises at least the extent of the FOV of the selected camera and the projected FOV area. This provides the user with a view of the geographical area ahead of what is being shown in the video stream as the geo-map shows geographical area that the camera view is moving towards, and which it will move into unless a change 20 of direction is made or the camera stops moving. In FIG. 4 the camera is moving straight forward and therefore the projected FOV area is in front of the camera. On the geo-map, the projected FOV area 740 is shown as an outlined greyed area and only the part of the FOV, which is not part of the FOV at the associated time is outlined. 25 The geo-map shown in FIG. 4 is centred as in FIGS. 2 and 3, but in some embodiments, the geo-map may be centred in the combined area covered by the FOV of the selected camera and the projected FOV area. FIG. 5 illustrates in schematic form an exemplary graphical user interface (GUIs) 30 of a VMS according to some embodiments. The GUI 700 in FIG. 5 is similar to the one shown in FIG. 4. Additionally, just as it is shown in FIG. 3, the geo-map 31 03 25 shown in FIG. 5 also displays other cameras 737 positioned within the geographical area shown in the map and outlines of their FOVs 739. However, as the geographical area shown is greater due to the projected FOV area being shown, more cameras may be displayed to the user. 5 FIG. 6 illustrates in schematic form an exemplary graphical user interface (GUIs) of a VMS according to some embodiments. The geo-map frame 720 in the GUI 700 shown in FIG. 6 is elongated, and instead of having a fixed compass bearing, the bearing of the map changes 10 according to the orientation of the selected camera 735. The geo-map is oriented such that the central line-of-sight of the camera is pointing to one of the shorter sides of the geo-map frame. If the geo-map was oriented such that the line-of-sight was pointing up, as in FIG. 1, a large geographical area would be shown to either side of the FOV 738 of the selected camera likely with most of it being of 15 little beneficial use to the user. This is avoided in the configuration shown in FIG. 6, wherein the geo-map displays the geographical area comprising the FOV 738, and projected FOV area 740, and some area around it, but not overly much. A second camera 737 and its FOV 739, which overlaps with the FOV 738 of the selected camera, is also shown. 20 Thus, the centering and bearing of the geo-map is optimized to aid the user in seeing as much detail in the area of interest, i.e. of the FOV 738, and possibly projected FOV area 740, as possible, while still displaying an area that comprises the FOV. 25 FIG. 7 illustrates in schematic form an exemplary graphical user interface (GUIs) of a VMS according to some embodiments. The GUI 700 in FIG. 7 is similar to the one shown in FIG. 5. However, the geo-map displays a map such that north in the map is always pointing up, i.e. towards the top of the display on which the GUI with the geo-map is running. Also, the selected camera 736 is now in a 30 geographical area, where it is moving along a road 800 and where there are 31 03 25 buildings 810, which may block the camera’s view. To account for this, an adjusted FOV may be determined as described in connection with FIG. 8. In FIG. 7 the selected video camera 735 is moving sideways as shown by the arrow 736 and therefore the projected FOV area 740 is shown to that side of the 5 illustrated FOV 738 of the selected camera. The geo-map frame 720 shows again other cameras 737 positioned within the geographical area shown in the map and outlines of their FOVs 739. One other camera has a FOV, which overlaps with the FOV 738 of the selected camera 735, while another camera, shown as a dotted outline has a FOV that does not. 10 In this way, the user is made aware of both cameras, but the one shown with a dotted outline is shown as likely being of less interest. FIG. 8 illustrates in schematic form an exemplary graphical user interface (GUIs) of a VMS according to some embodiments. The GUI 700 in FIG. 8 is similar to 15 the one shown in FIG. 7. The selected camera 736 is in a geographical area with an open area 800 and with structures, such as buildings 810 that are blocking part of the FOV of the selected camera. To account for this, an adjusted FOV 745 may be determined by a processing unit within the VMS based on FOV data and on Geographic Information System (GIS) data. The adjusted FOV indicates 20 unobscured FOV and / or limited-visibility FOV such that areas, which are not visible or only has limited visibility anyway can be visualised as such and possibly disregarded. Thus, the GUI 700 in FIG. 8 is configured accordingly such that the geo-map comprises at least the extent of the adjusted FOV 745 of the selected camera instead of also showing blocked or low-visibility areas of the FOV. 25 Alternatively, the geo-map may show the area of the FOV, but use graphics to illustrate, which areas of the FOV are not visible or have low visibility. Thus, the part(s) of the FOV of the camera for which the line of sight is interrupted by one or more structures described in the GIS data can be accounted for by the FOV being adjusted to not include the areas beyond the 30 interrupted line of sight or to mark one or more areas as having limited visibility. This may provide the user with a more correct view of the geographical area within the view of the selected video camera. 31 03 25 Likewise, an adjusted FOV 750 for other cameras 737 within the geographical areas shown in the geo-map can be determined and a graphical representation provided for the user of the VMS. 5 FIGS. 9A and 9B illustrate in schematic form an exemplary graphical user interface (GUIs) of a VMS according to some embodiments. The GUI 700 in FIGS. 9A and 9B are similar to the one shown in FIG. 8. The selected camera 735 is moving in an area, where several structures 810 are blocking its line-of-sight, decreasing the area that is visible to the video camera. 10 In front of the camera 735 is a door 815 that is closed off and leading to an open area 800 beyond the door. An adjusted FOV 745 of the selected camera 735 has been determined as described in connection with FIG. 8 and the geo-map is shown comprising the adjusted FOV without regard to the part of the FOV that is not visible to the 15 camera due to the structural parts 810 and 815. A distance scale 705 shown in the geo-map frame provides scale for the map. In FIG. 9B, the selected camera 735 has passed through the doors 815 shown in FIG. 9A. The doors 815 are shown as open although this is not necessarily known from the data available to the VMS, but when the camera has passed 20 beyond the doors 815, there are no known structures, which block the FOV and the map zooms out to show a larger geographical area comprising the adjusted FOV 745, which is now the same as the unadjusted FOV. The distance scale 705 in FIG. 9B has therefore adjusted compared to in FIG. 9A to reflect the scale for the map shown. 25 FIG. 10 shows a flow diagram of a computer-implemented video management method according to some embodiments. In step 505, a video management system receives a plurality of metadata streams, and associated with a plurality of video streams, respectively. Each 30 video stream is supplied by, or associated with, respective ones of a plurality of video cameras. 31 03 25 In step 510, FOV data is obtained. Each of the metadata streams may comprise FOV data. Additionally, FOV data may be obtained from other sources. The FOV data comprise: position and orientation of each camera, and image sensor and lens information of each camera. 5 In step 515, a processing unit comprised in the video management system determines the FOV associated with each video stream, where the determination is based on the FOV data at a time associated with the displayed video frame. In step 520, a user interface (III) client comprised in the VMS and configured to provide a graphical user interface (GUI) provides GUI instructions for the display 10 of the video stream of a selected camera and a geo-map. The geo-map comprises an icon representing the selected camera at a camera map position and the geo-map is continuously updated such that the geo-map comprises at least the extent of the FOV of the selected camera. A graphical representation of the FOV of the selected camera may be displayed on the geo-map. 15 Optionally, in step 525, one or more additional video cameras positioned within, or having a FOV that is at least partially within, the geographical area of the geomap are determined. Representative icons are displayed on the geo-map at respective camera map positions. A graphical representation of the FOV of the one or more additional video cameras may be displayed on the geo-map. 20 Optionally, in step 530, the direction of movement of the selected camera at the associated time is determined and from this is determined a projected FOV area, where the projected FOV area is an estimate of the FOV of the selected camera at a later time. A graphical representation of the projected FOV area may be displayed on the geo-map. 25 Steps may be performed in a different order than shown in FIG. 10 as some steps do not depend on each other in the illustrated order. FIG. 11 shows a flow diagram of a computer-implemented video management method according to some embodiments. Steps that are also shown in FIG. 10 30 are as described above in connection with FIG. 10. 31 03 25 In step 512, GIS data associated with the position of the selected camera is received. In step 516, an adjusted FOV associated with the video stream of the selected camera is determined, where the determination is based on the FOV data 5 obtained in step 510 and on the GIS data obtained in step 512, and where the adjusted FOV indicates unobscured FOV and / or limited-visibility FOV. Instead of, or in addition to, displaying the FOV on the geo-map, the adjusted FOV may be displayed on the geo-map. The geo-map may be configured to comprise at least the extent of the adjusted FOV of the selected camera instead 10 of the geo-map comprising at least the extent of the FOV. Optional steps 525 described in connection with FIG. 10 may comprise determining an adjusted FOV of the one or more additional video cameras, and a graphical representation of the adjusted FOV of the one or more additional video cameras may be displayed on the geo-map. 15 FIGS. 12A and 12B show swim lane diagrams of a computer-implemented video management method according to some embodiments. The diagrams illustrate the sharing of data to and from the VMS. In FIG. 12A is illustrated how a plurality of cameras 100c and associated devices, 20 e.g. a GPS device, generate respective video streams and metadata streams, possibly bound to timestamps. The video streams and metadata streams are provided to a VMS 300 as disclosed herein. Each camera of the plurality of video cameras comprise, or is associated with, a position detecting device and an orientation detecting device configured to add position metadata and orientation 25 metadata, respectively, to each of the respective video streams. The VMS 300 comprises a User Interface (UI) client, which provides the necessary instructions for display of a Graphical User Interface (GUI) on a display 450 receiving data from the UI client. The VMS 300 may act as a subsystem within a video surveillance system. 31 03 25 In FIG. 12B is illustrated in detail how the VMS 300 receives and shares data. Each column shown corresponds to the elements shown and described in connection with FIG. 12A. A plurality of cameras 100c record video streams. Together with metadata 5 streams generated by components within each camera 100c or by one or more associated devices, the video streams are transferred to the VMS 300. The VMS receives the video and metadata streams and determines the FOV of a selected camera. The video stream of the selected camera and a geo-map coordinated with the video stream is displayed on display 450 receiving 10 instructions via a III client comprised in the VMS 300. Additionally, the VMS may determine a projected FOV area as described herein. The projected FOV area may be used to determine the geographic area shown, via the III client, in the geo-map on the display 450. Finally, the VMS may receive GIS data, and from these determine an adjusted 15 FOV as described herein. The determined adjusted FOV may be used to determine the geographic area shown, via the III client, in the geo-map on the display 450. LIST OF REFERENCES 20 10 Video management system 100a, 100b Stationary video camera(s) 100c Movable video camera(s) 102c GPS device 110c FOV of video camera 25 200 Wired or wireless communication links / connections 300 VMS 310 Camera drivers (CD) 311 Inputted video streams 320 Recording server (RS) 30 330 Index server (IS) 340 Metadata repository (metadb) 350 Media repository (mediadb) 31 03 25 360 Interface 400 UI Client 450 Display 500-590 Method steps 5 700 GUI 702 Compass 705 Distance scale 715 Frame with control buttons and / or information 720 Frame with video stream from selected camera 10 730 Frame with geo-map 735 Selected camera 736 Direction of movement of selected camera 737 Non-selected camera positioned within geo-map view 737’ Non-selected camera positioned outside of geo-map view 15 738 FOV of selected camera 739 FOV of non-selected cameras 739’ FOV of non-selected camera partially within geo-map 740 Projected FOV area of selected camera 745 Adjusted FOV of selected camera 20 750 Adjusted FOV of non-selected camera 800 Road / open area / unobstructed view 810 Building / structures / obstructed view 815 Door C Centre of geo-map 31 03 25

Claims

1. A video management system (VMS) comprising:- a recording server configured for receiving and storing a plurality of video streams and associated metadata streams, each video stream being supplied by, 5 or associated with, respective ones of a plurality of video cameras, wherein the plurality of video cameras comprise at least one movable camera;- a user interface (III) client configured to:- provide a graphical user interface (GUI),- display, via the GUI, the video stream of a selected camera frame-10 by-frame, wherein the selected camera is the movable camera,- display, via the GUI, a geo-map, and- display an icon representative of the selected camera on the geomap at a camera map position,- a processing unit configured to receive data via a data communication interface, 15 and further configured to:- receive field-of-view (FOV) data associated with the plurality of video streams, the FOV data comprising: position and orientation of each camera, and image sensor and lens information of each camera,20 - determine the FOV of the selected camera at a time associatedwith the displayed video frame,- determine a direction of movement of the selected camera at the associated time, and- determine a projected FOV area, which is an estimate of the FOV25 of the selected camera at a later time, where the projected FOVarea is based on the direction of movement of the selected camera,wherein the UI client is further configured to:display, on the geo-map, a geographical area that additionally comprises at least the extent of the projected FOV area of the selected camera, and31 03 25continuously update the geo-map when at least one of the camera position and FOV data of the selected camera changes, wherein the updated geo-map comprises at least the extent of the FOV of the selected camera and the projected FOV of the selected camera.

52. A video management system (VMS) according to claim 1, wherein the III client is further configured to display, on the geo-map, a graphical representation of the FOV of the selected camera.10 3. A video management system (VMS) according to any of the previous claims,wherein the processing unit is further configured to:- determine the subset of the plurality of video cameras for which the position of the video camera is within the geographical area displayed in the geo-map and / or for which the FOV of the video 15 camera is at least partially within the geographical area displayed inthe geo-map;and wherein the III client is further configured to:- display an icon on the geo-map representative of each camera in the subset at a respective camera map position.

204. A video management system (VMS) according to claim 3, wherein the III client is further configured to display, on the geo-map, a graphical representation of the FOV within the geo-map of each of the cameras in the subset of the plurality of video cameras.

255. A video management system (VMS) according to any of claims 3-4, wherein the III client is further configured to display, on the geo-map, a user-activatable button associated with each of the cameras in the subset of the plurality of movable video cameras,30 wherein activating a button selects the associated camera in the subset, and31 03 25wherein, optionally, the user-activatable button is comprised in the icon representative of the respective camera in the subset at the camera map position of the respective camera.5 6. A video management system (VMS) according to any of the previous claims,wherein the metadata for the orientation of each camera comprises the compass direction and relative tilt of the respective camera.

7. A video management system (VMS) according to any of the previous claims, 10 wherein the processing unit is further configured to display, on the geo-map:- a graphical representation of the projected FOV area, or- a graphical representation of at least the part of the projected FOV area, which is not part of the graphical representation of the FOV of the selected camera.

158. A video management system (VMS) according to any of the previous claims, wherein the processing unit is further configured to:- receive Geographic Information System (GIS) data associated with the position of the selected camera;20 - determine an adjusted FOV associated with the video stream ofthe selected camera, the determination being based on the FOV data and on the GIS data, where the adjusted FOV indicates unobscured FOV and / or limited-visibility FOV,and wherein the FOV of the selected camera utilized in the displaying of the geo-25 map is the adjusted FOV.

9. A video surveillance system comprising:a plurality of movable video cameras arranged in a surveillance area and configured to generate respective video streams, wherein each camera30 of the plurality of video cameras comprise, or is associated with, a positiondetecting device and an orientation detecting device configured to add position metadata and orientation metadata, respectively, to each of the respective video streams; anda video management system (VMS) according to any of claims 1-8.

510. A computer-implemented video management method for a video management system (VMS), comprising steps:31 03 25a) receive, at a video management system, a plurality of video streams and associated metadata streams, each video stream being supplied by, or10 associated with, respective ones of a plurality of video cameras, whereinthe plurality of video cameras comprise at least one movable camera, b) receive field-of-view (FOV) data associated with the plurality of video streams, the FOV data comprising: position and orientation of each camera, and image sensor and lens information of each camera,15 c) determine the FOV of a selected camera at a time associated with the displayed video frame, wherein the selected camera is the movablecamera,d) determine a direction of movement of the selected camera at theassociated time,202530e) determine a projected FOV area, which is an estimate of the FOV of the selected camera at a later time, where the protected FOV area is based on the direction of movement of the selected camera,f) provide a graphical user interface (GUI) and display, to a user via the GUI, the video stream of the selected camera frame-by-frame,g) display, via the GUI, a geo-map,h) display, on the geo-map, an icon representative of the selected camera at a camera map position,i) display on the geo-map of a geographical area that additionally comprises at least the extent of the projected FOV area of the selected camera,j) update the geo-map continuously when at least one of the cameraposition and FOV data of the selected camera changes, wherein theupdated geo-map comprises at least the extent of the FOV of the selectedcamera and the projected FOV of the selected camera.31 03 2511. A computer-implemented video management method according to claim 10, further comprising steps:k) display, on the geo-map, a graphical representation of the FOV of the 5 selected camera.

12. A computer-implemented video management method according to any of claims 10 or 11, further comprising steps:I) determine a subset of the plurality of video cameras for which the position 10 of the video camera is within the geographical area displayed in the geomap and / or for which the FOV of the video camera is at least partially within the geographical area displayed in the geo-map;m) display an icon on the geo-map representative of each camera in the subset at a respective camera map position.1513. A computer-implemented video management method according to claim 12, further comprising steps:n) display, on the geo-map, a graphical representation of the FOV within the geo-map of each of the cameras in the subset of the plurality of video20 cameras.

14. A computer-implemented video management method according to any of claims 12-13, further comprising steps:o) display, on the geo-map, a user-activatable button associated with each 25 of the cameras in the subset of the plurality of movable video cameras,where activating a button selects the associated camera in the subset, and wherein, optionally, the user-activatable button is comprised in the icon representative of the respective camera in the subset at the camera map position of the respective camera.3031 03 2515. A computer-implemented video management method according to any of claims 10-14, further comprising steps:p) Display, one the geo-map, a graphical representation of the projected5 FOV area, ordisplay, on the geo-map, a graphical representation of at least the part of the projected FOV area, which is not part of the graphical representation of the FOV of the selected camera.10 16. A computer-implemented video management method according to any ofclaims 10-15, further comprising steps:q) receive Geographic Information System (GIS) data associated with the position of the selected camera;r) determine an adjusted FOV associated with the video stream of the15 selected camera, the determination being based on the FOV data and onthe GIS data, where the adjusted FOV indicates unobscured FOV and / or limited-visibility FOV, and wherein the FOV of the selected camera utilized in the displaying of the geo-map is the adjusted FOV.2017. A video management system (VMS) comprising a processing unit comprising microprocessor executable program instructions configured to carry out one or more of the method steps of claims 10-16.25

Images