Bike-share docks: station still plus overlay bikes-available, not a city film

The rack photo is the product. Recurring overlays for status. Cinematic downtown Veo is tourism-board work.

A bike-share dock is a specific station: map pin, kiosk, rack count, livery on the bikes that are actually in the bay. The useful post is that station, today, with a number you will stand behind — bikes available, docks free, a service alert. A golden-hour fly-through of downtown is a tourism board's feeling. It does not tell a rider whether the rack on their corner has a bike.

The rack photo is the product

Photograph the station you operate. Same angle every time: kiosk, rack, street signage that is really there. Crop so a rider who lives on that block recognises the corner. That still is the product. A generated skyline with plausible docks is a different city.

Do not prompt "cinematic bike share at magic hour, riders laughing, downtown bokeh." The model will invent bikes, riders, and a cousin kiosk. Generated riders are people you did not film. Keep humans out of the generate. A real person already in the street photo is not a reason to spawn extras.

Bike shops are a nearby retail audience: workshop, fitting, Saturday ride. This page is a dock. Do not paste a generated peloton onto the kiosk.

Lock the station jpeg before you buy motion or type. If the map-decal is already wrong, every recurring post is that wrong decal with a new number on top.

Recurring overlays for bikes-available

Status is the variable. The rack is not. Run a recurring video series turns a saved workflow into a cadence: you set the schedule once, each run can write a fresh plot while reusing the same characters, style, and assets, and you are charged when a run actually generates — not when you create the schedule.

For bike-share, reuse the station still as the locked asset. The "fresh" piece is the status line, not a new downtown. If each run is allowed to invent a city, you have scheduled a tourism film. Pin the photograph. Change the overlay.

Add a text overlay burns one authored line for the whole clip: top, center, or bottom. Type the number you will stand behind — "12 bikes at 4th and Pine" — in words you wrote, from a count you actually have. This is not a transcription. The kiosk is not speaking. Muted autoplay still needs the count. Overlay is how the count survives mute.

A series that regenerates the picture every morning is how the rack drifts. A series that regenerates the line on a locked plate is the job. If a video model is in the workflow, feed it the same still and prompt only "hold, no new bikes, no riders." Extra docks means you are posting a cousin station. Bike-share status is not a plot. It is a count on a plate.

Qwen for a status card if you need generated type

Sometimes the post is not a clip. It is a still card: station photo plus a readable availability line, 2K, posted as an image. Qwen Image 3 Text to Image is the catalog still for that lettering job: third-generation Qwen image model, strong prompt adherence, complex text rendering in Chinese and English, intelligent prompt rewriting on by default, 2K, 4 credits.

Use Qwen when the words have to hold on a card. Paste the exact status string. Do not ask Qwen to invent the rack. Generated kiosks miss the map pin. Type on an empty layout you composite onto the photo is the honest use.

Four credits is the listed still, not a city film. Iterate until the count matches the live station. A second pass that "makes it more urban" is how the letters drift. If the card is only photo plus overlay in an editor, skip the image model.

Downtown Veo is travel-agency work

Veo 3.1 is native audio, official 4K tier, 4 / 6 / 8 second clips, 40 credits. That is the cinematic row: dialogue, physics, a plate you will park on a large display. A downtown fly-through with invented cyclists is that row pointed at the wrong object. Riders cannot check availability on a feeling. You paid the talking-and-4K meter for a tourism still.

Travel agencies sell the feeling of being there, not the itinerary. Three posts a week, 9:16, Reels and Pinterest. Cinematic destination stories belong on that page. A bike-share operator who posts Veo downtown as "our network" has used the travel playbook on a dock that needs a count.

Do not generate riders so the rack "looks used." Do not schedule a recurring Veo city film and caption it with a bike count. Do not let Qwen redraw the kiosk because the type needed a second pass. Station still. Status overlay. Recurring on that pair. The city already exists in the photograph.

FAQ

Can each recurring run invent a new downtown as long as I overlay the count?

No. The rack has to be the station you operate. Run a recurring video series should reuse that still as the locked asset. A new skyline is a cousin dock. The overlay cannot fix a wrong corner.

Why Qwen Image 3 if the product is a photograph?

Qwen Image 3 Text to Image is for a 2K status card when the type has to hold: 4 credits, complex text in Chinese and English. The rack stays the photo. Qwen letters the line. It does not get to redraw the kiosk.

Is Veo 3.1 ever right for bike-share?

When you actually need a short cinematic clip with native audio and a 4K tier — which is not daily availability. Status is overlay on the station still. Downtown feeling is travel agencies, not this dock.

Do I need to generate riders so the dock looks popular?

No. Generated riders are not your users. If a real person is already in the station photo, keep them only if you would publish that street photo anyway. Do not spawn a crowd. The product is the rack and the count.