For ebird hotspots, I do know that polygons might be adopted in the future (within this calendar year seems to me very optimistic, from what I heard) but it seems to me that in terms of ebird hotspots there is some room for progress right now. This has also been discussed elsewhere, in general terms, but for NS and for what it's worth here's my opinion.I am not criticizing, just putting my 2 cents in.
-Not all spots are hotspots: I believe some cleaning would be in order, also here in NS. For example in Serbia they removed all spots that were neither known hotspots nor used. So they did *not remove a good hotspot with no visits, but they did remove poor locations with few visits. I did the same for some parts of Italy and I do not regret. Opposite example: Maine (US) where vistually any corner is a hotspot. I find it confusing if not miselading, and also annoying when entering my checklists.
In HRM: do we really need places such as
Spryfield--Jollimore Village
to be hotspot? in birding terms it is not hot (apart from perhaps a few fox sparrows in april), and nobody uses it.
-This is marginal and would take a lot of time but... Nomenclature is inconsistent. Much of these inconstintencies were already there before you guys (thankfully) took up the editing, but the conventional usage recommended by ebird has never been adopted so NS is different from many parts of the world. The double dash -- applies only to major real hotspots with their subdivision. Eg. Yosemite--Visitor center, and then Yosemite--Whatever trail. Halifax Peninsula is not a hotspot, Point pleasant is, so the name should simply be Point Pleasant Park. or St Mary's Boat Club. Same for Spryfield. As per ebird central instructions 2014.
-Vague/unnecessarily confusing hotspots, whereas finer scale would be appropriate.This is the case of names/locations such as
Aspotogan Peninsula--White Point (+ Northwest Cove)
which is not consitent with the common denomination (Aspotogan peninsula is unnecessary) and also idiosyncratic, in the (+ Northwest Cove) part
-General areas
In Southern California they removed all of them (eg. St Elijo Lagoon) and they put precise markers instead. The data remain in a big aggregator (now personal locations) but sublocations grew up really quick and finer scale is so much more convenient both when doing research and when entering checklists, also because of shorter distances, etc. etc. I did the same for Italy (apart from Venice, Roma, Florence) where I maintained these general areas for the (lazy) tourists and I do not regret. As soon as more specific locations are added, these general and generic and approximate locations (incidentally, mostly used by generic and approximative individuals) are gonna go. Think
Bedford Basin
or
Halifax Peninsula--Northwest Arm
or
St. Margaret's Bay
Are these intended to be general areas? or where the marker is put? in both cases people enter checklists that should be given exact location (esp. for bedford basin, where this perhaps means the Long Cove area, but also the Arm, where it collects anything from Dingle tower to Manulife building) and these locators are actually misleading because they work in the opposite direction, that is they aggregate data on a vague and not plotted location.
-Stakeouts
again, ideas taken from elsewhere, but I find it very interesting: rare bird appears in place that is not hot, such as a random parking lot near a mall- On ebird, hotspot with stakeout in the name appears so that all can put data in this stakehout hotspot marker when they see the rarity. The bird goes away, some months elapse, and the hotspot is reverted to personal location. All data are aggregated and stay in the system, but when entering checklists in the area in 2017 we do not have to slalom through hotspot markers for stale stakeouts from 10 years before. So convenient!
curious to think what you think
paolo