Latest Contributions by AletaVienneau

How was the data added to the map, and how were items added to the project: local path, UNC path, enterprise database connection? Did you check the option to Share outside of organization in the Create Project Template pane? This is the switch. Depending on how the data is accessed and the options you picked, copying the data into the project template is expected behavior. Project templates are a special type of project package. There is more info in the Help topic: Share a package—ArcGIS Pro If you run the Package Project tool and check the Package as template option and set the Share outside of organization option the same, what errors does it report? Not all errors produced by the tool are reported in the Create Project Template pane (which uses the tool internally to do some of its work). ... View more

How was the data added to the map, that is what type of path do the layers have to the data -- are they UNC paths? Is it a mosaic dataset or a raster dataset? What settings did you choose in the Create Project Template pane? ... View more

The tool runs checks on the toolboxes included in the project. This result is expected if you added Toolboxes that use older Python 2.x scripts from ArcCatalog/ArcMap instead of the Python 3 scripts that are used in Pro. Another scenario that will fail is if a toolbox contains a model that uses a tool that is available in ArcCatalog/ArcMap but is not available in Pro. ... View more

In PreRelease you won't be able to add CAD annotation to the map. In the PreRelease Update, CAD annotation will be handled as a point feature class that can be labeled like any other point feature in the map.  ... View more

There is no other place to make this change after you've started the software, and my understanding is there won't be a place within the software to do this, e.g. on the Licensing or Portal pages. ... View more

The XML file is the XML file provided with DIMAP raster data. ArcGIS for Desktop does not provide tools for processing DIMAP-format XML files. This is not an internationally adopted geospatial metadata standard. As far as ArcGIS for Desktop is concerned, this is not geospatial metadata, and we offer no support for it in the Description tab. The stylesheet that Desktop uses to display metadata does not recognize the format of the XML file, and therefore it displays the raw XML. This behavior is documented in the Help system: http://resources.arcgis.com/en/help/main/10.2/003t/003t00000029000000.htm Desktop will not defer to displaying the XML file's content using the stylesheet that is internally specified in the XML file when the file's content is displayed. When XML files are displayed in the Description tab any stylesheet references specified within the XML are ignored. If someone wants to display ALL metadata for all items using a custom XSLT stylesheet, this is possible by creating a custom metadata style, which is documented in the ArcGIS Metadata Toolkit (available for download from the support site). Most of the content that is provided in the DIMAP XML file will be incorporated into its associated raster dataset's metadata if you choose to automatically create metadata for it using ArcGIS for Desktop. If you then manually edit the raster dataset's metadata you could add the remaining content to it, if you like. For example, if you open the file you provided in a browser, you can copy/paste the text that isn't automatically included in the raster dataset's metadata into the appropriate metadata elements. Then you would be able to create a NAP-compliant XML file from the raster dataset's ArcGIS metadata document. As-is, the DIMAP-format XML file does not provide sufficient information to produce a valid NAP-compliant metadata document. If you truly want to create NAP-compliant metadata you will have to add content to what you already have. You can do this using the metadata editor that is available in the Description tab. ... View more

ArcGIS 10.x for Desktop is designed to create and manage metadata content that is in the ArcGIS metadata format. You don't have an Export button because you are using the default metadata style; this style is designed to support sharing content with ArcGIS Online, and to support organizations who aren't interested in or required to comply with a metadata standard. If you must create standard-compliant metadata, change the metadata style to one that supports this capability, for example, the NAP style. This provides you with access to full ArcGIS metadata content and an Export button that converts ArcGIS metadata to the standard XML metadata format that is associated with the selected metadata style. Instructions are here in the online Help system: http://resources.arcgis.com/en/help/main/10.2/003t/003t00000009000000.htm ... View more

It is exactly because of this problem that Desktop metadata system is designed the way it is. ArcGIS 10.x for Desktop is designed to create and manage metadata that is in the ArcGIS metadata format. All metadata is stored in the same internal format. You edit all metadata content with the same editor and the same user experience, except the specific set of content and validation rules you're working with are tailored to the metadata standard you are working towards as determined by your metadata style. With the FGDC CSDGM Metadata style, when you export metadata to a standard XML format, you get a CSDGM-formatted XML document. With the North American Profile of ISO 19115 2003 (NAP) metadata style, when you export metadata to a standard XML format, you get an NAP-formatted XML document.  If your metadata XML file is in the ArcGIS metadata format, you can export it to the North American Profile (NAP) metadata style simply by choosing the NAP metadata style instead of the CSDGM metadata style in the Options dialog box. Then, use the Export button in the Description tab to transform your content to the NAP XML format. ... View more

The brief Item Description isn't designed to support people who must create standard-compliant metadata content. This default style of metadata includes the content that is published or shared with items to ArcGIS Online and the content that is indexed and used by ArcGIS for Desktop Search. It is designed to support people who want to use the full capabilities of ArcGIS but aren't yet committed to fully documenting their items.  ... View more

The brief Item Description isn't designed to support people who must create standard-compliant metadata content. This default style of metadata includes the content that is published or shared with items to ArcGIS Online and the content that is indexed and used by ArcGIS for Desktop Search. It is designed to support people who want to use the full capabilities of ArcGIS but aren't yet committed to fully documenting their items.  ... View more

No, the metadata patch isn't released yet. ... View more

Aside from the method you describe, the other way to add a dll to the GAC is to use the gacutil.exe utility that is available from Microsoft. An example of how to use this method is provided in one of the above posts in this forum. That utility is available with different Microsoft products and toolkits. I have it through Visual Studio. You might want to check the Microsoft site to see if there are other ways to get it -- I don't know what they are. ... View more

This is a known issue for ArcGIS 10: NIM058011. The metadata geoprocessing tools are written in C#. If you add GpMetadataFunctions.dll and MetadataTranslator.dll to the Global Assembly Cache (GAC) the script will run successfully outside of ArcGIS. This issue affects all of the metadata geoprocessing tools, not just Export Metadata. NOTE: this issue has nothing to do with Map Automation, and probably belongs in a general geoprocessing forum. ... View more