#11718 closed enhancement (wontfix)
WMTS enhancement: custom projections
Reported by: | vanuan | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core imagery | Version: | |
Keywords: | wmts | Cc: |
Description (last modified by )
This WMTS has custom projection: http://213.227.232.41:6080/arcgis/rest/services/Aerofoto/MapServer/WMTS/1.0.0/WMTSCapabilities.xml
It looks like EPSG:4326
XMin: -10000.070003500176
YMin: -17000.000000000004
XMax: 8000.000000000004
YMax: 17000.070003500176
Spatial Reference: PROJCS["New_Projected_Coordinate_System",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTIONTransverse_Mercator,PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Scale_Factor",1.0],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0]]
http://213.227.232.41:6080/arcgis/rest/services/Aerofoto/MapServer?f=jsapi
Unfortunately, JOSM doesn't seam to recognize extents and doesn't produce proper tiles.
Here are some expected results:
Coords: 46.5405729,30.7477846
http://213.227.232.41:6080/arcgis/rest/services/Aerofoto/MapServer/WMTS/tile/1.0.0/Aerofoto/default/default028mm/1/2951/1660
http://213.227.232.41:6080/arcgis/rest/services/Aerofoto/MapServer/WMTS/tile/1.0.0/Aerofoto/default/default028mm/2/14756/8303
http://213.227.232.41:6080/arcgis/rest/services/Aerofoto/MapServer/WMTS/tile/1.0.0/Aerofoto/default/default028mm/3/29513/16606
http://213.227.232.41:6080/arcgis/rest/services/Aerofoto/MapServer/WMTS/tile/1.0.0/Aerofoto/default/default028mm/4/73784/41516
http://213.227.232.41:6080/arcgis/rest/services/Aerofoto/MapServer/WMTS/tile/1.0.0/Aerofoto/default/default028mm/5/147567/83033
http://213.227.232.41:6080/arcgis/rest/services/Aerofoto/MapServer/WMTS/tile/1.0.0/Aerofoto/default/default028mm/6/295135/166066
Attachments (1)
Change History (11)
comment:1 by , 10 years ago
Keywords: | wmts added |
---|---|
Summary: | WTMS enhancement: custom projections → WMTS enhancement: custom projections |
comment:2 by , 10 years ago
Description: | modified (diff) |
---|
comment:3 by , 10 years ago
Component: | Core → Core imagery |
---|
comment:4 by , 10 years ago
comment:6 by , 10 years ago
You can guess the projection and provide custom projection with proj4 compatibile string in JOSM settings.
comment:7 by , 10 years ago
So, the "does not support projection" is only a warning? JOSM would still try to load tiles?
comment:8 by , 10 years ago
It tries to load the tiles, if:
- the tile indexes based on custom projection are not negative
- the tile indexes based on custom projection are not exceeding MatrixWidth/MatrixHeight in getCapabilities document
You can avoid getting this warning, if you will provide following string in your projection definition:
+wmssrs=EPSG:0
But you still need to find proper parameters for this projection. I tried to convert the WKT that you provided to proj4 string, but it didn't gave proper results at location that you mentioned.
+proj=josm:smerc +datum=WGS84 +lat_0=0 +lon_0=0 +k=1 +x_0=0 +y_0=0 +ellps=WGS84 +units=m +no_defs +wmssrs=EPSG:0 +bounds=-180,-85.05112877980659,180,85.05112877980659
comment:9 by , 8 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Server is not responding anymore.
comment:10 by , 5 years ago
Work around:
- Save capabilities document to local storage.
- Edit capabilities document to mention the correct epsg
- In JOSM, point to edited capabilities document with file:///<location on local storage>
The xml document you linked states
crs="urn:ogc:def:crs:EPSG::0"
. This looks like a typo / missing configuration. Are you requesting that JOSM should somehow magically guess what is meant?