feeder field inside the JSON.
/data/Premisses[ ] record schema is shared.
| Field | Type | Description |
|---|---|---|
| feeder | string | Feeder identifier. Matches the NT08 segment in the filename. The unit of analysis: each file describes exactly one feeder. |
| SumSupplayForFeeder | number | Installed PV generation capacity (kVA) on the feeder, summed across all children. A non-zero value flags this node as PV-generating; multiply by the normalized PV curve to get instantaneous output (see Nº 08). supplay is the source spelling and is preserved verbatim. |
| DatabaseID | string | Source database tag (e.g. nisresbsayp) — identifies the system of record that produced the export. |
| SoftwareVersion | string | Date-stamp of the producing exporter (7/12/2023). Treat as a build marker, not as the export run-time. |
| primaryMeters / transformers | array | One of two mutually exclusive arrays — see Nº 04. The key present tells you which file you are reading. |
| Field | Type | Description |
|---|---|---|
| primaryMeters[ ] | array | List of primary meters on this feeder. |
| · OBJECTID | number | GIS object id of the meter (e.g. 53452) — the join key into the spatial layer. |
| · SumSupplayForPrimary | number | Installed PV capacity (kVA) at this primary meter. Non-zero → PV-generating primary; multiply by the PV curve (Nº 08) for the time-series. |
| · Premisses[ ] | array | Customer premises fed by this primary meter — see Nº 05. |
| Field | Type | Description |
|---|---|---|
| transformers[ ] | array | List of distribution transformers on this feeder. |
| · transformerID | string | Asset id of the transformer (e.g. "145573"). Note: string, not number. |
| · SumSupplayForTransformer | number | Installed PV capacity (kVA) at this transformer. Non-zero → PV-generating transformer; multiply by the PV curve (Nº 08) for the time-series. |
| · Premisses[ ] | array | Customer premises fed by this transformer — see Nº 05. |
OBJECTID vs transformerID) and the sum label differ. Everything else — including the Premisses sub-record — is identical. A single consumer can normalize the two into one shape with little effort.
| Field | Type | Description |
|---|---|---|
| PremissObjectID | number | GIS object id of the customer premise feature (e.g. 4587359). Use this to join into the spatial premises layer. |
| PremissID | number | Business/contract id of the premise (e.g. 602906865). The customer-facing key — what billing and CRM use. |
| PremissEID | number | Premise external/electrical id (e.g. 4083756) — typically the connection-point id from the electrical model. |
| supplay | number | Installed PV capacity (kVA) for this single premise. Rolls up into the parent's SumSupplayFor…. For primary-side premises, the absolute consumption curve lives in a separate per-customer file (see Nº 08). |
Medium-voltage line leaving the substation. Joined by the feeder string against the GIS feeder layer.
HV/MV metering point upstream of the customer. The OBJECTID is the row id in the meters GIS layer.
MV→LV transformer feeding a cluster of premises. transformerID joins into the transformers asset register.
Spatial feature of the supplied premise. Joined via PremissObjectID into the premises layer for map overlays.
Customer-account / contract identifier. PremissID joins into billing & CRM.
Premise's connection-point id in the electrical model. PremissEID joins into the network-electrical tables.
Identifier of the source database that produced the export. Use it to disambiguate when ingesting from multiple environments.
The file with no __primary / __trans suffix is structurally different: a full GIS export of the feeder's physical network (17 feature classes) plus per-transformer hourly demand. It's roughly 650 KB — three orders of magnitude bigger than the rollups.
| Field | Type | Description |
|---|---|---|
| SoftwareVersion | string | Date-stamp of the exporter (e.g. "29/6/2023"). |
| FeederID | string | Feeder identifier — "NT08". Note: capital-F variant of feeder from the rollups. |
| TimeOfExport | string | Actual export run timestamp (e.g. "4/14/2024 8:05:19 PM"). Not present in the rollups. |
| DatabaseID | string | Source DB tag ("nisresbsayp"), same as the rollups. |
| AllFcNames | array | 17 GIS feature classes (lines + points) that together describe the network. |
| AllTransformers | array | Per-transformer hourly consumption curves (not PV). |
| Field | Type | Description |
|---|---|---|
| InternalName | string | DB-side layer name, e.g. "NIS.PrimaryMeter". The NIS. prefix is the source schema. |
| DisplayName | string | Hebrew label, e.g. "מיכל מדידה" (primary meter). |
| fcType | string | "Polyline" (conductors, bridges, connectors) or "Point" (devices: meters, transformers, switches, premises). |
| Subtypes·Code / ·Desc | array | Sub-classification codes and Hebrew descriptions (e.g. an MV bus has subtypes "internal jumper", "MV cell", "MV bus"). |
| Domains | array | Coded-value lookups used by the Fields — each is {DomainName, DomainCode[ ], DomainDesc[ ]}. Lets you translate raw codes (e.g. DISTRICT="9") into descriptions ("ירושלים והנגב"). |
| Fields | array | Column definitions for data[ ]. Each is {FieldName, FieldDisplayName, DomainName}. |
| data | array | The actual feature rows. Each row has an OBJECTID plus the columns named in Fields. Polyline rows include an EIDs[ ] array with multi-segment geometry (From_EID, To_EID, Length, geo.paths in projected coords). |
| InternalName | Shape | Layer | Rows |
|---|---|---|---|
| NIS.MVInnerConnection | line | MV bus · פס צבירה | 34 |
| NIS.OHMVElectricLine | line | Overhead MV line | 26 |
| NIS.UGMVElectricLine | line | Underground MV cable | 10 |
| NIS.OHLVElectricLine | line | Overhead LV line | 7 |
| NIS.UGLVElectricLine | line | Underground LV cable | 3 |
| NIS.Connector | line | MV connector | 16 |
| NIS.Bridge | line | LV bridge | 7 |
| NIS.UG_Coupling | line | Underground splice | 3 |
| NIS.PrimaryMeter | point | Primary meter — the OBJECTID joined by __primary.json | 3 |
| NIS.Transformer | point | Distribution transformer — the transformerID joined by __trans.json | 3 |
| NIS.Switch | point | Switch · מנתק | 33 |
| NIS.Fuse | point | Fuse · נתיך | 8 |
| NIS.CircuitBreaker | point | Circuit breaker · מפסק זרם | 2 |
| NIS.Separator | point | Separator · הפרדה | 1 |
| NIS.FCBuildingConnection | point | Building connection · חיבור למבנה | 10 |
| NIS.FCPremises | point | Customer premise · חצר | 2 |
| NIS.DistributionNetwork_Junctions | point | Network junction | 54 |
| Field | Type | Description |
|---|---|---|
| TransformatorID | string | Transformer id (e.g. "145573") — same key as transformerID in __trans.json. |
| Vals | string | String slot; in the sample it carries no payload. |
| transSeason[ ] | array | Six rows — one per YEARSEASON × DAYTIME combination (Nº 09). |
| · YEARSEASON | number | 0 summer, 1 winter. |
| · DAYTIME | number | 1 weekday, 2 Friday/eve, 3 Saturday/holiday. |
| · HOURLYDEMAND1 … HOURLYDEMAND24 | number | Hour-by-hour absolute consumption for that typical day. Units track the source system (likely kW or kVA). |
HOURLYDEMAND… values are consumption curves, not PV. They live at the transformer level. The per-customer absolute curves still come from the separate file referenced in Nº 08.
Two non-JSON sources sit alongside the feeder files: a system-wide Globals workbook of equipment models, and per-customer absolute consumption curves. Together with the normalized PV curve, they turn the static topology into time-series.
System-wide equipment-models library — engineering parameters for every asset type the feeder export references: conductors, transformers, switches, voltage levels, line construction, taps, and substations.
| Aspect | Detail |
|---|---|
| Values | Absolute consumption (kW / kWh) — read directly, no multiplication. |
| Applies to | Premisses inside primaryMeters[ ].Premisses[ ] (the primary side only). |
| Joined by | PremissID — the customer/contract id from the leaf record (Nº 05). |
| Indexed by | Time of day, plus YEARSEASON × DAYTIME (Nº 09). |
| vs. transformer demand | Transformer-level hourly demand is embedded in the full feeder export (Nº 07). The per-customer file is finer-grained and primary-side only. |
SumSupplay…) was attributed to the Globals workbook. The delivered version (Globals_1.0-DR.xlsx) holds the equipment-models library only — the PV-shape curve itself is expected to ship in a sibling workbook or additional sheet. Indexing is the same either way: YEARSEASON × DAYTIME × hour.
net power = consumption (customer or transformer file) − PV (SumSupplay × normalized PV curve). The JSON gives you the wiring; the companions give you the load and the generation through time.
YEARSEASON × DAYTIME combination → 2 × 3 = 6 typical-day profiles per source.