Latest Contributions by DanielCota

‎01-07-2020

I think the factor to stress here is that while it may be possible to workaround this with some file manipulation and hackery, it is not supported and can likely lead to issues in the long-term. It is my understanding, as John mentioned, that best practice would be either to revert the change or to reinstall and reconfigure Enterprise. It'll be worth it to avoid the hours/days it can take to remedy the issues that would arise from any other workarounds if something breaks.

‎10-18-2019

Thanks for the reply Bruce Harold‌. Unfortunately I cannot share the file as it contains sensitive information. When you say "the elements will have a schema document alongside them," what would that look like? The only reference to schema when looking at the file in Notepad is in the first few elements within a "Document id" tag. I don't assume that is it? Either way, it sounds like Data Interop is a long-shot solution? Do you think the best way to get this done is with a third party tool or a script?

‎10-18-2019

I am running into a roadblock where I need to somehow export the data from a points KMZ/KML file into a tabular format where all fields in the dataset are accessible. So far, I have only had minor luck in using the KML to Layer tool to get a feature class with all the geometry appropriately visible, but the attribute table shows that all the original attribute data is shoved into one field called "PopupInfo" and formatted as XML. I have seen other threads where they mention that Data Interoperability may be the best solution to fully export all KMZ/KML fields into a tabular format with all original fields present, but I was wondering if anyone in the community has ever gone through this workflow. I do not have access to the original file that the KMZ was created from (at least, not yet) so for now, I am stuck. My end goal is to be able to get all the data into a table where I can then append additional data and create a new dataset from it. Any help is greatly appreciated.

‎09-20-2019

Take a look at the following doc... Geodatabases on Amazon Web Services—ArcGIS Enterprise on AWS | ArcGIS Enterprise The first "Note" that you see explains a reverse situation that what you described, but conceptually I think it will be the same. Given that AWS deployments entail hosting the applications/clients on Amazon servers in a specific region, your on premise database may or may not cause slowed performance, even if it does fall within the same region. By the way, I want to say it is NOT supported to distribute the Enterprise deployment between on premise and in the cloud. If it is, then it's probably highly not recommended. Let's say your server is on premise and the Portal is on AWS, I would imagine federating the two would lead to a slew of concerns or issues once security configurations come into play. For this reason, I think it would be better to have everything on one platform. Hope this helps! -Daniel

‎09-09-2019

Arpa Piemonte Geoportal Team‌ Check to make sure the layers in the project are indeed sourced in the proper enterprise geodatabases. Different versions/connection properties can affect the publishing process if you are referencing the data. For example, if the data is sourced in the same database, but accessed with a different user than what is registered with AGS, then it can result in this error. Best of luck!

Online Status	Offline
Date Last Visited	‎02-22-2021 03:51 PM

My Ideas

Latest Contributions by DanielCota

Re: change server url in enterprise

Re: Anyone ever successfully converted a KMZ/KML into a shapefile, feature class, or csv with ALL attribute fields present in a tabular format?

Anyone ever successfully converted a KMZ/KML into a shapefile, feature class, or csv with ALL attribute fields present in a tabular format?

Re: ArcGIS Enterprise 10.7.1 AWS Deployment Gotchas?

Re: ERROR 001487: Failed to update the published service with the server-side data location.

Re: ArcGIS Enterprise 10.7.1 AWS Deployment Gotcha...

Re: ERROR 001487: Failed to update the published s...