The fiber isn't salvageable. Google did an "experimental" deployment which turned out to be utter trash. The short summary is they dug tiny little trenches in the road, and filled the gap above the fiber with foam. Vehicles, snow plows, and construction happened, which all happens to fairly efficiently rip the guts of their network out.
That's why Google is leaving: They don't want to redeploy the entire network from scratch.
On side streets I heard the quality of workmanship dropped even further, from micro-trenches with cabling a few inches below the road surface to cables that were barely covered and eventually becoming tripping hazards.
Possibly Caused by shoddy work by contractors as well - I have heard documented horror stories of contractors cutting the ends off telegraph poles to make emplacing new poles quicker.
The reason why Google is pulling out is because they tried nano trenching the fiber into the street and sealing over the top of it with a rubber like sealer and they had major problems with that sealer bonding to the road. It would peel up and get destroyed as cars went over it. Google is backing out because their existing plan all needs to be removed and replaced and the road surface needs to be fixed. Giving a WISP access to that fiber would just be a cop out for Google to avoid fixing the issues that they caused.
The actual reason, the core of this, has nothing to do with micro-trenching and everything to do with them not being allowed to use the existing network of utility poles due to bigger telco's lobbying the governments against it, and winning. AT&T, Comcast etc were fighting tooth and nail to not allow Google on their poles, which led to google attempting micro-trenching as a proof of concept.
Incorrect historical revisionism. Google was always allowed to use the utility poles. It lobbied Louisville to get a special law passed that would allow it to not only use the utility poles, but relocate other peoples’ wires to make space on the poles while putting up their own. (Ordinarily, the owner of the lines does the relocation.) AT&T challenged that law in court.[1] The city defended the law at its own expense, and won fairly early in the process (on a motion to dismiss). AT&T did not appeal. That was two years ago. According to the article, Google didn’t even start nano-trenching and signing up people for “fiber hoods” until October 2017, after the lawsuit was already over.[2]
[1] AT&T did not challenge Google’s right to use the utility poles, only the law allowing Google contractors to relocate AT&T’s equipment and wires in the process. These laws are probably a good idea on the whole, but given the shoddy work Google’s contractors evidently did with the city’s streets, maybe AT&T’s complaint wasn’t so dumb after all.
[2] The whole concept of “fiberhoods” is another concession to Google that other providers do not get. Almost everywhere, franchise agreements require universal coverage of the city, not just build-out in places with demonstrated demand. Moreover, Google wasn’t required to pay for various additional concessions that Charter had to pay in Louisville, like wiring up government buildings and providing public access channels and a studio for government use. Those provisions are routine for cable franchises, but Google Fiber categorically refuses any deal that has them.
Google only lobbied for that law because AT&T was acting with malicious compliance -- intentionally doing the work as late as possible, so as to interfere with Google's rollout.
Not true. Google started negotiations with Louisville in 2015. The city passed the ordinance in February 2016 to become more attractive as a Fiber City candidate: https://www.courier-journal.com/story/news/politics/metro-go... (“Tonight's vote puts Louisville one step closer toward becoming a Google Fiber city.”). Google made the official selection of Louisville as a Fiber City in April 2017, and as of that date had not even applied for any work permits: https://www.techrepublic.com/article/google-fiber-officially.... The lawsuit was resolved by August 2017, four months after Google made the official selection and two months before Google started construction.
Google was right to lobby for the law—it’s a good law and there is ongoing work to require similar laws at the federal level. But as far as what happened in Louisville it’s a red herring. It was a theoretical fight over what AT&T theoretically could have done to hold up deployment, had Google theoretically chosen to deploy over poles. (Note additionally that AT&T proposed a compromise in the city council that would’ve allowed Google contractors to do the make-ready work, but they would have to file work plans in advance and give the equipment owners 60 days to object. So the actual fight was narrower than “one touch make ready,” and far narrower than “access to poles” at all, as stated above by OP.)
It should be underscored too that this is a large part of why the city government is hugely angry about this whole situation, even if they can't go on record about it.
The city agreed at huge cost to fight for the One Touch Make Ready laws to use the city pole infrastructure. They agreed that would be the city's "beta test". The city has a relatively well dispersed pole grid with only a single clear owner (the power company LG&E).
The city never agreed to the "nanotrenching", but Google's lawyers have made clear that by agreeing to "beta test" anything the city also agreed to "beta test" everything, including "nanotrenching" which would not have passed even a basic civil engineer inspection had it gone through appropriate planning channels.
>The actual reason, the core of this, has nothing to do with micro-trenching
I agree that incumbent providers were doing anything and everything they could to hinder Google but the fact of the matter is that if nanotrenching hadn't failed Google wouldn't have pulled out.
