Latest Contributions by berniejconnors

Under the ArcGIS JavaScript API 3.x the Web AppBuilder (WAB) was the best tool to configure online map viewers.  My organization, GeoNB, created many WAB apps.  Under the newer ArcGIS JavaScript API 4.x the Experience Builder (ExB) is the best tool to configure map viewers.  GeoNB has released one ExB app and is planning to replace more WAB apps with ExB apps.  Unfortunately, ExB apps require a GPU, WebGL support, and 8 GB RAM.  WAB apps do not require WebGL support and run very well on older computers with low resources and no GPU. Feature Web AppBuilder Experience Builder JS API 3.x 4.x Rendering DOM/Canvas (2D) WebGL (GPU) Depends on GPU ❌Minimal ✅Heavy Browser requirements Lower Higher Typical weak point CPU GPU / VRAM / drivers Compatibility Older browsers fine Needs modern GPU and WebGL support   We have just begun to discover that we have a significant number of users that cannot run the new ExB version of the GeoNB Map Viewer.  This may become a big issue for GeoNB and other GIS teams that are migrating apps from WAB to ExB. When we released the ExB version of the GeoNB Map Viewer we also allowed users to continue to use the WAB version.  We expected some users were just accustomed to the old interface and reluctant to change.  We did not expect to find many users unable to run the ExB version.  We may keep the WAB version and call it "GeoNB Map Viewer Lite".  But is this sustainable?  Can we maintain WAB and ExB versions for all GeoNB apps? To help identify users that cannot run the ExB version I have created a simple web page that will report the WebGL capabilities of a user's computer.  You can access the web page here: WebGL Capability & Performance Test. GeoNB Map Viewer ExB ⁠GeoNB Map Viewer WAB   Please tell me, are you also experiencing problems with users that cannot run ExB apps?  What are you doing to accomodate users with older/weaker computers.   Best regards, Bernie. ... View more

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