You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A DA is published on Planning Alerts, but it shouldn't be. It's someone's application for information on a development application. I have destroyed it, but because it's very recent, I'm guessing it will be picked up by the scraper again.
I'll put in an issue for reviewing the scraper for Stirling to not pick these up in the first place.
However, it would be useful to be able to hide DAs when there is an extra special problem like this. Even though it happens infrequently when it's flagged there's often a concern about privacy that's best handled promptly.
The text was updated successfully, but these errors were encountered:
On further inspection others are on display
Searched for others listed and we are also picking that up
eg.
COP24/1631 site:http://www.planningalerts.org.au/
Called City of Stirling Council about this today
Is this policy to publish requests for information details, have these inadvertently been shared?
They're calling back
A DA is published on Planning Alerts, but it shouldn't be. It's someone's application for information on a development application. I have destroyed it, but because it's very recent, I'm guessing it will be picked up by the scraper again.
I'll put in an issue for reviewing the scraper for Stirling to not pick these up in the first place.
However, it would be useful to be able to hide DAs when there is an extra special problem like this. Even though it happens infrequently when it's flagged there's often a concern about privacy that's best handled promptly.
The text was updated successfully, but these errors were encountered: