Latest Contributions by AyanPalit

@BrianBulla Although I am not knowledgeable in VertiGIS Mobile application; the typical mobile app would work off a feature service. There are many configuration parameters at the feature service, one of them being Date/Time. In the Publish Map Service pane, on the Configuration tab, click the Configure Parameters, under Date Fields, click the Time zone of the data drop-down arrow and choose the time zone in which your date values are stored. Specifying the time zone in which the dates are recorded allows date and time values to be converted correctly when users interact with the service. You only need to choose a time zone if your map contains layers with date fields. If you don't specify a time zone, the dates are assumed to be stored in UTC. Reference: Configure a map service ... View more

@Geodesy Editing of simple features should not cause any issues.  Refer to Client and geodatabase compatibility Per this compatibility matrix, you should keep the geodatabase (SDE) at version 10.8.1.x to remain compatible with both ArcMap 10.8.1 and ArcGIS Pro 2.6. Note that ArcGIS Enterprise 10.9.1 is the last (most compatible) version with ArcMap 10.8.2 (last release). Starting at ArcGIS 11.0, many ArcMap dependent features are deprecated.  Removal of ArcMap-based runtime from ArcGIS Enterprise Also, note that the compatibility matrix suggests staying at ArcGIS Pro 2.9 (if continuing to use ArcMap). I have seen users, editing with compatible version of ArcGIS Pro (say Pro 2.9); they may use later version for read-only functions, analysis, search, query (say Pro 3.1). You will quickly realize being in unsupported/incompatible versions for Desktop (ArcMap and Pro), Enterprise and Geodatabase. It becomes a huge issue for IT/GIS admins to maintain a mixed environment with limitations on upgrades, service packs, security patches. You may continue to operate mixed desktop apps, as long as there are no issues.  But this not a best practice and does not align with ArcGIS implementation architecture patterns.    There are many enhancements in ArcGIS including geodatabase objects created by ArcGIS Pro. Solutions like ArcGIS Utility Network, Trace Network, Parcel Fabric, Pipeline Referencing are developed for ArcGIS Pro and comprise of GDB objects that can only be read by ArcGIS Pro. GDB functions like Attribute Rules, Contingent Values are specific to ArcGIS Pro. @DanPatterson cited the lifecycle link that states ArcMap is in extended support and will be retired March 2026. There are many resources to start/plan Migration to ArcGIS Pro:  ArcGIS Pro migration guide Migrate from ArcMap to ArcGIS Pro ... View more

@AvaFarouche glad that you got going on this approach. At the Pollutant Monitoring table, you should have its own Sample Unique ID. This allows to relate how many samples are tied to a location. The date attribute is simply another way to filter or narrow down the search. It's OK to have multiple samples for the same date; they will have different Sample Unique ID's. You can summarize total pollutant measurements for certain time period for each location. There are multiple ways to roll-up or drill down through this type of data. ... View more

@AdrianWelsh  You can find the reference to CAD option at Pro 2.9 documentation: https://pro.arcgis.com/en/pro-app/2.9/help/data/cad/cad-options.htm  The option was deprecated at ArcGIS Pro 3.0 as a fix to BUG-000113773 ('Automatically convert the CAD file to a set of geodatabase feature classes' option does not work). Suggest using CAD To Geodatabase ... View more