ENTSOG - TP FAQ - v1.0
ENTSOG - TP FAQ - v1.0
TP Documentation
08 February 2024
Change History
Version Author Reason for the new version and list of modifications
0.1.00 Kathrine N. Stannov Document initialisation
1.0.00 Kathrine N. Stannov First version approved for upload by TRA WG
1.0.10 Kathrine N. Stannov Additional questions for data queries added
1.0.20 Kathrine N. Stannov Additional questions for data queries added
1.0.21 Kathrine N. Stannov Additional questions for data queries added
1.0.22 Kathrine N. Stannov Additional question about tariff publications added
1.0.23 Kathrine N. Stannov Additional question about links to UMMs added
Contents
TP Frequently Asked Questions.................................................................................................. 1
1. TP Functionalities ............................................................................................................... 1
1.1. Maps ............................................................................................................................ 1
1.2. Point data: Charts and tables ...................................................................................... 1
2. TP Data Publications ........................................................................................................... 3
2.1. Point data: Charts and tables ...................................................................................... 3
2.2. Tariffs data ................................................................................................................... 4
2.3. UMM data .................................................................................................................... 5
2.4. Export section .............................................................................................................. 5
2.5. Fetching data via APIs .................................................................................................. 5
1. TP Functionalities
1.1. Maps
Q: Is it possible to get the underlying GIS data behind the maps on the TP?
A: The maps on the TP are built on a custom layout system and not via GIS data. This information is not
shared publicly.
ENTSOG AISBL; Av. de Cortenbergh 100, 1000-Brussels; Tel: +32 2 894 5100; Fax: +32 2 894 5101; info@entsog.eu
www.entsog.eu, VAT No. BE0822 653 040
TP Frequently Asked Questions
TP Documentation
2. Dedicated URL for a UMM with all its versions in “xml-style view”:
a. Fill the UMM ID into the API call, example:
https://transparency.entsog.eu/api/v1/urgentMarketMessages?ummids=19041521X
-DE-F-A0A0A-2001
5. Link to RSS feeds – contains UMMs published since 11 pm D-1 to current day:
Example of popup with several versions (click the UMM ID in the first column)
Page 2 of 6
TP Frequently Asked Questions
TP Documentation
2. TP Data Publications
2.1. Point data: Charts and tables
Q: Why are the physical flows sometimes higher than the firm technical capacity?
A: This is related to the pipe-in-pipe setup at some interconnection points, where two or more TSOs
share the capacity a pipeline. All TSOs publish the measured physical flows as they are required to do
following the Transparency Guidelines.
Q: How does one correct for the duplicated physical flows at the pipe-in-pipe points?
A: Via the information available in the Point Information Download, one can identify the extra
operators at the points, and remove them from the summary of the flows.
Q: How does one find all the gas flows for imports to the EU from NONEU/Russia/Norway?
A: As there is only a publication requirement for the European TSOs, this information needs to be
selected via the data published by those entities. The simplest way is to use the Export Wizard and
chose download based on Point Type = ‘Cross-Border Transmission IP between EU and Non-EU
(Import)’, in combination with the indicators you are interested in. The exports can be delivered as
XML, CSV or XLSX files, or you can configure an API call for it (use the COPY API CALL button).
Afterwards you can filter on the relevant import country.
Example with API call for downloading one month of data in Excel-format:
Page 3 of 6
TP Frequently Asked Questions
TP Documentation
Q: How does one choose the correct physical flow for the IP Greifswald where two pipelines OPAL
and NEL are placed and 5 TSOs are publishing data?
A: The flows on OPAL are published by LBTG and OPAL, whereas the flows of NEL are published by
NGT, GUD and Fluxys. The sum is showing the overall flow at Greifswald IP. This is because you are
looking at two pipelines, connected to two different metering stations. The flows need to be summed
up for each pipeline (i.e., only one value per pipeline).
Q: Why does the TP data for gas consumption in Germany not align with other sources on gas
consumption?
A: Per agreement with the German regulator, only Final Customers which are connected to the
transmission network are published on the TP.
Q: How does one locate gas consumption on the TP, and can you isolate household consumption?
A: Data publications are based on “relevant points”, as defined in the Regulation (EC) No 715/2009. In
accordance with Annex I to Regulation (EC) No 715/2009, the information for single final customers
and for production facilities, that is excluded from the definition of “relevant points”, shall be published
in aggregate format, at least per balancing zone. The aggregation of single final customers and of
production facilities, excluded from the definition of relevant points as described under 3.2(1)(a), shall
be considered as one relevant point. Thus, the information for those points is published in aggregated
manner per balancing zone. ENTSOG TP allows the TSOs to define several types of aggregated points:
DIS, FNC and PDR. The applicability of those types to the aggregated relevant points of the individual
TSOs depends on the aggregation approach applied on national level and approved by the relevant
NRAs. To obtain data for “gas consumption” a balancing zone, one should consider physical flows to
final consumers (FNC) and distribution (DIS). These can be exported using the Export Wizard in .csv,
.xml or Excel format or via the dedicated API calls. The category ‘Final Consumers’ can include several
subcategories, incl. low and high calorific gas flows, and industrial users, depending on the agreement
between the TSOs and the NRAs in the individual Member States. Households are not isolated as a
separate category. For more detailed data on gas transportation and physical flows, we refer to the
TSOs’ individual websites or Eurostat.
Q: How can one assess the situation for “storage level and gas reserves” in Europe?
A: Please refer to AGSI+ and ALSI for transparency information about gas storage facilities and LNG
terminals.
Page 4 of 6
TP Frequently Asked Questions
TP Documentation
Q:
A: When the Tariff Network Code came into force, the TSOs prepared an implementation
document for the market. This also includes a section on tariff publications, chapter VIII.
In short, there’s 5 dates to pay attention to:
− The annual auctions, taking place on the first Monday in July. The publication
deadline is 30 days before the auction: Publication on the TP for
Interconnection Points, and the rest on TSO websites
− 30 days before the start of tariff period, which varies per TSO. This deadline
applies to flow-based charges and simulations. Publications about
Interconnection Points on the TP, and the rest on TSO websites.
− In rare cases of congestion of firm capacity, the reserve prices and simulations
may be updated after the auction has been finalized if tariff methodology
parameters are adjusted.
− Under normal circumstances there is no need to continuously pinging the API
calls for tariffs unless NRAs and/or TSOs are not ready with the tariffs.
To make it easier, we have added a dedicated field for a link to the tariffs on the TSOs websites
in the Operator document.
Page 5 of 6
TP Frequently Asked Questions
TP Documentation
A: As a rule, API call must be executable within 60 seconds, and users should make sure to make
maximum 6 API calls per minute. If the user receives a message about a time out or too many requests,
the user should wait (adding a cool down time).
Q: Do you have any tips for making data queries via API calls more efficient?
A: There are several ways to optimise the API call. As a rule, avoiding generic random calls is a good
start. In addition:
- Avoid concurrent (simultaneous) requests
- If you receive an error message about HTTP Code 429 Too many Requests, and the user should
add a cool down time (e.g., 50 % active requests, 50 % no requests)
- Always use the pointDirection parameter
- Always include the operatorKey parameter when you query pointKey parameters
- Specify the indicators you are looking for
- Additional filters to improve the API performance: periodFrom and periodTo, periodType,
PublicationDateTime
- Don’t use the sort-parameter for larger queries
This FAQ document is updated on ad-hoc basis, in collaboration with ENTSOGs TSO-Members. Please
use the “Submit a Question” form if you have additional questions.
Best regards
Page 6 of 6