codefornepal / nepalmap_federal Goto Github PK

The total population for the pre-federal NepalMap and the federal NepalMap both come from the 2011 census. However, the two versions do not agree on the total population. The pre-federal version counts 2,64,94,504 people while the federal version counts almost 6,00,000 fewer: 2,59,07,649.

Any idea why we might have this difference?

Pre-federal version:

Federal version:

This issue is meant to serve as a public discussion about if and how we can migrate data from the pre-federal NepalMap to the federal NepalMap.

Much of the data we have is data for the pre-federal government boundaries. Are there data sets that can be migrated? What would be necessary to do in order to migrate data accurately? If you have ideas or thoughts, please contribute them in a comment in this issue.

At the center of Rolpa is an area that OpenStreetMap has as "Liwang Bazar". It seems to be in the middle of Rolpa municipality. When you hover over it, it is shown as "Musikot" in Rukum West. This is almost surely wrong. Possibilities:

• It is actually part of the Rolpa muncipality that is both to the north and to the south of it on the map.
• It is some other municipal or local unit, not Musikot, not Rolpa muncipality.

To see this, go to https://beta.nepalmap.org/profiles/district-58-rolpa/ and hover over the local units on the map. When you hover over the little area in the middle (where OpenStreetMap has the legend "Liwang Bazar", you'll see that the tooltip calls it "Musikot" and another area just north of Rolpa district turns green along with it. You'll also notice the "Rolpa" local district is cut in half by that "Musikot". Why? Is that area really part of the Rolpa municipality? Is it something else. Are the two areas that are identified as the Rolpa municipality actually two different local units? Is one of them misidentified?

Our data set for population is missing data for one locality in Province 1. The data are available in our "Federal Data" in https://github.com/Code4Nepal/data/.

Add the data to the population.sql file. Please put the data in a logical place -- so that all data for the same district are in rows next to each other. That will make it easier to review in the future.

• When you add them, you will add one row for female population and another row for male population. See the current file for examples.
• You will need to update the totals for the district for that locality to include these additional data.
• You will need to update the totals for Province 1 to include these additional data.
• You will need to update the totals for Nepal to include these additional data.

Here are the localities whose data are currently missing.

• "Itahari" in "Sunsari" is "Itahari Sub-Metropolitian City" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%201/Sunsari/Itahari%20Sub-Metropolitian%20City.csv

The total population listed for Nepal using our current data set is 51 million. That seems very inaccurate!

Googling shows estimates between 26 and 30 million.

See https://beta.nepalmap.org/profiles/country-NP-nepal/

The inaccurate data are here: https://github.com/Code4Nepal/nepalmap_federal/blob/dev/sql/population.sql#L1750-L1751

Screenshot

settings.py defines the relationship between entities at different geographic levels. Update it to include definitions that fit the new federal structure.

See here for the old definitions: https://github.com/Code4Nepal/nepalmap_app/blob/dev/wazimap_np/settings.py#L21-L40

Update settings.py so that it includes the new definitions.

Please see the readme at https://github.com/Code4Nepal/nepalmap_federal/tree/master/wazimap_np/static/geo for a description of the metadata needed.

Geojson and topojson files for updating can be downloaded from http://localboundries.oknp.org/

This script was used with the old structure to add to each geojson file the correct metadata: https://github.com/Code4Nepal/maptools/blob/master/geo/set_vdc_geo_properties.py. It may be useful as a sample for what needs doing.

This issue related to #2

The wazimap framework will only display data when there is a data set that includes total population figures. Find a data set that has full population figures for each of the bodies at each of the new levels for federal Nepal. Data at higher levels can be derived from data at the local level. Create the appropriate table for these data and add them to the profiles and to the view templates.

See https://github.com/Code4Nepal/nepalmap_app/blob/dev/wazimap_np/demographics.py#L45-L48 as an example of how total population is used.

The data at http://cbs.gov.np/sectoral_statistics/population/Population%20of%20753%20Local%20Units should work.

Prior to recent updates of more data added by @pratimakandel , the male and female populations for each province are identical. Please see
https://github.com/Code4Nepal/nepalmap_federal/blob/7bc04d17ca409f722af09d939028159e5d86d426/sql/population.sql

That is the commit before @pratimakandel began adding data for missing districts.

There must be some sort of error in the calculation.

In order to build the federal instance of NepalMap, we should remove all of the data, views and supporting code for the old data sets. This includes:

General Guidelines

SQL files for data
table definitions
View definitions
Profile sections (see the profile definitions in nepalmap_app/wazimap_np/)
Geographic data files

Specifics

Here are some things that need to be removed:

• all files in https://github.com/Code4Nepal/nepalmap_federal/tree/dev/sql
• all files in https://github.com/Code4Nepal/nepalmap_federal/tree/dev/sql/simpletables
• all .geojson and .topojson files in https://github.com/Code4Nepal/nepalmap_federal/tree/dev/wazimap_np/static/geo
• all files in https://github.com/Code4Nepal/nepalmap_federal/tree/dev/wazimap_np/templates/profile/sections
• all of the .py files in https://github.com/Code4Nepal/nepalmap_federal/tree/dev/wazimap_np except __init.__py, profiles.py, settings.py and tables.py

These files need cleaning up:

• https://github.com/Code4Nepal/nepalmap_federal/blob/dev/wazimap_np/templates/profile/profile_detail.html#L10-L19 needs all references to the profile html files removed.
• https://github.com/Code4Nepal/nepalmap_federal/blob/dev/wazimap_np/profiles.py needs all of the get_<some_profile_name>_profile methods removed, except the get_census_profile method.
• https://github.com/Code4Nepal/nepalmap_federal/blob/dev/wazimap_np/profiles.py needs all imports from wazimap_np removed.
• https://github.com/Code4Nepal/nepalmap_federal/blob/dev/wazimap_np/profiles.py needs the PROFILE_SECTIONS removed.
• https://github.com/Code4Nepal/nepalmap_federal/blob/dev/wazimap_np/tables.py needs all FieldTable and SimpleTable definitions removed.

During the conversion of federal data to the format needed for Wazimap in #11, there was variation in the geography.sql mapping and the data scraped at federal-data.

Creating this separate issue to track that.

Our data set for population is missing data for one locality in Province 6. The data are available in our "Federal Data" in https://github.com/Code4Nepal/data/.

Add the data to the population.sql file. Please put the data in a logical place -- so that all data for the same district are in rows next to each other. That will make it easier to review in the future.

• When you add them, you will add one row for female population and another row for male population. See the current file for examples.
• You will need to update the totals for the district for that locality to include these additional data.
• You will need to update the totals for Province 6 to include these additional data.
• You will need to update the totals for Nepal to include these additional data.

Here are the localities whose data are currently missing.

• "Bheri" in "Jajarkot" is "Bheri Malika Municipality" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%206/Jajarkot/Bheri%20Malika%20Municipality.csv

Our data set for population is missing data for one locality in Province 2. The data are available in our "Federal Data" in https://github.com/Code4Nepal/data/.

Add the data to the population.sql file. Please put the data in a logical place -- so that all data for the same district are in rows next to each other. That will make it easier to review in the future.

• When you add them, you will add one row for female population and another row for male population. See the current file for examples.
• You will need to update the totals for the district for that locality to include these additional data.
• You will need to update the totals for Province 2 to include these additional data.
• You will need to update the totals for Nepal to include these additional data.

Here are the localities whose data are currently missing.

• "Aaurahi" in Dhanusa district is "Aurahi Gaunpalika" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%202/Dhanusa/Aurahi%20Gaunpalika.csv

The parent_code for a locality must match the geo_code for the district to which it belongs. However, the parent codes for localities that are in "dis-01" through "dis-09" are wrong. They incorrectly leave out the "0", incorrectly listing the parent code as "dis-1", etc.

See, for example, these lines: https://github.com/Code4Nepal/nepalmap_federal/blob/dev/sql/geography.sql#L164-L171

The parent code should be "dis-01", not "dis-1" because the district they belong to has the geo_code of "dis-01".

This needs to be corrected so that the associations can be made correctly.

From a profile, click "Show data", then select "Map" tab. Map view does not display correctly. "Table" and "Distribution" display correctly.

Example:

https://beta.nepalmap.org/data/map/?table=POPULATION&primary_geo_id=local-4003&geo_ids=local|district-28

Should look something like this:
https://nepalmap.org/data/map/?table=DISABILITY_SEX&primary_geo_id=district-04&geo_ids=district|country-NP

Nepal Rastra Bank publishes data on its "Financial Inclusion Dashboard" at http://www.emap.nrb.org.np/. Evaluate those data sets to see if any of them might be useful for inclusion in NepalMap. Some basic rules for useful data:

• If we publish data for a given level, every geographic unit at that level must have data in the data set. For example, if we want to publish data at the district level, we must have data for each of the 77 districts. If we publish data at the local level, we must have data for each of the 753 localities.
• There must be a good way to visualize the data. The two major ways in which the Wazimap framework can present data are in histograms, bar charts and pie charts. For examples, see the pre-federal NepalMap, Counting India and South Africa's Wazimap.
• They are data that someone might be reasonably interested in seeing.

To fulfill this issue, you can evaluate the NRB data by

• trying to determine the smallest level at which a data set has data for every geographical unit
• trying to imagine if there is a good way to visualize those data in the Wazimap framework
• trying to determine who might be interested or why.

The full list of geographical areas that we have can be found in the SQL file at https://github.com/Code4Nepal/nepalmap_federal/blob/dev/sql/geography.sql. You may find it useful to see them in a map. To do so, follow the readme directions to run a local instance of the federal version of NepalMap.

The "About NepalMap" sections have been copied over from the pre-federal NepalMap. Review those sections and update them as appropriate.

They can be seen at the bottom of https://nm-fed.eastus.cloudapp.azure.com/ and on the about view at https://nm-fed.eastus.cloudapp.azure.com/about

National parks, hunting and wildlife reserves and development area have no official population (although I'm sure we all know that someone lives in them). For our purposes, add counts of zero for each national parks, hunting and wildlife reserve and development area in the table below.

Add the data to the population.sql file. Please put the data in a logical place -- so that all data for the same district are in rows next to each other. That will make it easier to review in the future.

• When you add them, you will add one row for female population and another row for male population. See the current file for examples.

Please see the readme at https://github.com/Code4Nepal/nepalmap_federal/tree/master/wazimap_np/static/geo for a description of the metadata needed.

Geojson and topojson files for updating can be downloaded from http://localboundries.oknp.org/

This script was used with the old structure to add to each geojson file the correct metadata: https://github.com/Code4Nepal/maptools/blob/master/geo/set_vdc_geo_properties.py. It may be useful as a sample for what needs doing.

This issue depends on #2

https://nm-fed.eastus.cloudapp.azure.com/profiles/ -- shows 404 (See text below from current 404 page).

let's find best practice for useful to show on 404 page.

Text:

Using the URLconf defined in wazimap.urls, Django tried these URL patterns, in this order:

^$ [name='homepage']
^about$ [name='about']
^help$ [name='help']
^profiles/(?P<geography_id>\w+-\w+)(-(?P<slug>[\w-]+))?/$ [name='geography_detail']
^embed/iframe.html$ [name='embed_iframe']
^(embed_data/)?profiles/(?P<geography_id>\w+-\w+)(-(?P<slug>[\w-]+))?\.json$ [name='geography_json']
^compare/(?P<geo_id1>\w+-\w+)/vs/(?P<geo_id2>\w+-\w+)/$ [name='geography_compare']
^api/1.0/data/show/latest$ [name='api_show_data']
^api/1.0/data/download/latest$ [name='api_download_data']
^api/1.0/table$ [name='api_list_tables']
^api/1.0/geo/(?P<geo_id>\w+-\w+)/parents$ [name='api_geo_parents']
^tables/(?P<table>[a-zA-Z0-9_-]+)/$ [name='table_detail']
^data/$ [name='table_search_redirect']
^data/(?P<format>map|table|distribution)/$ [name='data_detail']
^examples/(?P<example_slug>[-\w]+)/$ [name='example_detail']
^locate/$ [name='locate']
^healthcheck$ [name='healthcheck']
^robots.txt$
^place-search/json/$ [name='place_search_json']

The current URL, profiles/, didn't match any of these.

As per @ravinepal's comment at #22 (comment), the government of Nepal lists the province names as:

Province 1
Province 2
Province 3
Gandaki Province
Province 5
Karnali Province
Province 7

Update Province 4 to be Gandaki Province and Province 6 to be Karnali Province. This will require updating the geojson and topojson files as well as the geography SQL file.

See: https://www.nepal.gov.np/NationalPortal/EN

We are currently using the Caddy docker image 0.11.5. The most recent version of the Caddy docker image is 1.0.3. An attempt to run 1.0.3 on beta.nepalmap.org suggests there may be some adjustment that needs to be made in order to run 1.X.

This is what the error looks like when the caddy server tries to start

caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
caddy_1     | timeout: unrecognized option: t
caddy_1     | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1     |
caddy_1     | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1     |
caddy_1     | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1     | Default SIG: TERM.
caddy_1     | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1     | wait-for-it: strict mode, refusing to execute subprocess
nepalmapfederal_caddy_1 exited with code 1

For each section in the profile, add a link to the original data set to allow users to double-check our work and to provide more accountability and transparency. For example, the Households summary would have a link to the National Data Profile (http://nationaldata.gov.np) underneath the section where the total number of households is shown in NepalMap. Links should be as specific as possible but can be more general when specificity is not possible. For example, we do not currently have the ability to link to the National Data Profile pages for a specific locality or district or province, so a link to the main National Data Profile page is appropriate.

Our data set for population is missing data for three localities in Province 3. The data are available in our "Federal Data" in https://github.com/Code4Nepal/data/.

See this comment for a link to a Jupyter notebook created by @amitness . You may be able to adapt it for your work.

Add the data to the population.sql file. Please put the data in a logical place -- so that all data for the same district are in rows next to each other. That will make it easier to review in the future.

• When you add them, you will add one row for female population and another row for male population. See the current file for examples.
• You will need to update the totals for the districts for each of these localities to include these additional data.
• You will need to update the totals for Province 3 to include these additional data.
• You will need to update the totals for Nepal to include these additional data.

Here are the localities whose data are currently missing.

• "Tripura Sundari" in Dhadhing district is "Tripurasundari Gaunpalika" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%203/Dhading/Tripurasundari%20Gaunpalika.csv
• "Lalitpur" in "Lalitpur" is "Lalitpur Metropolitian City" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%203/Lalitpur/Lalitpur%20Metropolitian%20City.csv
• "Tarkeshwar" in "Nuwakot" is "Tarakeshwor Gaunpalika" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%203/Nuwakot/Tarakeshwor%20Gaunpalika.csv

Our data currently uses province numbers. However, some provinces have adopted names instead. We should update our wazimap_geography SQL data and geo data to reflect those names.

https://en.wikipedia.org/wiki/Provinces_of_Nepal

The current beta version doesn't display the navigation map.

Current version

What we need (similar like older version)

With #78, the text of the homepage was updated. There is an identical section in the about.html template: https://github.com/Code4Nepal/nepalmap_federal/blob/dev/wazimap_np/templates/about.html#L4-L24

This should be updated to match the homepage content at https://github.com/Code4Nepal/nepalmap_federal/blob/dev/wazimap_np/templates/homepage.html#L75-L103

We should be able to re-use the ones from https://github.com/Code4Nepal/nepalmap_app/tree/dev/wazimap_np/static/geo

@Crackjack - let's discuss soon :)

The current description on the main page is

Whether you live in Morang or Mahottari, find out how many people in your district have passed School Leaving Certificate (SLC), or how many people still use wood to cook food.

The "Find facts" description should also be revised. It says

Data is broken down by category: Demographics, education.

These both should be changed to reflect data that we currently provide in the federal version. They can be updated later with new suggested ideas for things to look for.

South Africa portal (https://wazimap.co.za/profiles/country-ZA-south-africa/) has this beautiful icon navigation located at the top. This will make the data navigation easy because users don't have to scroll through the whole page. Create/Develop something similar for NepalMap.

South Africa display

NepalMap display

I believe the text "Code for Nepal is entirely built by volunteers..." should be "NepalMap is entirely built by volunteers..."

https://github.com/Code4Nepal/nepalmap_federal/blob/dev/wazimap_np/templates/homepage.html#L96

I would also suggest we could link to the GitHub contributors for the project: https://github.com/Code4Nepal/nepalmap_federal/graphs/contributors

@cliftonmcintosh I was doing some cross-checking of data to national portal and looks like there was an issue with the way I was aggregating data to find country-level totals. I had missed filtering the data to province-level before aggregating. So it was aggregating all (province + district + local) causing incorrect country-level data, but no effect on bar graphs(since they are in %). I will create a PR soon to fix this for the already merged sections(demographics + household).

Creating this issue to track this.

Our data set for population is missing data for one locality in Province 7. The data are available in our "Federal Data" in https://github.com/Code4Nepal/data/.

Add the data to the population.sql file. Please put the data in a logical place -- so that all data for the same district are in rows next to each other. That will make it easier to review in the future.

• When you add them, you will add one row for female population and another row for male population. See the current file for examples.
• You will need to update the totals for the district for that locality to include these additional data.
• You will need to update the totals for Province 7 to include these additional data.
• You will need to update the totals for Nepal to include these additional data.

Here are the localities whose data are currently missing.

• "Dhangadhi" in "Kailali" is "Dhangadhi Sub-Metropolitian City" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%207/Kailali/Dhangadhi%20Sub-Metropolitian%20City.csv

For each district, we should be able to provide counts of the total number of polling places, the number mayoralities won by each political party in each district, and the number of deputy mayoralities won by each political party in each district. Please note that we must have data for every district in order for the Wazimap framework to be able to present data at the district level. If we do not have district-level breakdowns, then determine if province-level or national figures are available.

There is supposed to be data at http://result.election.gov.np/, but that timed out for me. @nikeshbalami may have a link to a data set.

If we have those data at the local level, please suggest a way that this can be effectively visualized in the Wazimap framework that is used for NepalMap.

Our data set for population is missing data for several localities in Province 5. The data are available in our "Federal Data" in https://github.com/Code4Nepal/data/. There are some individual localities for which data is currently missing. All localities for the district of Nawalparasi West, a.k.a., Parasi, is missing.

See this comment for a link to a Jupyter notebook created by @amitness . You may be able to adapt it for your work.

Add the data to the population.sql file. Please put the data in a logical place -- so that all data for the same district are in rows next to each other. That will make it easier to review in the future.

• When you add them, you will add one row for female population and another row for male population. See the current file for examples.
• You will need to update the totals for the districts for each of these localities to include these additional data.
• You will need to update the totals for Province 5 to include these additional data.
• You will need to update the totals for Nepal to include these additional data.

Here are the localities whose data are currently missing.

• "Janki" in Banke district is "Janaki" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%205/Banke/Janaki%20Gaunpalika.csv
• "Sudhdhodhan" in "Rupandehi" is "Suddhodhan Gaunpalika" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%205/Rupandehi/Suddhodhan%20Gaunpalika.csv

For Nawalparasi West, see the "Parasi" files at https://github.com/Code4Nepal/data/tree/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%205/Parasi

• “Bardaghat” as “Bardaghat Municipality"
• “Palhi Nandan” as “Palhinandan Gaunpalika”
• “Pratappur” as “Pratapapur Gaunpalika”
• “Ramgram” as “Ramgram Municipality”
• “Sarawal” as “Sarawal Gaunpalika”
• “Sunwal” as “Sunawal Municipality”
• “Susta” as “Susta Gaunpalika”

Our data set for population is missing data for one locality in Province 4. The data are available in our "Federal Data" in https://github.com/Code4Nepal/data/.

Add the data to the population.sql file. Please put the data in a logical place -- so that all data for the same district are in rows next to each other. That will make it easier to review in the future.

• When you add them, you will add one row for female population and another row for male population. See the current file for examples.
• You will need to update the totals for the district for that locality to include these additional data.
• You will need to update the totals for Province 4 to include these additional data.
• You will need to update the totals for Nepal to include these additional data.

Here are the localities whose data are currently missing.

• "Kaligandagi" in "Syangja" is "Kaligandaki Gaunpalika" in the federal population data: https://github.com/Code4Nepal/data/blob/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold/PRADESH%204/Syangja/Kaligandaki%20Gaunpalika.csv

Wazimap 1.0 appears to allow for different data sets from different time periods. Evaluate this capability to determine if it would allow us to have one instance that presents both pre-federal and federal data.

The South Africa Wazimap is here: https://wazimap.co.za/profiles/country-ZA-south-africa/
The release docs are here: https://wazimap.readthedocs.io/en/latest/version_history.html
A blog post about the new South Africa data: https://openup.org.za/articles/wazimap-2016-update.html

The outcome of this issue is to determine whether or not this capability can be used by NepalMap. If so, the outcome should also include a technical description of how the new capabilities work.

Please see the readme at https://github.com/Code4Nepal/nepalmap_app/tree/master/wazimap_np/static/geo for a description of the metadata needed.

Geojson and topojson files for updating can be downloaded from http://localboundries.oknp.org/

This script was used with the old structure to add to each geojson file the correct metadata: https://github.com/Code4Nepal/maptools/blob/master/geo/set_vdc_geo_properties.py. It may be useful as a sample for what needs doing.

This issue is related to #2.

Our geographic data uses "Nawalparasi East" and "Nawalparasi West", but our population data has "Nawal" and "Parasi". The wikipedia says that "Nawal" and "Parasi" are the correct names for those districts. Is that accurate? If so, we should create an issue to correct our geographic data.

The unit of measurement for land holdings is the hectare, but we do not specify what unit we are using. We should update the display so that it states that the units is the hectare.

Current view for land holdings:

Sample with unit specified in old NepalMap (for a different statistic):

Our geographic data includes hunting reserves, wildlife reserves and national parks, but we have no population data for those areas. Where do we get population data for them?

Population data

Parks and reserves without any population data

The parent geo_codes for localities appear to be incorrect in https://github.com/Code4Nepal/nepalmap_federal/blob/dev/sql/geography.sql

In spot-checking the data, I have found that the codes for the districts do not match the codes for the muncipalities that should be in each district.

I have based my comparison on personal knowledge of some districts as well as comparison of the data in https://github.com/Code4Nepal/data/tree/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold

Examples of discrepancies:
Achham is dis-01, but municipalities (like Sunsari) in Achham are listed as belonging to dis-69
Arghakhanchi is dis-02, but Arghakhanchi municipalities are listed as belonging to dis-51
Bhaktapur is dis-10, but Bhaktapur muncipalities are listed as belonging to dis-26
Dadeldhura is dis-13, but Dadeldhura muncipalities are listed as belonging to dis-73

This list is an example. It is not comprehensive. In my spot-checking, I have found no muncipalities with the correct parent code.

Find a way to update new/current local levels name at TopoJSON and GeoJSON file, so that the new name can be displayed at a map while hovering.

Here is the list of the changed local bodies name: https://docs.google.com/spreadsheets/d/1Y3Na_CEWLHERczUng_lGfpc4jl0qalVAmF3Aioc6VEc/edit?usp=sharing

Github link goes to the pre-federal repository at https://github.com/Code4Nepal/nepalmap_app. Update it so that it points to the federal repository.

Once the data for population has been integrated as part of #7 , present the total population with a breakdown by gender.

This includes:

• defining a table in the tables.py file based on the table created for #7.
• creating a profile for demographics, like the one in the pre-federal NepalMap. This should include a total population and a breakdown by gender.
• integrating that profile into the base profiles.py
• creating a view for demographics that shows total population and breakdown by gender. See https://github.com/Code4Nepal/nepalmap_app/blob/dev/wazimap_np/templates/profile/profile_detail.html and https://github.com/Code4Nepal/nepalmap_app/blob/dev/wazimap_np/templates/profile/sections/demographics.html for an example of how this has been done in the pre-federal NepalMap.

Data sets for this are here: https://github.com/Code4Nepal/data/tree/master/Federal%20Data/753%20Local%20Unit%20Population%20and%20HouseHold
This only has provinces 1 and 2 right now, though.

Create the SQL data for the geographic units for the new federal structure.

At each level, the geo_code should be unique. For example, for local bodies, there can only be one local body in the entire country with a geo_code of "1".
Except for top-level of "Nepal", each record should include its parent's geo_code as well as the geographic level of its parent.

Please see the current data for an example of how it is structured.

In looking back at the scripts that were used 2 years ago, it appears that the geojson files were manipulated to include the correct metadata and then the SQL data was created from those files. If it seems like that is the way to do things this time, too, then this task should wait until after #3, #4, and #5 are complete.

See the scripts in the maptools project at https://github.com/Code4Nepal/maptools/tree/master/geo.

While reviewing the population data, we found many spelling mistakes of local levels name in geography.sql file.

If possible update the SQL file will full name, for example, "Kathmandu" with "Kathmandu Metropolitan City" and so on, this will make the data adding part easier for upcoming days.

Will soon create and share a new sheet with existing geo_code; to discuss the possibilities.

It says only population data, Since we already have more data now, it will be great to update those text.

This project is currently running on Wazimap 0.8.2, which uses Python 2.7. Python 2.7 is reaching end of life at the end of 2019. This project should be upgraded to the latest version of Wazimap, which includes an upgrade to Python 3.

There are breaking changes from 0.8.2 to 1.0.0 of Wazimap that will need to be dealt with. There are also breaking changes from 1.X Wazimap to 2.X Wazimap.

I would recommend a stepped approach by upgrading to 1.X and, from there, to 2.X.

Documentation
The Wazimap docs up to version 1.0.0, which documents the breaking changes in 1.0.0: https://wazimap.readthedocs.io/en/latest/version_history.html
The Wazimap repo's changelog that includes the update to 2.1.0: https://github.com/OpenUpSA/wazimap/blob/master/CHANGES.rst