#5620 closed defect (fixed)
download area display (yellow stripes) rectangular also for non-mercator projection
Reported by: | skyper | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | 16.08 |
Component: | Core mappaint | Version: | |
Keywords: | projection | Cc: | michael2402 |
Description (last modified by )
Hi
It is happening for around 10 days now, that not all data is downloaded at the boarder of the "downloaded area" or maybe the area is rendered to big. Anyway I end up with node within the downloaded area where not all connected ways are shown. This is dangerous. It does not happen all the time and it is not that easy to reproduce ( I tried it but failed so far.)
It happened several times last week !
Maybe it has something to do with lambert-9 projection, but I am not sure about it.
cu skyper
Attachments (1)
Change History (16)
comment:1 by , 14 years ago
follow-up: 4 comment:2 by , 14 years ago
I tried but could not see problem. If you can give a step by step description how to reproduce the problem, then it will be much easier for us to fix it. The difference can be as large as "impossible to fix" vs. "fixed in 1 minute". :)
comment:4 by , 14 years ago
Replying to anonymous:
I tried but could not see problem. If you can give a step by step description how to reproduce the problem, then it will be much easier for us to fix it. The difference can be as large as "impossible to fix" vs. "fixed in 1 minute". :)
At least I can show you what happens. I attached a osm-file. It was downloaded with mercator-projection, but if you switch to Lambert-cc9 (7) you notice that the downloaded area is rendered bigger and objects which where outside the downloaded area with mercator are now within it.
Have a look at the buildings in the lower right corner.
comment:5 by , 14 years ago
Priority: | critical → minor |
---|---|
Summary: | download does not download all data or downloaded area is rendered to big → download area display (yellow stripes) rectangular also for non-mercator projection |
The "downloaded area" is drawn rectangular, which is no longer true for non-mercator projection. I'm not sure if the added processing load required to fix this issue is really a good idea.
comment:6 by , 14 years ago
Then we'd also have to draw curved way segments. When you draw a way segment from west to east, the center of the line can be off by a few cm or m in north south direction, depending on the length of the segment. I found the effect to be negligible with Mercator projection and normal sized way segments (<1km).
That is, if a way segment is defined by "shortest line on the sphere" and not by "shortest line in Mercator". :)
comment:7 by , 13 years ago
Description: | modified (diff) |
---|---|
Keywords: | projection added |
comment:8 by , 12 years ago
If the downloaded area is not calculated for each projection at least, make sure that the download area rendered is not bigger than the "real" BBOX downloaded. Otherwise this can lead to unwanted edit errors (see comment:4).
comment:10 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Yes, I did not find the issue. It is displayed correctly now.
comment:11 by , 9 years ago
Component: | Core → Core mappaint |
---|---|
Milestone: | → 16.08 |
comment:12 by , 9 years ago
Component: | Core mappaint → Core |
---|---|
Milestone: | 16.08 |
Yes, can confirm at least for my example.
Thanks a lot
comment:13 by , 9 years ago
Component: | Core → Core mappaint |
---|---|
Milestone: | → 14.08 |
comment:14 by , 9 years ago
Milestone: | 14.08 → 16.08 |
---|
I happened again. I downloaded some data with merkator-projection and then switch to lambert-CC9. The downloaded area is rendered to big.