mirror of
https://github.com/bilawalsidhu/gods-eye-view.git
synced 2026-11-04 02:14:01 +00:00
docs(cctv): say the Houston pack needs TxDOT's written permission to enable
TranStar's Content Usage terms prohibit copying, distribution and external framing of its images without TxDOT's prior written permission. The opt-in text only said the pack was off unless CCTV_HOUSTON_ENABLED=1, without saying what an operator needs before setting it. Say "enable only if you hold TxDOT's written permission" in .env.example, the README, DATA_SOURCES.md, CURRENT-STATE and the changelog, matching the NYC and Florida packs, and fix the column of the .env.example comment. The houston-cctv credit now reads "(Houston, when enabled)" and links the Content Usage terms, like the Florida credit. Where the docs said frames are "never stored or redistributed", they now say what happens: frames are relayed on demand, buffered only per request, sent with no-store and not archived.
This commit is contained in:
1 parent
8cd0cc82f5
commit
f120989a2b
7 files changed
+37
-17
No files matched your search
+1
-1
@@ -256,7 +256,7 @@ AISSTREAM_API_KEY=
|
||||
# CCTV_TAIWAN_ENABLED=1 # set 0 to skip Taiwan Freeway Bureau (MOTC) road cameras
|
||||
# CCTV_TAIWAN_MAX_SOURCES=600 # cap Taiwan freeway cameras (1-2000); no API key required
|
||||
# CCTV_TAIWAN_URL= # override the Freeway Bureau MOTC 2.0 CCTV.xml URL
|
||||
# CCTV_HOUSTON_ENABLED= # set to 1 to opt in; off by default (TranStar terms)
|
||||
# CCTV_HOUSTON_ENABLED= # off by default; set 1 to load Houston TranStar cameras only if you hold TxDOT's written permission (TranStar's Content Usage terms prohibit copying, distributing or framing its images without it; see DATA_SOURCES.md)
|
||||
# CCTV_HOUSTON_MAX_SOURCES=250 # cap cameras loaded from the Houston TranStar catalog (nearest metro cores first)
|
||||
# CCTV_HOUSTON_CAMERAS_URL= # override the Houston TranStar catalog URL
|
||||
# CCTV_A22_ENABLED=1 # set 0 to disable the Autostrada del Brennero (A22, Italy) webcams
|
||||
|
||||
Reference in new issue
Block a user