categori.se

Aaron Kyle Dennis

A few notes (before I forget):
- we can indicate that this is for the current admin area (as of the time of writing)
- we can link to a discussion on pre-2015 admin area, and provide what we have for official spatial data files
- we can link to my notebook walkthrough of available data on the web to point to non-official data

Also refer to: https://mofald.gov.np/en/vdc

To do: 
* find ward-level list and append information into data file.
* add interface to select and download specific shapes for each sub-national administrative level.

I generated this from a MOFAGA PDF file, which is still available online and attached to this notebook as a PDF.  @Josh - There is still some clean-up work needed: a few places where we don't have an entry for municipality/rural municipality in Nepali due to the way I parsed the text.  There also appear to be a few bad characters in there.  I would like help to clean this up more.... then I would like to append these data into our `local_unit` data for a more complete and robust set of properties.

... leaving this in as a reminder that we should also find a way to encode in the ward-level data.... and we also ought to search for ward-level shapefiles... (later).

Any idea of we can make this zoomable? (e.g. w/ d3.zoom)?

Saneef H. Ansari

Thanks - and thanks for leaving the original function commented it!  I don't like the default zoom on these SVG.  Particularly on full width renderings, one's mouse tends to catch the window and start zooming the image rather than scrolling the page. I was / am interested to enable pan and zoom... particularly as we move into other ways of dealing with SVG that are intended to be printed at original view, but which contain lots of very small data (e.g. cadastral plots).  I've disabled this for now... Let's talk more about different options and approaches.

Here I intend to expose the 'extra' data that encoded into this dataset.  Work in progress.

We also should introduce  (above) the extra information provided by these datasets, and share more about the steps we're taking to link everything together... resulting is a nice, ADB "official" reference file. We'll start at the highest quality, and then present how to simplify.

To make sure I understand this correctly, your function for cross-checking and extending the JSON data is part of the export feature?  Above, I also wish to demonstrate how one can join together different data sources.  Could you also help to demonstrate there? https://observablehq.com/@adb/nepal-official-spatial-data-on-administrative-divisions#cell-710

Here, fields `GaPa_NaPa` and `DISTRICT` are from GeoJSON. Rest of the fields from matched data set from `admin_fcgo`.

Let's talk about the structure of the returned data at some point.

... After we finalize our fuse approach we'll move the content down a few cells. Leaving at the top for now to keep comments grouped.

We'll also need to comment on the 'missing' records.

These are the features that are missing the data

Cool. Let's talk about how to present this.  Also, would be interested to look more into issues e.g. matching while taking in variations in capitalization.

Also: Let's address names of provinces:
ID	Name		Name - Local
	1	Province 1		प्रदेश नं. १
	2	Province 2		मधेश प्रदेश
	3	Province 3		बागमती प्रदेश
	4	Province 4		गण्डकी प्रदेश
	5	Province 5		लुम्बिनी प्रदेश
	6	Province 6		कर्णाली प्रदेश
	7	Province 7		सुदुर पश्चिम प्रदेश

I had forgotten to add a note about how data matching is done last week. Here it is.