Latest Contributions by AlessandroValra

Hello, I am following this procedure to publish a scene layer from a file geodatabase with only multipatch featureclass. I seem to recall that I already performed such operation in the past, when this option was still in beta, and I succeeded. However, now it seems not to work anymore. This is what I am doing: I created a file geodatabase with only multipach inside, all in Web Mercator reference system (EPSG: 3857, or 102100). I zipped it and uploaded it to my AGOL (logged in as administrator), choosing to publishing it as a Feature Service. I can open and see it in a Map viewer. Now, inside the details of this same Feature Service, I click on the Publish button and then on "Scene Layer", but nothing happens. How can I solve this problem? Is there anything I did not consider in my workflow? Thanks. ... View more

I am trying to use the Data Interoperability extension within ArcGIS Pro (1.4.1) to reproduce what I was able to do from within ArcMap: converting a IFC to a ESRI fGDB format. The IFC has solid geometries and I would need to export them as multipatch. I attached the IFC if anybody is interested in helping. First thing I noted: there is no Quick Import in PRO. With ArcMap, I sued to use the Quick Import with the settings provided in this ESRI post and the translation was succesfull. In PRO I tried this workflow with no success (steps, figures, and results): Creation of a new ETL Tool from the Project Pane Location and Name choice Generate Workspace Window settings (Coord. System should be correct, and it worked with the Quick Import in ArcMap) IFC parameters settings as in ESRI post. Choice of the Feature Types (I left everything checked as the default) Model execution (through the green RUN button) The output is just a bunch of Tables and some empty linear featureclasses. Also, I attached the Translation Log if it might help. From ArcMap, using the same dataset, same coordinate system, and same IFC parameters as in the linked post, I am able to export multipatch geometries. Unfortunately, ArcMap is not an option right now, and I have to stick with PRO to do this. Any help will be greatly appreciated. Finally, I attached the zipped GDB derived from this process (test_DataInteropPRO_SR.gdb.zip). ... View more

I am having this problem: since generating the tile cache directly on AGOL consumes credits, I do it on my machine through the combination of "Manage Tile Cache" and "Export Tile Cache" tools. My mxd has two layers. The "Export Tile Cache" produces a Tile Package (TPK) file which I can upload to my AGOL and then publish it from the element details to have my hosted tile layer in my contents. I have another element in my contents which is the same service published as a hosted Featrue Service. All I want to do now is displaying my Tile layer in a Web Map and linking it to the Feature Service of the same name in order to query it. Unfortunately, I see only one layer in the legend of my tile layer, but it should have two. This way I can only link it to either one or another feature layer within my feature service one at a time, but I need to link both my tile layers to both the feature layers. This is not occurring when publishing directly using the Share As and selecting both Tile and Feature Access capabilities, but this consumes a lot of credits for my scale levels, and I have to avoid it. Any suggestion wuold be greatly appreciated, thanks. ... View more

Hi. Many times I publish feature services from ArcMap (10.4.1) with the button Share As to my AGOL account. I noticed that if the layers in the mxd are a lot, and somehow heavy (many geometries and many fields), the publishing processes sometimes throw errors. So, I always split my mxd in many different mxds with each one or two layers. While using this strategy I am able to finish the whole publishing process, after a "published succeeded" message, when I enter my AGOL and see my feature layers in the web map they are empty (no geometries nor attributes). The only this that have worked so far was to hide some fields in my layers before publishing them, and, after publishing them, I am able to see them correctly. I know there might be limitations due to the number of records/geometries, but it should also be stated that having too many fields will cause the feature layers not to upload correctly, although the publishing process from ArcMap does not throw any error. In my specific case, this happened (e.g.) with a polygon shapefile with 415 records, and 20 fields. It does not seem so much to me, also considering the fields are 50% text and 50% short intger. ... View more