Criterion<\/th>	PostGIS<\/th>	GeoPackage<\/th><\/tr><\/thead>
Multi-user<\/td>	✅<\/td>	❌<\/td><\/tr>
Large datasets<\/td>	✅<\/td>	⚠️<\/td><\/tr>
Portability<\/td>	❌<\/td>	✅<\/td><\/tr>
Simplicity<\/td>	⚠️<\/td>	✅<\/td><\/tr>
Deployment<\/td>	Server<\/td>	File<\/td><\/tr>
Offline use<\/td>	❌<\/td>	✅<\/td><\/tr>
Embedded projects<\/td>	❌<\/td>	✅<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n 👉 The two approaches do not compete \u2014 they complement each other<\/strong>.<\/p>\n\n\n\n \n\n\n\n <\/span>Conclusion<\/span><\/h2>\n\n\n\n The GeoPackage mode of S57Manager<\/strong> makes ENC data accessible without heavy infrastructure<\/strong>, while preserving:<\/p>\n\n\n\n \n ENC semantic richness,<\/li>\n\n\n\n rigorous data structuring,<\/li>\n\n\n\n consistent exploitation in QGIS.<\/li>\n<\/ul>\n\n\n\n It naturally complements the PostGIS approach<\/strong>, making S57Manager<\/strong> a versatile tool<\/strong> adaptable to:<\/p>\n\n\n\n \n institutional environments,<\/li>\n\n\n\n lightweight, mobile or exploratory use cases.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n <\/span>Import NOAA ENC nautical charts directly into QGIS with S57Manager<\/span><\/h1>\n\n\n\n ENC (Electronic Navigational Charts) are now the standard for digital marine cartography.<\/p>\n\n\n\n With the latest update to the S57Manager plugin<\/a>, QGIS now features a module dedicated to the official NOAA ENC catalog, allowing users to easily search, filter, and import ENC cells directly from the QGIS interface.<\/p>\n\n\n\n This new tool greatly simplifies the work of users working with marine, port, or coastal data.<\/p>\n\n\n\n \n\n\n\n <\/span>🔎 The NOAA ENC catalog: what is it?<\/span><\/h2>\n\n\n\n The NOAA (National Oceanic and Atmospheric Administration)<\/strong> provides an official catalog containing several thousand ENC cells covering:<\/p>\n\n\n\n \n U.S. coastlines,<\/li>\n\n\n\n ports and harbors,<\/li>\n\n\n\n estuaries,<\/li>\n\n\n\n inland waterways.<\/li>\n<\/ul>\n\n\n\n Each ENC cell is described by:<\/p>\n\n\n\n \n a unique identifier (e.g. US5NYCDF<\/em>),<\/li>\n\n\n\n a purpose<\/strong> (usage level, from overview to very high detail),<\/li>\n\n\n\n a nominal scale,<\/li>\n\n\n\n a precise geographic extent,<\/li>\n\n\n\n an official download URL.<\/li>\n<\/ul>\n\n\n\n Until now, accessing this catalog required external tools or manual searches. The NOAA module in S57Manager<\/strong> completely changes this workflow.<\/p>\n\n\n\n \n\n\n\n<\/span>🧩 A NOAA module fully integrated into S57Manager<\/span><\/h2>\n\n\n\n The new NOAA module is fully integrated into S57Manager and follows its core philosophy:<\/p>\n\n\n\n \n centralize all ENC-related tools in a single, coherent and efficient interface.<\/strong><\/p>\n\n\n\n $\"\"$ <\/a><\/figure>\n<\/blockquote>\n\n\n\n From QGIS, users can now:<\/p>\n\n\n\n \n load the official NOAA catalog (XML),<\/li>\n\n\n\n browse the complete list of available ENC cells,<\/li>\n\n\n\n dynamically filter the catalog,<\/li>\n\n\n\n import only the cells that are truly relevant.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n <\/span>🎛️ Filters designed for real cartographic workflows<\/span><\/h2>\n\n\n\n The NOAA module provides several combinable filters<\/strong>.<\/p>\n\n\n\n $\"\"$ <\/a><\/figure>\n\n\n\n <\/span>🔹 Filtering by purpose<\/span><\/h3>\n\n\n\n NOAA ENC cells are classified by purpose (1 to 6):<\/p>\n\n\n\n Purpose<\/th> Usage<\/th><\/tr><\/thead> 1<\/td> Overview<\/td><\/tr> 2<\/td> General<\/td><\/tr> 3<\/td> Coastal<\/td><\/tr> 4<\/td> Approach<\/td><\/tr> 5<\/td> Harbor<\/td><\/tr> 6<\/td> Berthing \/ Detail<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Users can precisely select the desired usage levels.<\/p>\n\n\n\n \n\n\n\n <\/span>🔹 Filtering by scale<\/span><\/h3>\n\n\n\n Each ENC cell has a nominal scale (e.g. 1:10,000; 1:50,000). The module allows defining minimum and maximum scales to avoid loading:<\/p>\n\n\n\n \n overly generalized data,<\/li>\n\n\n\n or excessively detailed data.<\/li>\n<\/ul>\n\n\n\n 💡 Tip:<\/strong> Purpose 5 and 6 cells typically use very fine scales (\u2248 1:2,000 to 1:12,000). To display them correctly, it is recommended to set the minimum display scale around 1:1,500<\/strong>.<\/p>\n\n\n\n \n\n\n\n <\/span>🔹 Filtering by QGIS map canvas extent<\/span><\/h3>\n\n\n\n This is one of the strongest features of the module.<\/p>\n\n\n\n Users can choose to list only ENC cells that intersect the current QGIS map canvas extent<\/strong>.<\/p>\n\n\n\n Workflow:<\/p>\n\n\n\n \n zoom to your area of interest,<\/li>\n\n\n\n activate the extent filter,<\/li>\n\n\n\n only relevant ENC cells are listed.<\/li>\n<\/ul>\n\n\n\n Technically, this relies on:<\/p>\n\n\n\n \n NOAA extents stored in EPSG:4326<\/a><\/strong>,<\/li>\n\n\n\n automatic reprojection to the current QGIS CRS.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n <\/span>⬇️ Importing a NOAA ENC cell in just a few clicks<\/span><\/h2>\n\n\n\n $\"\"$ <\/a><\/figure>\n\n\n\n Once a cell is selected:<\/p>\n\n\n\n \n the ENC file is downloaded from the official NOAA URL;<\/li>\n\n\n\n it is validated and processed by the S57Manager S-57 workflow;<\/li>\n\n\n\n layers are imported into the configured GeoPackage or PostGIS<\/strong> database;<\/li>\n\n\n\n standard S57Manager organization and symbology are automatically applied.<\/li>\n<\/ul>\n\n\n\n No manual handling is required.<\/p>\n\n\n\n \n\n\n\n <\/span>🌍 Multilingual and fully integrated in QGIS<\/span><\/h2>\n\n\n\n Like the rest of S57Manager, the NOAA module is:<\/p>\n\n\n\n \n fully multilingual (FR \/ EN \/ ES \/ PT<\/strong>),<\/li>\n\n\n\n compatible with recent QGIS versions (Qt6),<\/li>\n\n\n\n fully consistent with other ENC tools in the plugin.<\/li>\n<\/ul>\n\n\n\n It is not a standalone tool, but a natural extension of the ENC workflow in QGIS.<\/p>\n\n\n\n \n\n\n\n <\/span>Conclusion<\/span><\/h2>\n\n\n\n With this new NOAA module, S57Manager reaches a new milestone<\/strong>:<\/p>\n\n\n\n \n direct access to the official ENC catalog,<\/li>\n\n\n\n precise data selection,<\/li>\n\n\n\n fast and controlled import,<\/li>\n\n\n\n seamless integration into QGIS.<\/li>\n<\/ul>\n\n\n\n Whether you work on:<\/p>\n\n\n\n \n port cartography,<\/li>\n\n\n\n coastal analysis,<\/li>\n\n\n\n inland waterway management,<\/li>\n\n\n\n or institutional marine data,<\/li>\n<\/ul>\n\n\n\n this module provides a real productivity gain and better control over ENC data.<\/p>\n\n\n\n \n\n\n\n <\/span>Exploring ENC Data Before Import: The NOAA Catalogue at the Service of S57Manager<\/span><\/h1>\n\n\n\n Working with ENC (S-57) data presents a very specific challenge: their richness and complexity make any \u201cblind\u201d approach inefficient. Even before discussing data import or structuring in QGIS, a fundamental question arises: which charts should be loaded, and why choose these rather than others?<\/strong><\/p>\n\n\n\n This is precisely where the NOAA ENC catalogue<\/strong> comes into play \u2014 a resource that is still largely underused by GIS professionals.<\/p>\n\n\n\n After presenting how to import ENC S-57 data into QGIS with S57Manager \u2014 first using PostGIS, then GeoPackage \u2014 this final article focuses on a crucial but often overlooked step: exploring and selecting the relevant ENC cells upstream of the import process, using the official NOAA ENC catalogue<\/strong>.<\/p>\n\n\n\n \n\n\n\n <\/span>ENC Data: Abundance That Complicates Choice<\/span><\/h2>\n\n\n\n Unlike conventional GIS datasets, an ENC does not correspond to a single map covering a given area. Instead, it belongs to a set of chart cells, each defined by:<\/p>\n\n\n\n \n a precise geographic extent,<\/li>\n\n\n\n a nominal scale,<\/li>\n\n\n\n a cartographic usage (overview, coastal, approach, harbour, berth\u2026),<\/li>\n\n\n\n a navigation purpose.<\/li>\n<\/ul>\n\n\n\n For the same geographic area, several ENC cells may overlap at different scales. Importing all available ENC data without prior selection quickly leads to:<\/p>\n\n\n\n \n oversized databases,<\/li>\n\n\n\n unreadable QGIS projects,<\/li>\n\n\n\n degraded performance,<\/li>\n\n\n\n and above all, a loss of cartographic meaning.<\/li>\n<\/ul>\n\n\n\n Before exploiting ENC data, it is therefore essential to understand and contextualize it<\/strong>.<\/p>\n\n\n\n \n\n\n\n <\/span>The NOAA ENC Catalogue: A Key but Raw Resource<\/span><\/h3>\n\n\n\n NOAA (National Oceanic and Atmospheric Administration) provides an official ENC catalogue, distributed as an XML file compliant with ISO standards (notably ISO 19115).<\/p>\n\n\n\n For each ENC cell, the catalogue contains:<\/p>\n\n\n\n \n a unique identifier (cell_id),<\/li>\n\n\n\n a name,<\/li>\n\n\n\n a scale,<\/li>\n\n\n\n a usage \/ purpose,<\/li>\n\n\n\n a geographic extent,<\/li>\n\n\n\n an official download URL.<\/li>\n<\/ul>\n\n\n\n In theory, all the information required for informed selection is available. In practice, however, this catalogue is difficult to exploit:<\/p>\n\n\n\n \n XML format is hard to read,<\/li>\n\n\n\n no direct spatial visualization,<\/li>\n\n\n\n consultation often limited to specialized tools or ad hoc scripts.<\/li>\n<\/ul>\n\n\n\n The challenge is therefore clear: transform this technical catalogue into a usable GIS layer in QGIS<\/strong>.<\/p>\n\n\n\n \n\n\n\n <\/span>From XML Catalogue to a Spatial Index Layer<\/span><\/h3>\n\n\n\n Once the NOAA catalogue is properly parsed, it becomes possible to extract the geographic extents of all ENC cells and convert them into polygons.<\/p>\n\n\n\n The result is a spatial index layer<\/strong>, typically stored in a GeoPackage, containing:<\/p>\n\n\n\n \n one polygon per ENC cell,<\/li>\n\n\n\n essential attributes:\n \n cell_id<\/li>\n\n\n\n name<\/li>\n\n\n\n scale<\/li>\n\n\n\n purpose<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n This layer is lightweight, stable, and only needs to be generated once. It does not contain any detailed nautical geometry \u2014 only chart extents.<\/p>\n\n\n\n $\"\"$ <\/a><\/figure>\n\n\n\n \n\n\n\n <\/span>Loading and Exploring NOAA Extents in QGIS<\/span><\/h2>\n\n\n\n Once loaded into QGIS, this index layer becomes a highly effective exploration tool:<\/p>\n\n\n\n \n transparent polygons to preserve background readability,<\/li>\n\n\n\n visible outlines to distinguish cells,<\/li>\n\n\n\n labels displaying the cell identifier,<\/li>\n\n\n\n easy overlay with:\n \n a study area,<\/li>\n\n\n\n an existing project,<\/li>\n\n\n\n field data.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n Within seconds, it becomes possible to:<\/p>\n\n\n\n \n identify which ENC cells actually cover the area of interest,<\/li>\n\n\n\n compare available scales,<\/li>\n\n\n\n understand the charting logic,<\/li>\n\n\n\n avoid unnecessary imports.<\/li>\n<\/ul>\n\n\n\n Here, QGIS fully regains its role as a spatial analysis tool<\/strong>, not just a data viewer.<\/p>\n\n\n\n \n\n\n\n <\/span>From Exploration to Import: Integration with S57Manager<\/span><\/h2>\n\n\n\n The true value of this index layer emerges when it is connected to S57Manager<\/strong>.<\/p>\n\n\n\n Directly from QGIS, the user can:<\/p>\n\n\n\n \n visually explore ENC extents,<\/li>\n\n\n\n select a relevant cell,<\/li>\n\n\n\n trigger the import of that cell via a QGIS action.<\/li>\n<\/ul>\n\n\n\n This workflow enables:<\/p>\n\n\n\n \n targeted imports,<\/li>\n\n\n\n fine control over data volume,<\/li>\n\n\n\n alignment between operational needs and loaded data,<\/li>\n\n\n\n full compatibility with both storage modes supported by S57Manager:\n \n PostGIS,<\/li>\n\n\n\n GeoPackage.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n The workflow shifts from \u201cimport then sort\u201d<\/strong> to \u201cunderstand, select, then import.\u201d<\/strong><\/p>\n\n\n\n \n\n\n\n <\/span>Conclusion: Bringing Intelligence Upstream<\/span><\/h2>\n\n\n\n By exploiting the NOAA catalogue as a GIS layer, working with ENC data becomes clearer and more efficient. Instead of suffering from the complexity of S-57 data, GIS professionals regain control from the very first step: exploration, selection, and decision-making<\/strong>.<\/p>\n\n\n\n Combined with S57Manager, the NOAA catalogue is not an auxiliary tool, but the first building block of a coherent processing chain<\/strong>:<\/p>\n\n\n\n catalogue \u2192 selection \u2192 import \u2192 exploitation<\/strong><\/p>\n\n\n\n A step too often overlooked \u2014 yet essential for working confidently with complex nautical data in QGIS.<\/p>\n\n\n\n \n","protected":false},"excerpt":{"rendered":" Understanding electronic nautical charts before using them in a GIS Introduction ENC \u2013 Electronic Navigational Charts are now the global standard for professional maritime navigation. Produced by national hydrographic services, they comply with strict standards defined…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-16194","page","type-page","status-publish","hentry"],"aioseo_notices":[],"campaignId":"","jetpack_shortlink":"https:\/\/wp.me\/P6XU0A-4dc","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/pages\/16194","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=16194"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/pages\/16194\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=16194"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Contenu <\/p>\nToggle<\/span>

Understanding electronic nautical charts before using them in a GIS<\/a>
- Introduction<\/a><\/li>
- 1. A very strict international standard<\/a><\/li>
- 2. ENCs are not \u201clayers,\u201d but objects.<\/a>
  - 2.1 Object-oriented logic<\/a><\/li>
  - 2.2 Coded and non-explicit attributes<\/a><\/li><\/ul><\/li>
  - 3. A strict separation between geometry and information<\/a>
    - 3.1 Shared geometries<\/a><\/li>
    - 3.2 No embedded symbolization<\/a><\/li><\/ul><\/li>
    - 4. The concept of \u201cPurpose\u201d and scale<\/a><\/li>
    - 5. A logic designed for safety, not for analysis<\/a><\/li>
    - 6. Why a dedicated plugin is necessary in QGIS<\/a><\/li>
    - Conclusion<\/a><\/li><\/ul><\/li>
    - Import, structuring and use of official nautical charts in a robust spatial database<\/a>
      - Introduction<\/a><\/li>
      - 1. What is S57Manager?<\/a>
        1.1 Plugin objectives<\/a><\/li>
        1.2 General architecture<\/a><\/li><\/ul><\/li>
        2. Why PostGIS for S-57 data?<\/a>
        2.1 The challenges of ENC data<\/a><\/li>
        2.2 Advantages of PostGIS storage<\/a><\/li><\/ul><\/li>
        3. Configuring PostGIS mode in S57Manager<\/a>
        3.1 Connection settings<\/a><\/li>
        3.2 Structure of generated tables<\/a><\/li><\/ul><\/li>
        4. Importing an S-57 ENC into PostGIS<\/a>
        4.1 Launching the import<\/a><\/li><\/ul><\/li>
        4.2 Control and validation of ENC data in PostGIS<\/a>
        4.2.1 Verification of imported layers<\/a>
        Presence and completeness<\/a><\/li>
        Logical organization<\/a><\/li><\/ul><\/li>
        4.2.2 Geometric integrity<\/a>
        Valid geometries<\/a><\/li>
        Topological consistency<\/a><\/li><\/ul><\/li>
        4.2.3 Attribute consistency<\/a>
        Presence of essential attributes<\/a><\/li>
        Coded values and domains<\/a><\/li>
        Semantic consistency<\/a><\/li><\/ul><\/li><\/ul><\/li>
        Why these checks are essential<\/a><\/li>
        5. Use in QGIS<\/a>
        5.1 Display by object families<\/a><\/li>
        5.2 Filtering displayed layers<\/a>
        Filtering by purpose<\/a><\/li>
        Display scale<\/a><\/li><\/ul><\/li>
        5.3 Custom symbolization<\/a><\/li><\/ul><\/li>
        Conclusion<\/a><\/li><\/ul><\/li>
        Geopackage : A lightweight, autonomous and portable solution for marine data<\/a>
        Introduction<\/a><\/li>
        1. Why choose GeoPackage?<\/a><\/li>
        2. Configuring GeoPackage mode<\/a>
        2.1 Creating or selecting a GeoPackage<\/a><\/li>
        2.2 Layer organization<\/a><\/li><\/ul><\/li>
        3. ENC \u2192 GeoPackage import<\/a><\/li>
        4. Data control and consistency in GeoPackage<\/a><\/li>
        5. Working with ENC layers locally in QGIS<\/a><\/li>
        6. PostGIS \/ GeoPackage comparison<\/a><\/li>
        Conclusion<\/a><\/li><\/ul><\/li>
        Import NOAA ENC nautical charts directly into QGIS with S57Manager<\/a>
        🔎 The NOAA ENC catalog: what is it?<\/a><\/li>
        🧩 A NOAA module fully integrated into S57Manager<\/a><\/li>
        🎛️ Filters designed for real cartographic workflows<\/a>
        🔹 Filtering by purpose<\/a><\/li>
        🔹 Filtering by scale<\/a><\/li>
        🔹 Filtering by QGIS map canvas extent<\/a><\/li><\/ul><\/li>
        ⬇️ Importing a NOAA ENC cell in just a few clicks<\/a><\/li>
        🌍 Multilingual and fully integrated in QGIS<\/a><\/li>
        Conclusion<\/a><\/li><\/ul><\/li>
        Exploring ENC Data Before Import: The NOAA Catalogue at the Service of S57Manager<\/a>
        ENC Data: Abundance That Complicates Choice<\/a>
        The NOAA ENC Catalogue: A Key but Raw Resource<\/a><\/li>
        From XML Catalogue to a Spatial Index Layer<\/a><\/li><\/ul><\/li>
        Loading and Exploring NOAA Extents in QGIS<\/a><\/li>
        From Exploration to Import: Integration with S57Manager<\/a><\/li>
        Conclusion: Bringing Intelligence Upstream<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n\n
        \n\n\n\n
        <\/span>Understanding electronic nautical charts before using them in a GIS<\/span><\/h1>\n\n\n\n
        \n\n\n\n
        <\/span>Introduction<\/span><\/h2>\n\n\n\n
        ENC \u2013 Electronic Navigational Charts are now the global standard for professional maritime navigation.<\/p>\n\n\n\n
        Produced by national hydrographic services, they comply with strict standards defined by the International Hydrographic Organization (IHO).<\/p>\n\n\n\n
        \n\n\n\n
        However, when attempting to use them in a GIS such as QGIS, one thing quickly becomes clear:<\/p>\n\n\n\n
        \n
        an ENC is not a conventional vector layer.<\/p>\n<\/blockquote>\n\n\n\n
        It is neither an enhanced shapefile<\/a>, nor a simple GeoPackage<\/a>, nor even an ordinary spatial database.<\/p>\n\n\n\n
        ENCs are complex information objects, designed primarily for navigation, not for GIS analysis.<\/p>\n\n\n\n
        This article aims to explain why ENCs are complex, and how this complexity explains the difficulties\u2014but also the richness\u2014of using them in QGIS.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>1. A very strict international standard<\/span><\/h2>\n\n\n\n
        ENC are defined by the S-57 standard (and more recently S-101), published by the IHO.<\/p>\n\n\n\n
        This standard requires:<\/p>\n\n\n\n
        \n
        a precise data structure<\/li>\n\n\n\n
        standardized vocabulary<\/li>\n\n\n\n
        strict interpretation rules<\/li>\n\n\n\n
        a clear separation between:\n
        \n
        geometry<\/li>\n\n\n\n
        semantics<\/li>\n\n\n\n
        presentation<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
        👉 Result:<\/p>\n\n\n\n
        the data is consistent worldwide, but difficult to divert from its original use.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>2. ENCs are not \u201clayers,\u201d but objects.<\/span><\/h2>\n\n\n\n
        <\/span>2.1 Object-oriented logic<\/span><\/h3>\n\n\n\n
        In an ENC:<\/p>\n\n\n\n
        \n
        each entity is a nautical object<\/li>\n\n\n\n
        each object has:\n
        \n
        a standardized type (e.g., DEPARE, COALNE, LNDARE)<\/li>\n\n\n\n
        a geometry<\/li>\n\n\n\n
        a list of coded attributes<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
        Examples of objects:<\/p>\n\n\n\n
        \n
        depth zones<\/li>\n\n\n\n
        navigation aids<\/li>\n\n\n\n
        isolated hazards<\/li>\n\n\n\n
        coastlines<\/li>\n\n\n\n
        restricted areas<\/li>\n<\/ul>\n\n\n\n
        👉 Unlike traditional GIS,<\/p>\n\n\n\n
        \n
        we do not start with a geometry but with a semantic object.<\/p>\n<\/blockquote>\n\n\n\n
        \n\n\n\n
        <\/span>2.2 Coded and non-explicit attributes<\/span><\/h3>\n\n\n\n
        S-57 attributes:<\/p>\n\n\n\n
        \n
        are often digitally coded<\/li>\n\n\n\n
        require correspondence tables<\/li>\n\n\n\n
        only make sense within the context of the standard<\/li>\n<\/ul>\n\n\n\n
        Example:<\/p>\n\n\n\n
        \n
        CATOBS = 3<\/li>\n\n\n\n
        WATLEV = 2<\/li>\n<\/ul>\n\n\n\n
        Without IHO documentation, these values are unreadable.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>3. A strict separation between geometry and information<\/span><\/h2>\n\n\n\n
        <\/span>3.1 Shared geometries<\/span><\/h3>\n\n\n\n
        In an ENC:<\/p>\n\n\n\n
        \n
        multiple objects can share the same geometry<\/li>\n\n\n\n
        lines and nodes are stored separately<\/li>\n\n\n\n
        topology is implicit<\/li>\n<\/ul>\n\n\n\n
        👉 This allows for:<\/p>\n\n\n\n
        \n
        high accuracy<\/li>\n\n\n\n
        efficient updating<\/li>\n<\/ul>\n\n\n\n
        👉 But it complicates:<\/p>\n\n\n\n
        \n
        direct import into a GIS<\/li>\n\n\n\n
        understanding spatial relationships<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>3.2 No embedded symbolization<\/span><\/h3>\n\n\n\n
        ENC charts do not contain their own graphic style.<\/p>\n\n\n\n
        Visual representation:<\/p>\n\n\n\n
        \n
        depends on the navigation system (ECDIS)<\/li>\n\n\n\n
        follows complex rules (S-52)<\/li>\n<\/ul>\n\n\n\n
        In QGIS:<\/p>\n\n\n\n
        \n
        styles must be recreated<\/li>\n\n\n\n
        understand which rules apply depending on the context<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>4. The concept of \u201cPurpose\u201d and scale<\/span><\/h2>\n\n\n\n
        An ENC is not universal:<\/p>\n\n\n\n
        \n
        it is produced for a specific use, called Purpose.<\/p>\n<\/blockquote>\n\n\n\n
        Examples:<\/p>\n\n\n\n
        \n
        general view<\/li>\n\n\n\n
        coastal navigation<\/li>\n\n\n\n
        port approach<\/li>\n\n\n\n
        detailed port<\/li>\n<\/ul>\n\n\n\n
        Each ENC:<\/p>\n\n\n\n
        \n
        has a target scale<\/li>\n\n\n\n
        is not intended to be used out of context<\/li>\n<\/ul>\n\n\n\n
        👉 In a GIS, displaying all ENCs without filtering produces:<\/p>\n\n\n\n
        \n
        duplicates<\/li>\n\n\n\n
        inconsistencies<\/li>\n\n\n\n
        visual conflicts<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>5. A logic designed for safety, not for analysis<\/span><\/h2>\n\n\n\n
        ENC charts are designed to:<\/p>\n\n\n\n
        \n
        avoid human error<\/li>\n\n\n\n
        ensure unambiguous reading<\/li>\n\n\n\n
        comply with priority rules<\/li>\n\n\n\n
        ensure navigational safety<\/li>\n<\/ul>\n\n\n\n
        They are not designed for:<\/p>\n\n\n\n
        \n
        free spatial queries<\/li>\n\n\n\n
        classic GIS joins<\/li>\n\n\n\n
        multi-thematic analyses<\/li>\n<\/ul>\n\n\n\n
        👉 Any GIS exploitation therefore requires:<\/p>\n\n\n\n
        \n
        restructuring<\/li>\n\n\n\n
        interpretation<\/li>\n\n\n\n
        sometimes simplification<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>6. Why a dedicated plugin is necessary in QGIS<\/span><\/h2>\n\n\n\n
        Importing an ENC \u201cbrutally\u201d into QGIS often leads to:<\/p>\n\n\n\n
        \n
        dozens of unreadable layers<\/li>\n\n\n\n
        incomprehensible fields<\/li>\n\n\n\n
        fragmented geometries<\/li>\n\n\n\n
        a loss of nautical meaning<\/li>\n<\/ul>\n\n\n\n
        A tool such as S57Manager allows you to:<\/p>\n\n\n\n
        \n
        comply with S-57 logic<\/li>\n\n\n\n
        structure data<\/li>\n\n\n\n
        make attributes usable<\/li>\n\n\n\n
        prepare for display and analysis<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>Conclusion<\/span><\/h2>\n\n\n\n
        ENC are complex by design.<\/p>\n\n\n\n
        This complexity is not a flaw:<\/p>\n\n\n\n
        \n
        it guarantees reliability<\/li>\n\n\n\n
        international consistency<\/li>\n\n\n\n
        navigation safety<\/li>\n<\/ul>\n\n\n\n
        But for the GIS world, it requires<\/p>\n\n\n\n
        \n
        appropriate tools, a basic understanding of the standard, and an approach that respects nautical logic.<\/p>\n<\/blockquote>\n\n\n\n
        👉 Understanding this complexity is the first step before:<\/p>\n\n\n\n
        \n
        importing into QGIS<\/li>\n\n\n\n
        choosing PostGIS<\/a> or GeoPackage<\/li>\n\n\n\n
        using a specialized plugin such as S57Manager<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>Import, structuring and use of official nautical charts in a robust spatial database<\/span><\/h1>\n\n\n\n
        S57Manager<\/a> is a QGIS plugin that enables the structured import, validation and visualization of ENC (S-57) nautical charts using PostGIS or GeoPackage.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>Introduction<\/span><\/h2>\n\n\n\n
        Nautical charts in S-57 format<\/strong> (ENC \u2013 Electronic Navigational Charts) are official, structured, complex datasets with rich semantics.
        While they are widely used in professional navigation systems, their direct use in a general-purpose GIS such as QGIS<\/strong> remains challenging.(->Why ENCs (S-57) are complex data<\/a>)<\/p>\n\n\n\n
        \n\n\n\n
        The S57Manager plugin<\/strong> was created to address this issue:<\/p>\n\n\n\n
        \n
        to provide a reliable, structured and reproducible solution<\/strong> for importing, storing and displaying S-57 data in QGIS, relying on modern spatial databases.<\/p>\n<\/blockquote>\n\n\n\n
        In this first article, we present S57Manager as a whole<\/strong>, then focus on the PostGIS option<\/strong>, which is particularly well suited for professional, collaborative and multi-project workflows.<\/p>\n\n\n\n
        The plugin implements the automation of the processing chain described in the following two articles:<\/p>\n\n\n\n
        ENC charts in QGIS with PostGIS (1)<\/a>
        ENC charts in QGIS with PostGIS (2)<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>1. What is S57Manager?<\/span><\/h2>\n\n\n\n
        <\/span>1.1 Plugin objectives<\/span><\/h3>\n\n\n\n
        S57Manager aims to:<\/p>\n\n\n\n
        \n
        import S-57 ENC files into QGIS<\/li>\n\n\n\n
        decode their complex structure (objects, attributes, geometries)<\/li>\n\n\n\n
        store the data in a normalized and usable way<\/li>\n\n\n\n
        facilitate visualization and filtering in QGIS<\/li>\n<\/ul>\n\n\n\n
        👉 The plugin is intended for:<\/p>\n\n\n\n
        \n
        GIS specialists<\/li>\n\n\n\n
        port authorities<\/li>\n\n\n\n
        consulting firms<\/li>\n\n\n\n
        technical services working with marine data<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>1.2 General architecture<\/span><\/h3>\n\n\n\n
        \n
        Import via GDAL \/ OGR<\/li>\n\n\n\n
        Logical decoding of S-57 objects<\/li>\n\n\n\n
        Structured storage (PostGIS or GeoPackage)<\/li>\n\n\n\n
        Controlled display in QGIS<\/li>\n\n\n\n
        ENC-specific tools (usage purpose, scales, filters)<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>2. Why PostGIS for S-57 data?<\/span><\/h2>\n\n\n\n
        <\/span>2.1 The challenges of ENC data<\/span><\/h3>\n\n\n\n
        ENCs are not simple vector layers:<\/p>\n\n\n\n
        \n
        very large number of tables<\/li>\n\n\n\n
        implicit relationships between objects<\/li>\n\n\n\n
        coded attributes<\/li>\n\n\n\n
        large data volumes<\/li>\n\n\n\n
        possible updates<\/li>\n<\/ul>\n\n\n\n
        PostGIS perfectly meets these constraints.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>2.2 Advantages of PostGIS storage<\/span><\/h3>\n\n\n\n
        With S57Manager + PostGIS<\/strong>:<\/p>\n\n\n\n
        ✔ centralized storage
        ✔ high performance on large datasets
        ✔ advanced spatial queries
        ✔ multi-user access
        ✔ controlled backups and updates
        ✔ integration into existing GIS workflows<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>3. Configuring PostGIS mode in S57Manager<\/span><\/h2>\n\n\n\n
        <\/span>3.1 Connection settings<\/span><\/h3>\n\n\n\n
        Connection settings for the Postgresql\/postgis database are configured directly in QGIS. The plugin searches for and displays the connections available in the current project:<\/p>\n\n\n\n
        $\"\"$ <\/a><\/figure>\n\n\n\n
        \n\n\n\n
        <\/span>3.2 Structure of generated tables<\/span><\/h3>\n\n\n\n
        When you click OK in the previous dialog box, the plugin checks for the existence of five schemas in the selected database and creates them if necessary:<\/p>\n\n\n\n
        $\"\"$ <\/a><\/figure>\n\n\n\n
        \n
        enc, main schema where all imported S57 files will be stored<\/li>\n\n\n\n
        linesenc,pointsenc and polysenc, temporary import schemas. They host ogr imports to enable the necessary operations on the geometries. Once the processing is complete and the final data has been copied to the enc schema, they are emptied.<\/li>\n\n\n\n
        encm, not currently used but planned for future versions.<\/li>\n<\/ul>\n\n\n\n
        The ENC schema contains all the tables from the S57 files.<\/p>\n\n\n\n
        \n
        Separation by geometry type (points: pt_, lines: li_, polygons: pl_)<\/li>\n\n\n\n
        S-57 object tables<\/li>\n\n\n\n
        Relationship tables<\/li>\n\n\n\n
        RCID identifier management<\/li>\n<\/ul>\n\n\n\n
        $\"\"$ <\/a><\/figure>\n\n\n\n
        👉 The schema is designed to be readable, documentable, and queryable.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>4. Importing an S-57 ENC into PostGIS<\/span><\/h2>\n\n\n\n
        <\/span>4.1 Launching the import<\/span><\/h3>\n\n\n\n
        $\"\"$ <\/a><\/figure>\n\n\n\n
        The plugin searches for and loads all .000 files in the directory and subdirectories and performs the following:<\/p>\n\n\n\n
        \n
        selection of S-57 files<\/li>\n\n\n\n
        progress tracking<\/li>\n\n\n\n
        display of detailed logs<\/li>\n<\/ul>\n\n\n\n
        $\"\"$ <\/a><\/figure>\n\n\n\n
        \n\n\n\n
        <\/span>4.2 Control and validation of ENC data in PostGIS<\/span><\/h2>\n\n\n\n
        Importing ENC data into PostGIS is only a first step.
        Before any cartographic or analytical use, it is essential to carry out rigorous quality control<\/strong>.<\/p>\n\n\n\n
        As ENC data are standardized and critical for maritime safety<\/strong>, any structural or interpretative error may lead to inconsistent\u2014or even dangerous\u2014results.<\/p>\n\n\n\n
        Quality control relies on three complementary pillars:<\/p>\n\n\n\n
        \n
        verification of imported layers<\/li>\n\n\n\n
        geometric integrity<\/li>\n\n\n\n
        attribute consistency<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>4.2.1 Verification of imported layers<\/span><\/h3>\n\n\n\n
        After importing into PostGIS, the first check is to ensure that all expected object classes are present<\/strong>.<\/p>\n\n\n\n
        <\/span>Presence and completeness<\/strong><\/span><\/h4>\n\n\n\n
        Depending on the ENC content, one should notably find:<\/p>\n\n\n\n
        \n
        hydrographic objects (depth areas, soundings)<\/li>\n\n\n\n
        coastline and land areas<\/li>\n\n\n\n
        aids to navigation<\/li>\n\n\n\n
        hazards and obstructions<\/li>\n\n\n\n
        regulated or special areas<\/li>\n<\/ul>\n\n\n\n
        The absence of a layer may indicate:<\/p>\n\n\n\n
        \n
        an error during import<\/li>\n\n\n\n
        unintended filtering<\/li>\n\n\n\n
        incompatibility with the S-57 version used<\/li>\n<\/ul>\n\n\n\n
        <\/span>Logical organization<\/strong><\/span><\/h4>\n\n\n\n
        In PostGIS, data can be organized:<\/p>\n\n\n\n
        \n
        by schema (hydrography, navigation, regulations, etc.)<\/li>\n\n\n\n
        by geometry type (points, lines, polygons)<\/li>\n\n\n\n
        by S-57 object class<\/li>\n<\/ul>\n\n\n\n
        Clear structuring facilitates:<\/p>\n\n\n\n
        \n
        maintenance<\/li>\n\n\n\n
        understanding by third parties<\/li>\n\n\n\n
        automation of processing<\/li>\n<\/ul>\n\n\n\n
        👉 S57Manager<\/strong> helps maintain a readable organization compatible with GIS best practices.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>4.2.2 Geometric integrity<\/span><\/h3>\n\n\n\n
        ENC data rely on shared and topological geometries<\/strong>, which makes their import more delicate than a classic vector dataset.<\/p>\n\n\n\n
        <\/span>Valid geometries<\/strong><\/span><\/h4>\n\n\n\n
        It is essential to verify that:<\/p>\n\n\n\n
        \n
        polygons are closed<\/li>\n\n\n\n
        geometries are not self-intersecting<\/li>\n\n\n\n
        lines are not degenerated<\/li>\n\n\n\n
        points are not unnecessarily duplicated<\/li>\n<\/ul>\n\n\n\n
        In PostGIS, validation functions make it possible to:<\/p>\n\n\n\n
        \n
        detect invalid geometries<\/li>\n\n\n\n
        correct them if necessary<\/li>\n\n\n\n
        document anomalies<\/li>\n<\/ul>\n\n\n\n
        An invalid geometry may:<\/p>\n\n\n\n
        \n
        prevent display in QGIS<\/li>\n\n\n\n
        distort area or distance calculations<\/li>\n\n\n\n
        block subsequent spatial operations<\/li>\n<\/ul>\n\n\n\n
        <\/span>Topological consistency<\/strong><\/span><\/h4>\n\n\n\n
        Even if S-57 topology is not always preserved exactly after import, certain rules must remain consistent:<\/p>\n\n\n\n
        \n
        a depth area must not arbitrarily overlap a land area<\/li>\n\n\n\n
        the coastline must correspond to the land\/sea boundary<\/li>\n\n\n\n
        point objects must be located in logically compatible areas<\/li>\n<\/ul>\n\n\n\n
        These checks are particularly important during data aggregation or generalization.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>4.2.3 Attribute consistency<\/span><\/h3>\n\n\n\n
        S-57 attributes are both rich and constrained<\/strong>.
        They must be checked with the same level of care as geometries.<\/p>\n\n\n\n
        <\/span>Presence of essential attributes<\/strong><\/span><\/h4>\n\n\n\n
        Each object class includes attributes that are:<\/p>\n\n\n\n
        \n
        mandatory<\/li>\n\n\n\n
        conditional<\/li>\n\n\n\n
        optional<\/li>\n<\/ul>\n\n\n\n
        The absence of a key attribute may indicate:<\/p>\n\n\n\n
        \n
        an import error<\/li>\n\n\n\n
        misinterpretation of the S-57 schema<\/li>\n\n\n\n
        information loss during conversion<\/li>\n<\/ul>\n\n\n\n
        <\/span>Coded values and domains<\/strong><\/span><\/h4>\n\n\n\n
        Many attributes use:<\/p>\n\n\n\n
        \n
        coded numeric values<\/li>\n\n\n\n
        closed lists defined by the IHO<\/li>\n<\/ul>\n\n\n\n
        It is crucial to verify that:<\/p>\n\n\n\n
        \n
        values fall within authorized domains<\/li>\n\n\n\n
        codes match their intended meaning<\/li>\n\n\n\n
        fields do not contain aberrant values<\/li>\n<\/ul>\n\n\n\n
        An incorrect value can affect:<\/p>\n\n\n\n
        \n
        cartographic interpretation<\/li>\n\n\n\n
        object hierarchy<\/li>\n\n\n\n
        display or priority rules<\/li>\n<\/ul>\n\n\n\n
        <\/span>Semantic consistency<\/strong><\/span><\/h4>\n\n\n\n
        Finally, some checks are a matter of nautical common sense<\/strong>:<\/p>\n\n\n\n
        \n
        a hazard cannot be located on land<\/li>\n\n\n\n
        an aid to navigation must be consistent with its environment<\/li>\n\n\n\n
        a regulated area must have a compatible type and category<\/li>\n<\/ul>\n\n\n\n
        These cross-checks are often facilitated by:<\/p>\n\n\n\n
        \n
        PostGIS spatial queries<\/li>\n\n\n\n
        joins between layers<\/li>\n\n\n\n
        visualization in QGIS<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        <\/span>Why these checks are essential<\/span><\/h2>\n\n\n\n
        PostGIS offers exceptional analytical power, but it does not automatically correct semantic or normative inconsistencies<\/strong>.<\/p>\n\n\n\n
        In the case of ENC data:<\/p>\n\n\n\n
        \n
        data quality directly conditions reliability<\/li>\n\n\n\n
        errors may propagate through analyses<\/li>\n\n\n\n
        an initial quality check prevents downstream issues<\/li>\n<\/ul>\n\n\n\n
        👉 S57Manager<\/strong> follows this approach:
        not merely importing data, but importing it cleanly<\/strong>, with respect for both the structure and the nautical meaning of the data.<\/p>\n\n\n\n
        \n\n\n\n
        <\/span>5. Use in QGIS<\/span><\/h2>\n\n\n\n
        <\/span>5.1 Display by object families<\/span><\/h3>\n\n\n\n
        Given the richness and density of ENC data, displaying all layers simultaneously quickly results in an unreadable map.
        A recommended practice is to organize the display by object families<\/strong>, i.e. by major functional groups sharing a common nautical logic.<\/p>\n\n\n\n
        For example:<\/p>\n\n\n\n
        \n
        hydrographic objects (depth areas, soundings, isobaths),<\/li>\n\n\n\n
        coastline elements and land surfaces,<\/li>\n\n\n\n
        aids to navigation (buoys, lights, beacons),<\/li>\n\n\n\n
        hazards and obstructions,<\/li>\n\n\n\n
        regulated or special areas.<\/li>\n<\/ul>\n\n\n\n
        In QGIS, this organization can be implemented through:<\/p>\n\n\n\n
        \n
        layer groups,<\/li>\n\n\n\n
        shared styles by family,<\/li>\n\n\n\n
        conditional display filters,<\/li>\n\n\n\n
        or distinct schemas on the PostGIS side.<\/li>\n<\/ul>\n\n\n\n
        Displaying data by family offers several advantages:<\/p>\n\n\n\n
        \n
        it facilitates progressive map reading by revealing information through logical layers;<\/li>\n\n\n\n
        it allows quick visual checks of data consistency (missing objects, positional anomalies);<\/li>\n\n\n\n
        it prepares the ground for advanced styling, close to S-52 rules, without attempting to reproduce them fully.<\/li>\n<\/ul>\n\n\n\n
        👉 S57Manager<\/strong> follows this logic by preserving a structure compatible with ENC object families, allowing users to build readable, scalable QGIS projects adapted to their needs.<\/p>\n\n\n\n
        $\"\"$ <\/a><\/figure>\n\n\n\n
        \n\n\n\n
        <\/span>5.2 Filtering displayed layers<\/span><\/h3>\n\n\n\n
        The \u201cENC Tools\u201d<\/strong> menu allows filtering of displayed layers according to usage and\/or display scale<\/strong>.<\/p>\n\n\n\n
        <\/span>Filtering by purpose<\/span><\/h4>\n\n\n\n
        ENCs are designed for very different uses, ranging from route planning to coastal or port navigation.
        This diversity is formalized by the concept of purpose<\/strong>, which corresponds to the cartographic usage level of the data (general, coastal, approach, harbour, etc.).<\/p>\n\n\n\n
        Applying a purpose-based filter makes it possible to display only objects relevant to a given context, avoiding visual clutter and unnecessary information at the considered scale.
        An object that is valid in a general navigation ENC may become inappropriate\u2014or even misleading\u2014in a harbour context, and vice versa.<\/p>\n\n\n\n
        In a PostGIS \/ QGIS environment, this filtering can be implemented:<\/p>\n\n\n\n
        \n
        via attributes inherited from the ENC import,<\/li>\n\n\n\n
        through SQL views dedicated to each purpose,<\/li>\n\n\n\n
        or via scale-dependent visibility rules.<\/li>\n<\/ul>\n\n\n\n
        The benefits are multiple:<\/p>\n\n\n\n
        \n
        improved cartographic readability, adapted to the expected level of detail;<\/li>\n\n\n\n
        consistency between scale, usage and content;<\/li>\n\n\n\n
        a solid basis for differentiated styles according to navigation context.<\/li>\n<\/ul>\n\n\n\n
        👉 S57Manager<\/strong> facilitates this filtering by preserving purpose information during import and enabling layers and queries to be structured according to targeted uses, without imposing rigid symbolization.<\/p>\n\n\n\n
        $\"\"$ <\/a><\/figure>\n\n\n\n
        <\/span>Display scale<\/span><\/h4>\n\n\n\n
        In ENCs, scale is not a simple cartographic parameter: it conditions the very validity of the displayed information<\/strong>.
        Each object is designed to be interpreted within a given scale range, closely linked to its purpose and level of generalization.<\/p>\n\n\n\n
        Displaying an object outside its scale domain may lead to:<\/p>\n\n\n\n
        \n
        loss of readability (excessive object density),<\/li>\n\n\n\n
        false precision (over-detailed objects at small scale),<\/li>\n\n\n\n
        or even misinterpretation by the end user.<\/li>\n<\/ul>\n\n\n\n
        Managing display scale therefore makes it possible to:<\/p>\n\n\n\n
        \n
        automatically adapt layer visibility to zoom level,<\/li>\n\n\n\n
        preserve consistency between geometric detail and usage context,<\/li>\n\n\n\n
        bring QGIS behaviour closer to that of an ECDIS, while retaining GIS flexibility.<\/li>\n<\/ul>\n\n\n\n
        In a PostGIS or GeoPackage architecture, this logic can be implemented through:<\/p>\n\n\n\n
        \n
        scale ranges defined at layer level,<\/li>\n\n\n\n
        views or queries filtering objects according to the current scale,<\/li>\n\n\n\n
        or a combined purpose\/scale approach for finer control.<\/li>\n<\/ul>\n\n\n\n
        👉 S57Manager<\/strong> provides tools to define and adjust minimum and maximum display scales for selected layers, enabling progressive, readable cartography consistent with the ENC philosophy, without unnecessarily complicating the QGIS project.<\/p>\n\n\n\n
        \n\n\n\n<\/span>5.3 Custom symbolization<\/span><\/h3>\n\n\n\n
        When S-57 layers are loaded directly, they appear as points, lines and polygons with default symbology, far removed from a nautical chart.
        S57Manager<\/strong> makes it possible to directly apply an ECDIS-like symbolization<\/strong>.<\/p>\n\n\n\n
        $\"\"$ <\/a><\/figure>\n\n\n\n
        This requires two steps:<\/p>\n\n\n\n
        \n
        Installing the required SVG symbols<\/strong>
        These symbols are included in the plugin and are installed in the user profile by clicking the \u201cInstall SVG symbol library\u201d<\/em> button in the S57 Options dialog.<\/li>\n\n\n\n
        Installing default symbolization in the PostGIS database<\/strong>
        The \u201cInstall default S57 symbology\u201d<\/em> button checks whether the layer_styles<\/code> table exists in the public<\/code> schema of the PostGIS database.\n\nIf it does not exist, it is created and the default symbology for the 260 S-57 layers is added.<\/li>\n\n\n\nIf it already exists, the default symbologies for the 260 layers are added to the existing ones.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<\/a><\/figure>\n\n\n\n \n\n\n\n<\/span>Conclusion<\/span><\/h2>\n\n\n\nThe PostGIS mode of S57Manager<\/strong> provides a robust solution for the long-term integration of ENC data into a professional GIS. It is clearly aimed at environments where durability, performance and collaboration are essential criteria.<\/p>\n\n\n\n \n\n\n\n<\/span>Geopackage : A lightweight, autonomous and portable solution for marine data<\/span><\/h1>\n\n\n\n \n\n\n\n<\/span>Introduction<\/span><\/h2>\n\n\n\nWhile PostGIS<\/strong> is ideal for structured, collaborative and multi-project professional environments, it is not always necessary \u2014 nor desirable \u2014 for all use cases.<\/p>\n\n\n\n For:<\/p>\n\n\n\n\none-off or exploratory studies,<\/li>\n\n\n\n embedded or mobile projects,<\/li>\n\n\n\n data exchange between organizations,<\/li>\n\n\n\nor offline usage,<\/li>\n<\/ul>\n\n\n\nthe GeoPackage (GPKG)<\/strong> format represents a simple, robust and standardized alternative.<\/p>\n\n\n\nIn this article, we explore the GeoPackage mode of S57Manager<\/a><\/strong>, designed to offer the same level of structuring, control and data exploitation<\/strong> as the PostGIS mode, without any server dependency<\/strong>.<\/p>\n\n\n\n 👉 The plugin automates the processing chain described in the following articles:<\/p>\n\n\n\n \nENC charts in GeoPackage with QGIS \u2013 Final version: Part 1<\/em><\/li>\n\n\n\nENC charts in GeoPackage with QGIS \u2013 Final version: Part 2<\/em><\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>1. Why choose GeoPackage?<\/span><\/h2>\n\n\n\nGeoPackage is a widely adopted OGC standard in the GIS ecosystem.<\/p>\n\n\n\n Its key advantages include:<\/p>\n\n\n\n\nsingle-file storage,<\/li>\n\n\n\n OGC standard format,<\/li>\n\n\n\n portability (USB drive, external disk, cloud),<\/li>\n\n\n\n versioning capabilities,<\/li>\n\n\n\ncompatibility with QGIS, ArcGIS and GDAL\/OGR<\/strong>.<\/li>\n<\/ul>\n\n\n\n👉 It is particularly suitable for:<\/p>\n\n\n\n\nengineering consultancies,<\/li>\n\n\n\n field or onboard missions,<\/li>\n\n\n\n inter-agency data sharing,<\/li>\n\n\n\nlow-connectivity or offline contexts.<\/li>\n<\/ul>\n\n\n\n👉 In S57Manager, GeoPackage is not a degraded mode<\/strong>: it follows the same structural principles as PostGIS<\/strong>, adapted to file-based storage.<\/p>\n\n\n\n \n\n\n\n<\/span>2. Configuring GeoPackage mode<\/span><\/h2>\n\n\n\n<\/span>2.1 Creating or selecting a GeoPackage<\/span><\/h3>\n\n\n\nThe user defines the working directory used for GeoPackages.<\/p>\n\n\n\n <\/a><\/figure>\n\n\n\nThe plugin uses four GPKG files<\/strong>:<\/p>\n\n\n\n \nenc.gpkg<\/code> \u2192 main file containing the final result (up to ~260 S-57 tables)<\/li>\n\n\n\n three temporary import GeoPackages:\n\npointsENC.gpkg<\/code><\/li>\n\n\n\n linesENC.gpkg<\/code><\/li>\n\n\n\n polysENC.gpkg<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\nThese files are used as intermediate steps during the import process.<\/p>\n\n\n\n Plugin behavior:<\/p>\n\n\n\n \nGeoPackages are automatically created<\/strong> if they do not exist;<\/li>\n\n\n\n existing files are reused<\/strong>;<\/li>\n\n\n\n the enc.gpkg<\/code> file is progressively enriched<\/strong> with each import.<\/li>\n<\/ul>\n\n\n\n👉 As with PostGIS mode, the internal structure is fully managed by S57Manager<\/strong>, ensuring consistency and reproducibility.<\/p>\n\n\n\n \n\n\n\n<\/span>2.2 Layer organization<\/span><\/h3>\n\n\n\nData organization follows the same principles as in PostGIS:<\/p>\n\n\n\n \none table per S-57 object class<\/strong>,<\/li>\n\n\n\n clear separation between point, line and polygon geometries,<\/li>\n\n\n\n consistent naming and attributes across both modes.<\/li>\n<\/ul>\n\n\n\nThis consistency enables:<\/p>\n\n\n\n \nsmooth migration between GeoPackage and PostGIS,<\/li>\n\n\n\n easier interpretation by third parties,<\/li>\n\n\n\n reuse of styles and workflows.<\/li>\n<\/ul>\n\n\n\n👉 A QGIS project built on GeoPackage can later be migrated to PostGIS<\/strong> without changing layer logic.<\/p>\n\n\n\n \n\n\n\n<\/span>3. ENC \u2192 GeoPackage import<\/span><\/h2>\n\n\n\nENC import into GeoPackage relies on the same processing chain as PostGIS mode<\/strong>:<\/p>\n\n\n\n \ndecoding via GDAL \/ OGR,<\/li>\n\n\n\n logical interpretation of S-57 objects,<\/li>\n\n\n\n geometry-based separation,<\/li>\n\n\n\n creation of normalized final tables.<\/li>\n<\/ul>\n\n\n\nThe difference lies only in the storage backend.<\/p>\n\n\n\n The plugin guarantees:<\/p>\n\n\n\n \nidentical logging,<\/li>\n\n\n\n the same validation checks,<\/li>\n\n\n\n no functional loss compared to PostGIS.<\/li>\n<\/ul>\n\n\n\n👉 Choosing GeoPackage is therefore an architectural choice<\/strong>, not a compromise on data quality.<\/p>\n\n\n\n \n\n\n\n<\/span>4. Data control and consistency in GeoPackage<\/span><\/h2>\n\n\n\nEven with file-based storage, ENC data remains:<\/p>\n\n\n\n \nstandardized,<\/li>\n\n\n\n semantically rich,<\/li>\n\n\n\n critical from a navigational perspective.<\/li>\n<\/ul>\n\n\n\nThe data checks described in the PostGIS article therefore remain fully applicable:<\/p>\n\n\n\n \npresence of expected layers,<\/li>\n\n\n\n geometry validity,<\/li>\n\n\n\n consistency of coded attributes,<\/li>\n\n\n\n overall nautical logic.<\/li>\n<\/ul>\n\n\n\n👉 QGIS allows most of these checks directly on GeoPackage through:<\/p>\n\n\n\n \ngeometry validation tools,<\/li>\n\n\n\n expressions and filters,<\/li>\n\n\n\n internal SQL queries.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>5. Working with ENC layers locally in QGIS<\/span><\/h2>\n\n\n\nWorking in QGIS is identical to the PostGIS workflow<\/strong>:<\/p>\n\n\n\n \ndisplay by ENC object families<\/strong>,<\/li>\n\n\n\n filtering by purpose<\/strong>,<\/li>\n\n\n\n scale-dependent rendering,<\/li>\n\n\n\n nautical-oriented styles.<\/li>\n<\/ul>\n\n\n\nPerformance is generally very good for:<\/p>\n\n\n\n \nlimited spatial extents,<\/li>\n\n\n\n single-user workflows,<\/li>\n\n\n\n embedded projects.<\/li>\n<\/ul>\n\n\n\n👉 GeoPackage enables clear, progressive and coherent cartography<\/strong>, without requiring server infrastructure.<\/p>\n\n\n\n \n\n\n\n<\/span>6. PostGIS \/ GeoPackage comparison<\/span><\/h2>\n\n\n\nCriterion<\/th> PostGIS<\/th> GeoPackage<\/th><\/tr><\/thead> Multi-user<\/td> ✅<\/td> ❌<\/td><\/tr> Large datasets<\/td> ✅<\/td> ⚠️<\/td><\/tr> Portability<\/td> ❌<\/td> ✅<\/td><\/tr> Simplicity<\/td> ⚠️<\/td> ✅<\/td><\/tr> Deployment<\/td> Server<\/td> File<\/td><\/tr> Offline use<\/td> ❌<\/td> ✅<\/td><\/tr> Embedded projects<\/td> ❌<\/td> ✅<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n👉 The two approaches do not compete \u2014 they complement each other<\/strong>.<\/p>\n\n\n\n \n\n\n\n<\/span>Conclusion<\/span><\/h2>\n\n\n\nThe GeoPackage mode of S57Manager<\/strong> makes ENC data accessible without heavy infrastructure<\/strong>, while preserving:<\/p>\n\n\n\n \nENC semantic richness,<\/li>\n\n\n\n rigorous data structuring,<\/li>\n\n\n\n consistent exploitation in QGIS.<\/li>\n<\/ul>\n\n\n\nIt naturally complements the PostGIS approach<\/strong>, making S57Manager<\/strong> a versatile tool<\/strong> adaptable to:<\/p>\n\n\n\n \ninstitutional environments,<\/li>\n\n\n\n lightweight, mobile or exploratory use cases.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>Import NOAA ENC nautical charts directly into QGIS with S57Manager<\/span><\/h1>\n\n\n\nENC (Electronic Navigational Charts) are now the standard for digital marine cartography.<\/p>\n\n\n\n With the latest update to the S57Manager plugin<\/a>, QGIS now features a module dedicated to the official NOAA ENC catalog, allowing users to easily search, filter, and import ENC cells directly from the QGIS interface.<\/p>\n\n\n\n This new tool greatly simplifies the work of users working with marine, port, or coastal data.<\/p>\n\n\n\n \n\n\n\n<\/span>🔎 The NOAA ENC catalog: what is it?<\/span><\/h2>\n\n\n\nThe NOAA (National Oceanic and Atmospheric Administration)<\/strong> provides an official catalog containing several thousand ENC cells covering:<\/p>\n\n\n\n\nU.S. coastlines,<\/li>\n\n\n\n ports and harbors,<\/li>\n\n\n\n estuaries,<\/li>\n\n\n\ninland waterways.<\/li>\n<\/ul>\n\n\n\nEach ENC cell is described by:<\/p>\n\n\n\n\na unique identifier (e.g. US5NYCDF<\/em>),<\/li>\n\n\n\n a purpose<\/strong> (usage level, from overview to very high detail),<\/li>\n\n\n\n a nominal scale,<\/li>\n\n\n\n a precise geographic extent,<\/li>\n\n\n\nan official download URL.<\/li>\n<\/ul>\n\n\n\nUntil now, accessing this catalog required external tools or manual searches. The NOAA module in S57Manager<\/strong> completely changes this workflow.<\/p>\n\n\n\n \n\n\n\n<\/span>🧩 A NOAA module fully integrated into S57Manager<\/span><\/h2>\n\n\n\nThe new NOAA module is fully integrated into S57Manager and follows its core philosophy:<\/p>\n\n\n\n\ncentralize all ENC-related tools in a single, coherent and efficient interface.<\/strong><\/p>\n\n\n\n<\/a><\/figure>\n<\/blockquote>\n\n\n\nFrom QGIS, users can now:<\/p>\n\n\n\n\nload the official NOAA catalog (XML),<\/li>\n\n\n\n browse the complete list of available ENC cells,<\/li>\n\n\n\n dynamically filter the catalog,<\/li>\n\n\n\nimport only the cells that are truly relevant.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>🎛️ Filters designed for real cartographic workflows<\/span><\/h2>\n\n\n\nThe NOAA module provides several combinable filters<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/span>🔹 Filtering by purpose<\/span><\/h3>\n\n\n\nNOAA ENC cells are classified by purpose (1 to 6):<\/p>\n\n\n\n Purpose<\/th> Usage<\/th><\/tr><\/thead> 1<\/td> Overview<\/td><\/tr> 2<\/td> General<\/td><\/tr> 3<\/td> Coastal<\/td><\/tr> 4<\/td> Approach<\/td><\/tr> 5<\/td> Harbor<\/td><\/tr> 6<\/td> Berthing \/ Detail<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nUsers can precisely select the desired usage levels.<\/p>\n\n\n\n \n\n\n\n<\/span>🔹 Filtering by scale<\/span><\/h3>\n\n\n\nEach ENC cell has a nominal scale (e.g. 1:10,000; 1:50,000). The module allows defining minimum and maximum scales to avoid loading:<\/p>\n\n\n\n \noverly generalized data,<\/li>\n\n\n\n or excessively detailed data.<\/li>\n<\/ul>\n\n\n\n💡 Tip:<\/strong> Purpose 5 and 6 cells typically use very fine scales (\u2248 1:2,000 to 1:12,000). To display them correctly, it is recommended to set the minimum display scale around 1:1,500<\/strong>.<\/p>\n\n\n\n \n\n\n\n<\/span>🔹 Filtering by QGIS map canvas extent<\/span><\/h3>\n\n\n\nThis is one of the strongest features of the module.<\/p>\n\n\n\n Users can choose to list only ENC cells that intersect the current QGIS map canvas extent<\/strong>.<\/p>\n\n\n\n Workflow:<\/p>\n\n\n\n \nzoom to your area of interest,<\/li>\n\n\n\n activate the extent filter,<\/li>\n\n\n\n only relevant ENC cells are listed.<\/li>\n<\/ul>\n\n\n\nTechnically, this relies on:<\/p>\n\n\n\n \nNOAA extents stored in EPSG:4326<\/a><\/strong>,<\/li>\n\n\n\n automatic reprojection to the current QGIS CRS.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>⬇️ Importing a NOAA ENC cell in just a few clicks<\/span><\/h2>\n\n\n\n<\/a><\/figure>\n\n\n\nOnce a cell is selected:<\/p>\n\n\n\n\nthe ENC file is downloaded from the official NOAA URL;<\/li>\n\n\n\n it is validated and processed by the S57Manager S-57 workflow;<\/li>\n\n\n\n layers are imported into the configured GeoPackage or PostGIS<\/strong> database;<\/li>\n\n\n\nstandard S57Manager organization and symbology are automatically applied.<\/li>\n<\/ul>\n\n\n\nNo manual handling is required.<\/p>\n\n\n\n \n\n\n\n<\/span>🌍 Multilingual and fully integrated in QGIS<\/span><\/h2>\n\n\n\nLike the rest of S57Manager, the NOAA module is:<\/p>\n\n\n\n\nfully multilingual (FR \/ EN \/ ES \/ PT<\/strong>),<\/li>\n\n\n\n compatible with recent QGIS versions (Qt6),<\/li>\n\n\n\nfully consistent with other ENC tools in the plugin.<\/li>\n<\/ul>\n\n\n\nIt is not a standalone tool, but a natural extension of the ENC workflow in QGIS.<\/p>\n\n\n\n \n\n\n\n<\/span>Conclusion<\/span><\/h2>\n\n\n\nWith this new NOAA module, S57Manager reaches a new milestone<\/strong>:<\/p>\n\n\n\n\ndirect access to the official ENC catalog,<\/li>\n\n\n\n precise data selection,<\/li>\n\n\n\n fast and controlled import,<\/li>\n\n\n\nseamless integration into QGIS.<\/li>\n<\/ul>\n\n\n\nWhether you work on:<\/p>\n\n\n\n \nport cartography,<\/li>\n\n\n\n coastal analysis,<\/li>\n\n\n\n inland waterway management,<\/li>\n\n\n\n or institutional marine data,<\/li>\n<\/ul>\n\n\n\nthis module provides a real productivity gain and better control over ENC data.<\/p>\n\n\n\n \n\n\n\n<\/span>Exploring ENC Data Before Import: The NOAA Catalogue at the Service of S57Manager<\/span><\/h1>\n\n\n\nWorking with ENC (S-57) data presents a very specific challenge: their richness and complexity make any \u201cblind\u201d approach inefficient. Even before discussing data import or structuring in QGIS, a fundamental question arises: which charts should be loaded, and why choose these rather than others?<\/strong><\/p>\n\n\n\n This is precisely where the NOAA ENC catalogue<\/strong> comes into play \u2014 a resource that is still largely underused by GIS professionals.<\/p>\n\n\n\n After presenting how to import ENC S-57 data into QGIS with S57Manager \u2014 first using PostGIS, then GeoPackage \u2014 this final article focuses on a crucial but often overlooked step: exploring and selecting the relevant ENC cells upstream of the import process, using the official NOAA ENC catalogue<\/strong>.<\/p>\n\n\n\n \n\n\n\n<\/span>ENC Data: Abundance That Complicates Choice<\/span><\/h2>\n\n\n\nUnlike conventional GIS datasets, an ENC does not correspond to a single map covering a given area. Instead, it belongs to a set of chart cells, each defined by:<\/p>\n\n\n\n \na precise geographic extent,<\/li>\n\n\n\n a nominal scale,<\/li>\n\n\n\n a cartographic usage (overview, coastal, approach, harbour, berth\u2026),<\/li>\n\n\n\n a navigation purpose.<\/li>\n<\/ul>\n\n\n\nFor the same geographic area, several ENC cells may overlap at different scales. Importing all available ENC data without prior selection quickly leads to:<\/p>\n\n\n\n \noversized databases,<\/li>\n\n\n\n unreadable QGIS projects,<\/li>\n\n\n\n degraded performance,<\/li>\n\n\n\n and above all, a loss of cartographic meaning.<\/li>\n<\/ul>\n\n\n\nBefore exploiting ENC data, it is therefore essential to understand and contextualize it<\/strong>.<\/p>\n\n\n\n \n\n\n\n<\/span>The NOAA ENC Catalogue: A Key but Raw Resource<\/span><\/h3>\n\n\n\nNOAA (National Oceanic and Atmospheric Administration) provides an official ENC catalogue, distributed as an XML file compliant with ISO standards (notably ISO 19115).<\/p>\n\n\n\n For each ENC cell, the catalogue contains:<\/p>\n\n\n\n \na unique identifier (cell_id),<\/li>\n\n\n\n a name,<\/li>\n\n\n\n a scale,<\/li>\n\n\n\n a usage \/ purpose,<\/li>\n\n\n\n a geographic extent,<\/li>\n\n\n\n an official download URL.<\/li>\n<\/ul>\n\n\n\nIn theory, all the information required for informed selection is available. In practice, however, this catalogue is difficult to exploit:<\/p>\n\n\n\n \nXML format is hard to read,<\/li>\n\n\n\n no direct spatial visualization,<\/li>\n\n\n\n consultation often limited to specialized tools or ad hoc scripts.<\/li>\n<\/ul>\n\n\n\nThe challenge is therefore clear: transform this technical catalogue into a usable GIS layer in QGIS<\/strong>.<\/p>\n\n\n\n \n\n\n\n<\/span>From XML Catalogue to a Spatial Index Layer<\/span><\/h3>\n\n\n\nOnce the NOAA catalogue is properly parsed, it becomes possible to extract the geographic extents of all ENC cells and convert them into polygons.<\/p>\n\n\n\n The result is a spatial index layer<\/strong>, typically stored in a GeoPackage, containing:<\/p>\n\n\n\n \none polygon per ENC cell,<\/li>\n\n\n\n essential attributes:\n\ncell_id<\/li>\n\n\n\n name<\/li>\n\n\n\n scale<\/li>\n\n\n\n purpose<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\nThis layer is lightweight, stable, and only needs to be generated once. It does not contain any detailed nautical geometry \u2014 only chart extents.<\/p>\n\n\n\n <\/a><\/figure>\n\n\n\n \n\n\n\n<\/span>Loading and Exploring NOAA Extents in QGIS<\/span><\/h2>\n\n\n\nOnce loaded into QGIS, this index layer becomes a highly effective exploration tool:<\/p>\n\n\n\n \ntransparent polygons to preserve background readability,<\/li>\n\n\n\n visible outlines to distinguish cells,<\/li>\n\n\n\n labels displaying the cell identifier,<\/li>\n\n\n\n easy overlay with:\n\na study area,<\/li>\n\n\n\n an existing project,<\/li>\n\n\n\n field data.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\nWithin seconds, it becomes possible to:<\/p>\n\n\n\n \nidentify which ENC cells actually cover the area of interest,<\/li>\n\n\n\n compare available scales,<\/li>\n\n\n\n understand the charting logic,<\/li>\n\n\n\n avoid unnecessary imports.<\/li>\n<\/ul>\n\n\n\nHere, QGIS fully regains its role as a spatial analysis tool<\/strong>, not just a data viewer.<\/p>\n\n\n\n \n\n\n\n<\/span>From Exploration to Import: Integration with S57Manager<\/span><\/h2>\n\n\n\nThe true value of this index layer emerges when it is connected to S57Manager<\/strong>.<\/p>\n\n\n\n Directly from QGIS, the user can:<\/p>\n\n\n\n \nvisually explore ENC extents,<\/li>\n\n\n\n select a relevant cell,<\/li>\n\n\n\n trigger the import of that cell via a QGIS action.<\/li>\n<\/ul>\n\n\n\nThis workflow enables:<\/p>\n\n\n\n \ntargeted imports,<\/li>\n\n\n\n fine control over data volume,<\/li>\n\n\n\n alignment between operational needs and loaded data,<\/li>\n\n\n\n full compatibility with both storage modes supported by S57Manager:\n\nPostGIS,<\/li>\n\n\n\n GeoPackage.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\nThe workflow shifts from \u201cimport then sort\u201d<\/strong> to \u201cunderstand, select, then import.\u201d<\/strong><\/p>\n\n\n\n \n\n\n\n<\/span>Conclusion: Bringing Intelligence Upstream<\/span><\/h2>\n\n\n\nBy exploiting the NOAA catalogue as a GIS layer, working with ENC data becomes clearer and more efficient. Instead of suffering from the complexity of S-57 data, GIS professionals regain control from the very first step: exploration, selection, and decision-making<\/strong>.<\/p>\n\n\n\n Combined with S57Manager, the NOAA catalogue is not an auxiliary tool, but the first building block of a coherent processing chain<\/strong>:<\/p>\n\n\n\n catalogue \u2192 selection \u2192 import \u2192 exploitation<\/strong><\/p>\n\n\n\n A step too often overlooked \u2014 yet essential for working confidently with complex nautical data in QGIS.<\/p>\n\n\n\n \n","protected":false},"excerpt":{"rendered":"Understanding electronic nautical charts before using them in a GIS Introduction ENC \u2013 Electronic Navigational Charts are now the global standard for professional maritime navigation. Produced by national hydrographic services, they comply with strict standards defined…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-16194","page","type-page","status-publish","hentry"],"aioseo_notices":[],"campaignId":"","jetpack_shortlink":"https:\/\/wp.me\/P6XU0A-4dc","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/pages\/16194","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=16194"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/pages\/16194\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=16194"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}