Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

handles in potlatch too big when zooming in - zooming in stops too early - yahoo-image-bug while zooming #2468

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 6 comments

Comments

@openstreetmap-trac
Copy link

Reporter: dieterdreist
[Submitted to the original trac issue database at 4.42pm, Monday, 16th November 2009]

When I try to edit detailed objects in potlatch I find it gets impossible for several reasons:

  1. the yahoo-background disappears and there is a grey tile (should catch those tiles and scale available tiles instead)
  2. I cannot zoom in as much as I'd like in urban areas (because the zoom is locked). This prevents from seeing and editing details (which are important sometimes, but nice to have always)
  3. the lines and handles are way too big

to illustrate these issues I attached some screenshots from St.Peter's Square in the Vatican City (potlatch and mapnik rendering). As you can see, it is impossible to edit e.g. Bernini's Colonnades, but the detail is reasonable and not too much (e.g. I would like to have the portici (gates) at the ends, but had to draw them in JOSM as I couldn't zoom in in Potlatch to do the job).

@openstreetmap-trac
Copy link
Author

Author: Richard
[Added to the original trac issue at 9.06am, Tuesday, 17th November 2009]

1 cannot be trivially fixed. We are limited in what the Yahoo API can do. We are not allowed to access and scale the tiles directly.

2 unfortunately cannot be fixed in the current Potlatch codebase. Because Potlatch maintains the same display system across all zooms, it reaches the limit of Flash's co-ordinate resolution at z19 or thereabouts. If you were able to zoom in any further, you would still have the same resolution as at z19 - there would be an invisible 'grid' to which your edits would be locked. Fixing this would require rewriting all of Potlatch's display and projection code; it is not feasible. It will be fixed in Potlatch 3.

3 - please tell me what size you would like (as a proportion of the current) at which zoom levels. Please confirm also you have 'Use thin lines at all scales' switched on.

@openstreetmap-trac
Copy link
Author

Author: dieterdreist
[Added to the original trac issue at 2.50pm, Tuesday, 17th November 2009]

Replying to [comment:1 Richard]:

I'm happy that you generally agree with those issues, and sad that it seems complicated/impossible at the moment to solve them. 1. is really a pity because it encourages people to use even worse zoom levels than potlatch offers. 2. am waiting desperately for Potlatch3. I noted that this grid issue is quite confusing. I attached 2 screenshots to illustrate which practical effects this has: the obelisk seems broken in potlatch, but isn't as you can see in the JOSM-screenshot :(, this makes it virtually impossible for potlatch contributors to provide accurate data. 3. Thank you for the notification of the small-lines options. I turned them on and it got way better (I suggest to make small lines default). Still the nodes seem too big. What about scaling the surrounding square by 30-50% (*0.7) (selection brackets) and putting a cross instead of the inner red square? Unselected nodes/ways could remain like they are or get just slightly smaller (to 80-90%, otherwise it would be a pain to hit them with the mouse) Or if you don't like the crosses maybe scale the inner red square to 25% (*0.25) of it's current size.

@openstreetmap-trac
Copy link
Author

Author: Richard
[Added to the original trac issue at 2.59pm, Tuesday, 17th November 2009]

I wouldn't say you can't draw "accurate data" - you can certainly draw accurate data out in the countryside, for example, you just can't draw high-precision building data. I'd agree that JOSM is currently better for this task. I don't draw buildings so I can't say I miss it too much, but each to their own! :)

I'll look at making the nodes smaller.

@openstreetmap-trac
Copy link
Author

Author: dieterdreist
[Added to the original trac issue at 3.15pm, Wednesday, 18th November 2009]

Replying to [comment:3 Richard]:

I wouldn't say you can't draw "accurate data" - you can certainly draw accurate data out in the countryside, for example, you just can't draw high-precision building data. I'd agree that JOSM is currently better for this task. I don't draw buildings so I can't say I miss it too much, but each to their own! :)

yes, sorry, you cannot draw precision data, but of course it can be accurate (when positional correctness isn't too important). Still I consider this an issue because: many users edit only in potlatch, they don't even see the precision in their editorwindow, but are misled about the actual precision assuming that they see what is there, not the projection into a less precise grid.

I'll look at making the nodes smaller.

thank you, I appreciate this.

@openstreetmap-trac
Copy link
Author

Author: dieterdreist
[Added to the original trac issue at 3.22pm, Wednesday, 18th November 2009]

Replying to [comment:3 Richard]:

I don't draw buildings so I can't say I miss it too much, but each to their own! :)

I neither draw whatever building, just landmarks, as they are important for the city structure (and for orientation) and especially in cases like the one in my example their correct alignment/orientation matters! An obelisk/pyramids also other landmark buildings are most commonly aligned in axxis with other features. Slight rotation is very important in these cases (IMHO, must admit that beeing an architect I focus on these details)

@openstreetmap-trac
Copy link
Author

Author: Richard
[Added to the original trac issue at 1.04am, Monday, 23rd November 2009]

Fixed in 1.3.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant