The "New" Collector has a lot of issues when compared to "Old":
- In "Classic", when Collecting a new polygon, even without a GPS connection, you could just tap the screen and add 1, or many vertices and just "heads up digitize" you polygon. This is handy when:
- Training users
- Using Air Photo as a basemap, the user simply wants to digitize bases on an outlines (e.g a field bordered by trees or roads). Our firefolks exclusively use Collector this way (Why should I walk around a 3 mile perimeter when I can just sit in the truck and digitize it off air photo?).
- In "New", the first problem is:
- As soon as you pick the feature type (in this case there are 4 possible polygon types based on symbology), the first point starts averaging. I don't want a GPS point, I want to "digitize"!.
- So now I have my first vertex, in order to add more, I have to use "Use Target Location" and pan and zoom around to center target where I want it. Doing this with 30-50 vertices using Air Photo is simply not sustainable.
To summarize:
Classic: Don't have to wait for a GPS connection, don't actually need one. Just tap on the map where you want 50 vertices, and there they are.
New: First vertex has to be GPS only (You don't have a choice), have to zoom and pan for each of 49 additional vertices.
Using the workaround to use sideloaded basemaps (When taking the map offline, select "World" resolution so you can actually use a basemap, then select your offline basemap in the map)....everytime you switch a map, when using multiple maps offline, the basemap always defaults to "Default", which makes sense, it's called "Default", but that doesn't make it any less annoying. In "Classic", whatever basemap you were using in Map 1, is the one you get when going back and forth from Map 1 to Map 2.
I have one map with 4 layers, 2 of which are point. One of the points I turned clustering on, but I'm not getting clustering in New Collector. It defaults to the symbology baked into the service (same on old Collector). Is this something that's being planned (support clustering)? That sure would be handy.
