Profiles and authorities
Why each authority gets its own export profile, what a provisional profile means for your delivery, and what the marking on its files says.
Every authority that accepts as-built drawings has its own rules: which layers, which colours, which symbols, which fields in the title block. ruumica keeps all of that out of its program and in an export profile, one file per authority and version. The same project exported with two profiles gives two drawings that follow two authorities’ rules, from the same facts.
Provisional and production
A profile is production only when two things are true:
- it was written from the authority’s own layer and symbol specification, which the profile cites; and
- a drawing that this authority has accepted is on record, identified by its SHA-256, and the profile’s layers are checked against it.
Until both are true, a profile is provisional. It works, but nothing in it has been confirmed by the authority.
The marking on provisional files
Every file exported with a provisional profile says so on its face: PROFILE NOT AUTHORITY-VERIFIED. The export only goes ahead when you ask for it explicitly (--allow-unverified-profile), and the package’s manifest records production: false. Nobody can mistake such a delivery for one that follows an authority’s standard.
What it means for you:
- use a provisional profile for drafts, internal checks and conversations with the authority;
- for a formal submission, use a production profile for that authority;
- if you deliver with a provisional profile anyway, say so to the recipient. The marking already does.
Estonia today
ee.default.v1 is the only profile so far, and it is provisional. Its layer names start with ASB_ so they cannot be mistaken for a municipal standard. A production profile for an Estonian municipality needs that municipality’s specification and one drawing it has accepted. When both are available, the new profile is a file, not a program change, and the procedure is tested in advance.
Profiles never change in place
A profile’s SHA-256 is part of every manifest made with it. A published profile is therefore never edited: a change is a new version (v2), and older deliveries stay reproducible with the version they used (Exports never change).