http://c7700.com/list-19.html,Migration to PROJ6/GDAL3

最新推荐文章于 2022-12-05 10:30:21 发布
最新推荐文章于 2022-12-05 10:30:21 发布
阅读量1k 收藏 1
点赞数
文章标签： http://c7700.com/list-19.html
博客围绕坐标操作展开，介绍了在搜索可实例化坐标操作时，丢弃基准面信息对结果的影响。通过具体示例展示了不同情况下，如添加有效基准面标签、直接定义查找术语等，对找到的坐标操作数量和精度的影响。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

Coordinate operations

library(rgdal)

## rgdal: version: 1.5-1, (SVN revision 870)

## Geospatial Data Abstraction Library extensions to R successfully loaded

## Loaded GDAL runtime: GDAL 3.0.2, released 2019/10/28

## Path to GDAL shared files:

## GDAL binary built with GEOS: TRUE

## Loaded PROJ.4 runtime: Rel. 6.2.1, November 1st, 2019, [PJ_VERSION: 621]

## Path to PROJ.4 shared files: (autodetected)

## Linking to sp version: 1.3-3

run

We can first show what happens when searching for instantiable coordinate operations. These are coordinate operations that can be created by look-up in the PROJ database given the information in the input description. Here the datum has been discarded.

(discarded_datum

## Warning in showSRID("EPSG:27700", "PROJ"): Discarded datum OSGB 1936 in Proj4

## definition

## [1] "+proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000 +y_0=-100000 +ellps=airy +units=m +no_defs +type=crs"

## Warning in showSRID("EPSG:27700", "PROJ"): Discarded datum OSGB_1936 in CRS

## definition

Consequently, when searching for coordinate operations to transform to geographical coordinates and the WGS84 datum, and using importFromProj4() to instantiate the source SRS, the only operation found only has the Airy ellipse information to guide its search. The list_coordOps() function takes two SRS descriptions, and returns coordinate operations found by look-up. We need to add the type tag to a PROJ string here.

(x

## Candidate coordinate operations found: 1

## Strict containment: FALSE

## Visualization order: TRUE

## Source: +proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000

## +y_0=-100000 +ellps=airy +units=m +no_defs +type=crs

## +type=crs

## Target: EPSG:4326

## Best instantiable operation has only ballpark accuracy

## Description: Inverse of unknown + Ballpark geographic offset from unknown to

## WGS 84 + axis order change (2D)

## Definition: +proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2

## +k=0.9996012717 +x_0=400000 +y_0=-100000

## +ellps=airy +step +proj=unitconvert +xy_in=rad

## +xy_out=deg

## Candidate coordinate operations found: 1

## Strict containment: FALSE

## Visualization order: TRUE

## Source: +proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000

## +y_0=-100000 +ellps=airy +units=m +no_defs +type=crs

## Target: EPSG:4326

## Best instantiable operation has only ballpark accuracy

## Description: Inverse of unknown + Ballpark geographic offset from unknown to

## WGS 84 + axis order change (2D)

## Definition: +proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2

## +k=0.9996012717 +x_0=400000 +y_0=-100000

## +ellps=airy +step +proj=unitconvert +xy_in=rad

## +xy_out=deg

The best_instantiable_coordOp() function retuns the best instantiable coordinate operation, in this case the only one, with a description attribute. This is the current best available in calling spTransform() with "CRS" objects with discarded +datum= tags.

best_instantiable_coordOp(x)

## Warning in best_instantiable_coordOp(x): Best instantiable operation has only

## ballpark accuracy

## [1] "+proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000 +y_0=-100000 +ellps=airy +step +proj=unitconvert +xy_in=rad +xy_out=deg"

## attr(,"description")

## [1] "Inverse of unknown + Ballpark geographic offset from unknown to WGS 84 + axis order change (2D)"

## Warning in best_instantiable_coordOp(x): Best instantiable operation has only

## ballpark accuracy

## [1] "+proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717

## +x_0=400000 +y_0=-100000 +ellps=airy +step +proj=unitconvert +xy_in=rad +xy_out=deg"

## attr(,"description")

## [1] "Inverse of unknown + Ballpark geographic offset from unknown to WGS 84 +

## axis order change (2D)"

If we add back the discarded +datum= tag with a valid value, we give the search process what it needs to find more coordinate operations.

list_coordOps(paste0(discarded_datum, " +datum=OSGB36 +type=crs"), "EPSG:4326")

## Candidate coordinate operations found: 9

## Strict containment: FALSE

## Visualization order: TRUE

## Source: +proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000

## +y_0=-100000 +ellps=airy +units=m +no_defs +type=crs

## +datum=OSGB36 +type=crs

## Target: EPSG:4326

## Best instantiable operation has accuracy: 2 m

## Description: Inverse of unknown + axis order change (2D) + OSGB 1936 to WGS

## 84 (6) + axis order change (2D)

## Definition: +proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2

## +k=0.9996012717 +x_0=400000 +y_0=-100000

## +ellps=airy +step +proj=push +v_3 +step +proj=cart

## +ellps=airy +step +proj=helmert +x=446.448

## +y=-125.157 +z=542.06 +rx=0.15 +ry=0.247 +rz=0.842

## +s=-20.489 +convention=position_vector +step +inv

## +proj=cart +ellps=WGS84 +step +proj=pop +v_3 +step

## +proj=unitconvert +xy_in=rad +xy_out=deg

## Operation 8 is lacking 1 grid with accuracy 1 m

## Missing grid: uk_os_OSTN15_NTv2_OSGBtoETRS.tif

## URL: https://cdn.proj.org/uk_os_OSTN15_NTv2_OSGBtoETRS.tif

Now we have 7 operations, one the ballpark accuracy operation with unknown accuracy found above, 5 others that can be instantiated, of which the best has 2m accuracy, and an operation that cannot be instantiated because a publically available grid is missing. On download and installation of this grid, 1m accuracy could be achieved.

## Candidate coordinate operations found: 7

## Strict containment: FALSE

## Visualization order: TRUE

## Source: +proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000

## +y_0=-100000 +ellps=airy +units=m +no_defs

## +datum=OSGB36 +type=crs

## Target: EPSG:4326

## Best instantiable operation has accuracy: 2 m

## Description: Inverse of unknown + axis order change (2D) + OSGB 1936 to WGS

## 84 (6) + axis order change (2D)

## Definition: +proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2

## +k=0.9996012717 +x_0=400000 +y_0=-100000

## +ellps=airy +step +proj=push +v_3 +step +proj=cart

## +ellps=airy +step +proj=helmert +x=446.448

## +y=-125.157 +z=542.06 +rx=0.15 +ry=0.247 +rz=0.842

## +s=-20.489 +convention=position_vector +step +inv

## +proj=cart +ellps=WGS84 +step +proj=pop +v_3 +step

## +proj=unitconvert +xy_in=rad +xy_out=deg

## Operation 6 is lacking 1 grid with accuracy 1 m

## Missing grid: OSTN15_NTv2_OSGBtoETRS.gsb

## URL: https://download.osgeo.org/proj/proj-datumgrid-europe-latest.zip

If we pass the source WKT string to list_coordOps() we get 6 operations back, now without the ballpark accuracy operation; this would be the situation in which WKT comments if present were used to construct the source and target SRS:

wkt_source_datum

wkt_target_datum

(x

## Candidate coordinate operations found: 9

## Strict containment: FALSE

## Visualization order: TRUE

## Source: PROJCRS["OSGB 1936 / British National Grid", BASEGEOGCRS["OSGB

## 1936", DATUM["OSGB 1936", ELLIPSOID["Airy 1830",

## 6377563.396, 299.3249646, LENGTHUNIT["metre", 1]]],

## PRIMEM["Greenwich", 0, ANGLEUNIT["degree",

## 0.0174532925199433]], ID["EPSG", 4277]],

## CONVERSION["British National Grid", METHOD["Transverse

## Mercator", ID["EPSG", 9807]], PARAMETER["Latitude of

## natural origin", 49, ANGLEUNIT["degree",

## 0.0174532925199433], ID["EPSG", 8801]],

## PARAMETER["Longitude of natural origin", -2,

## ANGLEUNIT["degree", 0.0174532925199433], ID["EPSG",

## 8802]], PARAMETER["Scale factor at natural origin",

## 0.9996012717, SCALEUNIT["unity", 1], ID["EPSG", 8805]],

## PARAMETER["False easting", 400000, LENGTHUNIT["metre",

## 1], ID["EPSG", 8806]], PARAMETER["False northing",

## -100000, LENGTHUNIT["metre", 1], ID["EPSG", 8807]]],

## CS[Cartesian, 2], AXIS["(E)", east, ORDER[1],

## LENGTHUNIT["metre", 1]], AXIS["(N)", north, ORDER[2],

## LENGTHUNIT["metre", 1]], USAGE[ SCOPE["Engineering

## survey, topographic mapping."], AREA["United Kingdom

## (UK) - offshore to boundary of UKCS within 49°45'N to

## 61°N and 9°W to 2°E; onshore Great Britain (England,

## Wales and Scotland). Isle of Man onshore."],

## BBOX[49.75, -9, 61.01, 2.01]], ID["EPSG", 27700]]

## Target:

## GEOGCRS["WGS 84 (with axis order normalized for

## visualization)", DATUM["World Geodetic System 1984",

## ELLIPSOID["WGS 84", 6378137, 298.257223563,

## LENGTHUNIT["metre", 1]], ID["EPSG", 6326]],

## PRIMEM["Greenwich", 0, ANGLEUNIT["degree",

## 0.0174532925199433], ID["EPSG", 8901]], CS[ellipsoidal,

## 2], AXIS["geodetic longitude (Lon)", east, ORDER[1],

## ANGLEUNIT["degree", 0.0174532925199433, ID["EPSG",

## 9122]]], AXIS["geodetic latitude (Lat)", north,

## ORDER[2], ANGLEUNIT["degree", 0.0174532925199433,

## ID["EPSG", 9122]]]]

## Best instantiable operation has accuracy: 2 m

## Description: Inverse of British National Grid + OSGB 1936 to WGS 84 (6) +

## axis order change (2D)

## Definition: +proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2

## +k=0.9996012717 +x_0=400000 +y_0=-100000

## +ellps=airy +step +proj=push +v_3 +step +proj=cart

## +ellps=airy +step +proj=helmert +x=446.448

## +y=-125.157 +z=542.06 +rx=0.15 +ry=0.247 +rz=0.842

## +s=-20.489 +convention=position_vector +step +inv

## +proj=cart +ellps=WGS84 +step +proj=pop +v_3 +step

## +proj=unitconvert +xy_in=rad +xy_out=deg

## Operation 8 is lacking 1 grid with accuracy 1 m

## Missing grid: uk_os_OSTN15_NTv2_OSGBtoETRS.tif

## URL: https://cdn.proj.org/uk_os_OSTN15_NTv2_OSGBtoETRS.tif

## Candidate coordinate operations found: 6

## Strict containment: FALSE

## Visualization order: TRUE

## Source: PROJCRS["OSGB 1936 / British National Grid", BASEGEOGCRS["OSGB

## 1936", DATUM["OSGB 1936", ELLIPSOID["Airy 1830",

## 6377563.396, 299.3249646, LENGTHUNIT["metre", 1]]],

## PRIMEM["Greenwich", 0, ANGLEUNIT["degree",

## 0.0174532925199433]], ID["EPSG", 4277]],

## CONVERSION["British National Grid", METHOD["Transverse

## Mercator", ID["EPSG", 9807]], PARAMETER["Latitude of

## natural origin", 49, ANGLEUNIT["degree",

## 0.0174532925199433], ID["EPSG", 8801]],

## PARAMETER["Longitude of natural origin", -2,

## ANGLEUNIT["degree", 0.0174532925199433], ID["EPSG",

## 8802]], PARAMETER["Scale factor at natural origin",

## 0.9996012717, SCALEUNIT["unity", 1], ID["EPSG", 8805]],

## PARAMETER["False easting", 400000, LENGTHUNIT["metre",

## 1], ID["EPSG", 8806]], PARAMETER["False northing",

## -100000, LENGTHUNIT["metre", 1], ID["EPSG", 8807]]],

## CS[Cartesian, 2], AXIS["(E)", east, ORDER[1],

## LENGTHUNIT["metre", 1]], AXIS["(N)", north, ORDER[2],

## LENGTHUNIT["metre", 1]], USAGE[SCOPE["unknown"],

## AREA["UK - Britain and UKCS 49°46'N to 61°01'N, 7°33'W

## to 3°33'E"], BBOX[49.75, -9.2, 61.14, 2.88]],

## ID["EPSG", 27700]]

## Target: GEOGCRS["WGS 84", DATUM["World Geodetic System 1984",

## ELLIPSOID["WGS 84", 6378137, 298.257223563,

## LENGTHUNIT["metre", 1]]], PRIMEM["Greenwich", 0,

## ANGLEUNIT["degree", 0.0174532925199433]],

## CS[ellipsoidal, 2], AXIS["geodetic latitude (Lat)",

## north, ORDER[1], ANGLEUNIT["degree",

## 0.0174532925199433]], AXIS["geodetic longitude (Lon)",

## east, ORDER[2], ANGLEUNIT["degree",

## 0.0174532925199433]], USAGE[SCOPE["unknown"],

## AREA["World"], BBOX[-90, -180, 90, 180]], ID["EPSG",

## 4326]]

## Best instantiable operation has accuracy: 2 m

## Description: Inverse of British National Grid + OSGB 1936 to WGS 84 (6) +

## axis order change (2D)

## Definition: +proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2

## +k=0.9996012717 +x_0=400000 +y_0=-100000

## +ellps=airy +step +proj=push +v_3 +step +proj=cart

## +ellps=airy +step +proj=helmert +x=446.448

## +y=-125.157 +z=542.06 +rx=0.15 +ry=0.247 +rz=0.842

## +s=-20.489 +convention=position_vector +step +inv

## +proj=cart +ellps=WGS84 +step +proj=pop +v_3 +step

## +proj=unitconvert +xy_in=rad +xy_out=deg

## Operation 6 is lacking 1 grid with accuracy 1 m

## Missing grid: OSTN15_NTv2_OSGBtoETRS.gsb

## URL: https://download.osgeo.org/proj/proj-datumgrid-europe-latest.zip

best_instantiable_coordOp(x)

## [1] "+proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000 +y_0=-100000 +ellps=airy +step +proj=push +v_3 +step +proj=cart +ellps=airy +step +proj=helmert +x=446.448 +y=-125.157 +z=542.06 +rx=0.15 +ry=0.247 +rz=0.842 +s=-20.489 +convention=position_vector +step +inv +proj=cart +ellps=WGS84 +step +proj=pop +v_3 +step +proj=unitconvert +xy_in=rad +xy_out=deg"

## attr(,"description")

## [1] "Inverse of British National Grid + OSGB 1936 to WGS 84 (6) + axis order change (2D)"

## [1] "+proj=pipeline +step +inv +proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717

## +x_0=400000 +y_0=-100000 +ellps=airy +step +proj=push +v_3 +step +proj=cart

## +ellps=airy +step +proj=helmert +x=446.448 +y=-125.157 +z=542.06 +rx=0.15 +ry=0.247

## +rz=0.842 +s=-20.489 +convention=position_vector +step +inv +proj=cart +ellps=WGS84

## +step +proj=pop +v_3 +step +proj=unitconvert +xy_in=rad +xy_out=deg"

## attr(,"description")

## [1] "Inverse of British National Grid + OSGB 1936 to WGS 84 (6) + axis order change (2D)"

Turning to a different example, a Brazilian UTM25S Corrego Alegre 1970-72 datum, and looking for coordinate operations transform to UTM25S SIRGAS 2000, we see that a +towgs84= tag was preserved.

discarded_datum

## Warning in showSRID("EPSG:22525", "PROJ"): Discarded datum Corrego Alegre

## 1970-72 in Proj4 definition

## Warning in showSRID("EPSG:22525", "PROJ"): Discarded datum Corrego_Alegre_1970-72 in CRS definition,

## but +towgs84= values preserved

This meant that while only ballpark accuracy is reported, a Helmert transformation is carried out:

(x

## Candidate coordinate operations found: 1

## Strict containment: FALSE

## Visualization order: TRUE

## Source: +proj=utm +zone=25 +south +ellps=intl +units=m +no_defs

## +type=crs +type=crs

## Target: EPSG:31985

## Best instantiable operation has only ballpark accuracy

## Description: Inverse of UTM zone 25S + Ballpark geographic offset from

## unknown to SIRGAS 2000 + UTM zone 25S

## Definition: +proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl

## +step +proj=utm +zone=25 +south +ellps=GRS80

## Candidate coordinate operations found: 1

## Strict containment: FALSE

## Visualization order: TRUE

## Source: +proj=utm +zone=25 +south +ellps=intl

## +towgs84=-205.57,168.77,-4.12,0,0,0,0 +units=m +no_defs

## +type=crs

## Target: EPSG:31985

## Best instantiable operation has only ballpark accuracy

## Description: Inverse of UTM zone 25S + Transformation from unknown to WGS84

## + Inverse of SIRGAS 2000 to WGS 84 (1) + UTM zone

## 25S

## Definition: +proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl

## +step +proj=push +v_3 +step +proj=cart +ellps=intl

## +step +proj=helmert +x=-205.57 +y=168.77 +z=-4.12

## +rx=0 +ry=0 +rz=0 +s=0 +convention=position_vector

## +step +inv +proj=cart +ellps=GRS80 +step +proj=pop

## +v_3 +step +proj=utm +zone=25 +south +ellps=GRS80

best_instantiable_coordOp(x)

## Warning in best_instantiable_coordOp(x): Best instantiable operation has only

## ballpark accuracy

## [1] "+proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl +step +proj=utm +zone=25 +south +ellps=GRS80"

## attr(,"description")

## [1] "Inverse of UTM zone 25S + Ballpark geographic offset from unknown to SIRGAS 2000 + UTM zone 25S"

## Warning in best_instantiable_coordOp(x): Best instantiable operation has only

## ballpark accuracy

## [1] "+proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl +step

## +proj=push +v_3 +step +proj=cart +ellps=intl +step +proj=helmert +x=-205.57

## +y=168.77 +z=-4.12 +rx=0 +ry=0 +rz=0 +s=0 +convention=position_vector +step +inv

## +proj=cart +ellps=GRS80 +step +proj=pop +v_3 +step +proj=utm +zone=25 +south

## +ellps=GRS80"

## attr(,"description")

## [1] "Inverse of UTM zone 25S + Transformation from unknown to WGS84 + Inverse of

## SIRGAS 2000 to WGS 84 (1) + UTM zone 25S"

If we move to input WKT strings when searching for coordinate operations, we get to the same result with unknown accuracy but using a Helmert transformation:

wkt_source_datum

wkt_target_datum

(x

## Candidate coordinate operations found: 2

## Strict containment: FALSE

## Visualization order: TRUE

## Source: PROJCRS["Corrego Alegre 1970-72 / UTM zone 25S",

## BASEGEOGCRS["Corrego Alegre 1970-72", DATUM["Corrego

## Alegre 1970-72", ELLIPSOID["International 1924",

## 6378388, 297, LENGTHUNIT["metre", 1]]],

## PRIMEM["Greenwich", 0, ANGLEUNIT["degree",

## 0.0174532925199433]], ID["EPSG", 4225]],

## CONVERSION["UTM zone 25S", METHOD["Transverse

## Mercator", ID["EPSG", 9807]], PARAMETER["Latitude of

## natural origin", 0, ANGLEUNIT["degree",

## 0.0174532925199433], ID["EPSG", 8801]],

## PARAMETER["Longitude of natural origin", -33,

## ANGLEUNIT["degree", 0.0174532925199433], ID["EPSG",

## 8802]], PARAMETER["Scale factor at natural origin",

## 0.9996, SCALEUNIT["unity", 1], ID["EPSG", 8805]],

## PARAMETER["False easting", 500000, LENGTHUNIT["metre",

## 1], ID["EPSG", 8806]], PARAMETER["False northing",

## 10000000, LENGTHUNIT["metre", 1], ID["EPSG", 8807]]],

## CS[Cartesian, 2], AXIS["(E)", east, ORDER[1],

## LENGTHUNIT["metre", 1]], AXIS["(N)", north, ORDER[2],

## LENGTHUNIT["metre", 1]], USAGE[ SCOPE["Engineering

## survey, topographic mapping."], AREA["Brazil - onshore

## east of 36°W ."], BBOX[-10.1, -36, -4.99, -34.74]],

## ID["EPSG", 22525]]

## Target:

## PROJCRS["SIRGAS 2000 / UTM zone 25S", BASEGEOGCRS["SIRGAS

## 2000", DATUM["Sistema de Referencia Geocentrico para

## las AmericaS 2000", ELLIPSOID["GRS 1980", 6378137,

## 298.257222101, LENGTHUNIT["metre", 1]]],

## PRIMEM["Greenwich", 0, ANGLEUNIT["degree",

## 0.0174532925199433]], ID["EPSG", 4674]],

## CONVERSION["UTM zone 25S", METHOD["Transverse

## Mercator", ID["EPSG", 9807]], PARAMETER["Latitude of

## natural origin", 0, ANGLEUNIT["degree",

## 0.0174532925199433], ID["EPSG", 8801]],

## PARAMETER["Longitude of natural origin", -33,

## ANGLEUNIT["degree", 0.0174532925199433], ID["EPSG",

## 8802]], PARAMETER["Scale factor at natural origin",

## 0.9996, SCALEUNIT["unity", 1], ID["EPSG", 8805]],

## PARAMETER["False easting", 500000, LENGTHUNIT["metre",

## 1], ID["EPSG", 8806]], PARAMETER["False northing",

## 10000000, LENGTHUNIT["metre", 1], ID["EPSG", 8807]]],

## CS[Cartesian, 2], AXIS["(E)", east, ORDER[1],

## LENGTHUNIT["metre", 1]], AXIS["(N)", north, ORDER[2],

## LENGTHUNIT["metre", 1]], USAGE[ SCOPE["Engineering

## survey, topographic mapping."], AREA["Brazil - between

## 36°W and 30°W, northern and southern hemispheres,

## onshore and offshore."], BBOX[-23.8, -36, 4.19,

## -29.99]], ID["EPSG", 31985]]

## Best instantiable operation has accuracy: 5 m

## Description: Inverse of UTM zone 25S + Corrego Alegre 1970-72 to SIRGAS 2000

## (2) + UTM zone 25S

## Definition: +proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl

## +step +proj=push +v_3 +step +proj=cart +ellps=intl

## +step +proj=helmert +x=-206.05 +y=168.28 +z=-3.82

## +step +inv +proj=cart +ellps=GRS80 +step +proj=pop

## +v_3 +step +proj=utm +zone=25 +south +ellps=GRS80

## Operation 2 is lacking 1 grid with accuracy 2 m

## Missing grid: br_ibge_CA7072_003.tif

## URL: https://cdn.proj.org/br_ibge_CA7072_003.tif

## Candidate coordinate operations found: 1

## Strict containment: FALSE

## Visualization order: TRUE

## Source: BOUNDCRS[SOURCECRS[PROJCRS["Corrego Alegre 1970-72 / UTM zone

## 25S", BASEGEOGCRS["Corrego Alegre 1970-72",

## DATUM["Corrego Alegre 1970-72",

## ELLIPSOID["International 1924", 6378388, 297,

## LENGTHUNIT["metre", 1]]], PRIMEM["Greenwich", 0,

## ANGLEUNIT["degree", 0.0174532925199433]], ID["EPSG",

## 4225]], CONVERSION["UTM zone 25S", METHOD["Transverse

## Mercator", ID["EPSG", 9807]], PARAMETER["Latitude of

## natural origin", 0, ANGLEUNIT["degree",

## 0.0174532925199433], ID["EPSG", 8801]],

## PARAMETER["Longitude of natural origin", -33,

## ANGLEUNIT["degree", 0.0174532925199433], ID["EPSG",

## 8802]], PARAMETER["Scale factor at natural origin",

## 0.9996, SCALEUNIT["unity", 1], ID["EPSG", 8805]],

## PARAMETER["False easting", 500000, LENGTHUNIT["metre",

## 1], ID["EPSG", 8806]], PARAMETER["False northing",

## 10000000, LENGTHUNIT["metre", 1], ID["EPSG", 8807]]],

## CS[Cartesian, 2], AXIS["(E)", east, ORDER[1],

## LENGTHUNIT["metre", 1]], AXIS["(N)", north, ORDER[2],

## LENGTHUNIT["metre", 1]], USAGE[SCOPE["unknown"],

## AREA["Brazil - east of 36°W onshore"], BBOX[-10.1, -36,

## -4.99, -34.74]], ID["EPSG", 22525]]],

## TARGETCRS[GEOGCRS["WGS 84", DATUM["World Geodetic

## System 1984", ELLIPSOID["WGS 84", 6378137,

## 298.257223563, LENGTHUNIT["metre", 1]]],

## PRIMEM["Greenwich", 0, ANGLEUNIT["degree",

## 0.0174532925199433]], CS[ellipsoidal, 2],

## AXIS["latitude", north, ORDER[1], ANGLEUNIT["degree",

## 0.0174532925199433]], AXIS["longitude", east, ORDER[2],

## ANGLEUNIT["degree", 0.0174532925199433]], ID["EPSG",

## 4326]]], ABRIDGEDTRANSFORMATION["Corrego Alegre 1970-72

## to WGS 84 (3)", VERSION["PBS-Bra 1983"],

## METHOD["Geocentric translations (geog2D domain)",

## ID["EPSG", 9603]], PARAMETER["X-axis translation",

## -205.57, ID["EPSG", 8605]], PARAMETER["Y-axis

## translation", 168.77, ID["EPSG", 8606]],

## PARAMETER["Z-axis translation", -4.12, ID["EPSG",

## 8607]], USAGE[SCOPE["Medium and small scale mapping."],

## AREA["Brazil - Corrego Alegre 1970-1972"], BBOX[-33.78,

## -58.16, -2.68, -34.74]], ID["EPSG", 6192],

## REMARK["Formed by concatenation of tfms codes 6191 and

## 1877. Used by Petrobras and ANP until February 2005

## when replaced by Corrego Alegre 1970-72 to WGS 84 (4)

## (tfm code 6194)."]]]

## Target:

## BOUNDCRS[SOURCECRS[PROJCRS["SIRGAS 2000 / UTM zone 25S",

## BASEGEOGCRS["SIRGAS 2000", DATUM["Sistema de Referencia

## Geocentrico para las AmericaS 2000", ELLIPSOID["GRS

## 1980", 6378137, 298.257222101, LENGTHUNIT["metre",

## 1]]], PRIMEM["Greenwich", 0, ANGLEUNIT["degree",

## 0.0174532925199433]], ID["EPSG", 4674]],

## CONVERSION["UTM zone 25S", METHOD["Transverse

## Mercator", ID["EPSG", 9807]], PARAMETER["Latitude of

## natural origin", 0, ANGLEUNIT["degree",

## 0.0174532925199433], ID["EPSG", 8801]],

## PARAMETER["Longitude of natural origin", -33,

## ANGLEUNIT["degree", 0.0174532925199433], ID["EPSG",

## 8802]], PARAMETER["Scale factor at natural origin",

## 0.9996, SCALEUNIT["unity", 1], ID["EPSG", 8805]],

## PARAMETER["False easting", 500000, LENGTHUNIT["metre",

## 1], ID["EPSG", 8806]], PARAMETER["False northing",

## 10000000, LENGTHUNIT["metre", 1], ID["EPSG", 8807]]],

## CS[Cartesian, 2], AXIS["(E)", east, ORDER[1],

## LENGTHUNIT["metre", 1]], AXIS["(N)", north, ORDER[2],

## LENGTHUNIT["metre", 1]], USAGE[SCOPE["unknown"],

## AREA["Brazil - 36°W to 30°W"], BBOX[-23.8, -36, 4.19,

## -29.99]], ID["EPSG", 31985]]], TARGETCRS[GEOGCRS["WGS

## 84", DATUM["World Geodetic System 1984", ELLIPSOID["WGS

## 84", 6378137, 298.257223563, LENGTHUNIT["metre", 1]]],

## PRIMEM["Greenwich", 0, ANGLEUNIT["degree",

## 0.0174532925199433]], CS[ellipsoidal, 2],

## AXIS["latitude", north, ORDER[1], ANGLEUNIT["degree",

## 0.0174532925199433]], AXIS["longitude", east, ORDER[2],

## ANGLEUNIT["degree", 0.0174532925199433]], ID["EPSG",

## 4326]]], ABRIDGEDTRANSFORMATION["SIRGAS 2000 to WGS 84

## (1)", VERSION["OGP-C&S America"], METHOD["Geocentric

## translations (geog2D domain)", ID["EPSG", 9603]],

## PARAMETER["X-axis translation", 0, ID["EPSG", 8605]],

## PARAMETER["Y-axis translation", 0, ID["EPSG", 8606]],

## PARAMETER["Z-axis translation", 0, ID["EPSG", 8607]],

## USAGE[SCOPE["Accuracy 1m."], AREA["Latin America -

## SIRGAS 2000 by country"], BBOX[-59.87, -122.19, 32.72,

## -25.28]], ID["EPSG", 15894]]]

## Best instantiable operation has only ballpark accuracy

## Description: Inverse of UTM zone 25S + Corrego Alegre 1970-72 to WGS 84 (3)

## + Inverse of SIRGAS 2000 to WGS 84 (1) + UTM zone

## 25S

## Definition: +proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl

## +step +proj=push +v_3 +step +proj=cart +ellps=intl

## +step +proj=helmert +x=-205.57 +y=168.77 +z=-4.12

## +step +inv +proj=cart +ellps=GRS80 +step +proj=pop

## +v_3 +step +proj=utm +zone=25 +south +ellps=GRS80

If we define the look-up terms directly, in this case and unlike that for the OSGB36 datum, we find more operations than when using WKT strings. Now we find one operation with known accuracy (5m), and that a further operation would be possible if a required grid had been present, this grid is not in the PROJ download archive, as no URL is given.

(x

## Candidate coordinate operations found: 2

## Strict containment: FALSE

## Visualization order: TRUE

## Source: EPSG:22525

## Target: EPSG:31985

## Best instantiable operation has accuracy: 5 m

## Description: Inverse of UTM zone 25S + Corrego Alegre 1970-72 to SIRGAS 2000

## (2) + UTM zone 25S

## Definition: +proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl

## +step +proj=push +v_3 +step +proj=cart +ellps=intl

## +step +proj=helmert +x=-206.05 +y=168.28 +z=-3.82

## +step +inv +proj=cart +ellps=GRS80 +step +proj=pop

## +v_3 +step +proj=utm +zone=25 +south +ellps=GRS80

## Operation 2 is lacking 1 grid with accuracy 2 m

## Missing grid: br_ibge_CA7072_003.tif

## URL: https://cdn.proj.org/br_ibge_CA7072_003.tif

## Candidate coordinate operations found: 2

## Strict containment: FALSE

## Visualization order: TRUE

## Source: EPSG:22525

## Target: EPSG:31985

## Best instantiable operation has accuracy: 5 m

## Description: Inverse of UTM zone 25S + Corrego Alegre 1970-72 to SIRGAS 2000

## (2) + UTM zone 25S

## Definition: +proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl

## +step +proj=push +v_3 +step +proj=cart +ellps=intl

## +step +proj=helmert +x=-206.05 +y=168.28 +z=-3.82

## +step +inv +proj=cart +ellps=GRS80 +step +proj=pop

## +v_3 +step +proj=utm +zone=25 +south +ellps=GRS80

## Operation 2 is lacking 1 grid with accuracy 2 m

## Missing grid: CA7072_003.gsb

best_instantiable_coordOp(x)

## [1] "+proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl +step +proj=push +v_3 +step +proj=cart +ellps=intl +step +proj=helmert +x=-206.05 +y=168.28 +z=-3.82 +step +inv +proj=cart +ellps=GRS80 +step +proj=pop +v_3 +step +proj=utm +zone=25 +south +ellps=GRS80"

## attr(,"description")

## [1] "Inverse of UTM zone 25S + Corrego Alegre 1970-72 to SIRGAS 2000 (2) + UTM zone 25S"

## [1] "+proj=pipeline +step +inv +proj=utm +zone=25 +south +ellps=intl +step

## +proj=push +v_3 +step +proj=cart +ellps=intl +step +proj=helmert +x=-206.05

## +y=168.28 +z=-3.82 +step +inv +proj=cart +ellps=GRS80 +step +proj=pop +v_3 +step

## +proj=utm +zone=25 +south +ellps=GRS80"

## attr(,"description")

## [1] "Inverse of UTM zone 25S + Corrego Alegre 1970-72 to SIRGAS 2000 (2) +

## UTM zone 25S"

寒阳碎雪
关注
{“error“:“incorrect region, please use up-z1.qiniup.com“}
编程小白养成手记
11-28 4135
接入七牛云对象存储 注册七牛云账号，点右上角的密钥管理，key和secret需要复制到application.properties中。 因为用到对象云存储，放一些静态资源，所以还需要实名认证。 个人实名认证后，可以创建存储空间了，这个空间的名字也就是配置文件中对应的bucket，然后就有一个免费试用30天的外链域名。 配置文件 这时我上传文件的时候没有反应，发现返回状态是400，{"error":"incorrect region, please use up-z1.qiniup.com"}，然后在七牛云
100多个地理、测绘方面的数据网站
weixin_30446197的博客
11-20 4324
序号 网站名称 关键字 语言 国家 网站类型 数据类型 重要程度 地址 描述 40 美国全球陆地信息系统/USGS Earth Resources Observation and Science Center 地理系统,全球陆地 美国 1,地理学 USGS Earth Resources Observation and Science ...
nginx禁止特定UA访问
sinat_29193161的博客
06-03 1470
一、UA是什么？ User Agent 简称UA，就是用户代理。通常我们用浏览器访问网站，在网站的日志中，我们的浏览器就是一种UA。 二、禁止特定UA访问 最近有个网站（www.C.com）抄袭公司主站（www.A.com）的内容，除了域名不同，内容、图片等都完全是我们主站的内容。 出现这种情况，有两种可能: 一种是：它用爬虫抓取公司主站（www.A.com）的内容并放到自己服务器上显示； 另一种是：通过将访问代理至公司主站（www.A.com），而域名（www.C.com）是盗用者的，骗取流.
宝塔面板一个网站绑定两个域名配置SSL
11-20 7077
宝塔面板一个网站绑定两个以上的域名配置SSL 1、比如a.com b.com c.com 同时绑定一个网站 2、申请证书，获取pem、key 3、开启a.com 的ssl 4、点击左侧配置文件 <VirtualHost *:80> ServerAdmin webmaster@example.com DocumentRoot "/www/wwwroot/test.com/public" ServerName 7277db5a.test.com Serve
COM组件（MFC篇）
予衡飞翔
06-23 1953
目 录 第1章 创建进程内组件1 1.1 目标1 1.2 创建项目3 1.2.1 VC++6.03 1.2.2 VC++20104 1.2.3 VC++6.0与VC++2010的区别6 1.3 升级项目6 1.3.1 增加接口定义文件6 1.3.2 覆盖应用程序类的InitInstance函数7 1.3.3...
com.mchange.v2.resourcepool.ResourcePoolException: Attempted to use a closed or broken resource pool
David的博客
12-16 3285
idea ,mysql,hibernate,maven com.mchange.v2.resourcepool.ResourcePoolException: Attempted to use a closed or broken resource pool
【Django Geo模块新手必学】：掌握django.contrib.gis.shortcuts的6大核心技巧
[python库文件学习之django.contrib.gis.shortcuts](https://static.djangoproject.com/img/logos/django-logo-negative.1d528e2cb5fb.png) # 1. Django Geo模块概述 Django Geo模块，又称GeoDjango，是Django框架...
【R语言sf包全能攻略】：5大技巧让你的空间数据分析效率翻倍
[【R语言sf包全能攻略】：5大技巧让你的空间数据分析效率翻倍](https://opengraph.githubassets.com/135b945bbf9943e7fa3c2aa7ab851420a12c5a67fc5d32c98fcf8e21b8e3c2b5/r-spatial/sf) # 1. R语言和空间数据简介 #...
PostGresql组件部署和Oracle访问PostGresql的dblink配置
BIT工匠
03-16 2176
以下内容包括2部分： 1. 配置PostGresql和相关组件 2. 配置Oracle的dblink到PostGresql (1) 建立本地yum源 将RHEL 6.5 X86_64整个光盘内容拷贝到 /isoimage. 　  然后建立一个文件rhel6.5_local.repo在目录/etc/yum.repos.d下： [sms@RD-TEST-001 Package
基于django的web_使用Django和GeoDjango制作基于位置的Web应用
cumei1658的博客
07-13 2131
基于django的webThroughout this tutorial, you’ll learn how to use Django and GeoDjango to build a location-based web application from scratch. You’ll be building a simple nearby shops application that lis...
C语言实现COM组件
05-19
简单使用纯C语言实现COM组件，帮助理解COM实现机制
html樱花飘落特效js
existent
06-13 13万+
引入 <!-- 樱花特效引入 --> <script src="./sakura.js"></script> 或者 js源码 //樱花 sakura var stop, staticx; var img = new Image(); img.src = "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAUgAAAEwCAYAAADVZeifAAAACXBIWXMAAACYAAAAmAGiyIKYAAAHG2lUWHRY
http:/222.212.79/app/zscd.html,emscripten/src/shell.html at 1.29.12 · emscripten-core/emscripten · G...
热门推荐
weixin_36304957的博客
06-21 24万+
version="1.1"id="Layer_1"x="0px"y="0px"width="296px"height="78px"viewBox="420 120 100 170"enable-background="new 0 0 900 400"xml:space="preserve"inkscape:version="0.48.4 r9939"sodipodi:docname="emscri...
Android 查看内存使用情况
嗨皮的成长之路
07-18 6200
再看开发过程中，经常要通过内存的使用量来优化程序。 查看应用程序的命令：adb shell procrank 显示如下：   PID      Vss      Rss      Pss      Uss  cmdline   190   79560K   74736K   49624K   43604K  system_server 14335   55776K   55740K
C语言字符串com函数,C语言字符串函数集锦（一）
weixin_36209030的博客
05-17 482
说起字符串函数，我想大家都不陌生。字符串函数对二进制数据、字符串和表达式执行不同的运算。下面总结了C语言中的字符串函数。1、函数名: stpcpy功 能: 拷贝一个字符串到另一个用 法:char*stpcpy(char*destin,char*source);程序例:#include#includeintmain(void){charstring[10];char*str1="abcdefg...
电脑主板资料库 07【转至www.ongood.com.tw】【FreeXploiT收集整理】
FreeXploiT
11-28 1万+
MB(主機版)資料 第七頁AMI BIOS昇級步驟(取自BIOS維修網站)　 忠告：昇級、更新BIOS有一定的風險，除非你的電腦出現故障；否則如果運行正常，請慎重考慮！！ AWARD的刷新程序的使用方法我們已經很熟悉了，對於AMI刷新程序的使用方法，則是初學者們常問的一個問題，下面我們以AMI最高版本的刷新程序8.21版為例，說明一下其使用方法。同樣，刷新程序仍需要純DOS方式下運行，把下載的刷新
R语言中的地理/投影坐标系统（上）[翻译]
R语言学堂
05-25 2859
原文链接：https://mgimond.github.io/Spatial/coordinate-systems-in-r.html。译文分上、下两篇，这里为上篇。1 「关于PROJ环境更新的说明」新版本的sf工具包使用的是PROJ 6.0C库或更高版本。注意不要把PROJ的版本与R里的proj4工具包弄混淆——proj4和sf都是依赖于PROJ C库构建的R工具包，而...
SuperMap iClient for Leaflet对EPSG:4509图加载&滑动查询
SuperMap技术控
12-05 883
SuperMap iClient for Leaflet对EPSG:4509图加载&滑动查询
the &#39;kotlin-android-extensions&#39; gradle plugin is deprecated. please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with view binding (https://developer.android.com/topic/libraries/view-binding) and the &#39;kotlin-parcelize&#39; plugin.
最新发布
06-28
### 回答1： “kotlin-android-extensions” Gradle插件已经被弃用。请使用此迁移指南（https://goo.gle/kotlin-android-extensions-deprecation）开始使用视图绑定（https://developer.android.com/topic/libraries/view-binding）和“kotlin-parcelize”插件。 ### 回答2： 在 Android 开发中，我们通常使用 Kotlin 语言来编写应用程序。Kotlin-Android-Extensions 是一款使用 IntelliJ IDEA 来扩展 Android `View` 类型的插件，这种扩展可以让开发人员更加方便地使用 `View` 类型的属性和方法。 然而，Kotlin-Android-Extensions 插件在开发过程中存在一些问题。其中最大的问题是，它使用运行时反射机制来创建 `View` 对象，这不仅会影响应用程序的运行效果，还可能导致性能问题。为了解决这些问题，Google 官方发布了一个新的插件 —— View Binding。 View Binding 是一种类型安全、高效的方法，可替代 Kotlin-Android-Extensions 插件。使用 View Binding，您可以在编译时生成与布局文件中的每个视图对应的绑定类。这意味着您可以避免因视图引用而引起的错误，同时加快应用程序的启动速度和执行效率。 另一个插件是 Kotlin-Parcelize 插件，它可以轻松序列化和反序列化封装类。这个插件可以将您的数据类自动转换为可序列化类型，并且可以自动生成序列化方法。 所以，如果您正在使用 Kotlin-Android-Extensions，那么现在已经过时了，您应该迁移到 View Binding 和 Kotlin-Parcelize 插件上。使用迁移指南可以快速开发，同时获得更好的性能和可靠性。 ### 回答3： &#39;kotlin-android-extensions&#39; gradle插件已经被弃用，因此我们需要改用新的View Binding插件（https://developer.android.com/topic/libraries/view-binding）并使用&#39;kotlin-parcelize&#39;插件。这个改动对于那些使用Kotlin编写Android应用程序的开发者来说是一个重大的改动，因为在过去，它可以使得我们快速而轻松地在代码中使用UI控件，而不需要通过任何findViewByID方法。 现在，当我们使用View Binding插件时，我们可以更加安全和可靠地与我们的UI组件进行交互，并且我们不需要担心类型转换和编译时的错误。 当我们将我们的应用程序从&#39;kotlin-android-extensions&#39;转移到View Binding插件时，我们需要使用迁移指南（https://goo.gle/kotlin-android-extensions-deprecation）并下载最新的Android插件和Kotlin插件版本。我们需要为每个布局文件生成一个绑定类，并使用findViewById方法的方式取代View Binding中的方法。 Kotlin Parcelize插件是另一个开发者应该使用的插件，它为我们提供了一个方便且易于使用的方式将我们的Kotlin类序列化和反序列化。这对于使用Kotlin的开发者来说是一个非常有用的功能，而&#39;kotlin-android-extensions&#39;插件则没有这样的功能。 因此，虽然我们需要花费一些额外的时间来迁移到View Binding和Kotlin Parcelize插件，但这样做是值得的，因为它可以使我们的代码更加可靠和类型安全，从而使得我们可以更容易地维护和更新我们的应用程序。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值