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

[Martin Koppenhoefer]

2016-02-11 8:11 GMT+01:00 Stephan Knauss :

> 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).
>


+1, for the detail I suggest to keep whatever is hand drawn and is a
noticable improvement. To expand on this: If a piece of road is straight,
you shouldn't have more than one node at each end (as long as there aren't
any junctions or other reasons like changing attributes or features on the
road that require additional nodes), but when there are curves you can
obviously add endless nodes to approximate to the shape, and it will always
be smoother. In these cases I'd go with what the mapper has decided to put
and not simplify it automatically (as long as it is an improvement,
sometimes mappers draw many nodes so close but unprecise that the road gets
zigzag curvy because of missing precision, where it actually should be
smooth). In case of overnoding I suggest to improve the geometry manually,
because the douglas peucker algorithm that simplifies only by distance will
introduce problems in sharp curves/turns and leads to a loss of detail.

FWIW, any data consumer that needs simplified geometry can automatically
apply the algorithm and reduce the nodes by himself if that is what he
needs. Reducing is always easier, but enhancing detail automatically is not
possible.

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

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

[Paul Norman]

On 2/11/2016 11:03 AM, Oleksiy Muzalyev wrote:
I assume the old versions are kept in separate tables, and they are 
not used for rendering. 


Old versions are not present on the rendering servers at all.

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

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

[Oleksiy Muzalyev]

On 10/02/16 21:57, Mateusz Konieczny wrote:

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.
Certainly, I use Simplify Way only in extreme cases, and only if a 
geometry is not worsened. Even if I use it, I always adjust the geometry 
manually afterwards. Usually these are small lakes, short paths, and 
secondary roads. I never simplify sea or ocean coastlines.


At the last conference in New York I asked a man from UK who works with 
the OSM hardware why at the zoom levels 10, 11, 12 the OSM map is 
rendered only once a month. He replied that the rendering program must 
process enormous amount of data at these zoom levels.


Nowadays a lot of landuse=, natural=, etc. is being added in Ukraine, in 
Russia, Kazakhstan, etc. There are also a lot of landuse and natural in 
the USA which are not mapped yet, the same for Africa. These are very 
large territories, that is why I tried to pay attention to obvious 
over-nodding. The disks capacity and processing power are constantly 
growing, so sooner or later it will not be an issue for sure, the 
question is if they are growing fast enough. However, it seems that this 
my concern could be unfounded.


I assume the old versions are kept in separate tables, and they are not 
used for rendering.


brgds,
Oleksiy

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

[OSM-dev] Any JOSM developers/expert able to have a look at this login problem?

[Dave F]

Hi

I've a JOSM login problem. I've posted the details here:

https://help.openstreetmap.org/questions/48014/josm-enter-credentials-for-osm-api-failure

If you've a few minutes to see if you can find the problem I'd 
appreciate it.


Thanks
Dave F.

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


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

Re: [OSM-dev] Any JOSM developers/expert able to have a look at this login problem?

[Stephan Knauss]

Your email client seems to be intercepted by your Antivirus (quite intrusive) . 
Can you disable all protection to ensure that it is not hijacking your Internet 
connection and prevents JOSM from sending passwords...
Could explain why the OSM api doesn't receive your password and fails to 
authenticate. 



On February 11, 2016 4:38:56 PM GMT+01:00, Dave F  
wrote:
>Hi
>
>I've a JOSM login problem. I've posted the details here:
>
>https://help.openstreetmap.org/questions/48014/josm-enter-credentials-for-osm-api-failure
>
>If you've a few minutes to see if you can find the problem I'd 
>appreciate it.
>
>Thanks
>Dave F.
>
>---
>This email has been checked for viruses by Avast antivirus software.
>https://www.avast.com/antivirus
>
>
>___
>dev mailing list
>dev@openstreetmap.org
>https://lists.openstreetmap.org/listinfo/dev
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev