Transport Infrastructure (Ports) Regulation 2016

The schedule operates exclusively by mapping and terminology. The main drafting devices and concepts used, with examples from the schedule, are these:

• Area as the operative object: each entry commences with “For section X, the area described for the Port of Y is the area within the following,” and then lists points and lines (sch.2-sec.1; sch.2-sec.2). The schedule thus supplies the “area” that the main Act will treat as the port. The schedule does not create substantive duties itself; it supplies the spatial input other provisions will use.

• Coordinates and bearings: many entries consist of latitude and longitude pairs in degrees and minutes, sometimes qualified as “approximate”. The Port of Brisbane entry lists numerous precise coordinate pairs (for example latitude 26° 40.764' south, longitude 153° 08.341' east at Point Cartwright) and then ties them together by directional language (sch.2-sec.1).

• High-water mark and low-water mark: the schedule repeatedly uses the high-water mark as the landward limit for a boundary. Some entries use the low-water mark where reef edges are relevant (see sch.2-sec.4 Port of Cairns which moves from the high-water mark to the low-water mark at the edge of the coral reef around Green Island). The choice between high- and low-water mark matters because those concepts are physical measures that vary with time and require factual ascertainment.

• Geodesic, parallel, meridian, and direct lines: where straight courses over open water are required, the schedule sometimes specifies that the boundary follows a geodesic (the shortest line between two points on a spheroid), a line of latitude (parallel), or longitude (meridian). For example sch.2-sec.8 (Port of Hay Point) instructs “generally north-easterly along the geodesic” and then “east along the parallel” and “south along the meridian” to form its polygon. Sch.2-sec.3 (Bundaberg) includes “crossing in a direct line over all islands and any other land”.

• Sequential polygonal construction: each port area is defined by a sequence of points or markers connected in turn, closing the polygon where the last listed point returns to the first. That construction is standard for spatial instruments and implies the need for accurate plotting on charts or GIS.

• Variance in drafting detail and qualifiers: the schedule mixes exact coordinates, approximate coordinates, and plain topographical references (“to the high-water mark at the northern extremity of Connor Bluff on Curtis Island” sch.2-sec.7). Several entries use qualifiers such as “initially in a northerly direction” or “initially in a southerly direction” when describing how to follow a shoreline. Those qualifiers indicate that the drafter intended an initial direction but did not replace the entirety of the coastal line description with literal coordinates.

• Cross-references to the parent Act: every entry frames the area in terms of the section(s) of the Act it is meant to satisfy. For example, sch.2-sec.2 is explicitly “For section 6(1) and (2)”, and sch.2-pt.2-div.2 entries are “Ports for section 6(3)”. The schedule is thus subordinate to the parent Act; its legal effect depends on the sections that import these definitions.

Those concepts determine how the schedule will be operationalised. Plotting the boundaries requires converting the text sequence into mapped polygons, resolving the meaning of “high-water mark” on particular foreshore segments, and translating geodesic/parallel/meridian language into the datum and charting rules used by the implementing authority. The schedule therefore functions as a cryptic-but-authoritative spatial dataset embedded in the statute.

The immediate legal effect of the schedule is to determine which areas are “the Port of …” for the specified sections of the parent Act. Parties and entities that will therefore be affected include:

• Operators of vessels and owners of marine infrastructure: where rights, authorisations, or regulatory requirements in sections 5 or 6 of the main Act apply to the “Port of X”, the identity of the port area controls whether a vessel, berth, wharf, or marine operation falls within that regulatory perimeter. Because the schedule is the statutory definition, operators must compare their operational coordinates with the schedule’s polygons (for example, the multi-point polygon in sch.2-sec.1 for Brisbane).

• Port authorities, harbourmasters and agencies administering the parent Act: the schedule supplies the geographic limits port authorities will use to administer whatever statutory powers or duties the main Act confers in sections 5 and 6. They will need to translate each textual boundary into charts, signage, and administrative maps so that enforcement, licensing, planning and operational decisions reference the same spatial dataset that the statute uses.

• Landowners and waterfront occupiers adjoining the high-water mark: many entries expressly tie the port boundary to the high-water mark on the mainland or islands. That will affect the interface between port jurisdiction and adjacent land use regulation. For example, where the schedule moves “along the high-water mark of the southern bank of the Brisbane River to the north-western extremity of Bulimba Point” (sch.2-sec.1), the boundary runs immediately adjacent to terrestrial land parcels and their proprietors.

• Local councils and planning authorities: boundaries that run along or to the high-water mark, or that encompass riverbanks and estuaries, will intersect with local planning regimes. Those local bodies will need to understand whether approvals, overlays or coastal protections interact with the port area and how their planning instruments should be read alongside the parent Act’s spatial scope.

• Environmental and fisheries regulators: although the schedule does not itself impose environmental obligations, any environmental rules or consents that depend on the legal definition of “port” or the spatial application of the Act will rely on the areas in this schedule. For example, where a protected habitat lies inside vs outside the statutory port boundary, different statutory instruments may apply.

• Surveyors, hydrographers, and charting services: the drafting choices in the schedule create work for technical mapping professionals. The presence of geodesic instructions, meridian/parallel references, and “approximate” coordinates requires spatial conversion into the datum used by maritime charts and GIS. Those practitioners produce the map products that operators and regulators will rely upon.

• Insurers and financiers: underwriting of shipping and port infrastructure depends on regulatory perimeter. If an incident occurs inside the statutory port area that triggers port authority responsibilities under the parent Act, insurers and financiers will need to know whether operations were inside the schedule-defined area.

The schedule does not itself set any of these actors’ duties or grant rights, it only fixes the geographic scope that will be relevant when the main Act’s provisions operate. Therefore the distribution of effect flows from how the main Act applies within these areas; the schedule is the map that determines where that application occurs.

The schedule is a spatial definitional instrument. It does not, on its face, create novel statutory duties or rights. Its legal role is to identify the geographic domain to which duties and rights in the parent Act will attach. The schedule therefore performs a foundational function: it translates textual references to “the Port of X” in sections 5 and 6 into a set of mapped polygons that determine the reach of those sections.

Concretely, the key legal mechanism is this:

• Sections 5 and 6 in the parent Act refer to the “area” of a port. The schedule supplies that area for multiple ports by listing coordinates, shoreline links and references to high-water mark or low-water mark. Any duty or entitlement that the parent Act assigns to the port area therefore applies within the polygons the schedule sets out. For instance, where sch.2-sec.1 states “For section 5(1), the area is the area within the following,” and then lists the coordinates and shoreline links, that text makes those geographic limits the operative object for section 5(1).

Because the schedule uses the high-water mark, rights and duties that pivot on whether a point is landward or seaward of the high-water mark will be affected by factual determinations about the high-water mark. That has practical consequences:

• If a statutory power in the parent Act attaches at the high-water mark line (for example to licence activities in the port area up to the high-water mark), the precise location of that line on any parcel of shoreline will determine whether an activity is within the port area.
• Where the schedule refers to the low-water mark instead of the high-water mark (for example sch.2-sec.4 Port of Cairns uses the low-water mark at the outer edge of a reef), the seaward extent becomes operationally relevant.

Other drafting features that determine how rights attach:

• Use of geodesic and meridian/parallel language instructs the map-reader how to connect distant points around islands or across open water. Those connections determine whether a particular island, channel or bank sits inside or outside the port area.
• The schedule’s sequential polygonal phrasing creates closed areas. Rights that apply “within the port area” will only apply within the closed polygon delineated by the sequence of points that the schedule specifies.

The schedule therefore has a legal lever effect: by setting a boundary, it makes the parent Act’s duties and rights spatially contingent. Practitioners must therefore read the schedule side-by-side with the substantive sections of the Act that confer powers, obligations or benefits for the port area.

Note that the schedule itself does not state enforcement mechanisms, licensing processes, or fee regimes. Those instruments will be in the substantive sections and subordinate instruments made under the main Act. The schedule simply determines where, geographically, those other legal instruments can operate.

The text provided in this schedule contains no penalty provisions, no compliance offences, and no enforcement procedures. Its function is strictly spatial. Any penalty or enforcement consequences that flow from an activity being inside one of the schedule-defined port areas must therefore be located in the parent Act (the sections to which the schedule cross-references, namely section 5 and section 6) or in other statutory instruments and subordinate rules that rely on the schedule’s geographic definitions.

Several enforceability-related consequences follow from that architectural fact:

• The schedule fixes the spatial scope for enforcement; when an enforcement power or offence in the parent Act applies to “within the Port of X”, the schedule’s polygon determines whether an enforcement action or offence is engaged at a particular location. For enforcement agencies, the schedule is the map used to decide whether powers can be exercised at an incident site.
• Because the schedule uses the high-water mark in many entries, enforcing a provision up to or from the high-water mark will require factual determination of the position of that mark at the relevant time. High-water mark determination can be an evidential question in any enforcement proceeding where the precise boundary location is material.
• The schedule’s references to “approximate” coordinates and to non-numeric shoreline descriptions means that disputes about boundary placement may depend on expert survey evidence, charting and interpretation of the drafting language. Enforcement agencies, regulated parties and adjudicators will need reliable mapped products that reconcile the statutory text with chart datums.
• The schedule authorises no agency or official to enforce it directly; it is an enabling text. Which agency enforces offences that rely on the area will depend on the parent Act’s enforcement provisions and any delegation instruments.

Practically, therefore, one should not look to the schedule for penalties; the schedule is the spatial input that triggers penalty regimes elsewhere. The schedule does, however, create potential litigation and operational friction points where boundary interpretation is central to whether a penalty or enforcement action can be lawfully taken. Those friction points include the determination of “high-water mark” on particular foreshore parcels, the mapping of geodesic lines between coordinates, and the reconciliation of “approximate” coordinates with chart datums.

The schedule is a geographic definitional instrument intended to be used by the parent Act’s provisions that reference port areas. Its interaction with other laws occurs because many different legal regimes use port boundaries either directly or indirectly. The schedule therefore performs as a common spatial input across regimes, which creates several concrete interaction mechanisms:

• Parent Act interaction: the schedule is expressly tied to sections 5 and 6 of the main Act. Wherever those sections operate by reference to “the port” or “port area”, the schedule’s polygons supply the spatial boundary. The schedule therefore sits functionally downstream of the parent Act’s operation.

• Local planning, land use and property regulation: entries that follow the high-water mark or that run “to the high-water mark on the mainland” (for example sch.2-sec.1 Brisbane, sch.2-sec.3 Bundaberg) will interact at the edge with land-use planning instruments, coastal erosion protections, and private property boundaries. Interactions may arise where local law regulates activities seaward or landward of the high-water mark and the port area in the schedule overlaps those zones.

• Maritime navigation, safety and vessel regulation: although the schedule does not itself regulate navigation, port boundaries influence which maritime safety rules, pilotage requirements, harbour directions, mooring rules or vessel licensing provisions of other statutes or instruments apply within a port. In practice, port authorities and maritime safety agencies will use the schedule to determine the perimeter within which they issue directions or require pilots.

• Environmental, fisheries and protected area laws: marine parks, fisheries jurisdictions and environmental approvals frequently use geographic boundaries. The schedule’s polygons could therefore determine whether an activity falls within a protected marine zone or within the area where certain environmental rules apply, or whether a different authority has regulatory primacy.

• Statutory instruments and subordinate rules: port authorities commonly make local rules, by-laws or harbour directions that apply “within the port area”. The schedule will be the reference point for the legal validity of those subordinate instruments if they purport to operate only within a port. Any challenge to the territorial reach of such subordinate instruments will require examination of the schedule’s polygons and their proper plotting.

• Survey and cadastral law: the schedule’s reliance on high-water and low-water marks and on geodetic connections ties it into principles of coastal survey and the practical application of datum conventions. Conversion of statutory coordinates into usable titles, survey products, and navigation charts raises issues of datum, epoch and the legal method of determining foreshore boundaries in evidence.

In short, the schedule supplies the geographic element that is commonly used across a range of regulatory systems. The schedule’s text therefore functions as a nexus point through which the parent Act, local government, maritime safety, environmental regimes and cadastral processes will interact.

The schedule contains internal amendment annotations in the text that indicate updates made by subordinate legislation in 2020. The annotations identify specific clauses that have been varied and provide the statutory instrument reference. The explicit amendment notes in the text are:

• sch.2-sec.1 (Port of Brisbane) carries the note “sch 2 s 1 sub 2020 SL No. 94 s 29 (1)”. That records that section 1 of Schedule 2 was substituted by the 2020 subordinate legislation SL No. 94, section 29(1).

• sch.2-sec.5 (Port of Cape Flattery) is marked “sch 2 s 5 sub 2020 SL No. 94 s 29 (2)”. That records that section 5 of Schedule 2 was substituted by the same 2020 subordinate legislation at s 29(2).

• sch.2-sec.12 (Port of Mourilyan) has “sch 2 s 12 sub 2020 SL No. 94 s 29 (3)”, indicating substitution of that clause by the 2020 instrument at s 29(3).

• sch.2-sec.18 (Port of Karumba) includes “sch 2 s 18 amd 2020 SL No. 94 s 29 (4)”, indicating that section 18 was amended by the 2020 subordinate legislation at s 29(4).

These marginal notes show at least one discrete update operation in 2020 that substituted or amended specific schedule entries. No other amendment annotations appear within the supplied text. The presence of “sub” and “amd” in the notes indicates full substitution for some sections and amendment for another.

There is no further legislative history, such as earlier amendments, commencement dates for the schedule entries, or revocation clauses, included in the supplied text. If one requires the full amendment timeline, the parent Act’s version history and the referenced subordinate instrument SL No. 94 of 2020 would need to be consulted to confirm the precise changes made by s 29 of that instrument and the dates on which substitutions took effect.

Users who must rely on the schedule in practice should therefore confirm:

• whether other amendments post-dating SL No. 94 of 2020 have been made elsewhere; and
• the commencement dates of the 2020 substitutions and amendments to make sure which version of the boundary applied at particular times.

The annotated references in the schedule are the only explicit amendment history contained in the text provided.

The schedule contains no judicial decisions, case names, or references to litigation. It does not record any judicial interpretation or challenge to the boundaries listed. Consequently, within the text supplied there is no litigation history to cite.

That absence has two practical implications for lawyers and advocates:

• There is no textual record here to show how courts have interpreted phrases used in the schedule, such as “high-water mark”, “approximate”, or directional qualifications such as “initially in a northerly direction”. Where boundary interpretation is critical, litigants will likely need to rely on general principles of statutory interpretation, coastal boundary case law external to this text, maritime evidentiary practice, and expert surveyor evidence to establish where the schedule’s boundary lies on the ground.
• The absence of cases does not mean that litigation will not arise. The schedule’s reliance on coordinate plotting, shoreline description, and qualifiers creates points where dispute is foreseeable. For instance, an enforcement action that depends on whether an activity was “within the Port of X” may turn on which side of a plotted geodesic or of the high-water mark the activity occurred. Those will be evidentiary and interpretive questions.

For litigation practitioners preparing a potential boundary dispute, focal tasks will include:

• obtaining the authoritative map/chart that the relevant authority uses to implement the schedule, and identifying the datum and epoch used to plot the coordinates;
• instructing expert hydrographic/survey evidence to reconcile the schedule’s text with physical shorelines and navigation charts;
• identifying whether the parent Act supplies any statutory method for determining the high-water mark, and if not, building an evidentiary case based on established principles and expert testimony; and
• checking for any procedural prerequisites in the parent Act to challenge an administrative determination that relies on these boundaries.

Because the schedule itself contains multiple instances of “approximate” coordinates and non-numeric shoreline instructions, courts that consider disputes in the future will need to engage with the schedule text and the implementing evidence to determine the precise legal boundary. None of that interpretive history, if it exists, is recorded in the supplied schedule.

The schedule’s drafting choices create a number of practical and legal friction points. These are specific textual features that will produce real implementation questions and should be treated as risk points by practitioners:

• “Approximate” coordinates: several entries use the word “approximate” when giving latitude/longitude pairs (for example sch.2-sec.1 lists “approximate latitude 26° 40.764' south” and sch.2-sec.3 uses “high-water mark at latitude 24° 45.6' south, approximate longitude 152° 24.8' east”). The qualifier “approximate” creates immediate evidential uncertainty about the intended precision and whether the coordinate should be rounded or treated as indicative rather than definitive.

• High-water mark as a moving line: many boundaries are expressed “to the high-water mark” or “along the high-water mark”. High-water marks are physical features that can move over time due to tides, erosion, accretion and man-made works. The schedule does not state a methodology or a reference epoch for determining the high-water mark, which can lead to different parties relying on different surveys and thus to contested boundary placement.

• Mixed use of coordinate styles and topographic language: some entries rely mainly on numeric coordinates while others rely heavily on textual references to shoreline points, “initially in a northerly direction”, or named headlands. That mix requires careful reconciliation when producing a single coherent map. In practice, the authority implementing the schedule must decide how to prioritise or reconcile any conflict between a coordinate and a shoreline description.

• Use of geodesic, parallel and meridian: these terms require a datum and geodetic model to be used consistently. For example, sch.2-sec.8 (Hay Point) uses “generally north-easterly along the geodesic … east along the parallel … south along the meridian …”. The legal effect of such language depends on whether the geodesic and meridian references are plotted on WGS84, AGD66/84, or another datum, and whether map readers recognise the same geodetic model. The schedule does not specify the datum, so implementers must make an evidential choice and document it.

• “Crossing in a direct line over all islands and any other land”: sch.2-sec.3 (Bundaberg) contains the instruction to “cross in a direct line over all islands and any other land”. That language treats islands as not interrupting a straight-line connection between defined coastal points. In practice, a decision about whether an island is inside or outside the polygon will turn on how that “direct line” is plotted and whether the island’s high-water mark is included inside or outside the resultant polygon.

• Inconsistent place names and spellings in the schedule: the supplied text contains small drafting anomalies that ought to be noted as possible sources of confusion. For example, sch.2-sec.2 is headed “Port of Abbot Point” while the body text refers to “Port of Abbott Point” (two t’s in the body). Practitioners should be alert to possible typographical or naming inconsistencies and check which form the parent Act or subsequent instruments have used.

• Apparent coordinate anomalies: the text for sch.2-sec.17 (Port of Burketown) includes a coordinate stated as “to the high-water mark at latitude 17° 34.55' south, longitude 39° 45.89' east in the vicinity of Kangaroo Point”. That longitude differs in magnitude from neighbouring coordinates in northern Australia that use longitudes in the 139° east range. Such an apparent outlier in the schedule is a concrete drafting anomaly that requires confirmation from the authoritative legislative or mapping source. It may be an error in the schedule text or an artefact of transcription in the supplied copy. Practitioners must check the original published instrument and, where necessary, seek the authoritative map or an explanatory note.

• Multiple versions and substitutions: the amendment annotations show that at least some entries were substituted or amended in 2020. If a user of the schedule is relying on boundary placement for historical transactions or litigation they should confirm which version of the schedule applied at relevant times.

• Shoreline qualifiers like “initially”: the repeated use of “initially in a northerly direction” or “initially in a southerly direction” when describing “along the high-water mark” is open to interpretive debate about how much of the shore trace is intended by the text beyond the initial direction. That language may produce disputes over whether the boundary followed a particular meander or simply the initial course before another instructed change. Again, expert plotting will be necessary.

Each of these drafting features is a practical “gotcha” because they impose mapping, evidential, or interpretive work before the schedule’s polygons can be treated as certain on the ground. Practitioners should not treat the schedule text as a plug-and-play set of coordinates without converting the text into authoritative map products and documenting the conventions used for that conversion.

Because the schedule defines port areas, compliance in practice means ensuring that operations, permits, enforcement decisions, and land-use questions correctly reflect whether an activity or place lies within the statutory port area. The steps below are practical measures grounded in the schedule’s drafting features and should be treated as a checklist for affected parties and authorities.

1. Obtain the authoritative statutory and cartographic source

• Retrieve the parent Act (the sections that refer to the port “area”, notably s 5 and s 6 referenced in each entry) and confirm how those sections rely on the schedule.
• Ask the administering port authority or maritime agency for the official GIS shapefiles or navigational charts that they use to operationalise the schedule entries. The statute provides textual boundaries, but authorities typically publish mapped boundaries using a specific datum. Where available, use that authoritative map for compliance decisions.

2. Confirm datum, projection and epoch for plotting

• Before plotting any coordinate, confirm which geodetic datum (for example WGS84) and projection the implementing authority uses. The schedule does not specify a datum; differing datums can shift plotted positions by tens to hundreds of metres, which is material for high-water mark boundaries and narrow channels.

3. Commission hydrographic and foreshore surveys where necessary

• Where the boundary depends on the high-water mark on a particular foreshore, commission a coastal survey. Discuss the epoch and tidal datum to establish the high-water mark at the relevant time, and retain detailed survey reports for evidentiary purposes.
• For coordinates qualified as “approximate”, obtain precise GPS readings where you need certainty for compliance, permits or enforcement.

4. Reconcile textual shoreline descriptions with mapped lines

• For boundaries that follow “along the high-water mark” or that are intended to trace an island’s shore, use the surveyed foreshore line to draw the statutory polygon. Document and retain methodology notes explaining how the textual instruction was converted into the mapped line.

5. Pay attention to drafting anomalies and flagged substitutions

• If the schedule contains suspect coordinates or inconsistent naming (for example the Port of Burketown longitude anomaly or the Abbott/Abbot spelling inconsistency), seek written confirmation from the responsible legislative or mapping authority. Annex any official clarifications to internal compliance files.
• Check the amendment annotations for substituted sections (sch 2 s1 sub 2020 SL No. 94 s 29(1), etc.) to confirm which version of the schedule applies at given dates.

6. Update operational policies, permits and signage

• Port authorities and operators should ensure that harbour directions, licensing documents, mooring schemes and port maps refer to the same mapped polygon derived from the schedule. Update official documentation and public-facing charts so that regulated parties can locate the legal boundary easily.
• Where pilotage, fees, or harbour rules are triggered by being “within the port”, ensure permit forms and automated management systems reference the same shapefile.

7. Provide clear guidance to third parties

• For private operators, vessels, and landowners, provide guidance notes that explain how to check whether an activity falls within the port area. Include contact details for the agency that can confirm boundary placement and for the survey unit.

8. Preserve records for enforcement and litigation

• Keep records of the mapping conventions, datum, survey reports, and any official advice or corrections. Where an enforcement action is contemplated, the authority should be able to show the evidentiary chain establishing why a location fell inside the statutory polygon.

9. Use expert evidence where boundaries are challenged

• Anticipate that disputes over the position of the high-water mark, the plotting of geodesic lines, or “approximate” coordinates will require expert hydrographic, geomatic and surveying evidence. Retain experts early if a boundary placement is contested.

10. Coordinate with adjacent regulatory regimes

• Where port boundaries intersect planning overlays, environmental zones or marine parks, coordinate with those agencies to avoid duplication or jurisdictional uncertainty about consenting and enforcement. Provide the other agencies with the authoritative mapped polygon.

The schedule is a statutory mapping text not a procedural manual. Consequently, compliance in practical terms is about ensuring that the textual definitions are converted into consistent, documented and authoritative mapped products, and then consistently used across licensing, enforcement, planning, and advisory functions. Where the schedule contains drafting anomalies, authorities should seek and archive formal clarifications or corrigenda so that third parties can rely on a single coherent spatial dataset.