Potlatch 3.0 beta

Posted by Richard on 18 November 2020 in English (English). Last updated on 31 December 2020.

You can now download a development version of Potlatch 3.0 to run on your desktop.

At , you can download a Mac native app, or an AIR file for use on Windows or (possibly) Linux.

Potlatch 3.0 includes desktop-editing features such as Remote Control support, overview zoom levels, and an OAuth login flow for saving. Rendering is faster and there’s now Overpass API support in the tasks palette.

Installation on Linux is likely to be complex and I’d welcome reports from anyone who has successfully achieved it.

There’s much more to come in future weeks so watch this space. You can report issues at pending the creation of a dedicated 3.0 repository.

Location: Potlatch, Latah County, Idaho, United States

Comment from mmd on 18 November 2020 at 16:48

Tried a Docker image on Ubuntu 20.04 b/c I didn’t want to install some ancient libs on my box:


FROM nucleardreamer/air-docker
COPY Potlatch.air .
COPY Potlatch_CPU.air .

docker build . -t my_image

sudo docker run -ti –rm -e DISPLAY=$DISPLAY –net=host -v /tmp/.X11-unix:/tmp/.X11-unix my_image /bin/bash

Unfortunately, installing the app using the installer crashed with a segfault. I gave up at this point.

root@ubuntu:/air# air-install -silent -eulaAccepted  `pwd`/Potlatch_CPU.air 
The program 'air-install' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 196 error_code 2 request_code 130 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Application crashed with an unhandled SIGSEGV
Crashlog has been dumped in /tmp/airCrashLogs/1118_1641_67pN6X

Comment from Richard on 18 November 2020 at 17:12

That’s interesting - thanks mmd. I suspect there will be lots of ways to get it not to install, I’m just hoping that someone has the perseverance to find a way that it will install. :)

Comment from mmd on 18 November 2020 at 17:20

Documenting things that don’t work is a good way to save others lots of time (and frustration). In general, people trying this out should be aware that installing some really old software could potentially screw up their system (end of mandatory disclaimer).

Comment from Richard on 18 November 2020 at 17:38


Comment from mmd on 18 November 2020 at 19:46

At a first glance, it seems to be working using wine: –> download windows version

wine AdobeAIRInstaller.exe

download & unzip potlatch

cp Potlatch.air ~/.wine/drive_c/users/USER wine ‘C:\Program Files (x86)\Adobe\Flash Player\AddIns\airappinstaller\airappinstaller.exe’ C:\users\USER\Potlatch.air

wine ‘C:\Program Files (x86)\Potlatch\Potlatch.exe’

(replace USER by your login user name in Linux)

Comment from mmd on 18 November 2020 at 19:47

those should be two separate commands after all:

cp Potlatch.air ~/.wine/drive_c/users/USER
wine ‘C:\Program Files (x86)\Adobe\Flash Player\AddIns\airappinstaller\airappinstaller.exe’ C:\users\USER\Potlatch.air

Comment from mmd on 18 November 2020 at 19:53

Oh well, this seems to be somewhat unstable and tends to crash when panning the map.

Comment from mmd on 19 November 2020 at 07:19

I also tested Potlatch 3 on Windows 10 now. While the Flash based Potlatch 2 works quite smoothly on that machine, I’m seeing frequent lockups w/ Potlatch 3, in particular when panning the map. Windows Task Manager reports the app as “not responding”, and an impatient users gets prompted to kill the process. It usually takes about 5-30 seconds until it all clears all up again. Maybe there’s some processing going on that blocks the main thread, and Windows thinks the app is just unresponsive and dead.

Comment from Richard on 19 November 2020 at 07:48

Hm, interesting. Is that in a situation where P2 would cope? At (say) z16 for London then it’ll struggle, whereas at z19 it’d be fine. There are things I’d like to do in the future to optimise it but for now the focus is parity really.

Comment from mmd on 19 November 2020 at 08:05

I tested both versions in the same small townish area, that would still fit well in the 50k node limit for an export on z16. Although working on z16 feels a bit sluggish, it’s still feasible on P2. I experienced issues in particular when panning on z17+z18. Maybe there’s something special in my set up, that impacts P3. Let’s see what other users report back.

Comment from mmd on 19 November 2020 at 19:41

With today’s (19 November 2020) build, the Windows Task Manager “not responding” status issue seems to be gone. Also the linux wine environment crashes less frequently. I hope this is expected behaviour and not some coincidence?

I’m seeing some infrequent issues when P3 fails to show parts of the map. I couldn’t figure out, if the loading process itself isn’t working properly at times, or some parts of the map are simply not drawn. In any case, I don’t see any error message.

By the way, could you include some more detailed build information in the “Help” menu, maybe? That would be really helpful when reporting issues.

Comment from Richard on 19 November 2020 at 19:44

Brilliant - thanks for that info. I pushed a couple of small optimisations this morning which I hoped would improve rendering speed - good to know that they’ve made a difference.

I’ve encountered the missing parts of the map issue once or twice before… will see if i can find out what’s causing it. Good idea on build information - I’ll do that.

Comment from farhadGuli on 20 November 2020 at 08:17

this app uses for what ? purpose

Comment from tracker51 on 30 November 2020 at 02:55


Many thanks for the new Potlatch3. After installation I started it for a short test: It’s “tasting” almost like Potlatch2 - great! Would it be possible to show the same map area when starting P3 which was shown when finishing the previous session?

Best regards, tracker51

Login to leave a comment