Friday, 1 February 2013

ONS Postcode Import

Tagging Plans:




















































































































← Older revisionRevision as of 19:34, 1 February 2013
(2 intermediate revisions by one user not shown)
Line 13:Line 13:

== Schedule==


== Schedule==

-
The intention is to run this for the first time when ONS release their February 2013 dataset, and then again each quarter when they release it.

+
The intention is to run this for the first time when ONS release their February 2013 dataset, not sure whether it is worth running on a regular basis after that.


==Import Data==


==Import Data==

Line 40:Line 40:

Identify what method will be used for entering the imported data into the OSM database - e.g. API, JOSM, upload.py, etc.


Identify what method will be used for entering the imported data into the OSM database - e.g. API, JOSM, upload.py, etc.

-
This is a recurring import that will be generated from a script. The source of the script will be referenced here when completed.

+
Initially it will be a one time import, although there may be value in having it as a recurring import whenever ONS release their data. It will be generated from a script. The source of the script will be referenced here when completed.


Import method is TBD


Import method is TBD

Line 65:Line 65:

Describe your plan for mapping source attributes to OSM tags.


Describe your plan for mapping source attributes to OSM tags.

-
No plans at present, source information contained in the Changeset comments.

+
Not planning on tagging the source directly on the ways, the source information will be contained in the Changeset comments.


===Changeset Tags===


===Changeset Tags===


No comments:

Post a Comment