Skip to contentSkip to contact
Dennis KhorGeoTag Pro
Recruiter mode

Signal LabBuild or decode the public packet in your browser

Signal Lab

GeoTag Pro writes this 95-byte packet to a Sony Alpha camera over Bluetooth to geotag a photo. Build it from a golden vector or your own location, or paste one to decode, byte by byte, in your browser.

Public packet only. The camera also needs a validation handshake and timing beyond the public spec, and those are not published here. The format builds on the community's ILCE7M3ExternalGps protocol notes.

Latitude, bytes 11–14. Point at or tab to any byte to inspect it

Bits of the selected field, most significant first

Bytes 11–14, EB D1 DD 60

Latitude, Sydney Opera House

Offset
11 (0x0b)
Field
Latitude, bytes 11–14
Encoding
int32, big-endian, two's complement
Raw
EB D1 DD 60
int32, big-endian
−338,567,840
÷ 10,000,000
−33.8567840
Latitude
−33.856784°

Degrees times 10,000,000, rounded half away from zero. Negative is south.

Latitude: −33.856784°

Build or decode a packet

Start from a golden vector or your own inputs and watch the bytes above re-encode, or paste any packet in hex to see which rules it keeps.

Mode
Start from a vector
Inputs
Decimal degrees, negative is south.

Decimal degrees, negative is west.

Read as UTC. Your own time zone is not applied.

Minutes east of UTC. That is UTC+10:00.

Usually 0 or 60.

Matches the iOS golden vector byte for byte

Methodology

Byte layout

The layout comes from the community protocol document published by whc2001. There is no checksum, CRC or sequence number, so the decoder never pretends to verify one. GeoTag Pro is not affiliated with Sony.

The 95-byte location packet. Multi-byte values are big-endian; the 91-byte form stops after byte 90.
BytesFieldEncodingMeaning
0–1Lengthuint16, big-endianHow many bytes follow these two: 93 with the time zone, 89 without it.
2–4HeaderConstant bytesAlways 08 02 fc. The public document calls it a fixed header and does not say more.
5Time zone flaguint803 when the time zone and DST offsets are appended at the end, 00 when they are left out.
6–10Fixed dataConstant bytesAlways 00 00 10 10 10. Undocumented, but every packet carries it.
11–14Latitudeint32, big-endian, two's complementDegrees times 10,000,000, rounded half away from zero. Negative is south.
15–18Longitudeint32, big-endian, two's complementDegrees times 10,000,000, rounded half away from zero. Negative is west.
19–20Yearuint16, big-endianThe UTC year.
21Monthuint8The UTC month, 1 to 12.
22Dayuint8The UTC day of the month, 1 to 31.
23Houruint8The UTC hour, 0 to 23.
24Minuteuint8The UTC minute, 0 to 59.
25Seconduint8The UTC second, 0 to 59. Fractions of a second are dropped.
26–90PaddingZero bytes65 zero bytes. There is no checksum, CRC or sequence number anywhere in the packet.
91–92Time zone offsetint16, big-endian, two's complementMinutes east of UTC. For example +600 is 02 58 and -480 is fe 20.
93–94DST offsetint16, big-endian, two's complementThe daylight saving offset in minutes, usually 0 or 60.

Rounding coordinates

Each coordinate is multiplied by 10,000,000 and rounded half away from zero, which is what Swift's rounded() does. JavaScript's Math.round rounds halves up instead, so a direct port quietly disagrees with the iOS app on negative halves.

Latitude -0.00000005 gives -0.5. Rounded away from zero that is -1, written as ff ff ff ff. Math.round gives 0, written as 00 00 00 00. The lab uses Math.sign(x) * Math.round(Math.abs(x)).

What is verified

Four presets are the golden vectors from the GeoTag Pro repository: an independent Swift generator writes them, and the iOS test suite asserts the app's encoder against every byte. The fifth is the worked example in the public protocol document. They are regression anchors that separate encoders agree on, not captures from a camera.

This encoder is tested against all five, plus negative-half rounding, two's complement offsets, every corrupted constant and a round trip over 400 seeded inputs. The badge above only appears when the live encoding equals the expected hex.

Each vector re-encoded when this page was built and compared with its expected hex.
VectorSourceInputsResult
Null Island, UTC+8iOS app golden vectors0, 0
2025-01-02 03:04:05 UTC, tz 480
Byte for byte match
Sydney Opera HouseiOS app golden vectors-33.856784, 151.215297
2026-06-28 12:30:00 UTC, tz 600
Byte for byte match
San Francisco, UTC-8iOS app golden vectors37.774929, -122.419416
2025-12-25 23:59:59 UTC, tz -480
Byte for byte match
TokyoiOS app golden vectors35.689487, 139.691711
2025-07-15 00:00:01 UTC, tz 540
Byte for byte match
Public protocol examplepublic protocol document20.077731, 110.3332775
2020-11-05 04:02:42 UTC, tz 480
Byte for byte match

What is not published

This lab covers only the location packet written to characteristic DD11. The camera validation handshake beyond the public spec is kept private.

Read the GeoTag Pro case study

Ask about fit

Paste a job description. You get a verdict, the evidence that matches it with citations, and what the sources do not show.

Open to senior AI and software engineering roles: on site or hybrid in Sydney, or remote for Australian and US teams.

Email meBook 15 minCV