Preplanned Areas: Warning "Map Area is too large" is displayed even for large LOD's and a very small area.

doug-m / CollectorAuroraTesting

Manage testing feedback for Collector holistic testing.

0 stars 7 forks source link

Preplanned Areas: Warning "Map Area is too large" is displayed even for large LOD's and a very small area. #157

Open mschenker opened 5 years ago

mschenker commented 5 years ago

Issue

I keep getting the Warning "Map area" is too large even for large LOD's and a very small area. Note: This seems to be specific to this webmap.

Expected Behavior

The Warning should disappear once the LOD or area size is changed sufficiently.

Map and Credentials

Group Name: EsriSwitzerland2AuroraHolistic
Map Name: TestCollectorAugust2018Webmäp

Steps to Reproduce

Select "Manage Areas" from Item Description
Click "Create Area"
Zoom to Bookmark "Züri"
Sketch a (small) area --> Warning will appear and "create" is grayed out
Change the LOD to "World", Warning still remains and "create" is grayed out

Device Information

Device: Chrome Browser V. 68
OS Version: Win 10

offlinearea1

miaogeng commented 5 years ago

I can reproduce this issue using this map. It is interesting that I change the basemap and switch back to topo and save as another one. I don't see the issue. We will take a further look.

mschenker commented 5 years ago

I had a chat with our content specialist today. Apparently, there is some "VODOO" from the ArcGIS Online Content team which makes sure that users from Switzerland get another version of the topo basemap (two services in the basemap, one of them does not allow offline tiles). I did remove the service that cannot be downloaded from the webmap and saved the webmap. This should not be the cause of this behaviour, but there could be some artifacts from that "VODOO" that caused the issue.

simongis commented 4 years ago

I am experiencing a similar issue.

Collector 19.1.0
10.7.1 Base deployment on Azure
Custom Vector Tile package published to the portal

doug-m commented 4 years ago

@simongis I'd recommend contacting support so they can document the scenario. If you end up with a bug number from support please add that here.