Latest Contributions by berniejconnors

Currently, ExB designers have no control over the units of measurement presented in the Measurement widget.  There is a predefined list of units for linear and areal measurements.  The ExB designer cannot add to, remove from, or sort the list of units.  We have many lawyers and surveyors that use our ExB app and they frequently must deal with old Imperial measurement units such as rods (16.5 ft) and chains (66 ft). My idea:                In the config for the measurement widget, present a list of all the default units in a table with the unit’s name, abbreviation, and conversion factor from metres (or sq metres).  Allow the ExB designer to add, remove, and sort the rows of the table.  For example, linear units, the current default list of units is: Name Abbreviation Conversion to metres Inches in 0.0254 Feet ft 0.3048 Yards yd 0.9144 Miles mi 1609.3 Nautical miles NM 1852.0 Feet (US) ft(US) 0.3048006096 Millimeters mm 0.001 Centimeters cm 0.01 Decimeters dm 0.1 Meters m 1 Kilometers km 1000    If I were able to edit this list, I would immediately make the following changes: In my opinion, there is no need for units smaller than feet or metres in the mapping apps my organization will publish.  Adding the units of rods and chains are useful for users referring to old deeds or survey plans. There are several other similar "Ideas" proposed by other users - see links below.  These have a total of 56 kudos as of 2025-07-09.  Many people are asking for improvements to the Measurement widget.  Let’s get started! https://tinyurl.com/ym79ho3u  https://tinyurl.com/ywq9vk5l  https://tinyurl.com/yrjflwka  https://tinyurl.com/yl2fvas5   Thanks, Bernie.   ... View more

I was excited to see Shapefile exports added to ArcGIS Experience Builder in the June 2025 AGOL update. However, after a quick test in the GeoNB Map Viewer (https://lnkd.in/eNam9NC) I was quickly disappointed. The map projection of the Shapefile is forced to Web Mercator, EPSG 3857.  Even though our map service is published in EPSG 2953, the output is transformed to 3857.  I understand KML and GeoJSON require 3857, but a Shapefile can have any projection. Why not leave it in the source projection??  We do not use Web Mercator for any of our map services.  They are all published in EPSG 2953 - New Brunswick Stereographic Double.  It is the official map projection for the Province of New Brunswick and it does an excellent job of minimizing distortion. My Idea: By default, all file exports maintain the map projection of the source data whenever possible.  But also add a check box "Transform to Web Mercator".  The checkbox should be automatically checked and greyed-out if the user selects GeoJSON or KML as the output format.   ... View more

I was excited to see Shapefile exports added to ArcGIS Experience Builder in the June 2025 AGOL update.  Our users need a widely supported format for exporting a few features to be used in CAD or other software. However, after a quick test in the GeoNB Map Viewer (https://lnkd.in/eNam9NC) I was quickly disappointed. The user must have an AGOL account to export a Shapefile. We share most of our map viewers with the Public. We cannot expect members of the Public to have an AGOL account just to receive a tiny Shapefile.  Users can still download a CSV, JSON, or GeoJSON directly to their computer.  However, exporting to Shapefile, FGDB, or KML requires an AGOL account.  I cannot imagine a scenario where this makes sense. My Idea: By default, all exports can be directly downloaded to the user's computer.  But also add a check box "Export to AGOL".  If the user selects "Export to AGOL" then the AGOL login would be triggered and they can choose the AGOL folder for the exported data. Doesn't that make more sense?  Arbitrarily restricting the export of certain file formats to AGOL is non-sensical. ... View more