> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/understand-your-business/ai-features/vision-analytics/line-cross-search.md). # Line Cross Search Solink's **Line Cross Search** feature allows you to quickly track foot traffic in your store or vehicles crossing a line over a given period of time and combine that information with POS data to gather revenue statistics. **Note**: Line Cross Search is only available with a subscription to [**Vision Analytics**](https://solink.com/ai/vision-analytics/) (included in the Solink AI package). Line Cross Search allows you to gain insights into the following: * The **total number of people** who walked across either side of the drawn line, or the **total number of vehicles** that crossed a line within your camera footage during a given period of time. * The **daily average** of visitors. {% embed url="" %} **Note**: This feature requires your [Solink recording device (QNAP)](/docs/install-connect-and-integrate/identify-solink-recording-device-model.md) to have an [**AI chip**](/docs/release-notes/share-only/how-to-install-solink-s-ai-accelerator-chip.md) installed. Please reach out to our Support team if you are unsure if your recording device has an AI chip installed. *** ### How Line Cross Search Works Line Cross Search uses people/vehicle tracking AI to detect movement as individuals walk within your camera view. By drawing a virtual line, you can quickly review the **total number of people/vehicles** and **daily average of people/vehicles** on either side (if you select more than a day for the Start Time and End Time): ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-be5de3b1a273994967965c9fd39519a684da2890%2Fc55fc658c9c366b1.png?alt=media) *** ### Enable Line Cross Search You can access Line Cross Search in the Solink video player. However, you must first enable **Vision Analytics** on one of your cameras in order to use the feature for that camera. See [**Enable Vision Analytics**](/docs/understand-your-business/ai-features/vision-analytics/enable-vision-analytics.md) for information on how to enable Line Cross Search. **Note**: Additional permission is required to manage Vision Analytics on your cameras. Please reach out to our Support team if you require permission. **Note**: If you have exceeded the number of available cameras with Vision Analytics, you can disable Vision Analytics on one camera and enable it on another whenever required. *** ### Create a Line Once **Vision Analytics** are enabled on a camera, you can navigate to the video player to access the Line Cross Search feature. From the **Video** page, select the camera that has Vision Analytics enabled to open the video player. Next, select **AI** > **Line Cross** above the Video Player: To draw your line, select the starting point in the camera view. Then select the end point. If you want to clear the line to redraw/change the line location, select the **Clear** button in the top-right corner of the video player: To extend or pivot the line, select either of the end points and drag to the desired location: **Tip**: Refer to [Camera Placement Guide for People Tracking](/docs/understand-your-business/ai-features/vision-analytics/camera-placement-guide-for-vision-analytics.md) for more information on how the camera position and angle can impact Line Cross accuracy. #### Configure Line (Switch Directions) To switch the direction of the line, either: * Select the **Swap Direction** button: * Select the "triangle" icon on either side of the line: **Tip**: To track location occupancy, ensure the blue arrow points in to the site and the orange arrow points out, towards the entrance door. *** ### Path Analysis **Path Analysis** allows you to see where people/vehicles travelled within the camera view during the selected time range from the Line Cross Search window. Paths are represented by coloured lines and show where each person or vehicle crossed the line and in which direction. Path Analysis helps you: * See how traffic moves through an area. * Spot common routes, bottlenecks, and areas people or vehicles use most often. * Jump to video for a specific person or vehicle and follow their path over time. #### Enable Path Analysis In [Line Cross Search](/docs/understand-your-business/ai-features/vision-analytics/line-cross-search.md), select the **Path Analysis** toggle to turn the feature on. #### Show Paths by Direction When you have drawn a line, use Show paths by direction to include or exclude each direction: * Each toggle matches one side of your line (same colours as the direction circles in the count section). * Turn a direction off to hide paths for crossings on that side only. #### Heatmap for Path Analysis Turn on Heatmap to emphasize where paths overlap: * Cooler colours (blue) mean fewer overlapping paths. * Warmer colours (green/teal, to yellow and red) mean more paths use the same area. The following image shows an entrance area to an oil change bay where the Path Analysis heatmap is turned on. The entrance on the left side of the image shows more red/orange colours than the right. This suggests the bay entrance with the red/orange lines saw more frequent use than the bay next to it. This can help quickly spot check if there is an issue with business operations (one bay was closed during this period of time, for instance): Overlap sensitivity controls how strictly paths must overlap to count as “busy”: * **Low**: Only very close overlaps appear as high traffic. * **High**: Nearby parallel routes count more towards overlap/colour change. **Note**: When no line is drawn, Heatmap stays on so you can still see traffic concentration across the full view. #### Navigate to Paths in Video Player While Path Analysis is on: 1. Hover on a path to highlight one person or vehicle. 2. Select a path to open path details in the panel and isolate the path in the video player. 3. To navigate to the instance where the person/vehicle crosses the line, either: * Select **Next** or **Previous Line Cross** using the video player controls. * Select the line. Additionally you can do the following to navigate with Path Analysis: * In path details, select **Path start**, each **Line crossing time**, or **Path end** to jump the player to that timestamp. * Use **Back to Search** in the panel header to return to counts and Path Analysis settings. Path details list each line crossing for the selected path, with direction labels and colours that match your direction toggles. **Note**: While you are drawing or editing a line, you cannot select paths so you can finish placing the line. #### Tips for Path Analysis * Start with a shorter time range (for example, one busy hour), then widen the range as needed. * Place your line where people or vehicles actually cross, same as for accurate line cross counts. See [How do I draw a "good" line for Line Cross](#how-do-i-draw-a-good-line-for-line-cross)? * Use Heatmap to find choke points; use individual paths (Heatmap turned off) to verify a specific trip or unusual movement. *** ### Navigate to each Line Cross in Video Player Once you have created a line, you can use the **Next Line Cross** and **Previous Line Cross** buttons to navigate to each instance a person crossing the line. The orange and blue circles on the timeline correlate to someone crossing the line to either the blue or orange side of the line: ### FAQs and Troubleshooting This section outlines frequently asked questions and/or troubleshooting information for Line Cross. #### I created a line, why isn't data showing yet? If no data is being generated once you have created your line: * You may need to wait for a period of time to begin generating data. Data can only be captured from the time AI was set up on your camera, going forward. * If AI has been enabled on your camera for some time and you are still not seeing any data at all, try clearing the line and re-drawing it. * The line may have been drawn in an area where no people/vehicles would cross it. Ensure the line is placed in an area where people/vehicles will be crossing it throughout the day, such as a site entrance or an entranceway to another area of the site (for people), or a drive-thru lane (for vehicles). If data still is not showing, please contact your Customer Success representative to investigate further. #### How do I draw a "good" line for Line Cross? The best line for line cross depends on your intended use case - but one of the most common use cases is to track when people enter and leave the site. To draw a good entrance/exit line: 1. Ensure the camera is pointing at an angle to your site's entrance. An example is shown in the image below. 2. Draw the line just in front of the door. 3. Ensure the blue arrow points into the location and the orange arrow points towards the door to capture total occupancy correctly. Additionally, ensure camera placement is optimal - follow the [Camera Placement Guide here](/docs/understand-your-business/ai-features/vision-analytics/camera-placement-guide-for-vision-analytics.md). #### What kind of data can I track with a Line Cross widget? You can use the data generated from [Line Cross Events](/docs/understand-your-business/ai-features/vision-analytics/line-cross-events.md) to create widgets displaying Line Cross data. You can create a widget tracking the following Line Cross metrics: * **Entrance and Exit Count**: Total number of people/vehicles who crossed the line in both the "in" and "out" directions. * **Location Occupancy**: Tracks store occupancy at a given point in time. * **Conversion Rate:** Total people/vehicles that crossed the line divided by total number of transactions. Please reach out to your Customer Success representative if you require help creating these widgets. #### I'm having an issue with Path Analysis, what should I do? See below if you are experiencing a specific issue with Path Analysis for troubleshooting advice: **I turned on Path Analysis but I do not see paths** * Confirm [Vision Analytics](/docs/understand-your-business/ai-features/vision-analytics/enable-vision-analytics.md) is enabled on this camera and the time range is after AI was enabled. * Wait for path loading to finish. * Confirm people or vehicles were visible and moving in that period. * If you use direction toggles, ensure at least one direction is still enabled. **Paths disappeared when I selected something** * You may have opened path details for one path—the overlay focuses on that selection. Use **Back to Search** to see all paths again. **Counts look right but paths seem incomplete** * Very long searches may hit the path display cap; try a shorter range. * Camera angle and occlusion can shorten visible tracks; see the [Camera Placement Guide for People Tracking](/docs/understand-your-business/ai-features/vision-analytics/camera-placement-guide-for-vision-analytics.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.solink.com/docs/understand-your-business/ai-features/vision-analytics/line-cross-search.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.