@globalfishingwatch/i18n-labels 1.2.90 → 1.2.92

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/en/datasets.json CHANGED
@@ -2038,6 +2038,26 @@
2038
2038
  "description": "90% of EEZ",
2039
2039
  "schema": {}
2040
2040
  },
2041
+ "public-norway-fishing-effort": {
2042
+ "name": "Norway VMS",
2043
+ "description": "Vessel monitoring system (VMS) data is provided by the The Norwegian Directorate of Fisheries. Data is collected using Norway’s vessel monitoring system via satellites and is published on a three-day delay containing information on vessels’ location, speed, course, and movement. Global Fishing Watch analyzes this data using the same algorithms developed for automatic identification system (AIS) to identify fishing activity and behaviors. The algorithm classifies each broadcast data point from vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch’s fishing activity heat map. VMS broadcasts data differently from AIS and may give different measures of completeness, accuracy, and quality. Global Fishing Watch is continually improving its algorithms across all broadcast data formats to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified or that the heat map may show apparent fishing activity when fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing” or “fishing effort,” as apparent rather than certain. Any and all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at the user’s discretion. Global Fishing Watch’s fishing detection algorithms are developed and tested using actual fishing event data collected by observers and is combined with expert analysis of AIS vessel movement data, resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and to improve automated classification techniques",
2044
+ "schema": {
2045
+ "lat": "lat",
2046
+ "lon": "lon",
2047
+ "flag": {
2048
+ "keyword": "flag",
2049
+ "enum": {
2050
+ "NOR": "NOR"
2051
+ }
2052
+ },
2053
+ "hours": "hours",
2054
+ "vessel_id": "vessel_id",
2055
+ "elevation_m": "elevation_m",
2056
+ "vessel-groups": "vessel-groups",
2057
+ "distance_from_port_m": "distance_from_port_m",
2058
+ "distance_from_shore_m": "distance_from_shore_m"
2059
+ }
2060
+ },
2041
2061
  "public-panama-fishing-effort": {
2042
2062
  "name": "Panama VMS",
2043
2063
  "description": "Vessel monitoring system (VMS) data provided by the Panamanian Authority of Aquatic Resources (ARAP). Data is received by Panama’s VMS system via satellite and contains vessel identities, gear type, location, speed, direction and more. Panama’s carrier vessel data is also available here. Each point in the carrier vessel data layer represents a position of the carriers, but not all positions are displayed. Carrier vessel positions are displayed once per day. In the future, we expect to be able to display more positions. Click on a carrier vessel’s position to view the vessel’s complete track. Global Fishing Watch analyzes this data using the same algorithms we developed for automatic identification system (AIS) data to identify fishing activity and behaviors. The algorithm classifies each broadcast data point from vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. VMS broadcasts data quite differently from AIS and may give different measures of completeness, accuracy and quality. Over time our algorithms will improve across all our broadcast data formats. Global Fishing Watch’s fishing detection algorithm for VMS, as for AIS, is a best effort to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified, or that the heat map may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing,” and “fishing effort,” as “apparent” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch fishing detection algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of AIS vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification.",
package/es/datasets.json CHANGED
@@ -2038,6 +2038,26 @@
2038
2038
  "description": "90% of EEZ",
2039
2039
  "schema": {}
2040
2040
  },
2041
+ "public-norway-fishing-effort": {
2042
+ "name": "VMS de Noruega",
2043
+ "description": "Los datos del sistema de monitoreo de embarcaciones (VMS) son proporcionados por la Dirección de Pesca de Noruega. Los datos se recopilan utilizando el sistema de seguimiento de embarcaciones de Noruega a través de satélites y se publican con un retraso de tres días que contienen información sobre la ubicación, velocidad, rumbo y movimiento de las embarcaciones. Global Fishing Watch analiza estos datos utilizando los mismos algoritmos desarrollados para el sistema de identificación automática (AIS) para identificar la actividad y los comportamientos de pesca. El algoritmo clasifica cada punto de datos de transmisión de los barcos como pesca aparente o no, y muestra el primero en el mapa de actividad pesquera de Global Fishing Watch. El VMS transmite datos de manera diferente al AIS y puede brindar diferentes medidas de integridad, precisión y calidad. Global Fishing Watch mejora continuamente sus algoritmos en todos los formatos de datos de transmisión para identificar algorítmicamente la \"actividad de pesca aparente\". Es posible que no se identifique alguna actividad pesquera o que el mapa de calor muestre actividad pesquera aparente cuando en realidad no se está pescando. Por estas razones, Global Fishing Watch califica los términos “actividad pesquera”, “pesca” o “esfuerzo pesquero” como aparentes en lugar de confirmados. Toda la información de Global Fishing Watch sobre la \"actividad de pesca aparente\" debe considerarse una estimación y debe confiarse únicamente en la discreción del usuario. Los algoritmos de detección de pesca de Global Fishing Watch se desarrollan y prueban utilizando datos de eventos de pesca reales recopilados por observadores y se combinan con análisis expertos de datos de movimiento de embarcaciones AIS, lo que da como resultado la clasificación manual de miles de eventos de pesca conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de actividades pesqueras y mejorar las técnicas de clasificación automatizadas",
2044
+ "schema": {
2045
+ "lat": "lat",
2046
+ "lon": "lon",
2047
+ "flag": {
2048
+ "keyword": "flag",
2049
+ "enum": {
2050
+ "NOR": "NOR"
2051
+ }
2052
+ },
2053
+ "hours": "hours",
2054
+ "vessel_id": "vessel_id",
2055
+ "elevation_m": "elevation_m",
2056
+ "vessel-groups": "vessel-groups",
2057
+ "distance_from_port_m": "distance_from_port_m",
2058
+ "distance_from_shore_m": "distance_from_shore_m"
2059
+ }
2060
+ },
2041
2061
  "public-panama-fishing-effort": {
2042
2062
  "name": "VMS de Panamá",
2043
2063
  "description": "Esta capa utiliza los datos del Sistema de Seguimiento de Buques (VMS) proporcionados por la Autoridad Panamana de Recursos Acuáticos (ARAP). Los datos son recibidos por el sistema VMS de Panama vía satélite y contienen identidades de buques, tipo de engranaje, ubicación, velocidad, dirección y más. Los datos del buque portador de Panama también están disponibles aquí. Cada punto en la capa de datos del buque de transporte representa una posición de los transportistas, pero no todas las posiciones se muestran. Las posiciones del buque portador se muestran una vez al día. En el futuro, esperamos poder mostrar más posiciones. Haga clic en la posición del transportista para ver el camino completo de la compañía. Global Fishing Watch analiza estos datos utilizando los mismos algoritmos que desarrollamos para los datos AIS para identificar la actividad y el comportamiento de la pesca. El algoritmo clasifica cada punto de datos de emisión de los buques como pesca aparente o sin actividad pesquera y muestra el primero en el mapa de calor de la actividad pesquera del Observatorio Mundial de Pesca. El VMS transmite datos de forma muy diferente al AIS y puede exhibir diferentes medidas de integridad, precisión y calidad. Con el tiempo, nuestros algoritmos mejorarán a través de todos nuestros formatos de datos de difusión. El algoritmo de detección de pesca de Global Fishing Watch para VMS, como para AIS, es un mejor esfuerzo para identificar algorítmicamente “aparente actividad pesquera”. Es posible que no se identifique alguna actividad pesquera, o que el mapa de calor pueda mostrar una actividad pesquera aparente donde la pesca no se está llevando a cabo. Por estas razones, Global Fishing Watch califica los términos “actividad pesquera”, “pesca” y “esfuerzo pesquero” como “aparente” en lugar de brindar certeza sobre esa actividad. En un todo o en parte, la información de Global Fishing Watch sobre “actividad pesqura aparente” debe ser considerada una estimación y debe ser confiada únicamente bajo su propio riesgo. Los algoritmos de detección de pesca Global Fishing Watch son desarrollados y probados usando datos reales de eventos de pesca recopilados por observadores, combinado con el análisis experto de los datos del movimiento de los buques AIS resultando en la clasificación manual de miles de eventos de pesca conocidos. Global Fishing Watch también colabora ampliamente con investigadores académicos a través de nuestro programa de investigación para compartir datos de clasificación de actividades pesqueras y clasificación automatizada.",
package/fr/datasets.json CHANGED
@@ -2038,6 +2038,26 @@
2038
2038
  "description": "90% of EEZ",
2039
2039
  "schema": {}
2040
2040
  },
2041
+ "public-norway-fishing-effort": {
2042
+ "name": "Norway VMS",
2043
+ "description": "Description pending",
2044
+ "schema": {
2045
+ "lat": "lat",
2046
+ "lon": "lon",
2047
+ "flag": {
2048
+ "keyword": "flag",
2049
+ "enum": {
2050
+ "NOR": "NOR"
2051
+ }
2052
+ },
2053
+ "hours": "hours",
2054
+ "vessel_id": "vessel_id",
2055
+ "elevation_m": "elevation_m",
2056
+ "vessel-groups": "vessel-groups",
2057
+ "distance_from_port_m": "distance_from_port_m",
2058
+ "distance_from_shore_m": "distance_from_shore_m"
2059
+ }
2060
+ },
2041
2061
  "public-panama-fishing-effort": {
2042
2062
  "name": "Panama VMS",
2043
2063
  "description": "Vessel monitoring system (VMS) data provided by the Panamanian Authority of Aquatic Resources (ARAP). Data is received by Panama’s VMS system via satellite and contains vessel identities, gear type, location, speed, direction and more. Panama’s carrier vessel data is also available here. Each point in the carrier vessel data layer represents a position of the carriers, but not all positions are displayed. Carrier vessel positions are displayed once per day. In the future, we expect to be able to display more positions. Click on a carrier vessel’s position to view the vessel’s complete track. Global Fishing Watch analyzes this data using the same algorithms we developed for automatic identification system (AIS) data to identify fishing activity and behaviors. The algorithm classifies each broadcast data point from vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. VMS broadcasts data quite differently from AIS and may give different measures of completeness, accuracy and quality. Over time our algorithms will improve across all our broadcast data formats. Global Fishing Watch’s fishing detection algorithm for VMS, as for AIS, is a best effort to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified, or that the heat map may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing,” and “fishing effort,” as “apparent” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch fishing detection algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of AIS vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification.",
package/id/datasets.json CHANGED
@@ -2038,6 +2038,26 @@
2038
2038
  "description": "90% of EEZ",
2039
2039
  "schema": {}
2040
2040
  },
2041
+ "public-norway-fishing-effort": {
2042
+ "name": "Norway VMS",
2043
+ "description": "Description pending",
2044
+ "schema": {
2045
+ "lat": "lat",
2046
+ "lon": "lon",
2047
+ "flag": {
2048
+ "keyword": "flag",
2049
+ "enum": {
2050
+ "NOR": "NOR"
2051
+ }
2052
+ },
2053
+ "hours": "hours",
2054
+ "vessel_id": "vessel_id",
2055
+ "elevation_m": "elevation_m",
2056
+ "vessel-groups": "vessel-groups",
2057
+ "distance_from_port_m": "distance_from_port_m",
2058
+ "distance_from_shore_m": "distance_from_shore_m"
2059
+ }
2060
+ },
2041
2061
  "public-panama-fishing-effort": {
2042
2062
  "name": "VMS Panama",
2043
2063
  "description": "Data Vessel Monitoring System (VMS) disediakan oleh Panamanian Authority of Aquatic Resources (ARAP). Data diterima oleh sistem VMS Panama melalui satelit dan berisi identitas kapal, jenis alat tangkap, lokasi, kecepatan, arah, dan lainnya. Data kapal pengangkut Panama juga tersedia di sini. Setiap titik di layer data kapal pengangkut mewakili posisi pengangkut, tetapi tidak semua posisi ditampilkan. Posisi kapal pengangkut ditampilkan sekali sehari. Di masa mendatang, kami berharap dapat menampilkan lebih banyak posisi. Klik pada posisi kapal pengangkut untuk melihat trek lengkap kapal. Global Fishing Watch menganalisis data ini menggunakan algoritma yang sama dengan yang dkembangkan untuk data Automatic Identification System (AIS) untuk mengidentifikasi aktivitas dan perilaku penangkapan ikan. Algoritma tersebut mengklasifikasikan setiap titik data siaran dari kapal sebagai yang terlihat sedang memancing atau tidak sedang memancing dan menunjukkan titik data sebelumnya pada peta panas aktivitas penangkapan ikan Global Fishing Watch. VMS menyiarkan data dengan sangat berbeda dari AIS dan dapat memberikan ukuran kelengkapan, akurasi dan kualitas yang berbeda. Seiring waktu, algoritma kami akan meningkat di semua format data siaran kami. Algoritma deteksi penangkapan ikan Global Fishing Watch untuk VMS seperti untuk AIS, adalah upaya terbaik secara algoritma untuk mengidentifikasi \"aktivitas penangkapan ikan yang terlihat.\" Ada kemungkinan bahwa beberapa aktivitas penangkapan ikan tidak teridentifikasi, atau peta panas dapat menunjukkan aktivitas penangkapan ikan yang terlihat jelas di mana penangkapan ikan sebenarnya tidak terjadi. Untuk alasan ini, Global Fishing Watch mengkualifikasikan istilah \"aktivitas memancing\", \"memancing\", dan \"upaya penangkapan ikan\", sebagai \"terlihat jelas\" dan daripada pasti. Setiap / semua informasi Global Fishing Watch tentang \"aktivitas penangkapan ikan yang terlihat\" harus dianggap sebagai perkiraan dan harus diandalkan sepenuhnya dengan risiko Anda sendiri. Algoritma deteksi penangkapan ikan Global Fishing Watch dikembangkan dan diuji menggunakan data peristiwa penangkapan ikan aktual yang dikumpulkan oleh pengamat, dikombinasikan dengan analisis ahli dari data pergerakan kapal AIS yang menghasilkan klasifikasi manual dari ribuan peristiwa penangkapan ikan yang diketahui. Global Fishing Watch juga bekerja sama secara ekstensif dengan peneliti akademis melalui program penelitian kami untuk berbagi data klasifikasi aktivitas penangkapan ikan dan klasifikasi otomatis.",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@globalfishingwatch/i18n-labels",
3
- "version": "1.2.90",
3
+ "version": "1.2.92",
4
4
  "license": "MIT",
5
5
  "scripts": {
6
6
  "start": "kill-port 8000 && serve -p 8000 --cors=true",
package/pt/datasets.json CHANGED
@@ -2038,6 +2038,26 @@
2038
2038
  "description": "90% of EEZ",
2039
2039
  "schema": {}
2040
2040
  },
2041
+ "public-norway-fishing-effort": {
2042
+ "name": "Norway VMS",
2043
+ "description": "Dados de rastreamento por satélite são fornecidos pela Diretoria de Pesca da Noruega. Os dados são compilados utilizando o sistema de monitoramento de embarcações da Noruega e publicados com atraso de três dias, contendo informações sobre a identidade da embarcação, localização, velocidade, rumo, e movimentos. Global Fishing Watch analisa os dados usando os mesmos algoritmos desenvolvidos para o sistema de identificação automática (AIS) para identificar atividade de pesca e comportamentos. O algoritmo classifica para cada transmissão de localização em “pesca aparente” e “não pesca” e apresenta a atividade de pesca na forma de mapa de calor. As transmissões de rastreamento por satélite diferente do AIS podem fornecer diferentes medidas de integridade, precisão e qualidade. O Global Fishing Watch está continuamente melhorando seus algoritmos em todos os formatos de dados de transmissão para identificar algoritmicamente a \"atividade aparente de pesca\". É possível que alguma atividade de pesca não seja identificada ou que o mapa de calor possa mostrar uma atividade de pesca aparente quando a pesca não está realmente ocorrendo. Por essas razões, o Global Fishing Watch qualifica os termos \"atividade de pesca\", \"pesca\" ou \"esforço de pesca\" como aparentes em vez de certos. Toda e qualquer informação do Global Fishing Watch sobre \"atividade de pesca aparente\" deve ser considerada uma estimativa e deve ser considerada apenas a critério do usuário. Os algoritmos de detecção de pesca do Global Fishing Watch são desenvolvidos e testados usando dados reais de eventos de pesca coletados por observadores e são combinados com a análise de especialistas de dados de movimento de embarcações AIS, resultando na classificação manual de milhares de eventos de pesca conhecidos. O Global Fishing Watch também colabora extensivamente com pesquisadores acadêmicos por meio de nosso programa de pesquisa para compartilhar dados de classificação de atividades de pesca e melhorar as técnicas de classificação automatizada",
2044
+ "schema": {
2045
+ "lat": "lat",
2046
+ "lon": "lon",
2047
+ "flag": {
2048
+ "keyword": "flag",
2049
+ "enum": {
2050
+ "NOR": "NOR"
2051
+ }
2052
+ },
2053
+ "hours": "hours",
2054
+ "vessel_id": "vessel_id",
2055
+ "elevation_m": "elevation_m",
2056
+ "vessel-groups": "vessel-groups",
2057
+ "distance_from_port_m": "distance_from_port_m",
2058
+ "distance_from_shore_m": "distance_from_shore_m"
2059
+ }
2060
+ },
2041
2061
  "public-panama-fishing-effort": {
2042
2062
  "name": "Panama VMS",
2043
2063
  "description": "Vessel monitoring system (VMS) data provided by the Panamanian Authority of Aquatic Resources (ARAP). Data is received by Panama’s VMS system via satellite and contains vessel identities, gear type, location, speed, direction and more. Panama’s carrier vessel data is also available here. Each point in the carrier vessel data layer represents a position of the carriers, but not all positions are displayed. Carrier vessel positions are displayed once per day. In the future, we expect to be able to display more positions. Click on a carrier vessel’s position to view the vessel’s complete track. Global Fishing Watch analyzes this data using the same algorithms we developed for automatic identification system (AIS) data to identify fishing activity and behaviors. The algorithm classifies each broadcast data point from vessels as either apparently fishing or not fishing and shows the former on the Global Fishing Watch fishing activity heat map. VMS broadcasts data quite differently from AIS and may give different measures of completeness, accuracy and quality. Over time our algorithms will improve across all our broadcast data formats. Global Fishing Watch’s fishing detection algorithm for VMS, as for AIS, is a best effort to algorithmically identify “apparent fishing activity.” It is possible that some fishing activity is not identified, or that the heat map may show apparent fishing activity where fishing is not actually taking place. For these reasons, Global Fishing Watch qualifies the terms “fishing activity,” “fishing,” and “fishing effort,” as “apparent” rather than certain. Any/all Global Fishing Watch information about “apparent fishing activity” should be considered an estimate and must be relied upon solely at your own risk. Global Fishing Watch fishing detection algorithms are developed and tested using actual fishing event data collected by observers, combined with expert analysis of AIS vessel movement data resulting in the manual classification of thousands of known fishing events. Global Fishing Watch also collaborates extensively with academic researchers through our research program to share fishing activity classification data and automated classification.",
package/val/datasets.json CHANGED
@@ -98,7 +98,7 @@
98
98
  },
99
99
  "vessel_id": "crwdns18508:0crwdne18508:0",
100
100
  "elevation_m": "crwdns18510:0crwdne18510:0",
101
- "vessel-groups": "crwdns27267:0crwdne27267:0",
101
+ "vessel-groups": "crwdns30015:0crwdne30015:0",
102
102
  "distance_from_port_m": "crwdns18512:0crwdne18512:0",
103
103
  "distance_from_shore_m": "crwdns18514:0crwdne18514:0"
104
104
  }
@@ -519,8 +519,8 @@
519
519
  }
520
520
  },
521
521
  "private-indonesia-aruna-fishing-effort": {
522
- "name": "crwdns27166:0crwdne27166:0",
523
- "description": "crwdns27048:0crwdne27048:0",
522
+ "name": "crwdns30017:0crwdne30017:0",
523
+ "description": "crwdns30019:0crwdne30019:0",
524
524
  "schema": {
525
525
  "lat": "crwdns27050:0crwdne27050:0",
526
526
  "lon": "crwdns27052:0crwdne27052:0",
@@ -536,11 +536,11 @@
536
536
  }
537
537
  },
538
538
  "vessel_id": "crwdns27068:0crwdne27068:0",
539
- "vessel-groups": "crwdns27277:0crwdne27277:0"
539
+ "vessel-groups": "crwdns30021:0crwdne30021:0"
540
540
  }
541
541
  },
542
542
  "private-indonesia-aruna-presence": {
543
- "name": "crwdns27168:0crwdne27168:0",
543
+ "name": "crwdns30023:0crwdne30023:0",
544
544
  "description": "crwdns26370:0crwdne26370:0",
545
545
  "schema": {
546
546
  "lat": "crwdns26372:0crwdne26372:0",
@@ -614,7 +614,7 @@
614
614
  },
615
615
  "private-indonesia-ipnlf-fishing-effort": {
616
616
  "name": "crwdns27184:0crwdne27184:0",
617
- "description": "crwdns27074:0crwdne27074:0",
617
+ "description": "crwdns30025:0crwdne30025:0",
618
618
  "schema": {
619
619
  "lat": "crwdns27076:0crwdne27076:0",
620
620
  "lon": "crwdns27078:0crwdne27078:0",
@@ -630,12 +630,12 @@
630
630
  }
631
631
  },
632
632
  "vessel_id": "crwdns27094:0crwdne27094:0",
633
- "vessel-groups": "crwdns27283:0crwdne27283:0"
633
+ "vessel-groups": "crwdns30027:0crwdne30027:0"
634
634
  }
635
635
  },
636
636
  "private-indonesia-ipnlf-presence": {
637
- "name": "crwdns27186:0crwdne27186:0",
638
- "description": "crwdns27188:0crwdne27188:0",
637
+ "name": "crwdns30029:0crwdne30029:0",
638
+ "description": "crwdns30031:0crwdne30031:0",
639
639
  "schema": {
640
640
  "lat": "crwdns26416:0crwdne26416:0",
641
641
  "lon": "crwdns26418:0crwdne26418:0",
@@ -669,7 +669,7 @@
669
669
  }
670
670
  },
671
671
  "private-indonesia-pelagic-presence": {
672
- "name": "crwdns27100:0crwdne27100:0",
672
+ "name": "crwdns30033:0crwdne30033:0",
673
673
  "description": "crwdns24892:0crwdne24892:0",
674
674
  "schema": {
675
675
  "lat": "crwdns18026:0crwdne18026:0",
@@ -736,7 +736,7 @@
736
736
  },
737
737
  "private-indonesia-rare-fishing-effort": {
738
738
  "name": "crwdns27170:0crwdne27170:0",
739
- "description": "crwdns27104:0crwdne27104:0",
739
+ "description": "crwdns30035:0crwdne30035:0",
740
740
  "schema": {
741
741
  "lat": "crwdns27106:0crwdne27106:0",
742
742
  "lon": "crwdns27108:0crwdne27108:0",
@@ -752,11 +752,11 @@
752
752
  }
753
753
  },
754
754
  "vessel_id": "crwdns27124:0crwdne27124:0",
755
- "vessel-groups": "crwdns27291:0crwdne27291:0"
755
+ "vessel-groups": "crwdns30037:0crwdne30037:0"
756
756
  }
757
757
  },
758
758
  "private-indonesia-rare-presence": {
759
- "name": "crwdns27172:0crwdne27172:0",
759
+ "name": "crwdns30039:0crwdne30039:0",
760
760
  "description": "crwdns26458:0crwdne26458:0",
761
761
  "schema": {
762
762
  "lat": "crwdns26460:0crwdne26460:0",
@@ -791,7 +791,7 @@
791
791
  }
792
792
  },
793
793
  "private-indonesia-zebrax-presence": {
794
- "name": "crwdns27128:0crwdne27128:0",
794
+ "name": "crwdns30041:0crwdne30041:0",
795
795
  "description": "crwdns17443:0crwdne17443:0",
796
796
  "schema": {
797
797
  "lat": "crwdns17445:0crwdne17445:0",
@@ -891,20 +891,20 @@
891
891
  }
892
892
  },
893
893
  "private-panama-presence": {
894
- "name": "crwdns27028:0crwdne27028:0",
895
- "description": "crwdns27030:0crwdne27030:0",
894
+ "name": "crwdns30043:0crwdne30043:0",
895
+ "description": "crwdns30045:0crwdne30045:0",
896
896
  "schema": {
897
- "flag": "crwdns27032:0crwdne27032:0",
897
+ "flag": "crwdns30047:0crwdne30047:0",
898
898
  "shiptype": {
899
- "keyword": "crwdns27034:0crwdne27034:0",
899
+ "keyword": "crwdns30049:0crwdne30049:0",
900
900
  "enum": {
901
- "carrier": "crwdns27036:0crwdne27036:0",
902
- "fishing": "crwdns27038:0crwdne27038:0",
903
- "oil_tanker": "crwdns27040:0crwdne27040:0"
901
+ "carrier": "crwdns30051:0crwdne30051:0",
902
+ "fishing": "crwdns30053:0crwdne30053:0",
903
+ "oil_tanker": "crwdns30055:0crwdne30055:0"
904
904
  }
905
905
  },
906
- "vessel_id": "crwdns27042:0crwdne27042:0",
907
- "vessel-groups": "crwdns27299:0crwdne27299:0"
906
+ "vessel_id": "crwdns30057:0crwdne30057:0",
907
+ "vessel-groups": "crwdns30059:0crwdne30059:0"
908
908
  }
909
909
  },
910
910
  "private-peru-fishing-effort": {
@@ -1142,7 +1142,7 @@
1142
1142
  },
1143
1143
  "vessel_id": "crwdns18634:0crwdne18634:0",
1144
1144
  "elevation_m": "crwdns18636:0crwdne18636:0",
1145
- "vessel-groups": "crwdns27301:0crwdne27301:0",
1145
+ "vessel-groups": "crwdns30061:0crwdne30061:0",
1146
1146
  "distance_from_port_m": "crwdns18638:0crwdne18638:0",
1147
1147
  "distance_from_shore_m": "crwdns18640:0crwdne18640:0"
1148
1148
  }
@@ -1512,11 +1512,11 @@
1512
1512
  },
1513
1513
  "public-eez-areas": {
1514
1514
  "name": "crwdns29233:0crwdne29233:0",
1515
- "description": "crwdns29235:0crwdne29235:0",
1515
+ "description": "crwdns30063:0crwdne30063:0",
1516
1516
  "schema": {}
1517
1517
  },
1518
1518
  "public-eez-areas-12nm": {
1519
- "name": "crwdns29205:0crwdne29205:0",
1519
+ "name": "crwdns30065:0crwdne30065:0",
1520
1520
  "description": "crwdns29207:0crwdne29207:0",
1521
1521
  "schema": {}
1522
1522
  },
@@ -1542,7 +1542,7 @@
1542
1542
  },
1543
1543
  "public-fao-major": {
1544
1544
  "name": "crwdns29237:0crwdne29237:0",
1545
- "description": "crwdns29251:0crwdne29251:0",
1545
+ "description": "crwdns30067:0crwdne30067:0",
1546
1546
  "schema": {}
1547
1547
  },
1548
1548
  "public-fisheries-restricted-areas": {
@@ -1591,23 +1591,23 @@
1591
1591
  }
1592
1592
  },
1593
1593
  "public-global-encounters-events": {
1594
- "name": "crwdns9883:0crwdne9883:0",
1595
- "description": "crwdns9885:0crwdne9885:0",
1596
- "schema": {
1597
- "fields": "crwdns9887:0crwdne9887:0",
1598
- "event_id": "crwdns9889:0crwdne9889:0",
1599
- "event_end": "crwdns9891:0crwdne9891:0",
1600
- "vessel_id": "crwdns9893:0crwdne9893:0",
1601
- "event_info": "crwdns9895:0crwdne9895:0",
1594
+ "name": "crwdns30069:0crwdne30069:0",
1595
+ "description": "crwdns30071:0crwdne30071:0",
1596
+ "schema": {
1597
+ "fields": "crwdns30073:0crwdne30073:0",
1598
+ "event_id": "crwdns30075:0crwdne30075:0",
1599
+ "event_end": "crwdns30077:0crwdne30077:0",
1600
+ "vessel_id": "crwdns30079:0crwdne30079:0",
1601
+ "event_info": "crwdns30081:0crwdne30081:0",
1602
1602
  "event_type": {
1603
- "keyword": "crwdns9897:0crwdne9897:0",
1603
+ "keyword": "crwdns30083:0crwdne30083:0",
1604
1604
  "enum": {
1605
- "port": "crwdns9899:0crwdne9899:0"
1605
+ "port": "crwdns30085:0crwdne30085:0"
1606
1606
  }
1607
1607
  },
1608
- "event_start": "crwdns9901:0crwdne9901:0",
1609
- "event_vessels": "crwdns9903:0crwdne9903:0",
1610
- "event_mean_position": "crwdns9905:0crwdne9905:0"
1608
+ "event_start": "crwdns30087:0crwdne30087:0",
1609
+ "event_vessels": "crwdns30089:0crwdne30089:0",
1610
+ "event_mean_position": "crwdns30091:0crwdne30091:0"
1611
1611
  }
1612
1612
  },
1613
1613
  "public-global-fishing-effort": {
@@ -1685,23 +1685,23 @@
1685
1685
  }
1686
1686
  },
1687
1687
  "public-global-loitering-events": {
1688
- "name": "crwdns26776:0crwdne26776:0",
1689
- "description": "crwdns26778:0crwdne26778:0",
1690
- "schema": {
1691
- "fields": "crwdns26780:0crwdne26780:0",
1692
- "event_id": "crwdns26782:0crwdne26782:0",
1693
- "event_end": "crwdns26784:0crwdne26784:0",
1694
- "vessel_id": "crwdns26786:0crwdne26786:0",
1695
- "event_info": "crwdns26788:0crwdne26788:0",
1688
+ "name": "crwdns30093:0crwdne30093:0",
1689
+ "description": "crwdns30095:0crwdne30095:0",
1690
+ "schema": {
1691
+ "fields": "crwdns30097:0crwdne30097:0",
1692
+ "event_id": "crwdns30099:0crwdne30099:0",
1693
+ "event_end": "crwdns30101:0crwdne30101:0",
1694
+ "vessel_id": "crwdns30103:0crwdne30103:0",
1695
+ "event_info": "crwdns30105:0crwdne30105:0",
1696
1696
  "event_type": {
1697
- "keyword": "crwdns26790:0crwdne26790:0",
1697
+ "keyword": "crwdns30107:0crwdne30107:0",
1698
1698
  "enum": {
1699
- "port": "crwdns26792:0crwdne26792:0"
1699
+ "port": "crwdns30109:0crwdne30109:0"
1700
1700
  }
1701
1701
  },
1702
- "event_start": "crwdns26794:0crwdne26794:0",
1703
- "event_vessels": "crwdns26796:0crwdne26796:0",
1704
- "event_mean_position": "crwdns26798:0crwdne26798:0"
1702
+ "event_start": "crwdns30111:0crwdne30111:0",
1703
+ "event_vessels": "crwdns30113:0crwdne30113:0",
1704
+ "event_mean_position": "crwdns30115:0crwdne30115:0"
1705
1705
  }
1706
1706
  },
1707
1707
  "public-global-presence": {
@@ -1820,8 +1820,8 @@
1820
1820
  "schema": {}
1821
1821
  },
1822
1822
  "public-graticules": {
1823
- "name": "crwdns29241:0crwdne29241:0",
1824
- "description": "crwdns29253:0crwdne29253:0",
1823
+ "name": "crwdns30117:0crwdne30117:0",
1824
+ "description": "crwdns30119:0crwdne30119:0",
1825
1825
  "schema": {}
1826
1826
  },
1827
1827
  "public-gs-as-simplified": {
@@ -1841,7 +1841,7 @@
1841
1841
  },
1842
1842
  "public-high-seas-pockets": {
1843
1843
  "name": "crwdns29285:0crwdne29285:0",
1844
- "description": "crwdns29287:0crwdne29287:0",
1844
+ "description": "crwdns30121:0crwdne30121:0",
1845
1845
  "schema": {}
1846
1846
  },
1847
1847
  "public-indonesia-fishing-effort": {
@@ -1899,7 +1899,7 @@
1899
1899
  "Handline": "crwdns27164:0crwdne27164:0"
1900
1900
  }
1901
1901
  },
1902
- "vessel-groups": "crwdns27309:0crwdne27309:0"
1902
+ "vessel-groups": "crwdns30123:0crwdne30123:0"
1903
1903
  }
1904
1904
  },
1905
1905
  "public-indonesia-pelagic-presence": {
@@ -1924,7 +1924,7 @@
1924
1924
  }
1925
1925
  },
1926
1926
  "public-indonesia-zebrax-presence": {
1927
- "name": "crwdns27142:0crwdne27142:0",
1927
+ "name": "crwdns30125:0crwdne30125:0",
1928
1928
  "description": "crwdns10177:0crwdne10177:0",
1929
1929
  "schema": {
1930
1930
  "lat": "crwdns10179:0crwdne10179:0",
@@ -1950,7 +1950,7 @@
1950
1950
  },
1951
1951
  "public-mediterranean-area-of-interest-1": {
1952
1952
  "name": "crwdns25590:0crwdne25590:0",
1953
- "description": "crwdns25592:0crwdne25592:0",
1953
+ "description": "crwdns30127:0crwdne30127:0",
1954
1954
  "schema": {}
1955
1955
  },
1956
1956
  "public-mexico-fishing-effort": {
@@ -2015,17 +2015,17 @@
2015
2015
  },
2016
2016
  "public-mpa-all": {
2017
2017
  "name": "crwdns29245:0crwdne29245:0",
2018
- "description": "crwdns29259:0crwdne29259:0",
2018
+ "description": "crwdns30129:0crwdne30129:0",
2019
2019
  "schema": {}
2020
2020
  },
2021
2021
  "public-mpa-no-take": {
2022
- "name": "crwdns29255:0crwdne29255:0",
2023
- "description": "crwdns10277:0crwdne10277:0",
2022
+ "name": "crwdns30131:0crwdne30131:0",
2023
+ "description": "crwdns30133:0crwdne30133:0",
2024
2024
  "schema": {}
2025
2025
  },
2026
2026
  "public-mpa-no-take-partial": {
2027
- "name": "crwdns29249:0crwdne29249:0",
2028
- "description": "crwdns29227:0crwdne29227:0",
2027
+ "name": "crwdns30135:0crwdne30135:0",
2028
+ "description": "crwdns30137:0crwdne30137:0",
2029
2029
  "schema": {}
2030
2030
  },
2031
2031
  "public-mpa-restricted": {
@@ -2038,6 +2038,26 @@
2038
2038
  "description": "crwdns25608:0crwdne25608:0",
2039
2039
  "schema": {}
2040
2040
  },
2041
+ "public-norway-fishing-effort": {
2042
+ "name": "crwdns30147:0crwdne30147:0",
2043
+ "description": "crwdns30149:0crwdne30149:0",
2044
+ "schema": {
2045
+ "lat": "crwdns30151:0crwdne30151:0",
2046
+ "lon": "crwdns30153:0crwdne30153:0",
2047
+ "flag": {
2048
+ "keyword": "crwdns30155:0crwdne30155:0",
2049
+ "enum": {
2050
+ "NOR": "crwdns30157:0crwdne30157:0"
2051
+ }
2052
+ },
2053
+ "hours": "crwdns30159:0crwdne30159:0",
2054
+ "vessel_id": "crwdns30161:0crwdne30161:0",
2055
+ "elevation_m": "crwdns30163:0crwdne30163:0",
2056
+ "vessel-groups": "crwdns30165:0crwdne30165:0",
2057
+ "distance_from_port_m": "crwdns30167:0crwdne30167:0",
2058
+ "distance_from_shore_m": "crwdns30169:0crwdne30169:0"
2059
+ }
2060
+ },
2041
2061
  "public-panama-fishing-effort": {
2042
2062
  "name": "crwdns10287:0crwdne10287:0",
2043
2063
  "description": "crwdns10289:0crwdne10289:0",
@@ -2340,18 +2360,18 @@
2340
2360
  }
2341
2361
  },
2342
2362
  "public-rfmo": {
2343
- "name": "crwdns29229:0crwdne29229:0",
2344
- "description": "crwdns29257:0crwdne29257:0",
2363
+ "name": "crwdns30139:0crwdne30139:0",
2364
+ "description": "crwdns30141:0crwdne30141:0",
2345
2365
  "schema": {}
2346
2366
  },
2347
2367
  "public-tristan-seamounts-200-1618586314138": {
2348
2368
  "name": "crwdns25612:0crwdne25612:0",
2349
- "description": "crwdns25614:0crwdne25614:0",
2369
+ "description": "crwdns30143:0crwdne30143:0",
2350
2370
  "schema": {}
2351
2371
  },
2352
2372
  "public-tristan-seamounts-3000-1618586349746": {
2353
2373
  "name": "crwdns25616:0crwdne25616:0",
2354
- "description": "crwdns25618:0crwdne25618:0",
2374
+ "description": "crwdns30145:0crwdne30145:0",
2355
2375
  "schema": {}
2356
2376
  },
2357
2377
  "public-tristan-seamounts-existing-1618586378121": {