Ian

Had a quick test of this, it seems to break on lower zoom levels and you end up with some drag points that are way off, example screen shot ...

How many resolutions do you have for the crs ? It sounds a bit like there aren't enough for the available zoom levels, but I may well be talking out...

Ok, so I guess the exception problem is that fitBounds doesn't have any width/height, as its just a single point, so it hits infinity, and I guess the same issue...

Just thinking out loud. I suspect this may get hit before maxZoom gets checked, as fitbounds needs to calculate the zoom (and hit the error) first I assume before it...

I have some vague thoughts around it, just not had time really lately. I.e in the crs code we have.. ``` double zoom(double scale) { // Find closest number in...

Out of interest, could you try the examples on the LatLngToScreenPoint flutter_map example (that examples places an icon where you click on the screen). I'm wondering whether it's not registering...

I was trying to figure if CRS.simple could be used (or extended) in some ways...has anyone tried this (my suspicion would be something like a bounds/LL issue would get in...

I suspect those with more experience on CRS side will need to expand a little more of give specific examples of things that don't work. I.e my understanding is that...

I'm still a bit unsure about what the problem is with using a custom crs like crs.simple to get around reprojections ?

I think what would be useful is a kind of minimal case that highlights the problem and can't be done easily with the existing crs options. Some basic code which...