OpenStreetMap
I'm very new to OpenStreetMap, I came here after listening to a podcast from "Chaos Radio Computer Club".
Today I managed to map a lot in my neighbourhood, but then suddenly, after editing for about one hour or so, that f***ing program of JOSM crashed. F*** it! Please, community, develope a better tool, as this one is a pain in the a** to work with. Thanks!
Discussion
Ulasan andrewpmk terhadap 23 Mac 2009 pada 16:37
Next time, you should save more frequently while editing to avoid losing data.
Ulasan uwe_lehmann terhadap 23 Mac 2009 pada 16:48
That I'll do for sure. Is there no way that someone could get a program working for Mac OSX? I've been using the Mac version, but it didn't allow me to import the Yahoo imagery. I'm now using the Windows version via Parallels Desktop, but as I said it's a pain. I'm going to repeat the steps I took and work on my neightbourhood, but I'm not very fortunate with the program.
Ulasan Igor Shubovych terhadap 23 Mac 2009 pada 16:53
In my experience, when JOSM fails (what happens rarely), it allows you to cancel the operation and try it again.
Just always use tested version of JOSM, not tested. And commit more often.
And yes, community is making it better.
And yes, community is working on some other tools.
Ulasan Igor Shubovych terhadap 23 Mac 2009 pada 16:54
For Mac you could also try Merkaartor.
http://www.merkaartor.org/
Ulasan Tordanik terhadap 23 Mac 2009 pada 16:58
I have been using JOSM for about a year now and consider it rather stable, even when using the "latest" (untested) versions. Of course, as with any software, there will be bugs, and, as with any software, they are practically impossible to fix if the developers cannot reproduce them.
If you can describe more precisely what you did, what version of JOSM you were using etc., it might help the developers to fix the problem. I mean, seriously, what are developers supposed to do in response to your diary entry?
Ulasan uwe_lehmann terhadap 23 Mac 2009 pada 17:35
Hey guys,
I'm now working it all up again, and I'm doing pretty good, in my opinion. As beeing a developer myself I know the issues one is struggeling with. My diary entry wasn't meant to be mean, I was just angry that my work disappeared silently. I'm now saving more often, I'm uploading more often. I think this way I can limit the error counter to zero. You may check out my progress at "Lemsahl, Deutschland" (Germany). I'm doing all the field ways, the forrest and so. Lemsahl has a beautiful nature, and I think this is what matters at OSM, too. As one person in the podcast said: People are adding what's important to them.
Thanks for all your answers, I think with a little more patience and some time one can use JOSM very effective.
Ulasan HannesHH terhadap 23 Mac 2009 pada 18:29
When working with JOSM it is a good idea to upload frequently (every 5-10 minutes) and then also refetch the data to avoid conflicts with other mappers that might be editing the area.
When I first mapped I worked for a week locally and then wondered about uploading. Needless to say that I restarted from scratch (mapping much nicer due to my experience too). ;-)
Ulasan Deelkar terhadap 23 Mac 2009 pada 21:48
especially with WMS JOSM can use quite a bit of RAM, are you sure you used the right -Xmx parameter?
Ulasan uwe_lehmann terhadap 23 Mac 2009 pada 21:53
I'm now using 800MB RAM, as someone has mentioned in the Wiki earlier. It works, though. As I said I'm saving and uploading a lot more frequent.
Ulasan davidearl terhadap 24 Mac 2009 pada 18:55
I can't recall JOSM ever having crashed for me. I've been using it all day today, and even when Java ran out of memory JOSM told me but didn't crash. What did you do to upset it?
Ulasan uwe_lehmann terhadap 25 Mac 2009 pada 07:42
Since I'm using JOSM via Parallels Desktop (a virtualisation program for running other another OS on Mac OSX) with Windows XP Professional SP2 installed it told me that it ran out of memory. I confirmed, but a second later another popup was displayed, telling me again that JOSM is out of memory. I guess it's a problem with the virtualisation. I'm running JOSM now with the memory option, and 800M. This works fine for me. I didn't get the error again; I'm saving a lot and that saves me obviously a lot of trouble. So for the log: JOSM now works fine for me. Thanks for all your replies! :)
Ulasan Baloo Uriza terhadap 26 Mei 2009 pada 17:55
You are aware JOSM works on the Mac, right? It's Java, Java works everywhere. As far as the Yahoo WMS thing goes, there's something about that over on the wiki; though you should seriously consider finding a REAL WMS provider in your part of the world, since the Yahoo to WMS hack is wonky and unreliable at best.