Latest Contributions by MalcolmMeyer2

This idea of needing a named user to access web services is the #1 problem we are faced with in using Esri and  AGOL. I have 50+ users that want to use a secure map service (including one-off users where making them a named user makes no sense, and users that constantly change). This would mean mean purchasing 50 named users, and then updating those users on a monthly if not weekly basis. To be fair, I have found that other web service companies also charge $$ for securing map data or web pages in general. I supposed money needs to be made somewhere, but as a developer when I know it only takes a few lines of code to secure a webpage it makes it very frustrating. To that end we are looking at publishing our own map services to enable secure sharing for only the cost of a webserver, as it is unlikely I can increase my budget by over 500%. ... View more

How about just eliminating the need to have named users entirely? Just allow a map service to be password protected with a username:password. ... View more

A couple things - first the whole projection issue mentioned above is the result of ArcGIS Pro having by default a transformation enabled for NAD 83 <> WGS84, while ArcGIS Desktop and earlier versions of Pro do not. See this thread - Converting NAD83 to WGS84 ArcMap vs ArcPro. I have not found a way to override this transformation in Model Builder in Pro, so until I can convert all my data to WGS84 with the proper transformation, I will likely be sticking with ArcGIS Desktop or QGIS to handle creation of GeoJSON. The second issue is that even if you select "Project to WGS 84" when using Features to JSON tool, the coordinates stay in the native projection, meaning they do not get switched to decimal degrees per the GeoJSON spec (RFC 7946 - The GeoJSON Format). I have not tried this in a few months so I do not know if this has been fixed in any new versions. The workaround is to export a projected WGS84 layer, then run the Features to JSON tool on the newly projected layer. ... View more

Deleting the C:/users/AppData/Roaming/Esri/AcrGISPro folder worked. ... View more

Did you ever solve this issue? I am getting rendering errors on complex polygons from a GeoJSON pulled from a feature service query. GeoJSON that is pulled from my open data site does not result in rendering errors. In the image below the brighter area is not there. I prefer the query method as it is slightly faster and it guarantees access to the latest data. ... View more

Any data, well one other dataset. Let me try with a brand new geodb created in pro plus new data plus new wgs84 feature dataset. ... View more

My working data is in FIPS 3402. I then export this to geojson with no transformation and the only way to do that using Feature to JSON in Pro is to first export it to WGS84 (with no transformation applied, I know I know…). In ArcMap no transformation is applied by default, so until I get all my data transformed properly, I do not want to apply a transformation. I have had trouble with this not applying transformations method to my data in past versions of Pro before, I think I setup a custom ‘no transformation’, but then I just stopped using Pro a few months back for this data so I’m not sure if this worked or not. ... View more

That’s really it. My initial ideas – · Projection transformations – Are transformations global or unique to each map? How can I check on the transformation settings if global? · Corrupt data Tried creating a new Feature Dataset in WGS84 in Pro, same thing - See gif. Also on first run after a computer restart ArcPro sometime immediately crashes, separate issue probably. ... View more

What a productive afternoon.  Adding a file to a map. Feature dataset created in ArcGIS Desktop in WGS84 projection - multi-part polygon. ... View more

Don't fall for the GPU hype, buy as much CPU as you can afford. The new i9 processors from Intel look promising. I NEVER go over 20% GPU usage (though I don't do 3D work either), meaning I could have gotten away with the P2000 and gotten either a 1TB NVMe, a faster processor, or 32GB RAM. My 2018 workstation is an HP Z4 Workstation with a mid-level Xeon (W-2133 @ 3.6GHZ), 16GB of RAM, a Samsung 512 NVMe drive for the OS and working data, a large spinning disk for data backup, and an NVIDIA Quadro P4000. I think the total cost was around $4K. The fans are silent. If you need to keep costs down go with a gaming GPU, 16GB ram and an i7, i9 or Ryzen instead of a Xeon. My computer flies in ArcMap with data stored locally. In ArcPro, random things are slow and overall it feels like beta software with daily crashes, though I still plod along and am slowly converting my workflow to ArcPro, hoping for better results in the future. That said, looking over your post I would guess that the network is your main issue. You can use CrystalDiskMark to check the speeds of your network drives and compare these with your local drives. Pulling a raster over the network will be a disaster unless you have an amazing IT team that keeps the server in good shape and GB LAN. ... View more

Suggested additions to the actions  -  Ability to zoom the map, or fit the map bounds, to the filtered feature or features Add a loading icon or something to the map to let the user know that something is happening in the map as the filter process can be slow depending on the target features ... View more