README file last updated: January 16, 2019
This export contains data extracted from the Maryland Judiciary's charge database. The intent of this database is to provide a uniform listing of charges utilized by Maryland's Judicial system as well as other state and local agencies and private firms. More information about this data can be found on the charging language database page at the Maryland Judiciary's web page The latest export can be downloaded at http://www.mdcourts.gov/charge.zip .
The charge data is provided in 2 XML files. "cjiscode.xml" contains the criminal (CJIS) charges, and "trafcode.xml" contains the traffic violation charges. There are three unique identifers used for these charges. "cjisid" is a unique identifier for the criminal (CJIS) charges. "trafficid" is the unique identifier for the traffic violation charges. If a user needs to combine both criminal and traffic data into a single table, then the "chargeid" identifier can be used, which is a unique identifier for both criminal and traffic charges.
The same charge may appear in the database multiple times with different "date_begin" and "date_end" values. This allows a law change to be made but still have available the old charge information prior to the law change. This allows, for example, for someone to be charged, say on October 10th, for a charge that was committed on or about August 1st. If the penalty changed on October 1st, the old penalty information will still be available at the time the charge was committed.
readme.html - This file
cjiscode.xml - XML data for Maryland CJIS charges
trafcode.xml - XML data for Maryland traffic charges
(Note: all date fields are stored as "YYYY-MM-DD")
| Field Name |
Data Type |
Description |
|---|---|---|
| cjisid |
integer |
Unique numeric identifier for criminal (CJIS) data |
| chargeid |
integer |
Unique numeric identifier for charge (both CJIS and traffic) data. Use this identifier if combining CJIS and traffic data into a single table. |
| cjiscode |
integer (5 digits) |
5 digit number specify the base or numeric portion
of the CJIS code |
| class |
char(1) |
1 character field specifying the type of CJIS code.
Valid values are:
|
| cjisclass |
char(6) |
Combined cjiscode and class in the format of "1x2345",
where "12345" is the 5 digit cjiscode and "x" is the class. |
| describe35 |
char(35) |
Short description of charge |
| describe70 |
char(70) |
Short description of charge |
| describe(100) |
char(100) |
Short description of charge |
| date_begin |
date |
Effective date of charge. When the effective date
was unknown when entered, "1970-01-01" is used |
| date_end |
date |
Last date the charge was in effect. For example, if a charge was
repealed on October 1, 2012, then the last date the charge was in effect would
be September 30, 2012. |
| article |
char(4) |
Article |
| section |
char(6) |
Section |
| subsec |
char(10) |
Subsection |
| paragraph |
char(15) |
Paragraph |
| felony |
char(1) |
"Y" if a felony, "N" otherwise |
| jailable |
char(1) |
"Y" if a jailable offense, "N" otherwise |
| phrqd |
char(1) |
"Y" if a preliminary hearing is required, "N" otherwise |
| maxfine |
numeric(10,2) |
Maximum fine amount |
| timetype |
char(1) |
Type portion of maximum jail time, used in conjunction
with timeamt. Valid values are "D": days, "M": months, "Y":years, "L": life
and "X": death |
| timeamt |
integer |
Amount portion of maximum jail time, used in conjunction
with timetype |
| ruleno |
char(10) |
This field is no longer used. Previously, it was used to
indicate certain CJIS codes (typically serious felonies) that were subject to
release restriction / held without bond situations under certain circumstances.
If used, values are either "616 1/2" or "638B". |
| description |
BLOB |
Text of the charging language |
| notes |
BLOB |
Useful information related to the charge |
| mod_date |
date |
Date this charge was last updated. Use this field
to determine updated charges |
| new_date |
date |
Date this charge was first entered into the system.
Use this field to determine new charges |
(Note: all date fields are stored as "YYYY-MM-DD")
| Field Name |
Data Type |
Description |
|---|---|---|
| trafficid |
integer |
Unique numeric identifier for traffic charge data |
| chargeid |
integer |
Unique numeric identifier for charge (both CJIS and
traffic) data. Use this identifier if combining CJIS and traffic data into
a single table |
| describe35 |
char(35) |
Short description of charge |
| describe70 |
char(70) |
Short description of charge |
| describe100 |
char(100) |
Short description of charge |
| date_begin |
date |
Effective date of charge. When the effective date
was unknown when entered, "1970-01-01" is used |
| date_end |
date |
Last date the charge was in effect. If a charge was
repealed on October 1, 2012, then the last date the charge was in effect would
be September 30, 2012. |
| article |
char(2) |
Article |
| section |
char(2) |
Section |
| subsec |
char(6) |
Subsection |
| paragraph |
char(2) |
Paragraph |
| code |
char(1) |
|
| fine |
numeric(10,2) |
Maximum fine amount |
| finetype |
char(1) |
|
| mod_date |
date |
Date this charge was last updated. Use this field
to determine updated charges |
| new_date |
date |
Date this charge was first entered into the system.
Use this field to determine new charges |