SOLVED: Perfect
<Extension>
<CustomProjections>
<Projection epsg="2039">+proj=tmerc +lat_0=31.7343936111111
+lon_0=35.2045169444444 +k=1.0000067 +x_0=219529.584 +y_0=626907.39
+ellps=GRS80 +towgs84=23.772,17.49,17.859,-0.3132,-1.85274,1.67299,-5.4262
+units=m +no_defs +type=crs</Projection>
</CustomProjections>
</Extension>
</ApplicationDefinition>
בתאריך יום ב׳, 10 במרץ 2025 ב-11:56 מאת Jackie Ng <
jumpinjac...@gmail.com>:
> Ok some more things to look at.
>
> Yes, 0.14.10 no longer uses epsg.io, so it fetches the proj4 defn from
> spatialreference.org
>
> I did a check and found that epsg.io and spatialreference.org return
> *different
> proj4 defns* for EPSG:2039
>
> epsg.io (https://epsg.io/2039) gives this:
>
> +proj=tmerc +lat_0=31.7343936111111 +lon_0=35.2045169444444 +k=1.0000067
> +x_0=219529.584 +y_0=626907.39 +ellps=GRS80
> +towgs84=23.772,17.49,17.859,-0.3132,-1.85274,1.67299,-5.4262 +units=m
> +no_defs +type=crs
>
> spatialreference.org (https://spatialreference.org/ref/epsg/2039/proj4.txt)
> gives this:
>
> +proj=tmerc +lat_0=31.7343936111111 +lon_0=35.2045169444444 +k=1.0000067
> +x_0=219529.584 +y_0=626907.39 +ellps=GRS80 +units=m +no_defs +type=crs
>
> It could be that the shift in 0.14.10 is because it now fetches a proj4
> defn for EPSG:2039 from spatialreference.org which is missing the +towgs84
> parameter
>
> To see if this is the case, open the appdef in Maestro and edit the
> "Custom Projections" and manually register the following:
>
> EPSG Code: 2039
> proj4 definition: +proj=tmerc +lat_0=31.7343936111111
> +lon_0=35.2045169444444 +k=1.0000067 +x_0=219529.584 +y_0=626907.39
> +ellps=GRS80 +towgs84=23.772,17.49,17.859,-0.3132,-1.85274,1.67299,-5.4262
> +units=m +no_defs +type=crs
>
> Doing this will bypass the spatialreference.org lookup and instead use
> whatever you registered instead.
>
> - Jackie
>
>
> On Sun, 9 Mar 2025 at 05:48, Nimrod Cnaan <nimcn...@gmail.com> wrote:
>
>> במקרה כזה, כדאי להסביר את המצב הזה למנהל הפרויקט ולהציע חלופות אפשריות.
>> הנה הצעה לתגובה שתוכל לשלוח:
>> ------------------------------
>>
>> Hello,
>>
>> Thank you for your response.
>>
>> Unfortunately, I am unable to test previous versions (0.14.3 to 0.14.9)
>> due to a change in EPSG support: the EPSG.io API endpoints, which we rely
>> on for the EPSG:2039 projection,
>>
>> was deprecated on 01/02/25. As a result, these endpoints are no longer
>> functional for me.
>>
>> Given this limitation, is there an alternative way to troubleshoot this
>> issue?
>>
>> Would sharing my LAYOUT configuration help in diagnosing the issue?
>>
>> I appreciate your help and any guidance you can provide.
>>
>> Thank you in advance!
>>
>> Best regards,
>> Nimrod Cnaan
>> ------------------------------
>>
>> ההודעה הזו מסבירה את המגבלות שלך בצורה ברורה ומבקשת הצעות לפתרון חלופי.
>> אם תרצה לערוך או להוסיף משהו, רק תגיד! 😊
>>
>> בתאריך יום ג׳, 4 במרץ 2025 ב-12:08 מאת Jackie Ng via mapguide-users <
>> mapguide-users@lists.osgeo.org>:
>>
>>> For starters, if something worked in 0.14.2 and "broke" in 0.14.10 can
>>> you at least download all the releases in between (0.14.3, 0.14.4, ...
>>> 0.14.9) and identify the first release where this stopped working. That
>>> will at least help us narrow down the series of changes.
>>>
>>> - Jackie
>>>
>>> You wrote:
>>>
>>> Hello everyone,
>>>
>>> In previous version of *MapGuide-React-Viewer 0.14.2*, there was an
>>> option to influence the position of the *external base map* by setting
>>> the following in the *LAYOUT *to be compatible with the: (for example)
>>> <projection>EPSG:2039</projection>
>>>
>>> With this setting, the external map aligned correctly with the map &
>>> base map local coordinate\EPSG.
>>>
>>> This option doesn't seem to be working for the new version 0.14.10, it
>>> seems there is no effect on the External Base Map's positioning, and there
>>> is a misalignment between local layers and the external map background (See
>>> attached pic). This creates an issue where the alignment between the map
>>> and the data layers does not match.
>>>
>>> We are aware that changing the *Map *projection to *EPSG:900913* resolves
>>> the shifting issue, but this introduces a problem with the map's coordinate
>>> grid, and some of our clients are not willing to work with this coordinate
>>> system.
>>>
>>> Is there a way to work around this issue in version 0.14.10?
>>>
>>> Looking forward to your thoughts and potential solutions.
>>>
>>> Thank you in advance!
>>> _______________________________________________
>>> mapguide-users mailing list
>>> mapguide-users@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/mapguide-users
>>>
>>
>>
>> --
>>
>> בכבוד רב,
>>
>> *נמרוד כנען** | *גיאומינד שירותי GIS – פיתוח, ייעוץ ושירותי ענן
>> ישיר: 048101268 | נייד: 0525355483 | nim...@geomind.co.il
>>
>> נא בקרו באתר החדש שלנו http://geomind.co.il
>>
>>
>
> --
> http://themapguyde.blogspot.com
>
--
בכבוד רב,
*נמרוד כנען** | *גיאומינד שירותי GIS – פיתוח, ייעוץ ושירותי ענן
ישיר: 048101268 | נייד: 0525355483 | nim...@geomind.co.il
נא בקרו באתר החדש שלנו http://geomind.co.il
_______________________________________________
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users
