<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Bashkim,<span
style="font-family:"Arial",sans-serif;color:black"><o:p></o:p></span>
<blockquote type="cite"
cite="mid:00fd01d84aa7$8ff5bcb0$afe13610$@yahoo.com">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:black">Concerning
to EPSG 6316, as I understood, the only way is to create
new-separate CRS for North Macedonia with same parameters of
6316, in order to solve our problem. This means that we
should go back to EPSG with new request for new CRS! </span></p>
</div>
</blockquote>
if I were them, I would not be very excited to do that, as their
database is going to be a full mess if every user tries to add such
hacks into it<br>
<blockquote type="cite"
cite="mid:00fd01d84aa7$8ff5bcb0$afe13610$@yahoo.com">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:black">Do
you have any other idea? </span></p>
</div>
</blockquote>
<p>No, that's an hard topic. No easy solution. The solution might be
that QGIS would be modified to no longer select the default
transformation proposed by PROJ, and instead lets PROJ decide at
conversion time which transformation to apply for each point. But
that won't be perfect either, given that PROJ only uses a bounding
box approach, and not the polygonal shape of the extents. <br>
</p>
<p>Another solution if you want to create a custom installation is
to remove from the PROJ database the transformation(s) that you
don't want, but I understand that's not what you want to do.<br>
</p>
Even<br>
<blockquote type="cite"
cite="mid:00fd01d84aa7$8ff5bcb0$afe13610$@yahoo.com">
</blockquote>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>