Projected or local coordinates

[AljosaBudovic]

Hi,

I am trying to open geotiff map of Serbia with shape file of serbian municipalities on one layer but they are not overlapping. They have same latitude but different longitude. I have convert geotiff to same projected coordinate system as shp (WGS_1984_UTM_Zone_34N). Spatial metadata are identical except for the "in projected or local coordinates".

In projected or local coordinates of shape file are:
Left: 7419115.375374
Right: 7488795.926079
Top: 4994895.303551
Bottom: 4902262.058779

In projected or local coordinates of geotiff are:
Left: 419791.772719
Right: 500019.396384
Top: 4983483.460413
Bottom: 4871853.777608

I think it would be fine if I could put (or erase) number 7 in front of left and right coordinates 😄
Does anybody have a solution to this?

[MelitaKennedy]

Hi,

That would probably work fine! I didn't find exact matches in the EPSG registry for Serbia, but I think that both are using Gauss-Kruger zones, but one has added the zone number as the first digit of the easting values. This is pretty common in Europe. 

They do show an MGI or MGI 1901 Balkans zone 7 that has paraemeters that make sense--the false easting is 7500000. The scale factor is 0.9999. Many Gauss-Kruger zones I've seen use 1.0 instead.

It's possible one is using UTM instead. UTM uses 500000 for the false easting. But the scale factor for UTM is 0.9996. If the two datasets are offset, but not very much, it could be because of different scale factors.

What GCS/datum both datasets are using is unknown which could cause another problem.

Melita