New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show planning applications #76

Closed
gravitystorm opened this Issue Oct 8, 2012 · 4 comments

Comments

Projects
None yet
3 participants
@gravitystorm
Member

gravitystorm commented Oct 8, 2012

There is a planning application branch, which needs rebasing and finishing off.

The user interface is, if I recall, functionally complete - the parser and cron tasks for processing the planning application feed needs finishing.

The limitation of the current approach is that it requires downloading, reparsing and check/update/insert on all ~2 million planning application records every evening. If upstream now have a "records changed this hour/day" feed like OSM does, then we should use that instead. The vast majority of the records are unchanged each day, and parsing them all is a multi-hour process.

@gravitystorm

This comment has been minimized.

Show comment
Hide comment
@gravitystorm

gravitystorm Nov 1, 2012

Member

Rebased and some further work carried out (see a8e7ebd and parents).

More things to do:

  • need an index on openlylocal_id
  • need columns for the rest of the attributes in the feed
  • needs scheduling as a task

Two larger issues

  • Write some unit tests for the parser
  • Should the front-end code have a switch to turn the functionality on/off easily?
Member

gravitystorm commented Nov 1, 2012

Rebased and some further work carried out (see a8e7ebd and parents).

More things to do:

  • need an index on openlylocal_id
  • need columns for the rest of the attributes in the feed
  • needs scheduling as a task

Two larger issues

  • Write some unit tests for the parser
  • Should the front-end code have a switch to turn the functionality on/off easily?
@mvl22

This comment has been minimized.

Show comment
Hide comment
@mvl22

mvl22 Feb 15, 2015

Member

The GUI work is all in place. Here are screenshots of it:

1: Any member of the site can view list of planning applications matching their area(s) of interest,
shown most recent first. Each application has a page of its own.

1 - listing of planning applications

2: That application page has full details

[No screenshot available.]

3: On the page is a 'Convert to an issue' button:

2 - convert to an issue button

4: The data is cloned into the standard ‘New issue’ form:

3 - application cloned into new-issue form

at which point it can be submitted then like any other issue.

Member

mvl22 commented Feb 15, 2015

The GUI work is all in place. Here are screenshots of it:

1: Any member of the site can view list of planning applications matching their area(s) of interest,
shown most recent first. Each application has a page of its own.

1 - listing of planning applications

2: That application page has full details

[No screenshot available.]

3: On the page is a 'Convert to an issue' button:

2 - convert to an issue button

4: The data is cloned into the standard ‘New issue’ form:

3 - application cloned into new-issue form

at which point it can be submitted then like any other issue.

@nikolai-b

This comment has been minimized.

Show comment
Hide comment
@nikolai-b

nikolai-b Apr 1, 2015

Contributor

in master now!

Contributor

nikolai-b commented Apr 1, 2015

in master now!

@nikolai-b nikolai-b closed this Apr 1, 2015

@mvl22

This comment has been minimized.

Show comment
Hide comment
@mvl22

mvl22 Apr 1, 2015

Member

You are awesome, Nikolai :)

And so is Andy for getting this all started off so brilliantly!

Member

mvl22 commented Apr 1, 2015

You are awesome, Nikolai :)

And so is Andy for getting this all started off so brilliantly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment