Viet Nam coordinate system in RiskScape

Community
1

Hi,

I’m in the process of creating a step-by-step guideline for our Vietnam partners for MFAT funded dam safety project, but I’ve run into an issue.

I’m working with the vn2000_108mui3 coordinate system, which is used for Dak Lak and Phu Yen Provinces in central/southern Vietnam—two of our five case study provinces. This coordinate system is also equivalent to EPSG:9210, according to Google.

However, when I try to run RiskScape, I encounter the following error message. Is this something that will be addressed in a future update of the RiskScape engine, or does it simply mean that EPSG:9210 is not currently supported within the library?

Looking forward to your thoughts!

Cheers

ShengLin

Note that I defined it in bookmark as below,

[bookmark Building]
description = Dak Lak mockup buildings
location = data/DL_bldg_mk_vn2000.shp
crs-name = EPSG:9210

Could not find a Coordinate Reference System (CRS) called ‘EPSG:9210’ - check the CRS name carefully or try searching for it online. Make sure you have included the authority as well as the code, e.g. ‘EPSG:2193’ vs ‘2193’. For WGS84, try ‘EPSG:4326’ (lat, long) or ‘CRS:84’ (long, lat). Most valid EPSG codes should work with RiskScape.

2

Hi ShengLin,

It looks as though that code is not in RiskScape’s database, but assuming it’s a transverse mercator projection (it looks to be), there shouldn’t be any reason I can see why the projection itself shouldn’t work.

Does the shapefile have a prj file, e.g. data/DL_bldg_mk_vn2000.prj?

If it does, first try removing the crs-name parameter from your bookmark and see if your model runs. If it runs but you’re not getting any results (or you get an error) it’s possible that the provided prj file is in a non-standard format. In that case, you can replace the contents of that file with this using a text editor. That provides the definition of the projection in a format that RiskScape can understand.

Let me know how you get on,

Nick

3

Thanks for the quick tips, Nick!

Everything worked perfectly after removing the crs-name—both the inputs and outputs are now in the same locations and CRS.

Just for the record, the analysis did complete previously; the issue was that the results weren’t aligned correctly, likely due to a mix-up between the crs-name and the *.prj file.

Cheers

ShengLin

1 Like