Open bennyistanto opened 2 months ago
Using projection EPSG:32632, some of the test going well, and some has an error. The problem, warning and error are similar with what I have in Fiji test.
Link: https://drive.google.com/file/d/1euhgy5oQVPi_B-sUpQUMUjJrp30dYxAj/view?usp=drive_link All data has been converted into EPSG:32632
Thanks for this really detailed breakdown @bennyistanto. Just a question regarding CRS: is there any reason we can't just use epsg:3857 spherical Mercator? I think the accuracy loss will be minimal and we can avoid complicated workflows.
@timlinux Please see the child tickets below:
Thanks for this really detailed breakdown @bennyistanto. Just a question regarding CRS: is there any reason we can't just use epsg:3857 spherical Mercator? I think the accuracy loss will be minimal and we can avoid complicated workflows.
Hi @timlinux I did test using epsg:3857 and it's also working fine for most country. I don't know the idea behind why we use different projection for each country as written on this https://worldbank.github.io/GEEST/docs/user_guide.html#list-of-crss-for-sids My best guess would be on accuracy and distortion. The team try to avoid significant distortion on higher latitude.
But the epsg:3857 really not working on country like Fiji which located in 180th meridian and the area will be splitted. @dragosgontariu spent lot of time to work on Fiji without succeed (with various error), then he splitted the country into 2 file (west and east), and still experienced an error in some step.
Other reason will be the availability and geometry quality of the boundary it self. We rely on HDX for each country boundary. And for the case of Fiji, the boundary from HDX using World_Merctor_150
, is a modified Mercator projection centered on the 150E, and no standard EPSG code for this.
So, I decided to use epsg:8859 as alternative and it will recognized by QGIS.
Below picture is the Fiji boundary using 3857, translated from World_Merctor_150.
So there is a pretty crazy bug here, I am quite surprised how anything ever worked:
Above you can see what the signature for creating a vector layer is
Below we can see the original author (1) created a vector file (2) using the geojson dump of that file (I mean the actual json data, not the file handle) as its URI (3)
Also the processing tools as you rightly surmised @bennyistanto do not omit invald geometries. I have added logic that can let us do that but I need to work through each processing call and make sure that is set up...
Also the idea of writing utm data to geojson is not sound since geojson requires the data be in 4326:
Fiji, Test 12 Sep 2024
QGIS LTR 3.34.4 and GEEST 0.1.64 (Sent by Michelle via email on 5 Sep 2024) running on Windows 11 Pro
Initial Configuration
QGIS Processing Options: General > Invalid features filtering. Set to > Skip (ignore) features with invalid geometries
Projection: EPSG:8859
Fiji located in 180th meridian. Using Geographic projection EPSG:4326, it will splitted into different areas, while using UTM also divided into 2 zone. EPSG:8859 might the best option for Fiji as the projection will set the World centred on Asia and Pacific
Data
Link: https://drive.google.com/file/d/1-3UpliiCotIfNoTtB6_CmQoBjrj6z6bX/view?usp=sharing All data has been converted into EPSG:8859
Test result
FYI, @ClaraIV @mvmaltitz
Contextual
Each Factors in Contextual Dimension completed.
Contextual_score also succeed with some Python error. Although the Contextual_score.tif exist but the value is incorrect, then it means the script failed to generate the correct value and save as a file.
Accessibility
Women Travel Pattern
Women Travel Patterns completed successfully for each factors, which rely on ORS.
But aggregating the output into final WTP trigger a warning, although the file successfully created
Public Transport
Public Transport completed with Python error below. The file mentioned below is not used in other windows. My Windows only has 1 QGIS open for running GEEST.
Education and Training Facilities
Education and Training Facilities completed with Python error below. The file mentioned below is not used in other windows.
Health Facilities
Health Facilities completed with Python error below. The file mentioned below is not used in other windows
Financial Facilities
Financial Facilities completed with Python error below. The file mentioned below is not used in other windows
Accessibility Aggregate
Accessibility aggregate completed and file also successfully created and loaded as a layer in the map. But it also trigger a Python error below
Place Characterization
Active Transport
Active Transport is not responding without any error information, not long after pressing the Execute button
Safety
Safety trigger a warning on OGR when open the NTL data, although the data is available and loaded into map, dragged from Explorer window.
After Execute the button, the label next to the button appear with text:
See below the python warning
And below the Processing log
And OGR log
Digital Inclusion
Digital Inclusion working perfectly without any warning
Environmental Hazard
Progress Label show that Processing Complete!, but unfortunately no output files are generated. See the Processing log below.
Using self and manually generated Hazard layer and renamed following the Plugin requirement, the Aggregate Natural Disaster Risk also tested and it works perfectly with some warning in projection
Education
Education working perfectly
Fragility, Conflict, and Violence
FCV is not responding without any error information, not long after pressing the Execute button
Water and Sanitation
Water process failed. The label next to Execute button appear with text
And trigger a Python error below
And the Processing log below
Aggregate on Place Characterization
Using self and manually generated other Factors that failed during process via Plugin, the Place score aggregation also experiencing an error with trigger Python error below
And Python warning below
Final Aggregate
Using self and manually generated Place_score.tif, the final aggregation has been tested and failed, with below Python error
And Python warning
Insight
Step 1 Classify into discrete layer both completed
Step 2 Combined score also completed
Step 3 Aggregation also completed with warning on invalid geometries. See below