Legislative intelligence / 90R
SESSION 2027View project ↗

Transportation Code § 644.101: CERTIFICATION OF CERTAIN PEACE OFFICERS

1 bill in the 90th Legislature would change this section

Part of Transportation Code Chapter 644, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 644.101. CERTIFICATION OF CERTAIN PEACE OFFICERS. (a) The department shall establish procedures, including training, for the certification of municipal police officers, sheriffs, and deputy sheriffs to enforce this chapter.

(b) A police officer of any of the following municipalities is eligible to apply for certification under this section:

(1) a municipality with a population of 50,000 or more;

(2) a municipality with a population of 25,000 or more any part of which is located in a county with a population of 500,000 or more;

(3) a municipality with a population of less than 25,000:

(A) any part of which is located in a county with a population of 3.3 million; and

(B) that contains or is adjacent to an international port;

(4) a municipality with a population of at least 34,000 that is located in a county that borders two or more states;

(5) a municipality any part of which is located in a county bordering the United Mexican States;

(6) a municipality with a population of less than 5,000 that is located:

(A) adjacent to a bay connected to the Gulf of Mexico; and

(B) in a county adjacent to a county with a population greater than 3.3 million;

(7) a municipality that is located:

(A) within 25 miles of an international port; and

(B) in a county that does not contain a highway that is part of the national system of interstate and defense highways and is adjacent to a county with a population greater than 3.3 million;

(8) a municipality with a population of less than 8,500 that:

(A) is the county seat; and

(B) contains a highway that is part of the national system of interstate and defense highways;

(9) a municipality located in a county with a population between 60,000 and 69,000 adjacent to a bay connected to the Gulf of Mexico;

(10) a municipality with a population of more than 40,000 and less than 50,000 that is located in a county with a population of more than 285,000 and less than 300,000 that borders the Gulf of Mexico;

(11) a municipality with a population between 32,000 and 50,000 that is located entirely in a county that:

(A) has a population of less than 250,000;

(B) is adjacent to two counties that each have a population of more than 1.2 million; and

(C) contains two highways that are part of the national system of interstate and defense highways;

(12) a municipality with a population of more than 4,500 and less than 10,000 that:

(A) contains a highway that is part of the national system of interstate and defense highways; and

(B) is located in a county with a population between 175,000 and 190,000;

(13) a municipality with a population of less than 75,000 that is located in three counties, at least one of which has a population greater than 3.3 million;

(14) a municipality with a population between 13,900 and 17,000 that:

(A) contains three or more numbered United States highways; and

(B) is located in a county that is adjacent to a county with a population of more than 200,000;

(15) a municipality wit

The section continues: whole chapter.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.