POST
|
Thanks Geoff, as clarification - the problem lies in there being two difference country codes - not that ours was missing. There is the NATO code AS for Australia and the IHO code AU. The same applies for the UK where it is GB and UK respectively. This is because AML is a NATO initiative and considered to be linked to the military and not charting. We have also had allocated AN for Australian AML production through the IHO. As a production agency will typically only produce for itself, it is not a big problem to edit the file manually, but in principle the software should use a lookup table to work this out for itself. thanks again John
... View more
10-31-2013
12:48 PM
|
0
|
0
|
1406
|
POST
|
Bingo!! Thanks Geoff, duplicating the AU entry to AS gave the correct Producer Code!
... View more
10-30-2013
08:41 PM
|
0
|
0
|
1406
|
POST
|
Hello Geoff - we are using ArcGIS 10.1 with Service Pack 1 and all current patches (7 I believe) under Windows 7. - we have ArcGIS Maritime: Charting - Desktop - during export of the product, the production agency is not editable - but shows the correct value - "AS" in our case The curious thing is that if I re-import the exported product as "New Nautical Product - Import existing S57 cell", it recognises and creates the metadata with the "1B" UKHO producer code! Thanks John
... View more
10-30-2013
12:37 PM
|
0
|
0
|
1406
|
POST
|
Problem solved after consulting help! The product must be "Published" before it is allowed to be exported as a valid Exchange Set. However, this has led to the next problem as the "Production Agency" tag for the exported dataset defaults to "1B UKHO Test data" which no ECDIS regards as official data. I have set the "Production Agency" tag to our producer code and all features have the correct code associated with them in the "LNAM" field. Don't know if it requires a re-install of ArcGIS for Maritime or not...
... View more
10-29-2013
04:12 PM
|
0
|
0
|
1406
|
POST
|
Whenever I create an S57 Exchange set for an S57 .000 file in "Create S57 Exchange Set" tool in ArcCatalog, the resulting ENC_ROOT structure is not recognised as containing the .000 file when trying to load into an ECDIS. Upon examining the content of the Catalog.031 file, it appears different to ones produced by our other production system. Has there been a patch for this?
... View more
10-27-2013
06:30 PM
|
0
|
8
|
5202
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|