CONNECTIONPOINT

CONNECTIONPOINT shows all valid connection points and their type. Transmission loss factors are available for all connection points in TRANSMISSIONLOSSFACTOR.

Deprecation Warning

This table is in the HISTORICAL TABLES package, so is likely deprecated.

CONNECTIONPOINT data is confidential to each relevant participant

Source

CONNECTIONPOINT updates for new connection points as required.

Column Schema

CONNECTIONPOINTID

Connection Point Identifier

SQL Type: VARCHAR2(10) Polars Type: pl.Categorical

This column is mandatory, and a primary key.

ADDRESS1

Connection point location

SQL Type: VARCHAR2(80) Polars Type: str

This column is not mandatory.

ADDRESS2

Connection point location

SQL Type: VARCHAR2(80) Polars Type: str

This column is not mandatory.

ADDRESS3

Connection point location

SQL Type: VARCHAR2(80) Polars Type: str

This column is not mandatory.

CITY

City

SQL Type: VARCHAR2(40) Polars Type: str

This column is not mandatory.

CONNECTIONPOINTNAME

Connection point full description

SQL Type: VARCHAR2(80) Polars Type: str

This column is not mandatory.

CONNECTIONPOINTTYPE

Connection point type. transmission, distribution, station, genunit, or interconnector

SQL Type: VARCHAR2(20) Polars Type: pl.Categorical

This column is not mandatory.

LASTCHANGED

Last date and time record changed

For more information, see the dedicated documentation page.

SQL Type: DATE Polars Type: pl.Datetime()

This column is not mandatory.

Example: 2026/01/20 00:05:00

POSTCODE

Post Code

SQL Type: VARCHAR2(10) Polars Type: str

This column is not mandatory.

STATE

State of Australia

SQL Type: VARCHAR2(10) Polars Type: str

This column is not mandatory.

ADDRESS4

Not Used

SQL Type: VARCHAR2(80) Polars Type: str

This column is unused.

New Data Timing

When there are new connection points

Code Examples

Polars

Casting is enums, categoricals etc is not essential, but may speed up parsing. Swapping int for pl.UInt16, pl.Int32 would also speed up parsing. However some of the datatypes are inferred, so they may be wrong.

This code deduplicates for you. Deduplication is normally only required across multiple months.

This code assumes that all columns are present, which may not be true for older files.

import polars as pl
import polars.selectors as cs

# e.g. "2029/03/15 00:05:00"
dt_s_fmt = "%Y/%m/%d %H:%M:%S"

csv_paths = ["SOMEFILE.CSV", "OTHERFILE.CSV"]

lf = (
    pl.concat(
        [
            pl.scan_csv(
                csv_path,  # must be unzipped beforehand
                skip_rows=1,  # skip the header
                infer_schema=False,  # much faster
            )
            .filter(cs.by_index(0) == "D")  # drop the footer
            .select(~cs.by_index(range(4)))  # drop metadata columns
            for csv_path in csv_paths
        ],
        how="diagonal_relaxed",
    )
    .with_columns(
        pl.col("LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
    )
    .cast(
        {
            "CONNECTIONPOINTID": pl.Categorical,
            "ADDRESS1": str,
            "ADDRESS2": str,
            "ADDRESS3": str,
            "CITY": str,
            "CONNECTIONPOINTNAME": str,
            "CONNECTIONPOINTTYPE": pl.Categorical,
            "POSTCODE": str,
            "STATE": str,
            "ADDRESS4": str,
        }
    )
    # Drop deprecated/unused columns
    .drop("ADDRESS4")
    # Deduplicate
    # We want one row per ['CONNECTIONPOINTID']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(subset=["CONNECTIONPOINTID"], keep="last")
)

Nemosis

This table is not yet available in Nemosis.

Availability

AEMO's documentation states that this table's visibility is "Public". However, it is not available in the public monthly MMSDM archive. AEMO probably call this public because it is available to all market participants over private FTP.

There is a chance that is is still public to non-participants. It may only be available for some months; or (rarely) it may be available in a non-standard location.

Deduplication and PDR Loader Configuration

The primary keys are:

• CONNECTIONPOINTID

PDR Loader configuration does not mention this table, so it is unclear how to choose which row to keep when there are multiple rows for a given set of primary keys.

You should probably take the row with the maximum LASTCHANGED.

Indexes

• LASTCHANGED

Links

This page as JSON (schema documented here, but may change)

Download a JSON Schema specification for this table.

Official AEMO schema documentation

Other Information

Package: HISTORICAL TABLES

Copy as Markdown