[openstreetmap/openstreetmap-website] Set minimum changeset boundary size (#2010)

Jamie Guthrie notifications at github.com
Thu Oct 4 01:06:42 UTC 2018


@tomhughes 

How should the actual changeset rendering be handled, once the link has been clicked through from the history page. At the moment, its still the minimum size: https://www.openstreetmap.org/changeset/63058122

>From what I can tell, the changeset is rendered automatically using internal Leaflet GeoJSON code, based on data returned from the OSM API. So the API returns the tiny changeset bounds, and GeoJSON renders it automatically.

So to fix it, the actual data from the API has to be manipulated, either in the controller (so if the changeset has equal minlat/maxlat or minlon/maxlon values, then a minimum sized changeset is sent back instead), or by manipulating the xml data that is returned.

How would you handle it? Is it worth changing the API output so that the minimum changeset bounds are changed in the data layer before being sent back from the API, rather than being manipulated in the view layer?

Or should it just be left as it is and ignored for now?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/2010#issuecomment-426852299
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20181003/f82f8877/attachment-0001.html>


More information about the rails-dev mailing list