|
POST
|
How are you making a copy of the map? What steps are you using?
... View more
02-02-2022
01:41 PM
|
0
|
1
|
1210
|
|
POST
|
Sorry didn't notice the ArcMap 10.8 part.... If the three inputs into the Merge are all written to a file GDB or a single directory, and they are the only contents in that GDB or directory, you could create a submodel that used an iterator to step through each file in that GDB or directory and then use "Collect Values" to generate the input into your Merge.
... View more
02-01-2022
09:35 AM
|
0
|
3
|
4050
|
|
POST
|
Have you tried If Data Exists (Model Builder) If Data Exists (ModelBuilder)—ArcGIS Pro | Documentation
... View more
02-01-2022
08:41 AM
|
0
|
1
|
4053
|
|
POST
|
That is weird it looks right to me (as long as you aren't using the double quotes.. I.E. it should just be %scatchGDB%\OutputName no quotes).... Other than that you could try setting your scratch workspace in your ArcGIS Pro project to the default GDB of your project. That should make that GDB your ScratchGDB. You could try that and see if it works... maybe the folder your currently using for the GDB (C:\Users\kmakungo\AppData\Local\Temp\ArcGISProTemp26572\scratch.gdb) is read only for some reason. Have you checked that the GDB exists in that location?
... View more
02-01-2022
07:37 AM
|
1
|
0
|
4412
|
|
POST
|
I don't know PostGRE SQL, but slow in SQL Server equals a few things to me. Managing SQL Server logs to make them smaller and managing the geodatabase. Is the GDB (traditionally) versioned and are their a lot of edits stored in the Delta tables? Has it been a long time since your last rec/post? That can slow you down... or is that what you mean by clearing the metadata history? If its not that, it could be your Azure setup. I don't manage our Azure account, but I know their are different tiers and resource limits and I know you can check your Metrics to see if you are maxing any of them out. If you are you can scale up your resources (memory, number of cores, stuff like that).
... View more
02-01-2022
06:11 AM
|
0
|
0
|
1051
|
|
POST
|
Hmmm... so no matter what the user chooses (like if they type or choose "GIS_TMP") they are initially connected to the "CEAP_Routed_Output" database instead... Here is a post that addresses a similar situation. https://community.esri.com/t5/python-questions/python-script-using-arcpy-createdatabaseconnection/td-p/159152 I think it is saying that you have to fully quality the inputs your putting in your MakeValueArray. For example rather than populating the array with SQL_SERVER you would use database_platform="SQL_SERVER". I think the post is suggesting that since the optional inputs into the CreateDatabaseConnection_management function are being left blank, python needs the fully qualified inputs to know which array values are used to populate which parameters of the function. Sounds just crazy enough to work. The only other thing I can think of is that when your using the function from the app it isn't overwriting a current connection file having the same name as the one you are creating; and that existing file is pointed at "CEAP_Routed_Output". You might try setting overwriteoutput to true in your script or deleting any existing connection file with the same name in the same folder before creating the new one.
... View more
01-28-2022
11:58 AM
|
0
|
0
|
2542
|
|
POST
|
See below for a link to the ESRI docs about connecting ArcMap to a SQL Server EGDB. Connect to Microsoft SQL Server from ArcGIS—ArcMap | Documentation I think every machine running ArcMap has to have the appropriate SQL Server drivers installed. Back when this was happening to me installing the SQL Native Client installed the drivers I needed (that was 4 or 5 years ago), but maybe today its just an SQL driver you get from Microsoft... about half way down the page is the title: I would try installing the recommended SQL Server drivers again on the problem machine... maybe something has gone wrong with the drivers installed there already. The only other thing I can think of is that the user name and password might be wrong and the message you are getting is just generic for both errors (I.E. connection problems AND login problems)... but the UN and PW worked on the other computer so I doubt that's it.
... View more
01-28-2022
10:58 AM
|
0
|
0
|
1681
|
|
POST
|
You've probably checked this already, but when I used to get this error (back when we had an ArcObjects/C# custom add-in for ArcMap) updating the SQL Server Native client on the client machine would fix it. I seem to remember you could download it from my.esri.com, going to downloads and picking your software version; then it would include the appropriate client for your version in the downloadable files.
... View more
01-27-2022
02:41 PM
|
0
|
0
|
1728
|
|
POST
|
Are the "Randomly Assigned" tables not even contained in the database you are connecting to? Can you send images of success (in geoprocessing window) and failure (using the add-in)?
... View more
01-27-2022
02:12 PM
|
0
|
1
|
2576
|
|
POST
|
I'm using Branched Versioning. I've learned that I cannot write SQL queries in SQL Server to query my base table directly (in hopes of replicating the results of a versioned view), but that didn't stop me from trying. I did look at the SDE schema tables in SQL Server to see if I could figure out how the REST API could mine records from specific versions/queries. Granted I didn't look for hours, but it didn't look to me that the SQL Database alone contained the data necessary to make the queries. That leads me to believe that the datastore on the enterprise you published your service to is storing additional information about your branch versioned data. Is backing up my branch versioned database using SQL Server alone enough to ensure data security, or do I need to backup my SQL Database and the Enterprise Datastore? Any suggestions about best practices would be appreciated.
... View more
01-27-2022
07:04 AM
|
1
|
4
|
1827
|
|
POST
|
I think after some research, and I could be wrong here, so if I am please post a correction (I don't want to spread false info), the answers are: 1) Versioned views don't exist when you use branched versioning. 2) You cannot use a database (SQL) query to just pull the records you want out of the base tables directly in your DBMS (SQL Server in our case). You have to direct your queries through the service (REST API). 3) The answer to the P.S. I'm a little more unsure of, but I think those records just stay in the base table, since it is assumed your never going to use it directly anymore (only access is through the service). Maybe it is assumed the extra records its carrying around aren't a big deal... maybe you have to run some special API Service based Compress I haven't learned yet (now that I have to learn the REST API)...If anyone know the answer to this one I would still appreciate the info. Thanks.
... View more
01-27-2022
06:42 AM
|
0
|
0
|
3262
|
|
POST
|
If you absolutely have to use the same feature class I would use this scary method. BEFORE STARTING, BACK UP YOUR DATABASE FIRST AND ENSURE A RESTORE IS POSSIBE. Also I would experiment with a copy of your original data in a test environment or a file geodatabase before proceeding to a full implementation in production. Data safety is concern number one. That being said. 1. Use the "Split Line at Point" tool to create a new feature class. This should pretty much be the end result you want with the exception that it's a new feature class. You can stop here if you can use a different feature class, if not here is where the scary comes in...I almost hesitate to suggest it, so make sure you have a backup of the original data. If you have any concerns don't do it. 2. Select all line features in your original feature class and delete them. This will leave an "empty" feature class with all your attributes defined as you want them. Deleting all your lines will be scary. 3. Use the "Load Data" tool in the Catalog Pane to load the lines from the feature class resulting from the "Split Line at Point" tool into the now empty original feature class. You'll have to use field mapping to match the fields up between the two, but that should be pretty easy since the fields should have the same names in both files. Another note of caution here is that if you have related features linked to the original lines feature class, or other third party software linking to the lines, deleting all of those lines could have unpredictable and very negative consequences. The only other way I can think of is to either program it in Arcpy or build it in Model Builder. Either way you'll want to iterate through your points, going to each one, selecting the closest line to your point (using your search tolerance), and splitting the line at the point. Also something you should do in a test environment first after backing up your database.
... View more
01-27-2022
02:30 AM
|
1
|
1
|
855
|
|
POST
|
Sounds like a job for Arcade and Batch Calculation Rules to me. I wrote this in a text editor so its not code ready to run, but it should look something like this I think: var intRoomNum = $feature.RoomNumber var pntGeom = Geometry($feature) var fcRooms = FeatureSetByName($datastore, 'PolygonFloorPlanCall', ["globalId", "RoomNumber"],true) var ftJustOneRoom = filter(fcRooms, "RoomNumber = @intRoomNum") if (ftJustOneRoom == null){ return pntGeom } else { return Centroid(ftJustOneRoom) } Here is a great link to something very similar: https://www.youtube.com/watch?v=HFHJFCn2E1M Hope this helps. K
... View more
01-26-2022
02:17 PM
|
0
|
0
|
657
|
|
POST
|
I'm almost afraid to ask but here goes... We are transitioning a long standing data entry/editing process to a new Branch Versioned database. Using our legacy (traditionally versioned) database we ran processes against the versioned views. This method helped us ensure we were only running a third party application update on current records (those not in a non-posted version). But when I look at the Branch Versioned database tables in SQL Server I get worried. I see no versioned views and the "Base" tables contain records for all records ever created, edited, or even deleted in the feature class, even features in versions that were deleted and/or not yet rec and posted. I also don't see how to tell which records should exist (I.E. have not been deleted or never posted) from the records that should exist. If I go into ArcGIS Pro and open the table it looks right, but it is sure a mess in SQL and that is were our third party update process lives. Is there a way to filter a Branch Versioned Feature Table in SQL Server to see what a "Versioned View" would show. Or at least to tell which records in the Branch Versioned Feature Table in SQL are the currently existing features (I.E. have not been delete, or which are the most recent edits, etc). Is the only option to export the tables out of Pro into new tables in a different database? P.S. another issue is that we have some feature classes with 100,000 + features in them, if every deleted and edited and non-posted record gets written to the table, that will be thousands of extraneous features a year. Can I not get rid of deleted features or unreferenced features from deleted versions/database states? I must be misunderstanding something. Please set me straight. Thank you for your time.
... View more
01-26-2022
01:32 PM
|
0
|
2
|
3295
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-25-2025 07:54 AM | |
| 1 | 07-25-2025 10:45 AM | |
| 1 | 05-10-2022 11:06 AM | |
| 1 | 05-09-2022 04:05 AM | |
| 1 | 03-17-2022 04:04 AM |
| Online Status |
Offline
|
| Date Last Visited |
07-25-2025
07:47 AM
|