Re: [josm-dev] Latest josm seems to be crashing Xorg

[Richard]

On Tue, Feb 09, 2016 at 03:45:02PM +, ael wrote:
> On Mon, Feb 08, 2016 at 11:20:06PM +0100, Richard wrote:
> > On Mon, Feb 08, 2016 at 08:14:37PM +, ael wrote:
> > > I am not sure what is happeing here, but downloading the latest
> > > josm version a few minutes ago and attempting to run it crashes 
> > > Xorg with "Bus error at address 0x0".
> > > 
> > > I am on debian testing, and using
> > 
> > that is more a Debian problem but try running josm with
> >  strace -f java ... > trace.txt 2>&1
> >  ltrace -f java ... > ltrace.txt 2>&1
> > 
> > and look what happened before the Xserver crashed. Might be something
> > that is possible to workaround.
> 
> I was going to try with gdb: I hope there are dbg (with gdb symbols)
> versions of the packages around. Will try to find time to look further 
> maybe later today. As I said in my follow up message, I now don't think
> it is likely to be a josm problem.

gdb is surely the best thing to do, even without the debug packages.
However sometimes strace/ltrace might also be very usefull.
BTW I find it handy to attach strace, ltrace or gdb to running processes
with "-p PID"

> But I am surprised that no one else seems to have reported such a major
> issue. I have sent a message to openjdk@list.

it might be related to the particular video driver in the kernel. Did you
look at kernel messages?

Richard

___
josm-dev mailing list
josm-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/josm-dev

Re: [OSM-dev] changes in coastline are not rendered

[Mateusz Konieczny]

On Tue, 9 Feb 2016 11:21:37 +0100
Oleksiy Muzalyev  wrote:

> On the other hand, I am in doubt, - perhaps, people invested a lot of 
> time and labor in clicking these hundreds and hundreds of nodes, to
> make a nice looking map, and I am not sure if I am doing the right
> thing with the tool SHIFT+Y (Simplify Way). Maybe this excessive
> number of nodes is negligible for the database and rendering?

I am not sure is there real benefit from way simplification - except
extreme cases with distance between nodes that is below 1m.

Note that it is not reducing size of the main OSM database - as anyway
all old version are stored forever, so any edit will increase its size.

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [josm-dev] Latest josm seems to be crashing Xorg

[ael]

I have just tested with java-8 and there is no crash.

ael


___
josm-dev mailing list
josm-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/josm-dev

Re: [OSM-dev] changes in coastline are not rendered

[Mateusz Konieczny]

On Mon, 8 Feb 2016 20:20:39 +0100
Christoph Hormann  wrote:

> On Monday 08 February 2016, Gerd Petermann wrote:
> >
> > It was changed more than 3 days ago and the change is not rendered.
> >
> > I understand that coastline ways are special, but that seems too
> > long for me.
> >
> > Any hints why this takes so long ?
> 
> Coastline processing on openstreetmapdata.com is stuck for more than
> a month now, mostly because a lot of back and forth with tagging of
> large lakes as coastline.
> 
> For information: to avoid major disruptions of map rendering due to
> data errors the coastline is not updated if there are larger changes
> in the geometry compared to the last time it was successfully
> processed.  Any addition or removal of a lake with coastline tag will
> require manual intervention and we do not have the time to manually
> check the data every day because some mapper somewhere wants to
> scratch an itch and decides to tag a lake outline with
> natural=coastline.
> 

Thanks for the information! I added this data to
http://wiki.openstreetmap.org/wiki/Coastline#Rendering_in_Standard_tile_layer

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] changes in coastline are not rendered

[Stephan Knauss]

On 09.02.2016 11:21, Oleksiy Muzalyev wrote:

On the other hand, I am in doubt, - perhaps, people invested a lot of
time and labor in clicking these hundreds and hundreds of nodes, to make
a nice looking map, and I am not sure if I am doing the right thing with
the tool SHIFT+Y (Simplify Way). Maybe this excessive number of nodes is
negligible for the database and rendering?


This is the reason I suggest against using the simplify functionality. 
Just because some detail level is not to your liking you sort of "tell 
off" those mappers who invested a lot of time putting that details in 
the first place when deleting it.


There are special situations where it can be useful, but in case of 
"hand-drawn" data mostly it is fine to go forward with a handful of 
additional nodes. And don't worry about the size of the data. Those few 
nodes don't do much harm (we have 4 billions already).


Stephan


___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev