Under the hood of Sorell Council

More of the gory details of how information gets into PlanningAlerts. This is here so you can see and learn how it's done but also so you are able to fix things and see in detail what isn't working.

The steps

  1. Applications are published on the Sorell Council website in a human readable, non-structured form.
  2. The latest scraper code on Github is loaded by our scraping platform morph.io.
  3. The scraper planningalerts-scrapers/sorell on our scraping platform morph.io collects the information daily and converts it into a machine-readable format.
  4. If the scraper errors anyone who is watching the scraper on morph.io gets informed via a daily email alert.
  5. The machine readable data is validated, imported and geocoded by PlanningAlerts daily. If there are any validation errors on an application, the application is skipped and the error is logged. See below for the most recent logs.
  6. The information is published on PlanningAlerts, made available via the API, and people are informed of new applications via email alerts.

Most recent import logs

Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.123.1 Development Application 3 Linden Road, Primrose Sands', 183) while trying to save application 5.2020.123.1 Development Application 3 Linden Road, Primrose Sands for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.133.1 Development Application 9 Valley View Close, Sorell', 183) while trying to save application 5.2020.133.1 Development Application 9 Valley View Close, Sorell for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.163.1 Development Application 108 Weston Hill Road Sorell Representation Close Monday 10th August 2020', 183) while trying to save application 5.2020.163.1 Development Application 108 Weston Hill Road Sorell Representation Close Monday 10th August 2020 for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.164.1 Development Application 5 Shoalwater Way, Midway Point', 183) while trying to save application 5.2020.164.1 Development Application 5 Shoalwater Way, Midway Point for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.166.1 Development Application 646 Shark Point Road, Penna', 183) while trying to save application 5.2020.166.1 Development Application 646 Shark Point Road, Penna for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.173.1 Development Application 184 Gillingbrook Road, Forcett', 183) while trying to save application 5.2020.173.1 Development Application 184 Gillingbrook Road, Forcett for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.174.1 Development Application 238 Marion Bay Road, Bream Creek', 183) while trying to save application 5.2020.174.1 Development Application 238 Marion Bay Road, Bream Creek for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.175.1 Development Application 31 Abruzzi Court, Orielton', 183) while trying to save application 5.2020.175.1 Development Application 31 Abruzzi Court, Orielton for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.180.1 Development Application 139 Lewisham Road, Forcett', 183) while trying to save application 5.2020.180.1 Development Application 139 Lewisham Road, Forcett for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.182.1 Development Application 123 Weston Hill Road, Sorell', 183) while trying to save application 5.2020.182.1 Development Application 123 Weston Hill Road, Sorell for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.191.1 Development Application 25 Bay Road, Boomer Bay', 183) while trying to save application 5.2020.191.1 Development Application 25 Bay Road, Boomer Bay for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.209.1 Development Application 193 Orielton Road, Orielton', 183) while trying to save application 5.2020.209.1 Development Application 193 Orielton Road, Orielton for Sorell Council, TAS. So, skipping
Error Mysql2::Error: Data too long for column 'council_reference' at row 1: INSERT INTO `applications` (`council_reference`, `authority_id`) VALUES ('5.2020.36.1 Development Application 199 Carlton Bech Road, Carlton', 183) while trying to save application 5.2020.36.1 Development Application 199 Carlton Bech Road, Carlton for Sorell Council, TAS. So, skipping
1 application found for Sorell Council, TAS with date from 2020-07-30
26 applications errored for Sorell Council, TAS with date from 2020-07-30
Took 1 s to import applications from Sorell Council, TAS

What you can do next

If something isn't right with the scraper or the data coming in then you could do one or several of the following

If everything is working fine right now but you want to help if something goes wrong

  • Watch the scraper on morph.io, so you will get an email if it errors. Press the "Watch" button in the top right while you're logged in to morph.io.
  • View any scraper issues. Help fix them or comment on them if they are out of date

This week

Find PlanningAlerts useful?

This independent project is run by a local charity, the OpenAustralia Foundation. PlanningAlerts is powered by small, tax-deductible donations from the people who use it to stay informed about changes to their local area. If you find it useful, chip in to support PlanningAlerts.

Back PlanningAlerts