luomus / laji

Frontend for Finnish Biodiversity Information Facility (FinBIF) data portal laji.fi (and other *.laji.fi frontends)
MIT License
7 stars 0 forks source link

Use of Non-Standard CRS Names #556

Open AlpoTurunen opened 1 month ago

AlpoTurunen commented 1 month ago

As a user downloading or inputting occurrences into our systems, it might be difficult to understand coordinate reference systems as we are not using standard naming conventions.

Terms like "euref-fin" are unclear, as they do not specify a projection or coordinate order. There are multiple coordinate systems with the same or similar names. Actually "euref-fin" doesn't even refer to a coordinate system, it's only a datum.

My suggestion is to use standardized CRS names with EPSG codes to avoid possible errors:

mikkohei13 commented 1 month ago

For usability, the names need to be understandable in a short form. E.g. I would see them most often on Vihko Excel import files, which could show the first ~5 characters like this (column G):

image

YKJ is standard abbreviation for biologists (see https://laji.fi/about/5310), so it should be the primary name for this coordinate type.

So if we change these, I would suggest name like "YKJ (EPSG:2393)" or "YKJ yhtenäiskoordinaatisto (EPSG:2393)"

I don't know would this kind of change require any development work? Might be possible by just

This relates to epics about improving data usability: Obs download fieldnames, Field expansion, API v1.

AlpoTurunen commented 1 month ago

Yes, YKJ is good as well. I edited it to my original message. And this is not super important, just nice to have :). I am editing this comment as a test. Will is the best