-
hi, I do have problems whit maps. I guess problem is at: EPSG:3067 , https://epsg.io/3067 Firstly dowloadble maps cooridantes are out of system limits ! http://kartat.kapsi.fi/files/taustakarttasarja_jhs180/taustakartta_10k ,.... at http://kartat.kapsi.fi/ Secondly I have not succeed to generate WMSSERVER server request that works: WMSSERVER I'am trying to use https://kartat.kapsi.fi/ as source of maps, these maps are from Also like to note that whole europe location informations are available due Inspire Act |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
Sorry for having taken so long to respond. Yes, Xastir does not know how to do transformations between geographic or projected coordinate systems itself. There is some limited ability to handle UTM coordinates in NAD27 and NAD83, but only for maps in GeoTIFF format, which doesn't help you. There is NO capability to transform WMS maps, which actually must be in EPSG:4326 (WGS84 geographic (lat/lon) coordinates) in order that Xastir understand how to pop them into its world coordinate system. However, the server you provided can do that transformation just fine on the server side, and the following .geo file does work:
The important thing is to specify "SRS=EPSG:4326" in there, not EPSG:3067. This "works" if you're zoomed in close enough to Finland, but as you note does produce
if you zoom out too far, and shows nothing. That's because if you go out too far, the transformation from EPSG:3067 to EPSG:4326 is actually invalid and the server chokes. But so long as you're inside the region where EPSG:3067 transforms cleanly into EPSG:4326, it'll work fine. If you zoom in close enough, you can get a usable map, but it will be distorted because of the coordinate transformation needed. For example, if I naively zoom in to bits of Finland near Helsinki, with a typically American ignorance of what parts are actually interesting, I can see varying levels of detail, down to single buildings and streets: I hope this is good enough of an answer for you. |
Beta Was this translation helpful? Give feedback.
-
I will note, though, that the actual placement of features correctly on the map is entirely dependent on the accuracy of the transformation/warp performed by the WMS server itself. I expect that in this day in age it is safe to trust that accuracy, but your mileage may vary. |
Beta Was this translation helpful? Give feedback.
-
And perhaps a location that might be more interesting to you: Unfortunately, as I type this your last APRS positions sent to APRS-IS were about 10-20 minutes ago, and I only just updated my filter for my APRS-IS feed to include you, so I don't have any position reports from you to display on this view. |
Beta Was this translation helpful? Give feedback.
-
@tvrusso - Is reprojection something we would want to consider adding as a potential future feature? (With the understanding that it may not happen.) I'm guessing we would use GDAL to do that, which I know was previously ripped from Xastir because we weren't really using it. |
Beta Was this translation helpful? Give feedback.
-
And now that you're up and about, here's a screenshot of Xastir using the .geo I posted earlier: I switched back and forth between this map and Open Street Maps (OSM_tiled_mapnik.geo) and it looks like it's correctly georeferenced. |
Beta Was this translation helpful? Give feedback.
Sorry for having taken so long to respond.
Yes, Xastir does not know how to do transformations between geographic or projected coordinate systems itself. There is some limited ability to handle UTM coordinates in NAD27 and NAD83, but only for maps in GeoTIFF format, which doesn't help you. There is NO capability to transform WMS maps, which actually must be in EPSG:4326 (WGS84 geographic (lat/lon) coordinates) in order that Xastir understand how to pop them into its world coordinate system.
However, the server you provided can do that transformation just fine on the server side, and the following .geo file does work: