The POTAmap provides realtime map-based information about POTA activations, but it is probably more used as a planning tool. You can do complex searches on parks (show me parks within 50 miles that I haven’t activated and have zero CW activations), save and replay the searches, get driving direction, and access deeper stats than are available on POTA.app (specifically mode-based totals for parks).
If there’s something you’d like to see, or you run into a bug, drop 'em here.
Work In Progress
The current dev branch of POTAmap is targeted toward adding features for planning roves. For example, collecting parks into a rove based on PQL search criteria or manual addition, and efficient route planning among the rove parks. I’m leveraging Google Maps’ routing API for this.
The big change for non-rovers is a Notes area on the back of the data popup for each park. Basically you can click the marked corner of the popup, it spins around, and you have a space to take notes, drop research URLs, and so on. This is also where you add the park manually to a rove.
I’m shooting for a late November release on this version. I’ll likely do a preliminary release, see how it is being used, then a follow-up release based on what I’ve learned.
Also in the works, maybe for November, is to link parks back here to the PN&R Discourse forum, so that you can open a park on the map and see a ‘Discuss This Park’ link that will bring you here, creating a new Sites topic if it doesn’t exist. A similar function will link PN&R reviews back here for discussion.
One thing I notice is that using Safari on my Macbook, when I hover over a marker for a park, the park ID pops up and then disappears. Sure would be nice if it didn’t disappear.
I don’t use google maps. It would be nice if clicking for directions went to Apple Maps instead.
I’ve added Apple Maps to the feature list, I’m in the same boat. I haven’t been able to reproduce your hover problem, but I did log a bug against it to investigate.
I have problems seeing park boundaries in the Greater Katahdin Parktrapolitan area. There are a bunch of parks and park impersonators all smashed together and I can’t tell what summits are in a POTA park and what summits are not.
As I say, these are all together in a string of green blocks of land. Not all the boundaries between them are visible to me.
IDK if my inability to see the boundaries is anything that is fixable. If it’s that way in the source map data then I’ll just suffer. 
I’ve just released v1.4 of POTAmap. The notable addition for this version is a way to capture notes on a park. Click a spot to open the datasheet, then spin the datasheet around to record notes on the back. It supports a (very) limited version of Markdown to format URLs, in the pic there are two, one straight URL and one link to a Bear note. Clicking the Bear link opens Bear (a notetaking and organizational tool), and if your fave note-taking tool exposes a link, we can add it. Parks with Notes are styled with a blue ring on the map. There’s also a new ?NOTES:1|0 PQL query filter. This is early days but I wanted to get this out and see how people use it before going too far down the path…
These are the supported link schemes right now: https?|app|bear|obsidian|note|file
I already have pages in Bear for many parks where I store maps, photos, notes, links to review, and so on, and now I can just click on the map and open that set of data directly. Even just storing the link to a PDF of the park map is going to be useful on the road.
I’ve been poking around the Discourse API. It looks like I can automate a linkage from the POTAmap back to Discourse, for example to create or open a thread here in Field Notes when someone clicks ‘Discuss This Park’ on the map.
I think that’ll be the next sprint. I keep putting rove routing off, I don’t know why – I have a handle on how to implement it – but this’ll be a good step to pull all the pieces together.
More Discourse API poking. It looks like anything you can do from the UI is available in the API, and authentication is key-based and pretty solid. I think it’ll be pretty simple to link back to Discourse from the POTAmap.
I’ll need a backend server to listen for the inbound ‘Discuss This’ request, since I can’t just distribute a Discourse key to the clients. Node’s the obvious choice, and there are a few more projects simmering that might need a backend anyway.
This is part of making POTAmap an entry point for a lot of what PN&R offers. From the POTAmap you’ll be able to use PQL, filters, and embedded notes for high-level research, and then each park will offer a link to a full park review if it is published on PN&R, and a Discuss This button that opens the topic in the forum, creating it if necessary.
The topics linked from the POTAmap are in the Field Notes category. I intend to start really asking activators to send anything at all to report@pota.news in terms of a field report, and those become Field Notes. The next piece is linking to Discourse Field Notes from the main PN&R reviews. Might need to be a manual step for a while.
I think this makes the map even more valuable, as now it can be a repository for shared knowledge about each park.
