Latest Contributions by TomNeer

Working in an area where I am dealing with a subdivision from the 1920s. The plat has limited information and conflicts with modern surveys. I am reconstructing from multiple modern surveys. As a result I am switching between records constantly which commonly have differing ground-to-grid conversions. Proposed Enhancement: When setting a Ground To Grid Correction, extend the Record to support storing the Ground To Grid Correction Settings. From the Record Menu, add the following actions: Ground To Grid Conversion Save Ground To Grid Conversion - Saves the current Ground to Grid Conversion settings into the Record Load Ground To Grid Conversion - Loads the saved Ground to Grid Conversion settings. Greyed out if no settings are saved. This would be helpful because it saves time not having to manually enter Ground To Grid Conversion every time a user switches Records. Also, the Ground To Grid Conversion may not represent the Basis of Bearing and this allows users to load what was used previously used. Bonus! When activating a Record with a stored Ground To Conversion setting, ArcGIS Pro prompts the user if they way to switch to the stored Ground To Grid Conversion settings. ... View more

That is a limitation of this formula. It is possible, but my spherical trigonometry is pretty rusty. Would be easier if Esri just supported projections in Arcade. ... View more

@DavidColey - Here is the Arcade expression that can return either latitude or longitude. So at first, I thought my code was **bleep** because it was returning slightly different values than Esri's Calculate Geometry tool (even double-checking my transformations), but I ran several test SPC through NGS Coordinate Conversion and Transformation Tool (NCAT) (noaa.gov) and this code is more accurate than Esri's. Go figure...     // Calculates the latitude or longitude of a State Plane coordinate // Source: https://community.esri.com/t5/coordinate-reference-systems-questions/formula-for-state-plane-to-lat-lon-conversion/td-p/870543/page/2 // Get Colorado State Plane North (2231) coordinates from geometry var x = Geometry($feature).x; var y = Geometry($feature).y; // Projection Information (this must be changed if you are not using EPSG 2231) var linear_unit = 0.3048006096012192; var false_easting = 3000000.000316083; var false_northing = 999999.999996; var central_meridian = -105.5; var sp1 = 39.71666666666667; var sp2 = 40.78333333333333; var latitude_of_origin = 39.33333333333334; var semimajor_axis = 6378137.0; var semiminor_axis = 6356752.314140356; function degToRad(deg) { return (deg * PI / 180) } function radToDeg(rad) { return (rad * 180) / PI } function tVal(t) { return (Tan((PI / 4) - (t / 2)) / Pow((1 - (ecc * Sin(t))) / (1 + (ecc * Sin(t))), (ecc / 2))) } // Convert projection information into radians var lorR = degToRad(latitude_of_origin); var sp1R = degToRad(sp1); var sp2R = degToRad(sp2); // Spherical Trig voodoo var flat = 1 / (semimajor_axis / (semimajor_axis - semiminor_axis)); var ecc = Sqrt(2 * flat - Pow(flat, 2)); var n = (Log(Cos(sp1R) / Pow((1 - Pow(ecc, 2) * Pow(SIN(sp1R), 2)), 0.5)) - Log(Cos(sp2R) / Pow((1 - Pow(ecc, 2) * Pow(SIN(sp2R), 2)), 0.5))) / (Log(tVal(sp1R)) - Log(tVal(sp2R))) var f = (Cos(sp1R) / Pow((1 - Pow(ecc, 2) * Pow(SIN(sp1R), 2)), 0.5)) / (n * Pow(tVal(sp1R), n)) var rf = (semimajor_axis * (1 / linear_unit)) * f * Pow(tVal(lorR), n) var rz = Pow(Pow((x - false_easting), 2) + Pow((rf - (y - false_northing)), 2), 0.5) var tz = Pow((rz / ((semimajor_axis * (1 / linear_unit)) * f)), (1 / n)) var zz = Atan((x - false_easting) / (rf - (y - false_northing))); // Latitude iterations in radians var latTR = (PI / 2) - (2 * Atan(tz)) var lat1R = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(latTR))) / (1 + (ecc * Sin(latTR))), (ecc / 2))))) var lat2R = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(lat1R))) / (1 + (ecc * Sin(lat1R))), (ecc / 2))))) var lat3R = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(lat2R))) / (1 + (ecc * Sin(lat2R))), (ecc / 2))))) var lat4R = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(lat3R))) / (1 + (ecc * Sin(lat3R))), (ecc / 2))))) var latFR = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(lat4R))) / (1 + (ecc * Sin(lat4R))), (ecc / 2))))) // Longitude calculations in radians var lonR = ((zz / n) + degToRad(central_meridian)); // Latitude and Longitude values in degrees var latitude = radToDeg(latFR) var longitude = radToDeg(lonR) // Change me return longitude; ... View more

It would be extremely helpful to have access to a projection library (e.g., PROJ4JS | Proj4js) in ArcGIS Arcade to support the calculation of coordinates in differing systems (e.g., USNG and Latitude\Longitude). Arcade will only return the XY coordinates in the projection of the dataset. The only solution is to translate the spherical trig into Arcade   // Calculates the latitude of a State Plane coordinate // Get Colorado State Plane North (2231) coordinates from geometry var x = Geometry($feature).x var y = Geometry($feature).y // Projection Information var linear_unit = 0.3048006096012192 var false_easting = 3000000.000316083 var false_northing = 999999.999996 var sp1 = 39.71666666666667 var sp2 = 40.78333333333333 var latitude_of_origin = 39.33333333333334 var semimajor_axis = 6378137.0 var semiminor_axis = 6356752.314140356 function degToRad(deg) { return (deg * PI / 180) } function radToDeg(rad) { return (rad * 180) / PI } function tVal(t) { return (Tan((PI / 4) - (t / 2)) / Pow((1 - (ecc * Sin(t))) / (1 + (ecc * Sin(t))), (ecc / 2))) } // Convert projection information into radians var lorR = degToRad(latitude_of_origin) var sp1R = degToRad(sp1) var sp2R = degToRad(sp2) // Spherical Trig voodoo var flat = 1 / (semimajor_axis / (semimajor_axis - semiminor_axis)) var ecc = Sqrt(2 * flat - Pow(flat, 2)) var n = (Log(Cos(sp1R) / Pow((1 - Pow(ecc, 2) * Pow(SIN(sp1R), 2)), 0.5)) - Log(Cos(sp2R) / Pow((1 - Pow(ecc, 2) * Pow(SIN(sp2R), 2)), 0.5))) / (Log(tVal(sp1R)) - Log(tVal(sp2R))) var f = (Cos(sp1R) / Pow((1 - Pow(ecc, 2) * Pow(SIN(sp1R), 2)), 0.5)) / (n * Pow(tVal(sp1R), n)) var rf = (semimajor_axis * (1 / linear_unit)) * f * Pow(tVal(lorR), n) var rz = Pow(Pow((x - false_easting), 2) + Pow((rf - (y - false_northing)), 2), 0.5) var tz = Pow((rz / ((semimajor_axis * (1 / linear_unit)) * f)), (1 / n)) // Latitude iterations in radians var latTR = (PI / 2) - (2 * Atan(tz)) var lat1R = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(latTR))) / (1 + (ecc * Sin(latTR))), (ecc / 2))))) var lat2R = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(lat1R))) / (1 + (ecc * Sin(lat1R))), (ecc / 2))))) var lat3R = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(lat2R))) / (1 + (ecc * Sin(lat2R))), (ecc / 2))))) var lat4R = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(lat3R))) / (1 + (ecc * Sin(lat3R))), (ecc / 2))))) var latFR = (PI / 2) - (2 * Atan((tz * Pow((1 - (ecc * Sin(lat4R))) / (1 + (ecc * Sin(lat4R))), (ecc / 2))))) // Latitude values in degrees var latitude = radToDeg(latFR) return latitude;     ... View more

  Nana, You probably figured this out but use the @ symbol in front of your variables to call them inline. var sql = "LASTUPDATE BETWEEN @myDate1 and @MyDate2";   ... View more

This is a major flaw of the "tight" integration of ArcGIS Pro with Portal for ArcGIS. The only simple way to change the symbology of a Hosted Feature Layer is through the items "Visualization" tab. However, this is Visualization interface is based on the ArcGIS API for JavaScript 3.x which is currently planned to reach end-of-life next year. The only path I see right now is to create a map in the new Map Viewer. Crack open the map in AGOL Assistant, extract the Renderer object, open the Item in AGOL Assistant and insert the Renderer object. Optionally, you could go through the ArcGIS Server Admin interface and do this too.  Could we pass on Migrating from 3.x to 4.22 | Overview | ArcGIS API for JavaScript 4.23 | ArcGIS Developer to the Portal for ArcGIS developers?  This is a major design flaw of using Hosted Feature Layers in Portal for ArcGIS. ... View more

Same issue. Looks to be a serious oversight. Source data is from Survey123 in WKID:4326. Looking in the Developer Console. there is a warning: [esri.tasks.support.ProjectParameters] DEPRECATED - Module: esri.tasks.support.ProjectParameters Replacement: esri.rest.support.ProjectParameters Version: 4.20 t._consoleWriter @ https://js.arcgis.com/4.22/init.js:105 This occurs in both the SAAS and Developer Editions of ArcGIS Experience Builder. How can this get fixed in the source code? Effectively, this seems to be stopping all projection capabilities of Experience Builder. ... View more

It is my understanding that Esri has adopted the Mapbox Vector Tile Specification. Not sure which version, assuming 2.0 or earlier). Hopefully, Esri can confirm. PBF specification is at Specification | Vector tiles | Mapbox  ... View more

Haven't heard anything.  ... View more

Bruce, Thanks for the quick response. Yes, we are just starting to work with migrating clients to NG9-1-1 schema. We are looking at ways to best integrate the standard with other Esri schema such as LGIM and with the Locator. Based on your post, we are going back to refactor our schema again so both ETL and SQL views do not need to be utilized. Lots going on here. Lots of unknowns. Honestly, haven't mucked around under the hood of ArcGIS Locators since 9.x. I remember it not being much fun... ... View more

Thank you for the writeup. So effectively, concatenate the fields down into something Esri's Locator can consume? Will this concatenation affect the quality of the scoring of the geocoder (e.g. "Main Street North" vs "Main Street North Extension")? How do we resolve the issue of Postal City vs Incorporated City vs Unincorporated Community best? One of the issues the NENA standard resolves is the Postal Address vs Situs Address confusion. In some cases, their Situs Address falls under a different Postal Code but they use another Post Office. Set up a composite locator duplicate locators for both the Situs Address (using Incorporate City or Unincorporated Community and State) and Postal Address (using Postal Community and Postal Code) for both the RoadCenterlines and Site/StructureAddressPoints? What is the best scenario for road centerlines along international borders? Do we hard code this value? ... View more

Thank you for the responses. We were directed by Esri Staff at the UC to look at the PBF format for some of the large Feature Services we were working with. However the documentation on Output formats—ArcGIS REST API: Services Directory | ArcGIS for Developers only states "f=pbf: The response is in the Protocol Buffers format. The PBF format is binary and is thus smaller and faster for clients to parse than JSON. It is used by newer versions of some Esri APIs and applications to improve efficiency. The PBF format is supported by some feature service operations in ArcGIS Enterprise 10.7 as well as hosted feature layers in ArcGIS Online." This infers that PBF can be used by some feature service operations in ArcGIS Enterprise 10.7 and APIs but I have been unable to find any additional information or examples to its use outside of vector tiles. We are actually currently exploring integrating a Quantum Ledger Database into our Web GIS to fulfill our needs. This resolves several major issues with the lack of modern datatypes (INT8/SERIAL and JSONB, specifically), ability to store various geometry type, and provide an immutable transaction log.  ... View more