Latest Contributions by AyanPalit

@farah_SrourAlotoum1012 Real world raw data can be used to model pipeline/utility assets using ArcGIS Pipeline Referencing. This ArcGIS Pro extension does have a simple information model. The raw data may have to be pre-processed to meet the requirements of data types, attributes etc - these are detailed at the documentation link: LRS Data Model ... View more

@GraemeBrowning_Aurizon There are 2 primary use cases to Route creation and my notes on how I see this worked out. Route bulk load: This may employ 'Append Route' tool or other data loading tools. A best practice is to prepare and QC the source data (typically in a file geodatabase where schema is exact match to the target enterprise GDB). I have helped users come up with QC routines and automation on the source fGDB prior to the load. This takes care of load fails, LRS errors and issues like your example. Create Individual Route: This uses the Create Route tool and offers interactive wizard based steps. Although the tool is simple, I coach users to be prepared with all the relevant details to build the route. Entering key attributes like Route Names, Measures should be a well thought out process. This is mostly handled through end-user training and awareness. QC routines developed for method #1 may also be used as guardrails; user can create the route in fGDB, validate and then re-create the route.      ... View more

@Nico9 It will help to know the data types for your use case and what is the data maintenance process. I concur with comments from @DuncanHornby and @curtvprice on shapefile; also unsure of the source cited: http://www.wlm.at A best practice is to model schema objects (feature class, tables, other classes), in a geodatabase format that allows standardization for attribute fields, data types and stipulates precision, scale among other specifications. All robust GIS databases that act as authoritative repository/source of truth, should be modeled such. Legacy formats like shapefiles may be used to export/import for workflows or third-party solutions that are limited to this consumption format. Increasingly, modern solutions, architectures are using services or SQL ETL for data exchange. Most vendors, data/service providers have also moved to file geodatabase formats that preserve data types, field names etc. In summary, if the requirement is high-precision, high-accurate data and preserving the fidelity, develop a process that will not downgrade the data. Shapefile format inherently has some known limitations. ... View more

@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