They're now showing the 'lat and lon', but I suspect that it is really pixels on a map or offsets from an arbitrary starting position. They certainly don't match any local lat/lon values.
The tbxy coordinates are relative to the center tag.
See geoConvertTBXY() for the Sacramento, SLO and Fresno comm/dispatch centers.
See http://www.chp.ca.gov/depts_divs_offs/dispatchcenters.html for all CHP communication centers.
e.g.
GGCC -> Golden Gate Communications Center
1551 Benicia Road
Vallejo 94591-7568
This is approximately: 38.085628, -122.202795
Grabbing some GGCC incident data from the xml...
tbxy:
6043421, 2128915
6048874, 2118027
5991498, 2085191
6054990, 2125580
Approximate coordinates (longitude, latitude) based on sigalert/google traffic data for the same incidents:
-122.293797, 37.829311
-122.274957, 37.798662
-122.471166, 37.705146
-122.254679, 37.819514
tbx scale: 0.0000034843
longitude scale: 1.17306
tby scale: 0.00000275533
latitude scale: 0.83924
FYI these scaling factors may be a bit off because I wasn't particularly careful with my rounding.
PHP:
<Center ID = "GGCC">
<Dispatch ID = "GGCC">
<Log ID = "2163D0607">
<LogTime>"6/7/2011 9:37:06 PM"</LogTime>
<LogType>"1125A - Traffic Hazard - Loose Animal"</LogType>
<Location>"SB I680 JNO SR24"</Location>
<Area>"Contra Costa"</Area>
<ThomasBrothers>"612 5B"</ThomasBrothers>
<TBXY>"6108173:2153096"</TBXY>
<LogDetails>
<details>
<DetailTime>" 9:37PM"</DetailTime>
<IncidentDetail>"LIVE DEER RUNNING AROUND IN CD"</IncidentDetail>
</details>
</LogDetails>
</Log>
...
