Feature types and fields
Use catalogue map and equipment types with their validation rules.
Last updated:
Catalogue source
GET /api/meta returns types, equipment, status, modules, placement, faces and validation constraints. Use this response for form fields and selection lists. Enabled organisation modules and general availability affect catalogue visibility.
Creating a map feature requires type and a suitable geometry. Catalogue fields such as name, note and status are not all automatically required. The fields list defines fields and choices; the server also applies type-specific rules.
Map types
| Key | Interface name | Geometry | Module |
|---|---|---|---|
pop |
POP / exchange | Point | Shared site |
cabinet |
Site cabinet | Point | Shared site |
closure |
Splice closure | Point | Fiber |
customer |
Address entrance | Point | Address and building |
building |
Building | Point | Shared site |
site |
Site | Point | Shared site |
manhole |
Manhole | Point | Shared site |
handhole |
Handhole | Point | Shared site |
pole |
Pole | Point | Shared site |
cable |
Fiber cable | LineString / MultiLineString | Fiber |
duct |
Duct / conduit | LineString / MultiLineString | Shared site |
trench |
Trench route | LineString / MultiLineString | Shared site |
aerial |
Aerial line | LineString / MultiLineString | Shared site |
area |
Area | Polygon / MultiPolygon | Core |
ref |
Reference feature | Supported point, line or area type | Core |
electric_cable |
Electrical cable | LineString / MultiLineString | Electric — Coming soon |
ref is a special type independent of the field catalogue and requires an active ref_layer_id belonging to the same project. Electric cable is defined in the catalogue, but its module is disabled by default and is Coming soon.
Geometry rules
General editing accepts Point, LineString, MultiLineString, Polygon and MultiPolygon. It does not directly accept MultiPoint. Longitude must be a finite number from −180 to 180 and latitude from −90 to 90.
A line requires at least two distinct points; an area ring must be closed with at least three vertices. Spatial validity of areas is checked. A single geometry accepts up to 100,000 vertices. Third and later coordinate components are not stored.
Shared attributes
status options are planned, construction, existing, retired; their interface labels are Planned, Under construction, Existing, Retired.
Where defined, design_length_m and measured_length_m are positive lengths in metres. Do not use zero for an unknown length; leave the field empty. For cables, cores is an integer from 1 to 1,728 and tubes from 1 to 144. When fiber count is omitted, the technical fiber layout may assume 12 fibers; integrations should send the actual count explicitly.
For catalogue choices, send the technical option value rather than the Turkish label. For example, use "existing" rather than "Mevcut" for status.
Fiber equipment
type |
Interface name | Main validation |
|---|---|---|
rack |
Rack | Has no ports; units, if supplied, is 1–200 |
odf |
ODF / patch panel | ports is required, 1–1,024 |
cassette |
Splice tray | slots is required, 1–1,024; per_slot, if supplied, is 1–24 |
olt |
OLT | ports identifies PON ports; uplink_ports and uplink_turu are separate |
olt_card |
OLT card | ports is required, 1–1,024; parent must be an OLT |
splitter |
Splitter | ratio options are 2, 4, 8, 16, 32, 64; defaults to 8 |
ont |
ONT / ONU | Incoming PON ports; ports defaults to 1 |
wdm_mux |
WDM mux / demux | channels and kayip_db are required; one common port and channel ports |
oadm |
OADM | channels and kayip_db are required; two line ports and channel ports |
Equipment must belong to an active node. When parent_id is supplied, the parent type must comply with catalogue placement rules. An OLT card belongs under an OLT; a splice tray may be directly in a node or under an ODF. A rack cannot be placed under another device.
For OLTs and OLT cards, out is the PON face and in the uplink face. On an ONT, in is the PON input. For a WDM mux/demux, in is common and out the channel face; for an OADM, in is the line face and out the channel face. Active equipment inputs and outputs are not joined as an internal optical pass-through. Obtain channel choices and loss fields from the catalogue.
New equipment labels in label accept up to 60 characters; port labels accept up to 32. port_labels uses port numbers as string keys, within the equipment's port range:
{"port_labels": {"1": "Giriş A", "2": "Giriş B"}}
Changing equipment port counts or placement also checks existing connections and child records. Sending a value within its field range does not guarantee acceptance. See Editing API.
