Member Avatar for jamello

I have a challenge. I need to provide a solution that would enable me capture images of occupants of several motor vehicles scattered around a geographical area. These images could be still images or video transmitted over the web to my server in my headquaters.

I can program in JSP, ASP.NET, PHP in the order of preference. I did not want to recieve an infraction by not multiposting under these languages.

so idea(s) are welcome. What is the simplest, cost/time effective approach.

Admin: Is there a part where these type of scenario can be taken care of. that is, Ideas or solutions discussed irrespective of language used. Please permit my idiocy! lol.

  • 1 Contributor
  • 1 Reply
  • 97 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by jamello

Dani AI

Generated

A short addendum to 's follow-up: the on-vehicle capture + backend approach works, but a few practical choices make deployments reliable, legal, and cost-effective. The language you use on the server is secondary to the capture/transport/retention architecture — focus on capture triggers, connectivity resilience, security, and privacy first.

Decide stills vs video up front. Stills (periodic photos or event-triggered snaps) greatly reduce bandwidth and storage; short pre/post-event clips give context without constant streaming. Use local ring buffering so the device keeps recent footage when the network drops, then uploads when connectivity returns. Start with moderate resolution (720p) and low frame rates (10–15 fps) to preserve facial detail while controlling bitrate; many setups tune to ~500 kbps–1.5 Mbps depending on compression. For planning, remember 1 Mbps is roughly 0.45 GB per hour.

  • Local ring storage + upload-on-connectivity is essential.
  • Embed timestamp and GPS (keep device clocks synced via NTP).
  • Require per-device auth tokens and TLS for all uploads.
  • Define retention and access policies and run a legal/privacy review before recording.

On the server side, accept secure HTTP uploads for stills and use appropriate ingest for streams (low-latency browser use favors WebRTC; chunked delivery can use HLS). Keep incoming files in immutable storage, index metadata (device, time, GPS) in a database, and provide a short-term hot store for quick review with long-term cold archive. Implement device heartbeats and a simple dashboard to catch offline units.

Capturing occupants is privacy-sensitive. Verify local rules and consent requirements (see GDPR overview for EU considerations). Never record audio where law or consent forbids it. Pilot with a few vehicles to validate mounting, lighting, data costs (SIM caps), timezones, and authentication before scaling.

For protocol details see WebRTC (webrtc.org) and HLS (RFC 8216) (rfc8216).

Member Avatar for jamello

Thanks Guys!
i found that what I needed was to install Network IP-Cameras in those vehicles, administer them with a backend software like webcamXP. Thanks again!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.