GeoEra-GIP / Project-Support-WP8

Science Project Data provider support
https://geoera-gip.github.io/support/
7 stars 2 forks source link

Reprojecting datasets documentation and implications for global datasets #346

Open nmtoken opened 3 years ago

nmtoken commented 3 years ago

Re documentation:

http://egdi-public.gitlabpages.geus.dk/egdi-documentation/#/main-content/SpatialData?id=projections

THe EGDI platform by default displays maps and data sets in projection EPSG:3034. If necessary, individual maps can be set up in other projections, but included data sets will then have to also support that projection or be able to be re-projected on the fly. On the fly re-projection can slow down the map and also distort the details of images.

The EGDI platform by default delivers data sets as WMS in the following projection EPSG:4326, EPSG:4258, EPSG:3043, EPSG:3044, EPSG:3045, EPSG:25831, EPSG:25832, EPSG:25833, EPSG:32631, EPSG:32632, EPSG:32633, EPSG:32618, EPSG:32619, EPSG:32620, EPSG:32621, EPSG:32622, EPSG:32623, EPSG:32624, EPSG:32625, EPSG:32626, EPSG:32627, EPSG:32628, EPSG:3034, EPSG:900913 and EPSG:3857.

Setting aside that there is no EPSG:900913 :)

THe EGDI platform by default displays maps and data sets in projection EPSG:3034.

Does that mean that other projections will be allowed to be selected, if so which ones will be selectable?

If necessary, individual maps can be set up in other projections, but included data sets will then have to also support that projection or be able to be re-projected on the fly

If datasets are provided as services for consumption by the EGDI portal I can see that they must provide support for the supported projections, but I don't understand the implications for supplied datasets. Surely the EGDI platform services/API will do the necessary reprojections.

For HOVER we have a global dataset, whilst EPSG:3034 is limited to Europe, what are the implications for the dataset?

PROJCRS["ETRS89-extended / LCC Europe", BASEGEOGCRS["ETRS89", ENSEMBLE["European Terrestrial Reference System 1989 ensemble", MEMBER["European Terrestrial Reference Frame 1989", ID["EPSG",1178]], MEMBER["European Terrestrial Reference Frame 1990", ID["EPSG",1179]], MEMBER["European Terrestrial Reference Frame 1991", ID["EPSG",1180]], MEMBER["European Terrestrial Reference Frame 1992", ID["EPSG",1181]], MEMBER["European Terrestrial Reference Frame 1993", ID["EPSG",1182]], MEMBER["European Terrestrial Reference Frame 1994", ID["EPSG",1183]], MEMBER["European Terrestrial Reference Frame 1996", ID["EPSG",1184]], MEMBER["European Terrestrial Reference Frame 1997", ID["EPSG",1185]], MEMBER["European Terrestrial Reference Frame 2000", ID["EPSG",1186]], MEMBER["European Terrestrial Reference Frame 2005", ID["EPSG",1204]], MEMBER["European Terrestrial Reference Frame 2014", ID["EPSG",1206]], ELLIPSOID["GRS 1980",6378137,298.257222101, LENGTHUNIT["metre",1,ID["EPSG",9001]], ID["EPSG",7019]], ENSEMBLEACCURACY[0.1], ID["EPSG",6258]], PRIMEM["Greenwich",0, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]], ID["EPSG",8901]], ID["EPSG",4258]], CONVERSION["Europe Conformal 2001", METHOD["Lambert Conic Conformal (2SP)", ID["EPSG",9802]], PARAMETER["Latitude of false origin",52, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]]], PARAMETER["Longitude of false origin",10, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]]], PARAMETER["Latitude of 1st standard parallel",35, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]]], PARAMETER["Latitude of 2nd standard parallel",65, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]]], PARAMETER["Easting at false origin",4000000, LENGTHUNIT["metre",1,ID["EPSG",9001]]], PARAMETER["Northing at false origin",2800000, LENGTHUNIT["metre",1,ID["EPSG",9001]]], ID["EPSG",19985]], CS[Cartesian,2, ID["EPSG",4500]], AXIS["Northing (N)",north, ORDER[1]], AXIS["Easting (E)",east, ORDER[2]], LENGTHUNIT["metre",1,ID["EPSG",9001]], USAGE[SCOPE["Conformal mapping at scales of 1:500,000 and smaller."], AREA["Europe - European Union (EU) countries and candidates. Europe - onshore and offshore: Albania; Andorra; Austria; Belgium; Bosnia and Herzegovina; Bulgaria; Croatia; Cyprus; Czechia; Denmark; Estonia; Faroe Islands; Finland; France; Germany; Gibraltar; Greece; Hungary; Iceland; Ireland; Italy; Kosovo; Latvia; Liechtenstein; Lithuania; Luxembourg; Malta; Monaco; Montenegro; Netherlands; North Macedonia; Norway including Svalbard and Jan Mayen; Poland; Portugal including Madeira and Azores; Romania; San Marino; Serbia; Slovakia; Slovenia; Spain including Canary Islands; Sweden; Switzerland; Turkey; United Kingdom (UK) including Channel Islands and Isle of Man; Vatican City State."], BBOX[24.60,-35.58,84.17,44.83]], ID["EPSG",3034]]

mh-geus-dk commented 3 years ago

Setting aside that there is no EPSG:900913 :)

Yes, EPSG:900913 is deprecated and replaced by EPSG:3857 but nevertheless still being used by many.

Does that mean that other projections will be allowed to be selected, if so which ones will be selectable?

In principle, the web-GIS can display maps in all EPSG codes but we recommend sticking to EPSG:3034 because it is well-tested and other projections will involve work for GIP to adjust base maps, tools, and other functionality.

If datasets are provided as services for consumption by the EGDI portal I can see that they must provide support for the supported projections, but I don't understand the implications for supplied datasets. Surely the EGDI platform services/API will do the necessary reprojections. For HOVER we have a global dataset, whilst EPSG:3034 is limited to Europe, what are the implications for the dataset? Global data sets can be delivered in e.g. EPSG:4326 or EPSG:3857. In case your data set is contains lines or polygons that cross the poles it's more tricky and we might need to investigate further in order to give the best advise.

nmtoken commented 3 years ago

There never was an EPSG:900913 not that it's deprecated, it never existed, that is, there never was a code 900913 in the EPSG Geodetic Parameter Dataset; I know though that doesn't stop people advertising that they support it.

EPSG:3857 is not global coverage, it cuts off the poles, which is problematic for some Arctic (and less important for Europe Antarctic) datasets.

In principle, the web-GIS can display maps in all EPSG codes but we recommend sticking to EPSG:3034 because it is well-tested and other projections will involve work for GIP to adjust base maps, tools, and other functionality.

I'm still not sure what this means for portal functionality, does it mean that a viewer can request to view any data in any EPSG code, and indeed any CRS code, (for example CRS:84 used by GeoJSON), in the Web GIS, or does it mean that the Web GIS will only support a limited number of projections, (the by default list)?

For the HOVER dataset (NetCDF or GeoTIFF) data will be in EPSG:4326, if viewing the data in EPSG:4326 is possible in the Web GIS then there is no issue. Reprojecting will be possible, but likely problematic