JosefWN

I feel your pain @joosakle. On paper `flutter_map` suports custom CRS, but in practise it's pretty hairy because parts of the code, especially the layers, are not written with them...

@joosakle, technically you don't have to fork the repo, but it's hairy (and I admittedly ended up forking it too). Here is a proposed ugly hack for your floor plan...

Using the `master` version of `flutter_map`, but also present in older versions. I think the issue is twofold: - One is the zoom/out of bounds issue, which is not alleviated...

By default (`FitBoundsOptions`) there is a 14px or so padding on the point, so it shouldn't effectively be a single pixel, but yes, it could be too small still, if...

> But I'm a little unclear about whats desired here...if people want to focus on a point, shouldn't they be using a center and not fitBounds ? That would complicate...

You are right, I found I only get out of bounds issues with singular bounds. Perhaps supporting singular bounds would make the API more confusing (although we might benefit from...

Could https://github.com/flutter/flutter/issues/140730 be related? In general flutter itself seems quite messy on the touch/gesture side right now.

I also work in cartesian coordinates, where `flutter_map` admittedly struggles a bit. Coincidentally I've also worked with LiDAR mapping a bit, but not with `flutter_map` specifically. I would say that...

> We could look at creating an extension for LatLng that allows working with meters or a constructor for latlng that takes meters. Not sure how that would work without...

Other than the bugs I have reported relating to planar projections (such as polar stereographic projection), I think my main gripe is the API's are only intended for `LatLng` rather...