During the conversion process from S-57 to S-101 using the toolbox in ArcGIS Pro, I have a few questions:
During the conversion process, a S-101 Feature Catalogue is required. Where can I find other standard datasets, such as S-131, S-111, etc.?
I am displaying based on a downloaded “MaritimeS101project2_1.aptx” (I found a S-101 Group.lyrx in the help documentation. Where can I download it?) Is this the best way to display S-101 in Pro? Where can I get the latest version of this file at any time? Are there any other display strategies?
If I want to modify the display symbol , do I need to draw according to the <symbol><svg>...</symbol></svg> in the S101 Feature Catalogue XML document and then save it into the layer file in Pro? This is too difficult for me.
Can Maritime Server support the display of S-101?
If I need to add a feature, in addition to modifying the XML catalog, is it done by creating subtypes in the geodatabase in Pro?
thanks!
1. The converter tool is specifically targeting the S-101 standard given its broad use and breadth of features. There's no automated conversation for other S-100 based product standards at this time, but many of them are significantly smaller than S-101 and could use an ETL process to transform between schemas.
2. The “MaritimeS101project2_1.aptx” file has been deprecated due to schema changes in newer versions of S-101. The "S-101 Group.lyrx" layer file is the recommended approach to visualize S-101 data imported into an Esri Maritime schema. This file comes with the ArcGIS Pro Maritime Data Installer which can be downloaded from your MyEsri portal if you have that extension.
3. ArcGIS Pro supports SVG files if you want to modify the symbol used to render a feature.
4. Maritime Server does not support rendering S-101 at this time. Support for rendering the native S-101 file is in the roadmap for future development.
5. The support for producing S-101 using ArcGIS Maritime is driven by the S-100 Feature Catalogue: the schema is built using this XML and importing/exporting from S-101 and the geodatabase leverages this XML to perform the mapping. Adding a novel feature type would involve modifying the feature catalogue as you suspected. To introduce a new subtype that this feature will be mapped to when you import the feature catalogue, you'll also need to modify S-101FeatureClassMap.xml in ArcGISPro: <install directory>\Resources\Maritime\S-101FeatureClassMap.xml.
thanks for your reply.
2.I will download this file :S-101 Group.lyrx
4.arcgis pro can support rendering S-101? ,when I loaded the 101(eg:101C100100103.000) format to pro (ver:3.1), but it is not displayed.
5 If I want to conduct a research based on S-131, is the same approach applicable, that is, do I need to construct a configuration file similar to S-101FC_1.0.1, such as S-131fc.xml?
thanks.
I have a new question: Why is the "depth" field missing from the "soundingP" feature in S-101? how to display depth label?
2. Based on the image you attached to your previous message, it looks like you are already using the S-101 Group layer.
4. No. You cannot yet view S-101 natively in Pro or Enterprise like you can with S-57. Currently, you need to import the S-101 dataset into a geodatabase and use the S-101 Group layer file (as you have shown in the image you put in your previous comment). S-102 and S-111 can be added to ArcGIS Pro without conversion and the ability to view the S-101 datasets directly will be available in a future release.
5. You can download the S-131 feature catalogue from the IHO website referenced in my previous comment. Here is a direct link to S-131
From there you can use the Import S-100 Feature Catalogue geoprocessing tool to create the S-131 geodatabase schema. S-131 datasets are GML, and Esri does not yet support import and export of GML datasets. That will come in a future release. For now, you can create the S-131 schema using the feature catalogue and the Import S-100 Feature Catalogue tool, and you can create features in the S-131 geodatabase.
The Soundings are not labeled because they are multipoint - this is according to the specification. However, we have a task in our backlog to pull the z values out so that the soundings can be labeled individually.
Thank you, I now understand that it is a multi-point feature. There were originally 1441 records, but now there are only 11 records. then, I hope to label of water depth. I used the tool "Add Z information" to pull the Z values from the multi-point feature, but there are only 11 values, which doesn't seem right. .Can you give me a suggestion?
1. Feature Catalogues can be downloaded from the IHO Registry
https://registry.iho.int/productspec/list.do
2. The S-101 lyrx file is available in the product files download, which you can access using MyEsri. Below are instructions:
3. Modifying the symbology for S-101 using the layer file follows standard ArcGIS Pro symbology conventions - it is the same as any other feature layer in ArcGIS. You do not need to modify anything in the feature catalogue.
4. Support for natively rendering S-101 datasets in ArcGIS Server is in the roadmap. In the meantime, you can use the S-101 layer file and publish from ArcGIS Pro, similar to how you would publish feature services for other feature layers using Pro.
5. If you want to add features to the S-101 geodatabase, that is standard editing in ArcGIS Pro (using Create Features pane and Attributes pane). If you are asking how to extend the data model to include additional features beyond what is in the S-101 specification, then you need to modify the feature catalogue to add these elements. Then, when you use the Import S-100 Feature Catalogue tool, it will automatically add the additional features from the feature catalogue to the database.
thank you very much!
1.When I downloaded the latest version of the data file, I found it S-101_FC_1.2.3.xml
2. With your help, I have already downloaded this file.
3 and 4 I understood
5. I ‘m sorry ,it means extend the data model,not add feature, in the past,when I extend S-57 object,it was achieved by adding subtypes. I'm not sure if S-101 follows the same approach.
thanks again!