Right now the get-buildings call just requests all attributes. It'd be nice if we had --include and --exclude flags like tippecanoe does, to give users more control over the attributes they want.
To tackle this issue the get_buildings command in cli.py should have two more flags added, and then download_buildings should get them in. Then the select_values variable should be tweaked with the right logic. Can leverage DuckDB's exclude command to form the sql, and the include would just pass the values in. It'd likely make sense to just not allow a user to use both include and exclude, as that'd be funky logic to get right.
Right now the get-buildings call just requests all attributes. It'd be nice if we had
--includeand--excludeflags like tippecanoe does, to give users more control over the attributes they want.To tackle this issue the get_buildings command in cli.py should have two more flags added, and then download_buildings should get them in. Then the select_values variable should be tweaked with the right logic. Can leverage DuckDB's exclude command to form the sql, and the include would just pass the values in. It'd likely make sense to just not allow a user to use both include and exclude, as that'd be funky logic to get right.