|
POST
|
🤔 and the list goes on, only a single level of versions, No "posting version" between protected default and private editor version, etc. what a shake-up Considerations Consider the following when editing the data in a named version: Branch versioning allows only one level of named versions to be created from the default version. In other words, you cannot create a named version from a named version. Only one editor per named branch version is allowed, or multiple users can read from the named version. Once an editor begins editing data in a named version, an exclusive lock is obtained and no other user can connect to the version. You can undo and redo edits when editing the data in a named version. Reconcile and post operations are done using the default version as the target version; you cannot reconcile with or post to another named version. Because the branch versioning model is a temporal model in which all records and edits are tracked in the same base table, there is no requirement to compress.
... View more
06-25-2025
08:26 AM
|
0
|
0
|
1616
|
|
POST
|
separate everything to its own pair/trio of machines
... View more
06-25-2025
08:17 AM
|
1
|
0
|
730
|
|
POST
|
😯😮😲 This is due to all branch versioned data is in a single table
... View more
06-24-2025
02:50 PM
|
0
|
3
|
1666
|
|
POST
|
Neeraj Rajasekar @NeerajRajasekar has some tips in here that might help https://www.esri.com/arcgis-blog/products/analytics/analytics/multiprocessing-with-arcgis-raster-analysis
... View more
06-24-2025
09:39 AM
|
1
|
1
|
1198
|
|
POST
|
head this off as much as possible: the person collecting/entering the GIS data is required to be responsible for maintaining it if they have to fix it they will care more about doing it correctly, hold them accountable so you don't need another "team" to QC everything and end up starting all over example, send a "team" of interns, light-duty out with GPS gear, iPads, etc. to get all our infrastructure created and then "hand it off" to the technician/analyst to connect the dots and maintain it after that that tends to get you sanitary sewer man holes entered as storm drain man holes, fire hydrants as street lights, etc.
... View more
06-24-2025
09:31 AM
|
1
|
0
|
779
|
|
POST
|
This esri document shows field names and index names limit is 128 (SQL Server) Enterprise geodatabase size and name limits https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/enterprise-geodatabase-limits.htm But this esri document shows "ArcGIS imposes a limit of 16 characters for attribute index names." Attribute indexes in the geodatabase https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/attribute-indexes-in-the-geodatabase.htm#GUID-D03A2079-9D75-4293-B73D-6ED23649ABE2 if the limit is 16, this must be a BUG? ArcGIS Enterprise 11.and ArcGIS Pro 3.3/3.4/3.5 should be allowed to create (and maintain) field names and attribute index names up to 128 ArcGIS Pro should not truncate the name down to 16 We should not have to use the SQL Server database tools to create and maintain the attribute index so we can go up to the 128 characters (esri warns about fooling with the enterprise geodatabase directly using SQL Server tools without Enterprise/ArcGIS Pro tools and probably would not /support that) Any additional details about doing this with traditional versioning, core tables, adds table, delete table, history table, etc.? This cannot be "as designed" because the 128 change in ArcGIS for filed names has to be the same behavior to create indexes with names up to the limit of the underlying DBMS (128) Reminds me of the old Arc/Info Coverage limitations shown in this Library of Congress Collection https://www.loc.gov/preservation/digital/formats/fdd/fdd000284.shtml Naming restrictions: There are some limitations on the names that can be used by coverages. The following are some limitations on the coverage names: Cannot be longer than 13 characters Cannot contain spaces Cannot start with a number Does not have an extension Must be in all lowercase letters And the old ArcGIS 10 Resource Center for Fields in coverage attribute tables https://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00140000000q000000.htm INFO uses the following conventions to define the format of each item (field) in a data file: Item formatDescription Item name Any name with up to 16 alphanumeric characters Item width Number of spaces (or bytes) used to store item values Output width Number of spaces (or bytes) used to display item values Item type The data type of the item Number of decimals The number of digits to the right of the decimal place for item types that hold decimal numbers Item format definitions
... View more
06-24-2025
09:09 AM
|
0
|
7
|
1692
|
|
POST
|
can you confirm you are hitting SSD high speed disks for everything and high speed/bandwidth network for your off premise setup?
... View more
06-24-2025
08:09 AM
|
0
|
2
|
1201
|
|
POST
|
https://community.esri.com/t5/net-maps-sdk-questions/why-globalid-changes-to-lower-case-when-getting/td-p/412904 @VesaLaakko @FreddieGibson @dotMorten_esri @DougBrowning https://community.esri.com/t5/arcgis-field-maps-questions/field-maps-is-creating-lowercase-globalid-but-agol/m-p/1126721 @HarshalGharat @suntoygeo
... View more
06-23-2025
09:06 AM
|
1
|
0
|
1204
|
|
POST
|
2-cents, ArcGIS field data types (ArcGIS Pro 3.3, 3.4, 3.5) https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/arcgis-field-data-types.htm#ESRI_SECTION1_91A7053C06624624ABEE2E6765F15083
... View more
06-23-2025
08:53 AM
|
1
|
0
|
1214
|
|
POST
|
@WilliamTarpai you might like some of the content in here Human Brain WebGIS
... View more
06-18-2025
09:00 AM
|
0
|
0
|
1517
|
|
POST
|
not sure what you trying to do can you explain a bit more?
... View more
06-16-2025
08:26 AM
|
0
|
1
|
1248
|
|
POST
|
Allow tables to be stored into FeatureDataset https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idi-p/921909#comments Reference: thinking workarounds? for any "table" you want to include in a feature dataset, give it a couple fields for x and y coordinates calc them both to something like = 1 or even lat/long to "Null Island" make it a point feature class and add it into the feature dataset that will give you access to the "attribute table"
... View more
06-13-2025
09:28 AM
|
1
|
0
|
388
|
|
POST
|
great! do you have a procedures sheet of what you did that you can share here too?
... View more
06-13-2025
09:16 AM
|
1
|
0
|
1950
|
|
IDEA
|
thinking workarounds? for any "table" you want to include in a feature dataset, give it a couple fields for x and y coordinates calc them both to = 1 or even lat/long to "Null Island" make it a point feature class and add it into the feature dataset that will give you access to the "attribute table"
... View more
06-13-2025
08:44 AM
|
0
|
0
|
277
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 1 | 06-13-2025 09:16 AM | |
| 1 | 01-18-2019 11:15 AM | |
| 1 | 08-12-2021 02:36 PM | |
| 3 | 08-26-2025 03:11 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|