-
Notifications
You must be signed in to change notification settings - Fork 19
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
Must be able to display disputed borders #788
Comments
@tonio will look into this next week. |
I will provide links by email to an updated ADM boundary layer, that attribute the northern Jammu&Kashmir ADM0 area to Pakistan -- I changed the ADM0 name -- and the southern area to India (there are two areas called Jammu&Kashmir in the version used currently). The new files are date labelled 020217. Edit: I realised this won't work, as it effectively shows J&K as part of the countries without a disputed border, which is not correct either. |
If we adjust only the ADM0 code in the underlying boundary files, to match India (southern J&K) and Pakistan (northern J&K) would that enable J&K to be assigned hazard levels and also show India+J&K together on the map, or does the process also rely on the ADM unit name? |
I cannot answer this. We will have to wait for Antoine and François to return next week. |
There might be no matching regions between administrative divisions and Hazard set. |
Contingent on resolving #818 |
A python script is available in Thinkhazard/Basemap_processing for editing original WB boundaries into SHP for thinkhazard.
|
We need to be able to show disputed borders on the map,
Jammu and Kashmir area is key example:
See dashed lines in the below World Bank map. We have a field, DISP_AREA, in the attributes of the files g2015_2014_0_upd270117 / g2015_2014_1_upd270117 / g2015_2014_2_upd270117
At each level, where DISP_AREA=YES, the border should be displayed as dashed. DISP_AREA=NO should remain solid
The text was updated successfully, but these errors were encountered: