[GRASS-dev] New GUI startup: Next steps in GSoC and beyond
Helmut Kudrnovsky
hellik at web.de
Sun Jul 12 02:24:35 PDT 2020
Hi Vaclav, all,
wenzeslaus wrote
> Testing the Location Wizard and Data tab in
> GRASS GIS (from master branch) is also a good way.
just tested master with
GRASS Version: 7.9.dev
Code revision: e321f7589
Build date: 2020-07-11
Build platform: x86_64-w64-mingw32
GDAL: 3.0.4
PROJ: 6.3.2
GEOS: 3.8.1
SQLite: 3.29.0
Python: 3.7.0
wxPython: 4.0.7
Platform: Windows-10-10.0.19041-SP0 (OSGeo4W)
nice work!
maybe something for beyond GSoC:
EPSG is reworking their data models [1] and website/web services:
"Following the publication of the revised ISO 19111:2019 data model, IOGP is
in the process of upgrading the EPSG data model. The changes to the data
model being applied to the v10.0 EPSG Dataset and Dataset available via the
Beta Site are:
- Identification of dynamic datums and of CRSs based on these. For datums
and CRSs affected by this change, there will be no changes to existing EPSG
codes.
- Addition of a new construct of ‘datum ensemble’. A datum ensemble groups
together successive realizations of a datum as one. Some CRSs will be
associated with a datum ensemble rather than a single datum. These will
include the generic WGS 84 CRSs (EPSG CRS codes 4326 [geographic 2D], 4979
[geographic 3D] and 4978 [geocentric]). Existing EPSG codes will be
unchanged.
- Addition of a new CRS subtype ‘derived projected’. The term is from the
ISO model and is consistent with other terms in the model, but is a
misnomer. It is a CRS which is based upon an existing projected CRS, so
‘derived from projected’ would be a more accurate description. Many seismic
bin grids are defined relative to a projected CRS – others are defined
independently and later referenced to a projected CRS. Examples of both
approaches will be included in the upgraded dataset.
- Some CRS, datum or coordinate operation entities will be associated with
multiple ‘usages’ – scope/extent (area) pairings."
new PROJ library versions (>=7 AFAIK) will be considering partly these
changes.
a GeoRepository API [2] will be available to query the official EPSG
database.
in future it may be worth to link to the offical EPSG web services/database
instead to epsg.io.
[1] https://epsg.org/data-model-changes.html
[2] https://apps.epsg.org/api/swagger/ui/index
-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
More information about the grass-dev
mailing list