Contenu <\/p>\n Toggle<\/span>

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><\/ul><\/nav><\/div>\n\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 👉 In the next article, we will see how S57Manager<\/strong> enables a lighter and more autonomous approach through the use of GeoPackage<\/strong>.<\/p>\n\n\n\n \n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":" Import, structuring and use of official nautical charts in a robust spatial database S57Manager is a QGIS plugin that enables the structured import, validation and visualization of ENC (S-57) nautical charts using PostGIS or GeoPackage. Introduction…<\/p>\n","protected":false},"author":1,"featured_media":16151,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","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,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3394,1377,3931],"tags":[3965,3961,3943,3967,3963,3957,3955,3959,3939],"class_list":["post-16226","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pluigin-en","category-qgis-en","category-s57-en","tag-ecdis-gis","tag-electronic-navigational-charts","tag-enc-postgis","tag-hydrographic-data-postgis","tag-marine-gis-data","tag-nautical-chart-gis","tag-nc-charts","tag-qgis-s-57-plugin","tag-s-57-qgis"],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.sigterritoires.fr\/wp-content\/uploads\/2025\/12\/S57Manager_postgis_dislay.png?fit=2424%2C1578&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p6XU0A-4dI","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/16226","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"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=16226"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/16226\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media\/16151"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=16226"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/categories?post=16226"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/tags?post=16226"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}