Pelican riding a bicycle

The user wants an SVG of a pelican riding a bicycle. This is a fun creative request. Let me think carefully about how to construct this with SVG shapes. I need to draw: 1. A pelican — recognizable features: large body, long neck, distinctive big beak with a pouch underneath, white/cream body often with grayish wings, webbed feet. 2. A bicycle — two wheels with spokes, frame (diamond shape), handlebars, pedals, seat. 3. The pelican positioned on the bike — sitting on the seat, wings on handlebars or holding handlebars, feet on pedals. Let me plan the coordinate system. I'll use a viewBox of something like 0 0 800 600. Bicycle: - Rear wheel center: (220, 420), radius 90 - Front wheel center: (560, 420), radius 90 - Bottom bracket (pedal crank center): around (350, 420) - Seat tube goes from bottom bracket up to seat at ~(310, 260) - Head tube at front: from ~(540, 300) down to ~(520, 380) - Top tube from seat post area to head tube - Down tube from head tube to bottom bracket - Chain stay from bottom bracket to rear wheel center - Seat stay from seat area to rear wheel center - Fork from head tube down to front wheel center - Handlebars at top of head tube ~(545, 280), curving back - Seat at (300, 250) - Pedal cranks: rotating around bottom bracket, with pedals at ends Pelican: - Sitting on the seat around (300, 250) - Body: large ellipse, maybe centered (300, 200), tilted - Tail feathers behind - Neck: S-curve from body up to head at maybe (400, 100) - Head: small circle at (410, 100) - Beak: long, pointing forward (to the right), with pouch. Beak from head extending to maybe (520, 130), pouch hanging below - Eye: small circle on head - Wing: draped forward toward handlebars - Legs: from body down to pedals Let me write the SVG carefully. I'll use groups and reasonably simple paths. I should make it look decent: nice colors, strokes, maybe a ground line, sky background. Let me be more careful with geometry so it actually looks like a pelican on a bike. Canvas: viewBox="0 0 800 600". Ground line at y=510. Wheels touch ground: wheel radius 90, centers at y=420. Good. Rear wheel center: (210, 420). Front wheel center: (570, 420). Wheel radius 85. Then ground at 505. Frame: - Bottom bracket: (360, 425) - Seat tube: from (360, 425) to seat post top (310, 270). Slope back. - Seat at (305, 265): draw a seat shape (ellipse-ish path). - Top tube: from (315, 285) to head tube top (535, 295). - Head tube: from (535, 290) to (550, 355). - Down tube: from (545, 345) to (360, 425). - Chain stays: (360, 425) to (210, 420). - Seat stays: (312, 280) to (210, 420). - Fork: (548, 350) to (570, 420). - Handlebar stem: from (535, 290) up to (528, 265), then handlebar curving forward-down: path like M 528 265 Q 560 255 570 275 or drop bars. Let me do a simple curved handlebar: from stem at (528, 262), a path curving toward the viewer's right and down: M 528 262 C 555 250, 585 255, 590 285. Pedals: crank center (360, 425). Crank arms: one pedal forward-down at (400, 460), other back-up at (320, 390). Pedals as small rects. Chain: from chainring circle at bottom bracket (radius ~28) to rear hub small circle (radius ~12): two lines forming chain run: top line from (360, 397) to (210, 408), bottom from (360, 453) to (210, 432). Actually simpler: draw ellipse-ish chain lines. I'll draw a chainring circle at (360, 425) r=26, rear cog r=12 at (210, 420), and two lines tangent-ish: (360, 399) to (210, 408) and (360, 451) to (210, 432). Pelican (facing right, riding to the right): - Body: ellipse centered at (310, 195), rx=85, ry=55, rotated maybe -15 degrees (tail up at left, chest at right). Actually tail at left-back (lower?) Let's have body tilted so tail points up-left. Rotate -20°. - Tail feathers: a few triangles at the left end of body, around (230, 165). - Legs: pelican sits on seat at (305, 265). Hip around (330, 240). Leg to front pedal (400, 460)? That's far — leg length ~ sqrt(70² + 220²) ≈ 231. Hmm, that's long but pelicans have longish legs; still, maybe adjust so body is a bit lower or pedals closer. Alternatively raise the seat? Seat is at 265, pedals at ~460 — that's a 195 vertical drop. Bicycles: seat to pedal distance roughly 60-70 cm with wheel radius ~34cm; scaled: wheel radius 85 px = 34cm, so 1cm ≈ 2.5px. Seat-to-pedal ~ 70cm → 175px. So vertical drop of ~170-190 is fine actually. Legs bent though — when pedal is down, leg is nearly extended. Distance from hip (330,240) to pedal (400,460): dx=70, dy=220, dist=231. Slightly long. I could move hip to (330, 250) and pedal at (395, 455): dist = sqrt(65²+205²)=215. Fine — cartoon style, no need for perfect realism. I'll draw legs as thick stroked paths with bent knee: thigh from hip to knee, shin from knee to pedal, orange color, thick stroke (10-12), with webbed foot at pedal. Front-down leg: hip (335, 245) → knee (390, 350) → foot (400, 455). Back-up leg: hip (330, 250) → knee (310, 350) → foot (330, 395)? The other pedal at (320, 390) — foot slightly above pedal at (322, 385). Hmm, let me place: back pedal at (322, 392), foot on top of pedal: foot at (322, 386). Knee between: (295, 330). OK. Actually wait — cranks are opposite: if one pedal is at angle θ, the other is θ+180°. Bottom bracket (360,425), crank length 45. Pedal 1 at (360+45cos, 425+45sin). Let's pick pedal 1 at angle ~45° below horizontal to the right-front: (392, 457). Pedal 2 opposite: (328, 393). Good, matches above. - Neck: pelicans have a strong S-curve neck. From body's front-top (360, 160) curving up: path M 360 165 C 360 110, 390 120, 405 95... Let me draw neck as a thick tapering shape. Simpler: use a path filled shape for neck+head as one silhouette. Might be easier to do: neck as a stroked path with stroke-width ~26, white fill none, stroke white... but then the outline won't be visible. Better: draw the whole pelican (body, neck, head) as filled white shapes with dark outlines. Approach: Use separate filled shapes with stroke: 1. Body ellipse (white fill, dark stroke). 2. Neck: a filled path forming a tapering S shape. Could approximate with two curves forming a closed shape: Path: M 350 180 C 345 120 380 115 400 85 C 408 72 428 70 436 82 L 452 70 ... hmm, head separate is easier. Simpler plan: - Neck as a thick stroked path (stroke width 30, round linecap), colored white, then overlay a slightly thinner... no. Just make the stroke white with a dark outline is not possible with a single stroke. Alternative: draw the same path twice: first with stroke-width 34 in dark color, then with stroke-width 26 in white on top. That creates an outlined tube! That's a neat trick. Do the same for legs (dark 14, orange 9). Neck path: from chest (355, 175) up with S-curve to head position (415, 95): M 355 175 C 350 130 370 105 385 100 — hmm I want a forward-leaning S: pelicans often have neck pulled back then head forward. Let's do: start (350, 175), curve down-right then up: M 350 175 C 355 140 340 120 360 105 C 375 93 390 95 402 100. Head circle at (410, 100) r=22. Actually let me make the neck go up and slightly forward with a graceful curve: path "M 345 180 C 350 130 375 120 395 105" with head at (405, 98). Hmm, head should be forward of neck top so beak points right. - Head: circle at (410, 95), r=20, white fill, dark stroke. - Eye: circle at (417, 88), r=3.5, dark. Maybe white highlight dot. - Beak: the iconic part! Long beak from head pointing right and slightly down, with pouch beneath. Upper beak: path from (425, 88) to tip (545, 105): a slender triangle-ish shape, orange/yellow. Pouch: from under head (415, 105) sagging down to (500, 150) connecting to beak tip: filled with warm orange/yellow, path: M 418 102 C 430 150 480 160 540 108 ... then close along bottom of upper beak. Let me define: - Upper mandible: M 422 84 L 548 102 L 546 110 L 420 98 Z — a thin tapering shape, fill #f4a300 (orange), stroke dark thin. Actually make it slightly curved: M 422 82 Q 490 88 548 100 Q 548 106 544 108 Q 485 98 420 96 Z. - Pouch: M 420 96 Q 470 165 544 108 Q 485 98 420 96 Z — fill slightly darker orange #e8940f? Actually pouch often more yellow/pinkish. Use #f6b93f for pouch and #ef9f1f for upper beak? Or upper beak gray-orange, pouch vivid. Pelicans (white pelican) have orange-pink bill with pouch. I'll do upper beak #f2a33c, pouch #f7c15b or vice versa. Let me: upper beak #e8921e, pouch #f6b23e. Pouch line visible. Hmm wait, beak tip at x=548 — front wheel is at x=570 with top of front wheel at y=335. Beak at y~105 is way above; fine. Beak tip 548 vs handlebar at ~528-590 — beak is above handlebars. Good, no overlap visually? Handlebar at y~255-285. Beak at y~100. Fine. - Wing: from shoulder (330, 170) reaching forward-down to handlebars at (545, 262)? That's a long reach: dx=215. The wing tip should be near the handlebar grips at ~(585, 280)? Distance from shoulder (330,175) to (585,280) ≈ 277. Long but cartoonish OK — like wings stretched forward to hold bars. Alternatively, wing rests on the top tube or the pelican's wing just folded at side, and one wing extends to handlebar. For humor and readability, extend wing to handlebar. Wing shape: a tapering filled path from shoulder to "hand" at handlebar: M 320 160 C 400 150 490 200 575 265 (upper edge to grip) then small foot/hand: L 580 278 C 570 285 560 282 555 275 (rounded tip) then lower edge back: C 480 225 400 200 325 200 Z. Something like that. Fill slightly gray (#d9dee6) with dark stroke, plus a few feather lines. Hmm, the wing crossing over the top tube area... top tube runs from (315,285) to (535,295). Wing lower edge passes ~ y 200-265, above the top tube mostly. Fine. Also add second hint of far wing? Keep simple. - Tail: at rear-left of body: a few pointed feathers: path M 235 175 L 175 150 L 215 185 L 165 190 L 220 205 — like zigzag; fill gray. Body ellipse covers right part. Let me place body center (310, 195) rx 85 ry 52, rotate -18°. Its left end around (232, 230)?? With rotation -18° (counterclockwise), left end goes down? Rotation -18° in SVG rotates... positive angle is clockwise in SVG (y down). So rotate(-18) rotates counterclockwise on screen, meaning left end of ellipse goes down and right end up? Let's compute: ellipse major axis along x. Rotate by -18° (CCW visually since y is down, positive rotation is CW; -18 is CCW visually... actually in SVG, positive angles rotate clockwise because y-axis points down). rotate(-18): the point (rx, 0) maps to (rx cos(-18), rx sin(-18)) = (80.9, -26.3) — y negative = up on screen. So right end up, left end down. Hmm, I want tail up at left maybe? A riding pelican leaning forward: body tilted with tail up, chest down-forward. So right end (chest) lower, left end (tail) higher. That's rotate(+18): (rx,0) → (80.9, +26.3): right end down. Yes use rotate(18) around center? Wait transform rotate(18 310 195). Then chest end at (310+81, 195+26) = (391, 221), tail end at (229, 169). Good: tail up-left, chest down-right. Then neck starts at chest top ~(370, 190)?? The chest around (380, 210). Neck start (355, 175) may be off-body. Let me recompute: body center (310,195), rx85 → along tilted axis, points: front-bottom (chest): (391, 221); rear-top (tail): (229, 169). Top of body midline ~ (310, 143)? The upper edge... The neck should emerge from the front-upper part of the body, around (350, 165)? Body upper edge at x=350: roughly y ≈ 195 - 52*sqrt(1-(40/85)²) adjusted for tilt ≈ 195 - 52*0.88 - tilt effect... approx y≈150-160. Let's start neck at (350, 168) — inside body, fine since body drawn first, neck drawn after? If neck drawn after body, its bottom end will overlap body with its own outline visible — could look off. Draw neck BEFORE body? Then body outline covers neck base — cleaner. But neck stroke overlap: draw neck tube (dark then white), then body on top. The neck enters body seamlessly. But then the body's outline crosses the neck... The body ellipse outline would show through where neck attaches? No — body is drawn after neck, so body fill covers the neck's lower part, and body's stroke is on top of neck fill. The neck would appear to emerge from behind the body edge. That looks fine and natural. Similarly head: draw head circle after neck so it covers neck top. And beak after head. Order: tail feathers, neck (dark stroke pass, white fill pass), body, wing, legs?, head, eye, beak, pouch. Wait — legs: hips at (330, 240) — inside body? Body front-bottom chest at (391,221); at x=330, lower edge y ≈ 195 + 52*0.93 + tilt ≈ 245. So hip (330, 240) is inside body near lower edge. Legs drawn after body: thigh emerges from body's lower edge. The leg's dark outline at hip will be visible over body — acceptable, looks like leg in front. Good. But wait: wing also drawn after body — wing shoulder at (320, 160) on top of body. Fine. Layering order: 1. Background sky rect (light blue), sun maybe, clouds. 2. Ground (green strip or line) at y=505. 3. Bicycle (rear parts): rear wheel, frame, chain, crank, front wheel, fork, handlebars, seat. 4. Pelican: tail, neck, body, legs+feet (feet on pedals, drawn over pedals), wing, head, eye, beak+pouch. 5. Maybe motion lines. Wait legs over pedals: pedal at (392,457): draw crank+pedal, then foot on top. Back pedal (328,393): foot on top. Hmm, one issue: the down-pedal and chain area near (392,457) — fine. Seat: at (305, 265): seat path: M 275 262 Q 305 252 335 260 L 332 268 Q 305 276 278 270 Z, dark gray fill. Seat post from (310, 268) to (315, 300)? Seat tube from (360,425) to (313, 268). Let me make seat tube line from (358, 422) to (312, 270). Seat sits atop at ~(308, 262). Pelican bottom should be at seat: body lowest point around (330, 247)... body chest bottom (391, 221)?? That doesn't reach seat at 265. Hmm. Body center (310,195) with ry=52 rotated: the lowest point of rotated ellipse: max y = sqrt((rx sinθ)² + (ry cosθ)²) = sqrt((85*0.309)² + (52*0.951)²) = sqrt(26.3² + 49.5²) = sqrt(692+2450)= sqrt(3142)=56. So lowest y ≈ 195+56 = 251. Close to seat top 262 — the pelican's bottom at 251 vs seat at 262: slightly hovering; nudge body center to (310, 202) → lowest 258. Then recompute other things. Or just move seat up to 258. Eh — let me set body center (312, 200), and seat at y 262; gap ~6px, hidden by feathers/legs. Actually there'd be visible gap maybe. Let me just lower body to center (312, 205): lowest point 261. Touches seat. But then head/neck positions shift +5: neck start (352, 173), head (410, 100) stays (neck path adjust). Fine — I'll recompute a clean set of numbers now. FINAL GEOMETRY: Sky: rect 0 0 800 600 fill #cfeef9 (light sky). Sun: circle (700, 80) r 45 fill #ffd93d, maybe. Clouds: ellipse groups at (150,90), (600,60)... optional. Keep light: two clouds using ellipse clusters, fill white opacity 0.9. Ground: rect 0 505 800 95 fill #7ec850 (grass green); darker line at top: rect 0 505 800 8 fill #5aa63c? Or just a line. Also small road? Keep grass. Wheels: r=85, centers (210, 420) and (570, 420). Tires: circle stroke #333 width 12, fill none... plus inner rim circle stroke #999 width 4 at r=70? Spokes: lines from hub to rim every 30°: 12 spokes. Hub circle r=10 fill #444. To keep code compact, I could define a wheel as a with . Use with id="wheel": circle r85 stroke #2d2d2d sw 11 fill none; circle r 68 stroke #b9c0c7 sw 5 fill none; 8 spokes via lines rotated; hub circle r 9 fill #555. Spokes: rotated 0,45,90,135 → that gives 8 spokes (each line is diameter). Then 26 — no overlap. Good. Now, wing drawn after near leg? Wing shoulder area (322,158)-(330,205) overlaps body top; near leg hip at (340,235) below wing. Order: wing then head etc. Fine. Motion lines: a few short lines behind bike: M 60 300 h 50, M 40 350 h 40, M 70 400 h 45, stroke #ffffff or #9fd8ef... on sky background white lines might be subtle; use #ffffff with opacity 0.8? Or little dust puffs near rear wheel: circles at (95, 470) r 12, (70, 455) r 8, fill #fff opacity .7. Cute. Also small speed lines behind at (60,430) etc. Wheel rotation: not animated (static SVG). Could add simple animation with for wheels spinning! That's a nice touch — rotate spokes group around center. And maybe the crank+legs... too complex to sync legs. I could animate wheels only. But if it's meant as static image, animation optional. I'll add gentle wheel spin animation — it degrades gracefully. Hmm, but legs won't pedal — could look odd with wheels spinning while legs static. Still charming. I'll include slow rotation. Actually, let me include it — animateTransform rotate 0→360 over 2s on spoke group within each wheel def. With , the animation in defs applies to both uses. Nice. But careful: with animation inside referenced element works fine. Also could animate pelican bobbing? Skip — keep code manageable. Let me also double-check the neck-head-beak: head (412,94) r21. Upper beak starts (424,84) — that's inside head (dx=12, dy=-10 → dist 15.6 <21) good; beak drawn after head, so beak base overlaps head edge — draw beak after head so attachment clean, but the beak's left edge (the Q 419 90 424 84 Z closing edge) will show over head as a line... The closing edge from (424,97) to (424,84) — a short vertical-ish line inside head — visible stroke. Hmm, that would draw a line across the head. To avoid: make beak path start/end at head boundary and not close visibly... Any closed path with stroke shows all edges. Option: draw beak fill without stroke for the base edge... simplest: accept small line but place it mostly outside head boundary: start beak at x=430 (head edge at y: circle: (x-412)²+(y-94)²=441; at x=430: dy² = 441-324=117 → dy=10.8 → y from 83.2 to 104.8). So beak base from (430, 84) to (430, 104) lies just at/outside right edge of head. The closing line at x=430 vertical from 84 to 104 — near head edge, slight overlap. Alternatively draw beak BEFORE head: head covers base — but then beak appears behind head, tip still visible — actually that's fine too! Beak under head: the head circle would cover the beak base making beak appear from behind head edge. Real pelican beak emerges from head. Draw pouch+beak first, then head on top? Then head outline over beak base — looks like beak behind head — not great; beak should be in front (attached to face). Better: use a single path for head+beak+pouch silhouette? Complex. Alternative accepted approach: draw head, then beak shapes; the base closing edge of beak is short and positioned at head's edge where it reads as the beak's base line — actually having a visible line at beak base is natural (beak meets face). I'll position base edge right at head boundary: base points (429, 83) and (429, 104). It'll look intentional. Similarly pouch base at (429, 103): pouch path M 429 102 Q 495 100 556 110 C 540 152 478 172 445 150 Q 424 133 429 102 Z. The left closing edge from (445,150) region to (429,102): the Q 424 133 429 102 creates edge along chin — visible over head slightly. Eh. Let me instead start pouch at (432, 105) with Q 428 128 445 150... I'll just write something reasonable; small imperfections OK for a cartoon. Actually, cleaner: make the pouch+upper beak share the mouth line, and draw BOTH before the head is... no wait, head before beak. Let me just try final paths: Upper beak: M 428 82 Q 500 85 566 100 L 564 108 Q 498 96 428 96 Z Closing line from (428,96) to (428,82): vertical at x=428, near head edge (head right edge at 433... x=428 is inside head by 5). Slight line over head. I'll set x=430: head edge at y83: x range... at y=83: dy=-11 → dx² = 441-121=320 → dx=17.9 → x up to 429.9. So (430,83) is just outside. Use base x=430, from y=83 to y=105: at y=105: dy=11 → dx=17.9 → edge x=429.9 — so (430,105) just outside too. Upper beak: M 430 83 Q 502 86 566 101 L 564 109 Q 500 97 430 105 Z Hmm the beak height at base: from 83 to 105 = 22 tall — too thick at base? Pelican upper mandible is deep at base actually. But then mouth line... The pouch attaches along bottom edge (430,105)→(564,109). OK. Hmm, actually wait: beak spanning from y83 to y105 at base with head r21 — beak depth 22 ≈ head diameter-ish... a bit much. Reduce: base from (430, 86) to (430, 103) → 17 deep. Fine. Upper beak: M 430 86 Q 504 88 568 102 L 566 110 Q 502 98 430 103 Z Pouch: M 430 103 Q 502 98 566 110 C 546 154 486 174 448 152 Q 424 134 430 103 Z Check pouch: bottom-most around y ~160 at x~490. Sag 50-55px below mouth line. Reasonable. The left edge Q 424 134 430 103: goes from (448,152) up to (430,103) with control (424,134) — slight outward bulge left — over head lower right. Minor overlap, fine. Tip: both beak shapes meet near (566-568, 100-110) forming tip point. Good. Add tiny hook: after L 566 110, maybe Q 570 108 568 102... skip. Nostril: line M 448 92 L 476 93.5 stroke #c96f10 2? Use darker #b96a12 width 2 round. Eye at (419,87): relative to beak base x430 — eye left of beak base, on head. Good. Head detail: maybe a little feather tuft on top back of head: small path M 398 76 Q 392 64 402 60 ... optional; skip or add tiny crest: M 396 79 Q 388 66 400 62 Q 398 72 404 74 Z fill #fff stroke... skip to reduce fiddly bits. Actually a tiny tuft is cute: path M 392 80 Q 383 66 396 62 Q 395 71 402 72 Z fill #fff stroke #2d2d2d 2. Position: head top-left (head center 412,94, r21 → top y=73 at x=412; top-left point ~(397,79)). Tuft from (392,80)... slightly overlapping head. Draw before head? Then base hidden. Yes: draw tuft before head. Hmm wait, tuft before head but after neck. OK. Legs check: near leg knee (392,350) — that's forward (right) of body, over the down tube? Down tube from (543,350) to (360,425): at x=392, y = 425 + (350-425)*(392-360)/(543-360) = 425 -75*(32/183) = 425-13.1 = 411.9. Knee at (392,350) is above down tube — leg crosses down tube? Leg from hip (340,240) to knee (392,350): passes x~370-392, y~300-350 region; down tube at those x: at x=370: y=419; at x=392: y=412. Leg is well above (300-350 vs 412) — no crossing until shin goes down: shin from (392,350) to (394,445): crosses down tube at y~412-415, x~393. Yes shin crosses down tube — since near leg drawn after frame, shin passes IN FRONT of down tube. Near-side leg in front of down tube: correct! Great. Far leg: hip (330,240) → knee (300,330) → ankle (326,385): does it cross seat tube (360,425)-(313,272)? Seat tube param: at y=330: x = 360 + (313-360)*(425-330)/(425-272) = 360 - 47*(95/153) = 360-29.2 = 330.8. Far leg knee at (300,330): left of seat tube (330.8). At y=300: tube x = 360-47*(125/153)=360-38.4=321.6; leg at y~300: between hip (330,240) and knee (300,330): x ≈ 330 - 30*(60/90) = 310. Leg x=310 < tube 321.6 → leg is left of tube... wait "left" meaning smaller x — leg crosses? At y=330: leg at 300, tube at 330.8 — leg left. At y=272 (tube top): tube x=313; leg at y=272: x = 330-30*(32/90)=319.3 — leg RIGHT of tube (319 > 313). So somewhere they cross: between y=272 and y=330, leg x goes 319→300, tube x goes 313→331: crossing around y~295 where both ≈ 316. So frame seat tube crosses over far leg (frame drawn after far leg) — far leg behind seat tube: correct for far side! Chain stays: (360,425)-(210,420): far leg ankle region (326,385) above; foot at (310-342, 376-396) — chain stay at x 326: y ≈ 425 - 5*(34/150)? Line from (360,425) to (210,420): slope = -5/-150 → at x=326: y = 425 + (326-360)*((420-425)/(210-360)) = 425 + (-34)*(−5/−150)= 425 - 34*0.0333 = 423.9. Foot at y≤396 — no overlap. Good. Far foot on far pedal (312-344 x, 387-397 y): foot path M 310 384 Q 326 376 342 382 L 338 391 Q 322 396 310 391 Z — foot bottom ~391-396 overlapping pedal rect (387-397). Good. Near foot on near pedal (376-408, 451-461): foot path M 384 449 Q 400 441 418 449 L 414 458 Q 398 464 386 458 Z — bottom ~458-464, pedal 451-461: overlap. Good. Wheel spokes with animation: (rim) Note: inside as child — should be a child of the animated element. Yes placing animateTransform inside g animates that g's transform. Works. Then and translate(570 420). Also include xlink? Modern browsers accept href. I'll use href (and add xmlns:xlink not needed). Wait — tire: outer circle stroke width 11 at r85 → outer edge 90.5, ground at 505: wheel bottom at 420+90.5=510.5 — slightly into ground (505). Adjust: ground top at y=512. Wheel outer edge 510.5 — floats 1.5px. Set ground rect y=510. Bottom 510.5 → touches ~. Good: ground rect 0 510 800 90, plus darker grass line at top: rect 0 510 800 6 fill #66b03c? Let me do main grass #7ec850 from y510, and a darker strip #5ea63e height 8 at 510. Fine. Shadow under bike: ellipse cx 390 cy 512 rx 260 ry 12 fill rgba(0,0,0,0.12). Draw before wheels, after ground. Sun: circle (702, 84) r 42 fill #ffd76a; maybe rays skip. Add subtle: stroke none. Clouds: Cloud 1: ellipses at (150, 95): ellipse 150 100 rx 45 ry 18; ellipse 125 88 rx 28 ry 15; ellipse 172 86 rx 30 ry 16; fill #ffffff opacity .9. Cloud 2 at (585, 70) smaller similar. Actually sun at 700; cloud2 at (520, 65)? avoid overlapping beak (y~100 at x 430-570; cloud at y 50-80 x 480-560 might touch beak visually—beak tip x566,y~102; cloud bottom ~80 — ok gap). Fine. Sky color: #cdeffd... use #c9ecf7. Motion/speed lines: stroke #ffffff opacity 0.85 width 5 linecap round: lines: (55,330)-(115,330)? Actually place behind rear: M 40 300 L 100 300; M 25 355 L 95 355; M 55 410 L 110 410. Hmm those are in sky area behind pelican tail (tail at x 170-250, y 108-196). Speed lines at x 25-110, y 300-410 — behind wheel area, white on sky+grass? y 410 is sky (ground 510). White on light blue: visible. OK. Maybe #b3e5f2? White fine with opacity. Also little dust puffs at rear wheel: circles (120, 495) r 10, (95, 502) r 7, (140, 503) r 6 fill #e8f7ee opacity .8? On grass. Use #dff3d0. Eh, optional — include two small ones. Handlebar detail: also brake lever? skip. Text label? No. Let me also reconsider neck curve: M 348 180 C 348 130 372 110 404 98 — hmm from (348,180) straight-ish up then curving right to (404,98). With stroke width 27 white over 34 dark. The neck at head: head at (412,94) — neck top end (404,98) inside head. Looks like neck rises from chest and head sits at top — but pelicans riding look better with neck extended forward. Alternative: give slight S: M 350 182 C 342 138 366 122 380 112 C 396 100 406 96 416 94. Two cubics; head at (412,94)... endpoint (416,94). Let me simplify to one path with nice curve: M 350 184 C 340 130 372 108 414 96 That's a single cubic: start (350,184), cp1 (340,130) pulls up-left slightly, cp2 (372,108), end (414,96). Curve: goes up from 184 with slight left bow then sweeps right to head. Nice swan-like S-ish. Good. Check neck tube width 27 vs head r21(diameter 42): neck thinner than head — good. Wing shoulder: wing drawn after body: shoulder region covered? Wing upper edge starts (322,158): body top edge near x 322: compute body boundary: point (322,158): dx=10, dy=-47 → x' = 10*.951 + (-47)(.309) = 9.5-14.5 = -5.0; y' = -10*.309 + (-47)(.951) = -3.1-44.7=-47.8. (5/86)² + (47.8/54)² = 0.003+0.784 = 0.787 <1 → inside body. Good, wing base inside body. Wing lower edge endpoint (330,205): inside body obviously. Wing tip at (584,268)/(590,282) near grip (588,282): overlaps grip — wing tip covers grip; looks like holding. Good. But also the handlebar curve C 552 252 580 254 588 282 — mid part at y~255-260; wing upper edge at x~550: from curve M 322 158 C 420 148 510 205 584 268: at t~0.8, point ≈? Bezier at t=0.8: B = (1-t)³P0+3(1-t)²tP1+3(1-t)t²P2+t³P3. t=0.8: coeff: 0.008, 0.096, 0.384, 0.512. x = 0.008*322+0.096*420+0.384*510+0.512*584 = 2.6+40.3+195.8+299.0 = 537.7. y = 0.008*158+0.096*148+0.384*205+0.512*268 = 1.26+14.2+78.7+137.2=231.4. So wing upper edge at (538,231). Handlebar at x538: bar path M 528 266 C 552 252 580 254 588 282: at x~538 y~260. Wing edge above bar. Wing lower edge at x 538: from C 500 240 415 205 330 205 reversed... lower edge from tip (574,287) back: C 500 240 415 205 330 205 — at t=0.15 from tip: point ≈ (1-t)³(574,287)+... t=0.15: coeff .614,.325,.057,.003: x=.614*574+.325*500+.057*415+.003*330=352.4+162.5+23.7+1.1=539.7; y=.614*287+.325*240+.057*205+.003*205=176.2+78+11.7+0.7=266.6. So lower edge at (540,267) — bar at (540, ~260): wing lower edge just below bar → wing covers bar around there. So bar partially hidden behind wing between x~520-570 — reads as wing over handlebar. One more: the stem line M 534 294 L 528 266 — wing covers part. Fine. Top tube from (316,288) to (534,296): body bottom at ~261 (center 205 + 56)... wait body center (312,205), lowest 261. Top tube at x~316: y=288. Gap between body bottom (261) and top tube (288): 27px — see-through gap between belly and top tube. That's actually fine/normal for a bike (rider's bottom on seat above top tube... hmm, actually riders sit above top tube; the seat at 262 and top tube at 288-296 below seat — but body bottom at 261 hovers over seat at 262 — good). But wait, does the body visually connect to seat? Body lowest 261, seat top ~256 (seat path y 250-268ish). Overlap. Hmm wait, seat path: M 276 264 Q 305 250 336 259 L 331 269 Q 304 276 280 270 Z → top edge ~250-264. Body bottom 261 → overlaps seat top. Good, butt on seat. But hold on — seat tube top at (313,272), seat drawn at (276-336, 250-276) — seat post implicit. Add small post line M 313 272 L 310 260? The seat covers. Fine, add line from (314, 274) to (310, 258) stroke #555 width 6? It'd be behind seat (drawn before seat). Add it. Also rear rack or basket? Skip. Maybe a little flag on back for fun? Could add small pennant on rear: pole from (210, 420) up... behind pelican tail. Skip — composition is busy enough. Head/eye/cheek: maybe blush circle? skip. Let me now also verify body vs neck tube: neck dark stroke width 34 centered on path from (350,184): dark tube spans 17px each side — base region y 167-201 at x~350 — body drawn after covers lower part. Body top edge at x=350: point (350, y): solve (350-312)dx... x'= (38)(.951) + (y-205)(.309)... find boundary: (x'/86)²+(y'/54)²=1 where x' = 38*.951 + dy*.309 = 36.1+0.309dy; y' = -38*.309 + dy*.951 = -11.7+0.951dy. At dy=-40: x'=36.1-12.36=23.77; y'=-11.7-38.04=-49.7: (23.77/86)²+(49.7/54)² = 0.076+0.847=0.92<1 inside. dy=-45: x'=36.1-13.9=22.2; y'=-11.7-42.8=-54.5: 0.067+1.019=1.086>1 outside. So boundary ~dy=-42 → y=163. Neck at x~350 top part: the neck curve at x 350 near start (350,184) — the tube from y~150 up. Body boundary at 163: neck emerges above y~163 at that x. The neck's dark edge crossing body's top edge... body drawn AFTER neck → body fill covers neck below boundary, body stroke on top. So neck appears from behind body's top edge. But wait — wing drawn after body with shoulder at (322,158)-(330,205) — wing also covers neck base region? Wing base spans y 158-205 at x 322-330 — neck at x~350 — no overlap. OK. Now beak tip (568, ~102-110) — front wheel top at (570, 335)? Wheel top = 420-90.5 = 329.5. No conflict. Does the beak overlap the handlebar visually? Beak y~86-110; bar y~250-285. No. Now check pouch bottom y~174 max vs top tube (316,288)-(534,296): at x~490: y≈293. Pouch bottom 174 — well above. OK. Everything seems consistent. Let me also add a small "head feather sweep" line inside head? skip. Eye placement (419,87): head center (412,94) — eye up-right: good for forward-looking. Let me write out coordinates for spokes lines rotated: instead of computing rotated lines, I use 4 lines with rotation transforms: 4 lines = 8 spokes. Could add 45°-offsets another 4 for 16 spokes; 8 is fine, or use another 4 lines for 45° increments at other angles: lines at 22.5° etc need cos/sin: 70cos22.5=64.7, 70sin22.5=26.8. Add two more lines: (-64.7,-26.8)-(64.7,26.8) and (-26.8,64.7)... that gives 12 spokes. Eh, 8 is fine visually with animation. Hmm — animation might be undesirable if user wants static; but it's a delight. Keep dur="1.2s". Also maybe animate a slight bob of pelican? skip. Also: pedals/cranks static while wheels spin — minor. Could animate crank rotation too... then feet wouldn't follow. Keep static cranks. Actually, spinning wheels with static legs might look slightly odd but it's fine — wheels spin, coasting! It's coasting downhill. Let me assemble final SVG code. Here's a pelican cruising on a bicycle — complete with the iconic pouch, wings on the handlebars, and spinning wheels: ```xml ``` A few details worth noting: - **Spinning wheels** — the spokes are animated, so it looks like the pelican is coasting along. Remove the `` element if you want a fully static image. - **Proper bike mechanics** — the far leg and pedal sit behind the frame, the near leg crosses in front of the down tube, and both webbed feet rest on their pedals. - **Pelican essentials** — the S-curved neck, long hooked beak, and a big saggy pouch that bobs just above the handlebars. Paste it into any `.svg` file or HTML page to see it ride. 🚲

svg of a pelican riding a bicycle