Latest Contributions by GeoffreyGomez

Hi Gabit, I believe you should be looking at the Mapping and Charting solutions for Desktop. The Maritime Charting solution interacts with the NIS via ArcGIS Desktop clients. Here is a link to the Administrators Guide Book. Geodatabases and the ArcGIS for Maritime: Charting products—Help | ArcGIS for Desktop Hope this helps! Geoff ... View more

John, Thank you for the added information. You are correct the AML export should properly reference the listing of NATO codes. At 10.1 we altered the way we use metadata and write out the header information, since then there haven't been as many AML users on the newer releases as ENC so it most likely slipped by. I will reproduce this issue and log a bug to fix the problem. Again thank you for bringing this to my attention. Regards, Geoff ... View more

Bingo!! Thanks Geoff, duplicating the AU entry to AS gave the correct Producer Code! Awesome! Glad it worked. Can you do a favor by clicking the green check mark to indicate that it has been answered. Summary: Agency value assigned to features and metadata for a given product is being dropped upon export. A little digging uncovered that it is not contained in the product_config.xml which is used to map the characters to a valid code upon export. Solution: Make sure that the product_config.xml file in the install location possesses a reference to the agency code being used. If it doesn't have an entry, add one to ensure the string is mapped to the metadata header upon export of the S-57 file. All client machines will need to have the updated product_config.xml since it is a local configuration file and not centrally managed in the Product Library. As an aside: We maintain that list of agencies based on the IHO registry, if you have a value you would like to use and have captured in the COTS software, make sure to register with IHO. G. ... View more

Hi John, I will be happy to see if I can provide some help. I have a few questions first: I am just curious what version are you working with? Are you using the solution as Enterprise or Desktop? When you generated the product did you input the proper producing agency in the metadata form? When exporting, I believe the default agency code is pulled from the initial metadata record made during the new product wizard. When exporting a new edition, you should be able to update it to the correct one and have it exported accordingly. Is this in line with what you see? I look forward to hearing more, Geoff ... View more

Hi Alec, I wonder if it would be possible for you to provide me with a SDE Intercept log to see if we can get more information about why your process is failing. I regularly use a number of environments without issue, so hopefully we can identify what the problem you are encountering relates to. Can you please run the new product wizard after establishing the SDEINTERCEPT following the steps below? 1. Save and stop any ArcGIS edit sessions 2. Close all ArcGIS applications on the client machine 3. Right click on My Computer 4. Select Properties 5. Go to Advanced system settings 6. Click Environment Variables 7. Under System variables, add the following environment variables Variable name:      sdeintercept Variable value:      crwtf sdeinterceptloc:     C:\temp\sde_client sdeverbose: TRUE (Note that the C:\temp folder must already exist on the client computer)                                                                                              8. Click OK to exit the Environmental Variables dialog 9. Click OK to exit the System Properties dialog 10. Reproduce the error using ArcGIS for Desktop 11. Copy the direct connect log (C:\users\<user>\AppData\Local\Temp\sdedc_SQLServer.log) to the C:\temp directory 12. Send zipped sde_client files created in C:\temp along with the sdedc_SQLServer.log 13. Remove the environment variables created above from the client machine. The PMErrors.xml found in your %appdata% path is also helpful! Regards, Geoff ... View more

Hi Alec, Have you tried the same workflow using an english client/settings? I noticed that some of the windows display with chinese text. I am curious to know if there is a problem when executing the "SELECT from" statements based on the error you reported missing expression. Regards, Geoff ... View more

Hi Alec, I will be looking into this and determining how to best help you. One thing that stood out was that the CKB_FILE that is being complained about belonged to SDE.CKB_FILE (Master Instance Repository Administrator) when it should belong to PL user (Data Owner) in a separate user schema. I am not sure if you followed the guidebook for setting up the enterprise environment in Oracle but here is a link to the introduction to see if that helps:http://resources.arcgis.com/en/help/main/10.1/0106/01060000038n000000.htm I am not a DBA by any means, but hope by pointing out some references I can help get you started again. Regards, Geoff ... View more

Here are some questions remaining : 1. From the description in guide book, all tables should be versioned except ELM, UCE.... and Pcat_NIS,Pcat_ENC??      Pcat_NIS "table" doesn't exist, and there might be some mistake in the guide book. 2. Should the Pcat_NIS, Pcat_ENC  "feature class" be versioned also? 3. After versioning finished, do i have to do any process of archiving?     In the first thread i post, there is also a difference between the two guide page, and the difference is about "archiving" Hi, I wish to go through your questions one by one to make sure that I provide you with enough information for each. Before I do, can you tell me the version of the software are you working with? My assumption is that you are not on the 10.1 release as I am certain the sample PL (GDB and XML) contains the PCat_NIS_AOI feature class. I will reference the second help topic you provided and I confirmed was accurate in the last post. http://resources.arcgis.com/en/help/main/10.1/#/Configuring_the_nautical_product_library_geodatabase/010600000383000000/ 1. From the description in guide book, all tables should be versioned except ELM, UCE.... and Pcat_NIS,Pcat_ENC??      Pcat_NIS "table" doesn't exist, and there might be some mistake in the guide book. Based on the contents of the PL provided out of the box at 10.1, the instructions intend to aide with selecting all of the tables and version them in one step. As a result, the items listed in step 2 of the topic should be excluded from your selection. You can do this in the contents portion of ArcCatalog using the shift and ctrl keys to narrow the selection. [ATTACH=CONFIG]20409[/ATTACH] 2. Should the Pcat_NIS, Pcat_ENC  "feature class" be versioned also? Yes, in step 5 of the topic it says to select the three AOI feature classes (PCat_ENC_AOI, PCat_CHART_AOI and PCAT_NIS_AOI) and version them. The reason behind doing this in two steps is because you cannot register the tables and feature classes at the same time. 3. After versioning finished, do i have to do any process of archiving?     In the first thread i post, there is also a difference between the two guide page, and the difference is about "archiving" No, at 10.1 you do not need to archive the items you registered as versioned. This is old guidance and will be corrected based on your input. Again thank you for pointing this out. Please let me know if this helps you. I look forward to your response about the software version you are on. Also depending on what you are trying to accomplish, you may be able to use the sample PL as a file GDB for evaluation purposes. This may simplify your effort. Thanks! Geoff ... View more

First, thank you for bringing this to our attention. The second topic you provided the link for has been updated recently and should be used as guidance for setting up an Enterprise Product Library. (version all tables with the exception of the ELM and UCE tables) We will take action to update the other topics to ensure they are consistent. I hope this helps you. Please let me know if you have any further questions related to setting up your Product Library. Regards, Geoff ... View more

Martin, There are a couple of things at play here that should be considered and may help you determine the best path forward. Reserved Subtype values: Your suggestion to set aside some number range to avoid any potential conflicts (reuse of a subtype value by COTS) down the road is a really good thought. I don�??t wish to dictate what that range should be, but seems like the 500-600 range you suggested provides ample spacing to avoid reuse. I am not sure how to formalize this convention, but it would help if both the solution team and other users were aware of this going forward. Perhaps we can look for a place to present this within help or the online blog. Determining where to add the new subtype: What is the new subtype depicting and is there a natural place for it within the COTS data model? I agree with your initial mapping of the new subtype to the RegulatedAreasAndLimitsL feature class since the area EXEZNE features are stored in the RegulatedAreasAndLimitsA feature class and all the attributes are present. This brings us to the next question. What attributes do you wish to encode for your new subtype? Here is where your goals for this new subtype dictate the decision. If you wish to encode all the attributes needed to generate the EXEZNE area features within the new linear subtype then you have two options: Add the new subtype to the RegulatedAreasAndLimitsL feature class. You will need to configure field configurations for just the new subtype since the feature class already has all the attribute fields needed for EXEZNE features. Add the new subtype and all the required attributes to the UserDefinedFeaturesL feature class. In addition you will need to set field configurations for both the new subtype and any existing subtypes(to mask the new fields). Wherever you decide to store the new subtype you may wish to indicate that the features within this subtype are to exist only in the NIS. You can do so by setting the NIS_PRODUCTS value to 999 (none). This will keep the features from being sent down to the product databases based on arguments in the default extraction filter. I imagine this would be the desired approach with the example you provided EXEZNE (line) features. General best practice considerations: Stick to COTS data models if at all possible When extensions to the data models must be made, consider these types of requirements prior to beginning �??live�?� production. This will remove most of the complexity of rolling out changes. Changes made prior to products existing will require the extended data model schema to be added to the product library as a new DMV (Data Model Version). This will ensure that new products have the latest schema changes and any replica that is registered will include the new subtype. Should products already exist when changes are made to the NIS schema you will need to carryout the above process as well as propagate the schema change across the replicas. For more information see the link here. I mentioned this above but wanted to reinforce it. When extending the data model for the NIS and products, field configuration settings must be updated. This will ensure the new linear EXEZNE subtype shows only the relevant attribution within feature manager. The extent of the update depends on where the subtype is added. (This is something we had to alter when you added your own user defined fields) Last but not least, the product XML ultimately controls what can be imported and exported from/to S-57. You have some flexibility on where you wish to add this new subtype, that said, you should leave the product xml's unchanged to ensure that regardless of where the features exist (NIS and/or product) you will still be exporting compliant S-57 data. Hope this helps, it is by no means a comprehensive list of instructions more of a conversation about what to consider. If you need to have a more in-depth discussion I would be glad to pull together some people to do so. Cheers! Geoff ... View more

Alexander, The answer to your question in the simplest form is, no ArcGIS Desktop does not support the reading of S-63 encrypted S-57 data. The background as to why is a little more involved. Essentially, the International Hydrographic Organization (IHO) S-63 Data Protection Scheme was conceived to impede unofficial distribution of nautical information for safety concerns and to prevent copyright infringement and data piracy; S-63 intends to protect the integrity of an S-57 ENC and to provide the mariner with a "certificate of authenticity". Is not a technical problem, is a legal problem; the IHO OEM's agreement establishes that the system (commonly an ECDIS -Electronic Chart Display and Information System used in the bridge of a ship) can't share unencrypted ENC data outside its own system, Esri as a GIS software company is not an OEM and legally banned for decryption, because our software can alter "official" data. Technically we could develop an application to decrypt S-57 ENCs, but legally it would be a breach of the OEM agreement. Esri as a member of a NGO, participates in IHO meetings and is trying to promote the use of unencrypted ENCs for non-navigational purposes. I hope this provides you with some insight. Geoff ... View more

Thank you for you forum question! The ArcGIS Maritime Charting Solution provides an INT1 style file. More importantly the solution includes the logic to apply the symbology to features according to the INT1 specification based on a rich set of criteria. If you would like to discuss further and can provide some more background we may be able to provide you with the INT1 style. Please feel free to contact me directly with a private message and I will be glad to put you in touch with the correct people. Thanks! Geoff ... View more

Hi Oleg, I was browsing forum threads and stumbled across this post of yours. Please find the application Tim mentioned here: http://www.esri.com/software/arcgis/extensions/esri-s57 Hope this helps! ... View more

Here is a link to the download: http://www.esri.com/software/arcgis/extensions/esri-s57 ... View more