Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

Not closed border lines error when loading ESE file


Jonas Kuster
 Share

Recommended Posts

Jonas Kuster
Posted
Posted

I'm getting a "not closed border lines error" when loading the sectors for EURW which I cannot understand why it is generated. I would appreciate some other people familiar with working ESE files could have a look into it. The exact error message is:

Error: Not closed border lines LFMM·LFMM FIR·000·195/1753/1320 in line 33591

 

The borderline referenced to is the following (the line starting with "BORDER"):

SECTOR:LFMM·LFMM FIR·000·195:00000:19500
OWNER:FM
BORDER:1753:1315:1354:1355:1356:1357:1348:635:634:1361:1308:1513:1757:1758:1759:1760:1761:1762:1449:1450:1451:1371:1378:1452:1280:1281:1763:1288:1287:1286:1285:1435:1434:1764:1553:1549:1667:850:1666:1395:195:194:1397:1724:1383:1382:1381:1324:1320:1723:1062:1313
DEPAPT:LFKB:LFKC:LFKF:LFKJ:LFLB:LFLL:LFLS:LFLU:LFLY:LFMD:LFMN:LFTW:LFLC:LFMA:LFMI:LFML:LFMO:LFMV:LFMP:LFMT:LFMU:LFTW:LFTH
ARRAPT:LFKB:LFKC:LFKF:LFKJ:LFLB:LFLL:LFLS:LFLU:LFLY:LFMD:LFMN:LFTW:LFLC:LFMA:LFMI:LFML:LFMO:LFMV:LFMP:LFMT:LFMU:LFTH:LFTW

 

The mentioned points in the error message (1753 and 1320) do not reflect the actual first and last bits of the border definitition. 1753 is the first one, but 1320 is not the last. So it is correct that these two sectorlines do not close the sector. It would be 1313 that closes with 1753, which I verified. So why does ES think that 1320 should close the sector? Is there a limit for the items forming the border definition?

 

Here some extracts from the sectorline definitions to show that I would not expect an error.

 

SECTORLINE:1753 ; GLO20891-GLO937
COORD:N046.30.00.000:E004.24.00.000
COORD:N046.30.00.000:E003.16.00.000

 

SECTORLINE:1320 ; GLO27306-GLO27307
COORD:N044.53.04.000:E003.01.57.000
COORD:N045.13.24.000:E003.01.16.000

 

SECTORLINE:1324 ; GLO27306-GLO841
COORD:N044.53.04.000:E003.01.57.000
COORD:N044.37.29.000:E003.02.28.000

 

SECTORLINE:1313 ; GLO843-GLO937
COORD:N046.20.00.000:E002.55.00.000
COORD:N046.30.00.000:E003.16.00.000

 

Any ideas appreciated.

Jonas Kuster
Network Supervisor
Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland
GNG Support Team | gng.aero-nav.com
ES Plugin Developer | CCAMS

Link to comment
Share on other sites

Mark Walsh
Posted
Posted

I would [Mod - Happy Thoughts]ume that you should have connected lines between 1753 and 1320. Need to see the lines 1723,1062 and 1313. [Mod - Happy Thoughts]uming the lines are not connected between these. This looks like GNG. If you use the map function, you should be able to see it better.

Mark Walsh

Vatsim Network Supervisor

Link to comment
Share on other sites

Jonas Kuster
Posted
Posted

Yes, it looks like ES is expecting that this border closes between 1753 and 1320, where it actually isn't. I can't understand why.

 

It is a GNG generated file. But I couldn't find any incorrect definition that would explain the error shown by ES to me. So I think it's not the time yet to involve GNG staff.

Here are the remaining line definitions:

SECTORLINE:1723 ; GLO27307-GLO844-GLO27308
COORD:N045.13.24.000:E003.01.16.000
COORD:N045.42.45.000:E003.00.16.000
COORD:N046.15.19.000:E002.55.39.998

 

SECTORLINE:1062 ; GLO27308-GLO843
COORD:N046.15.19.000:E002.55.39.998
COORD:N046.20.00.000:E002.55.00.000

 

SECTORLINE:1313 ; GLO843-GLO937
COORD:N046.20.00.000:E002.55.00.000
COORD:N046.30.00.000:E003.16.00.000

Jonas Kuster
Network Supervisor
Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland
GNG Support Team | gng.aero-nav.com
ES Plugin Developer | CCAMS

Link to comment
Share on other sites

  • 2 weeks later...
Mark Walsh
Posted
Posted

Here is what I see

SECTORLINE:1753 ; GLO20891-GLO937

COORD:N046.30.00.000:E004.24.00.000

COORD:N046.30.00.000:E003.16.00.000

[NEED COMMON POINT WITH 1062 HERE]

 

SECTORLINE:1062 ; GLO27308-GLO843

COORD:N046.15.19.000:E002.55.39.998 ; Connects to 1723

COORD:N046.20.00.000:E002.55.00.000

[NEED COMMON POINT WITH 1753 HERE]

 

SECTORLINE:1723 ; GLO27307-GLO844-GLO27308

COORD:N045.13.24.000:E003.01.16.000 ; Connects to 1320

COORD:N045.42.45.000:E003.00.16.000

COORD:N046.15.19.000:E002.55.39.998 ; Connects to 1062

 

SECTORLINE:1320 ; GLO27306-GLO27307

COORD:N044.53.04.000:E003.01.57.000 ; Connects to 1324

COORD:N045.13.24.000:E003.01.16.000 ; Connects to 1723

Mark Walsh

Vatsim Network Supervisor

Link to comment
Share on other sites

  • 3 months later...
Jonas Kuster
Posted
Posted

Felix from the GNG team did some tests and identified the following (undocumented) limitation by EuroScope, which is a maximum of 49 lines for a sector. If there are 50 or more, the remaining ones are disregarded, hence the error displayed.

Conclusion:

If you get the following error displayed in ES, it might be that the sector mentioned has more than 49 lines for it's definition.

Error: Not closed border lines ...

You need to reduce the number of lines. Easiest is by dividing the concerned sector in two. Then you will have two sectors to display. However, the limitation is on the lines per sector, which will then be about half.

Jonas Kuster
Network Supervisor
Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland
GNG Support Team | gng.aero-nav.com
ES Plugin Developer | CCAMS

Link to comment
Share on other sites

  • 8 months later...
Jonas Kuster
Posted
Posted

For anyone coming across this issue, the limit has been lifted to 200 in the r25 version.

Jonas Kuster
Network Supervisor
Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland
GNG Support Team | gng.aero-nav.com
ES Plugin Developer | CCAMS

Link to comment
Share on other sites

 Share