Proclamation - Murray Marine Park

The central legal concepts in the schedule are spatial delimitation, zoning by IUCN category, datum and legal referents for maritime limits, and express exclusion of State coastal waters. Each concept is present in the text and has an operational consequence.

Spatial delimitation: Each Part contains a closed polygon described in sequential points and connectors (geodesic, meridian, parallel). The schedule uses precise degrees, minutes and seconds for latitude and longitude in the GDA94 datum (see the footnote relating to GDA94). The use of geodesics in several legs signals that boundary segments are to be interpreted as the shortest route on the ellipsoid between two geographic coordinates rather than straight lines on a flat projection; meridians and parallels are also used where the boundary follows a fixed longitude or latitude. These choices determine how the line between two points is to be plotted for compliance and charting.

Zoning by IUCN category: The Parts are headed with IUCN categories (Part 2: Category Ia , Strict Nature Reserve; Parts 3 and 4: Category VI , Managed Resource Protected Area). The label is a descriptive attribution; the schedule does not, in its text, convert those labels into specific legal entitlements, prohibitions or permitted activities. The presence of the label functions as a policy pointer, but the schedule contains no operative glossary or list of permitted/forbidden practices corresponding to those categories.

Exclusions and inter‑jurisdictional references: Parts 1 and 4 expressly exclude "coastal waters in relation to the State of South Australia" (Parts 1 and 4, text). The schedule therefore sets the park’s area in the Southern Ocean outside those State coastal waters. The schedule defers the definition of "coastal waters" to the Coastal Waters (State Powers) Act 1980 and Coastal Waters (Northern Territory Powers) Act 1980 (footnote). It also ties the "outer limit of the exclusive economic zone" to a proclamation under the Seas and Submerged Lands Act 1973 consistent with the United Nations Convention on the Law of the Sea (footnote). These cross‑references make the schedule dependent on other statutes and proclamations for operational jurisdictional limits.

Datum and gazette reference: All coordinates are expressed in GDA94, as described in a particular Commonwealth Gazette (GN35 of 6 September 1995). That datum reference fixes the ellipsoid and map reference that must be used when converting the coordinates for charting, ranging, geofencing, or software implementation.

Practical mapping language: The schedule uses terminology such as "commencing at", "then", "to its intersection with", and "generally north‑westerly and westerly along the outer limit", which are drafting conventions for sequential polygon descriptions. The combination of precise coordinates, geodesic segments and references to external limits (coastal waters, outer limit of EEZ) is the instrument’s method of creating legally certain lines on the surface of the ocean.

The schedule contains no other statutory apparatus , there are no management objectives, no definition of what "Special Purpose" permits, no enforcement mechanism, no declaration of managing authority and no timetable for review or amendment within the text provided.

The schedule affects persons, vessels and activities that are located in, enter, navigate through, or propose to use the marine area defined by the coordinates and described boundaries. The instrument itself limits its text to spatial descriptions; it therefore affects behaviour only to the extent that other legal instruments apply those coordinates as the area subject to regulation, management or prohibition. Nevertheless, from the text alone the following parties can be identified as having an interest or exposure.

Operators and owners of ships and vessels: Any vessel whose operations intersect the polygons described in Parts 1-4 will be geographically within the area that the schedule identifies as Murray Marine Park or one of its internal zones. The schedule's reliance on GDA94 coordinates and geodesic plotting requires vessel operators, charting services, marine pilots and electronic navigation system providers to consult the same datum and lines when determining whether a vessel is within a particular zone.

Commercial fishers and aquaculture operators: The schedule delineates three internal zones, two labelled IUCN Category VI and one labelled IUCN Category Ia. Although the schedule does not itself set activity rules, the selection and labelling of zones indicates that fisheries, aquaculture or other extractive uses that intersect those polygons will be affected to the extent that separate regulatory instruments apply management consistent with those labels.

Resource companies and prospective exploration or exploitation permit holders: The outer boundary extends to or near the outer limit of the exclusive economic zone (Parts 1-3 reference the EEZ outer limit). Where the polygon meets the outer limit of the EEZ, operators with interests in seabed or water column resources near that limit will need to map their activity against the schedule’s coordinates.

South Australian state government operations and coastal interests: The schedule expressly excludes coastal waters in relation to the State of South Australia in Parts 1 and 4. That textual exclusion creates an interface between Commonwealth marine area descriptions and state coastal jurisdiction, meaning that South Australian coastal waters are not captured by these polygons and that State authorities retain the definitionally applicable coastal waters.

Charting, mapping and compliance service providers: Because the schedule fixes coordinates in GDA94 and references geodesic plotting, providers that prepare management plans, geofences, navigational charts, vessel monitoring systems, enforcement zone overlays and compliance interfaces will need to implement the precise datum and geodetic plotting method indicated.

Regulatory and enforcement agencies: The schedule does not nominate a managing authority, nor does it confer enforcement powers. Any agency that is asked to apply regulatory controls, surveillance, or enforcement will need to look to other legislation or management instruments to find jurisdiction and duties. The schedule affects their work insofar as it supplies the spatial input required for any enforcement or regulatory overlay.

Indigenous groups, conservation NGOs, and the public: The text itself does not reference consultative obligations or rights; however, these stakeholders may be substantively affected in practice if subsequent management arrangements or regulatory measures (not contained in this schedule) alter access, use, or conservation in the delineated zones.

In sum, the schedule creates a cartographic fact: a marine park and internal zones with precise coordinates and datum. It does not on its face create obligations or authorise actions; therefore the parties affected in legal terms are those whose activities are regulated by separate instruments that adopt these coordinates as the regulated boundary.

The instrument supplied contains no express duties, rights, licences, permit regimes or authority‑allocating provisions. Its entire text is devoted to spatial descriptions and three footnotes linking to other instruments (coastal waters Acts, GDA94 Gazette, EEZ proclamation). Consequently the schedule itself does not confer rights to enter, use, exploit or protect the areas, nor does it state duties of a managing authority, obligations on third parties, or administrative processes.

Two limited positive legal statements are present and have operational consequence:

• The schedule designates certain polygons as "Sanctuary Area Zone (IUCN Category Ia , Strict Nature Reserve)" and others as "Special Purpose Area Zone" or "Multiple Use Area Zone (IUCN Category VI , Managed Resource Protected Area)" (Parts 2-4 headings). These are categorical labels. The schedule does not translate those labels into rights or duties but the labelling functions as a classificatory statement that other instruments may adopt and give operative effect to.
• The schedule explicitly excludes "coastal waters in relation to the State of South Australia" from Parts 1 and 4. This exclusion is a legal delimitation which operates as a statement that the polygon does not purport to cover State coastal waters (see the express exclusion language in Parts 1 and 4).

Because the schedule lacks prescriptive content, the duties and rights that will affect stakeholders must be sought in implementing legislation, regulations, management plans, permits or administrative instruments. In practice, an implementing instrument that adopts these coordinates would normally specify:

• which activities are permitted, restricted or prohibited in each zone;
• which authority administers permits and enforces rules;
• monitoring, reporting and compliance obligations for users; and
• consequences for contraventions.

None of those elements appear in the text provided. Therefore practitioners must treat this schedule as a spatial input and not as a self‑standing source of operational duties or rights.

The schedule contains no penalty clauses, enforcement mechanisms, compliance regimes, enforcement agency designations, infringement notices, evidentiary provisions or appeals processes. There is no text in any Part that creates an offence, prescribes fines, specifies enforcement powers (such as boarding, seizure, or search), or sets out administrative sanctions.

Because the schedule is a description of boundaries and zone labels, the enforcement framework, if any, must be supplied by other legal instruments. The schedule’s footnotes point to other statutes that define maritime limits (Coastal Waters (State Powers) Act 1980 and Coastal Waters (Northern Territory Powers) Act 1980; Seas and Submerged Lands Act 1973 for the EEZ limit), but they do not grant or record enforcement powers.

Operational implications flowing from that absence:

• Enforcement agencies, prosecutors or compliance managers cannot cite this schedule as the sole legal basis for prosecuting activity. They will need to reference a separate statutory or regulatory prohibition that applies within the coordinates.
• Persons concerned about liability must locate the substantive regulatory instruments , fisheries law, environmental protection regulations, shipping and navigation laws, petroleum and mineral tenure laws, or park management plans , that adopt these coordinates as the spatial basis for offences or administrative sanctions.
• Technical enforcement depends on the schedule’s mapping precision: enforcement actions will require the use of GDA94 coordinates and geodesic plotting to determine whether conduct took place inside a named zone. Any discrepancy in datum, plotting method, or charting could be material to enforcement.

Because the schedule is silent on enforcement, implementation risk arises from gaps between the map and the applicable regulatory apparatus. The schedule is necessary for spatial definition but not sufficient for enforcement.

The schedule explicitly interacts with three legal referents and implicitly interacts with any legislative or regulatory regime that seeks to apply rules within the coordinates. The explicit interactions are in the footnotes and in the exclusion language.

Coastal waters: The schedule excludes "coastal waters in relation to the State of South Australia" in Parts 1 and 4 and then states that "The coastal waters are defined in relation to each State and the Northern Territory by the Coastal Waters (State Powers) Act 1980 and Coastal Waters (Northern Territory Powers) Act 1980." That means the schedule depends on the definition of coastal waters in those Acts to determine where the Commonwealth polygon begins or where exclusion applies. Practically, mapping the exact line where the schedule picks up or leaves out coastal waters requires consulting those Acts and any instruments that set the outer limit of coastal waters.

Exclusive economic zone: Several parts refer to the "outer limit of the exclusive economic zone" and the schedule footnote states that the EEZ has been declared under the Seas and Submerged Lands Act 1973 in accordance with UNCLOS (Proclamation dated 26 July 1994 published in Gazette S290 of 29 July 1994). The schedule therefore treats the EEZ outer limit as a legal referent; plotting the boundary where the schedule follows the outer limit requires application of that earlier proclamation and any legal or cartographic determinations it contains.

Geodetic datum and gazette: All coordinates are given in GDA94, and the schedule cites Commonwealth Gazette GN35 (6 September 1995) as the description of GDA94. This interaction is technical but legally significant: any legal instrument, enforcement action, mapping decision or geofencing algorithm implementing the schedule must use the GDA94 datum. If a different datum is used without appropriate transformation, positional errors may arise.

Implicit interactions with substantive regimes: The schedule’s zoning labels (IUCN categories) indicate a conservation-oriented intent but do not themselves create regulatory content. Therefore the schedule interacts with, but does not replace, substantive laws such as:

• statutory instruments that create marine parks and specify their management, permitted activities and offences;
• fisheries management legislation that regulates fishing activity in Commonwealth waters; and
• environmental protection laws that regulate impacts to protected species or habitats.

Because those interactions are not present in the schedule, any user seeking to understand legal obligations should look for the implementing Commonwealth marine parks legislation, regulations, management plans, or delegated instruments that attach substantive rules to these zones. The schedule is a spatial annex; it must be read with those other instruments to determine the applicable legal regime.

Where overlaps or interfaces exist with State jurisdiction: The express exclusion of South Australian coastal waters indicates an intention to avoid overlapping or supplanting State coastal jurisdiction within that geographic band. The effect is that the schedule only seeks to regulate (or describes) areas outside State coastal waters; interaction with State laws will be limited to the excluded coastal waters, and any cross‑boundary activities will need coordination between Commonwealth and State regimes.

In all of these interactions the schedule is definitional and referential. It does not itself amend, repeal, or directly implement other Acts. Its legal significance depends entirely on being read together with other legislation and instruments.

The schedule as provided contains no amendment history statements, no savings or transitional provisions, and no dating or signature block within the text excerpt. It cites a number of external proclamations and gazettes for definitions and datums, but it does not record prior or subsequent amendments to itself.

Consequences of that absence:

• There is no internal record in the schedule of the date of its making, amendment dates, or repeals. Practitioners seeking to know whether these boundaries have been subsequently amended or superseded must search the parent or enabling Act, the statute book for amending instruments, or the official legislative database for modification records.
• Because the schedule uses external instruments (for coastal waters definitions, EEZ proclamation and GDA94), any subsequent amendments to those external instruments (for example, a later proclamation changing the EEZ limit, or a change in the legal definition of coastal waters) may affect the practical plotting or legal interpretation of the schedule. The schedule itself, however, contains no clauses to automatically pick up changes in those external instruments.
• The schedule’s reliance on GDA94 as the datum is potentially time‑sensitive in practice: if future legislative drafting preferences or mapping standards change the legal datum (for example, to GDA2020 or another standard), the schedule does not contain transitional provisions describing datum conversion or legal effect. The schedule simply fixes GDA94 as the stated datum.

Because no amendment history is included, any assertion about changes over time would be outside the text provided. Users must therefore treat the schedule as a static map annex and verify currentness by reference to the parent legislative instrument or official legislative records.

The schedule contains no references to judicial determinations, no annotations of litigation, and no case citations. It does not include any text describing disputes, judicial review outcomes, or declaratory judgments related to its boundaries, interpretations, or implementation. There is therefore no litigation history recorded within the text provided.

Practically, the absence of litigation history in the schedule means:

• Legal counsel or researchers cannot rely on the schedule alone to understand how courts have interpreted its language; any relevant case law, if it exists, would need to be located in external databases or court records referring to the parent Act or to enforcement actions that used these coordinates.
• Potential ambiguities raised by phrasing such as "generally north‑westerly and westerly along the outer limit" or the use of geodesic plotting could have been the subject of litigation elsewhere, but the schedule gives no indication of whether such disputes have arisen or been resolved.

If precise legal certainty is required for enforcement or high‑value commercial activity, practitioners should search for any judicial or administrative decisions that have considered the same or similar boundary language, and verify whether subsequent instruments or management plans have clarified interpretive questions.

The schedule is concise but contains multiple features that create practical and legal risks if not handled carefully. These are concrete, source‑grounded items to watch when using the schedule for mapping, regulation, enforcement or commercial decision‑making.

Datum and coordinate accuracy: All coordinates are explicitly in GDA94 (footnote). Failure to use GDA94 or to apply correct datum transformations will produce positional discrepancies. Electronic charts or vessel navigation systems using a different datum without proper transformation can misplace the boundary by tens to hundreds of metres.

Geodesic vs straight‑line plotting: The schedule instructs use of "geodesic" for many connecting legs. That requires plotting on the ellipsoid rather than Cartesian straight lines on a projection. Software packages and charting services may default to great circle or rhumb lines depending on settings. Users must ensure that geodesic computation consistent with GDA94 is used.

External referents for boundaries: Several legs are defined by intersection with the "outer limit of the coastal waters" and the "outer limit of the exclusive economic zone". Those referents exist in other instruments (see footnotes). The precise location of those limits, and any subsequent amendments to them, can change the plotted polygon even though the schedule’s latitude/longitude points remain the same. For example, where a leg runs "to its intersection with the parallel of latitude X" or "to its intersection with the outer limit", mapping requires access to official charts or proclamations for the coastal waters or EEZ outer limit.

Exclusion of State coastal waters: Parts 1 and 4 expressly exclude coastal waters "in relation to the State of South Australia". If a user assumes the schedule covers up to low‑water mark or another maritime baseline, they may be mistaken. The schedule defers to the Coastal Waters (State Powers) Act 1980 and the Coastal Waters (Northern Territory Powers) Act 1980 for that definition. Misreading this could produce regulatory overlap or double compliance.

Potential for adjacent or overlapping zones: The same coordinates and points appear across multiple Parts (for example, 37°49′10″S 137°47′38″E appears in Parts 1-4). The schedule partitions the area into named zones using shared points. Errors in plotting or inconsistent application of the GDA94 datum could make boundaries appear to overlap or to leave gaps. Implementers must ensure discrete polygon topology so that each location is unambiguously assigned to a single zone.

No operational rules in the schedule: The IUCN category labels are not converted into legal rules in this text. If a regulator or operator treats the labels as self‑executing prohibitions, they will be mistaken. Users must locate management plans or regulations that translate those category labels into permitted and prohibited activities.

Ambiguous language: Phrases such as "generally north‑westerly and westerly along the outer limit of the exclusive economic zone" introduce a small interpretive margin. For enforcement, that margin could be material, so implementers should obtain official cartographic depictions and, where necessary, ministerial or agency coordinates in a GIS format.

No enforcement or administration detail: Because no authority or penalty provisions are included, one cannot, from the schedule alone, determine who issues permits, who enforces rules, or how infringements are dealt with. Procurement of a management plan or parent Act is required to operationalise the schedule.

In sum, the gotchas are technical and jurisdictional: datum, geodesic plotting, reliance on other instruments for referent limits, exclusion of State coastal waters, and the absence of operational rules. These are gaps in the schedule that must be closed by reference to other documents for reliable implementation.

Compliance with the legal effects of this schedule requires two distinct steps: (1) implement the schedule as a precise spatial datum; and (2) identify and comply with the substantive regulatory instruments that apply within the zones described. The schedule supplies only the first; it must be used as an input to find the second.

Step 1 , Spatial implementation (mandatory from the schedule)

• Use the exact coordinates and descriptors in Parts 1-4 to plot the park and internal zones. The schedule explicitly requires use of the Geocentric Datum of Australia 1994 (GDA94) for all coordinates (footnote). Do not substitute another datum without applying formally accepted transformation parameters.
• Plot geodesic legs as geodesics on the ellipsoid consistent with GDA94 rather than as straight Euclidean lines on a flat projection. Where the text uses "meridian" or "parallel", follow the specified longitude or latitude as the boundary.
• For legs defined by intersection with "the outer limit of the coastal waters" or "the outer limit of the exclusive economic zone", obtain the authoritative legal or cartographic description of those limits from the referenced instruments (Coastal Waters (State Powers) Act 1980 and Coastal Waters (Northern Territory Powers) Act 1980 for coastal waters; the Seas and Submerged Lands Act 1973 proclamation published in Gazette S290 for the EEZ outer limit).
• Produce a GIS polygon file in GDA94 coordinate reference system, and produce chart overlays for Electronic Chart Display and Information Systems and other navigation tools. Include metadata citing the schedule, the GDA94 gazette reference (GN35 of 6 September 1995), and the proclamation for the EEZ.

Step 2 , Locate operative regulatory instruments (mandatory for legal compliance)

• Identify and obtain the parent Act or management instrument that incorporates this schedule into law and that contains the substantive rules (permitted activities, prohibited activities, permit requirements, enforcement powers, penalties and the managing authority). The schedule alone does not provide these.
• Where the schedule’s zones are labelled with IUCN categories, find the management plan or regulations that explain what those labels mean in legal terms for each zone (for example, whether Category Ia translates to a prohibition on extractive activities, research permit requirements, or access restrictions).
• For activities that may straddle State coastal waters and the Commonwealth polygons, consult the Coastal Waters (State Powers) Act 1980 and Coastal Waters (Northern Territory Powers) Act 1980 to determine jurisdictional boundaries and applicable rules in the coastal waters excluded by the schedule.
• For operations near the EEZ outer limit, confirm any cross‑jurisdictional coordination required with the rules established under the Seas and Submerged Lands Act 1973 proclamation, particularly where resource or navigation activities approach the outer limit.

Operational compliance practices

• Ensure that vessel‑monitoring systems, compliance geofences, Port State control briefs and commodity extraction plans use the GDA94 polygon files and geodesic plotting to avoid positional disputes.
• Require contractors, mariners and corporate operators to use the same mapping inputs and metadata when preparing navigation plans, environmental impact statements, or licence applications.
• Where management rules are silent or ambiguous, obtain formal written advice from the managing authority, regulator, or counsel, and seek authorisations or licences early rather than relying on the schedule as authority.
• Factor in timing and transformation: if mapping or navigation software uses a different datum, validate conversions and document the transformation parameters to be used in audits or prosecutions.

Records and audit trail

• Maintain records that show which datum and plotting method were used for any compliance decision, including metadata linking back to the Commonwealth Gazette GN35 reference for GDA94 and the EEZ proclamation Gazette S290. This will be necessary for any enforcement action or dispute about whether an activity occurred inside a specified zone.

In short, compliance begins with precise cartography in the GDA94 datum and geodesic plotting, and continues with identification of the substantive regulatory instruments that give legal effect to the mapped zones. The schedule itself is a mandatory spatial input but not a stand‑alone compliance code.