Currently, tzconv uses tzdata locations that are generated by dumping (my) local /usr/share/zoneinfo/tzdata.zi with tzdump.py script.
But tzdata has only selected locations for big cities and people may find it convenient to just type city name like Seattle that doesn't have a dedicated location in tzdata. Now you have to use existing timezone for Seattle like America/Los_Angeles.
So why not extend the tzdata with a community driven list of locations? In the end, there should be a huge location -> tzdata timezone where location is used for fuzzy matching and tzdata timezone for the actual time conversion (this is required by Go API - https://golang.org/pkg/time/#Time.In).
Currently,
tzconvuses tzdata locations that are generated by dumping (my) local/usr/share/zoneinfo/tzdata.ziwith tzdump.py script.But tzdata has only selected locations for big cities and people may find it convenient to just type city name like Seattle that doesn't have a dedicated location in tzdata. Now you have to use existing timezone for Seattle like America/Los_Angeles.
So why not extend the tzdata with a community driven list of locations? In the end, there should be a huge
location -> tzdata timezonewherelocationis used for fuzzy matching and tzdata timezone for the actual time conversion (this is required by Go API - https://golang.org/pkg/time/#Time.In).