Police import #226
Open
Police import #226
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks - could the binary commit please explain why it's necessary? |
dracos
force-pushed
the
master
branch
3 times, most recently
from
f8a2f78
to
bcb87c5
Compare
dracos
force-pushed
the
master
branch
2 times, most recently
from
21f5add
to
8547a77
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a helper to others, this fixtures file creates the types needed to run the police areas import command with the following:
./manage.py mapit_UK_import_police_force_areas --commit --generation_id 1 --area_type_code PDG --name_type_code "P" --code_type "police_id" [path/to/police/kmls]I don't know where to document this, as the main docs don't seem to include anthing about the police importer.