The message is not clear :"Parking lot post-processing thresholds are tuned for z18"

[toren77]

1. I received the message when executed rs features for parking . I guess it means "zoom 18"
2. What happened if I used zoom 20 for parking till now (by mistake or lack of knowledge on the particular issue)? Do I need to execute all process from the beginning with zoom 18 , specially rs train ?

[daniel-j-h]

The thresholds for post-processing are currently bound to pixels. And because the thresholds are tuned for zoom level 18 they need to be adapted for other zoom levels:

robosat/robosat/features/parking.py

Lines 11 to 14 in 6c7f547

	class ParkingHandler:
	kernel_size_denoise = 20
	kernel_size_grow = 20
	simplify_threshold = 0.01

I just quickly prototyped a changeset in #88 to base these thresholds on meters and then calculate the pixel equivalent based on the zoom level and the tiles. It's untested but that's where we want to go with it in the future.

Right now what you can do is change the pixel based thresholds and remove the following line

robosat/robosat/features/parking.py

Lines 20 to 21 in 6c7f547

	if tile.z != 18:
	raise NotImplementedError("Parking lot post-processing thresholds are tuned for z18")

Zoom level 20 is a bit high for parking lots to be honest; internally we are running with zoom level 18 on aerial imagery and that is already more than enough to get really precise results. It could be that your results on z20 from the model are even worse than on lower zoom levels.

If you want to re-start the pipeline with zoom level 18 you have to start all the way from creating a dataset since you will need both images and masks on zoom level 18.

[himanshu-sikaria]

@daniel-j-h I see that in branch issue/51 this issue is resolved, however in the master branch and the docker image post-processing is only optimised for z18. So a little confused here if this issue is resolved for not.

Currently want to use this for building detection at z19.

[daniel-j-h]

@himanshu-sikaria you will need pull request #88 which it not in master yet. If you find it useful maybe you can test it, finish it, and then we can bring it into master?