[Geomoose-users] GM3 Coordinate Display precision
James Klassen
klassen.js at gmail.com
Sun Jan 13 15:01:40 PST 2019
Ok. That makes sense then.
It looks like that fix is in master and what will become 3.2.2, but not in
3.2.1.
On Sun, Jan 13, 2019, 13:19 Kevin Grootendorst <kgrootendorst at gmail.com
wrote:
> I'm using 3.2.1
> If I set to an integer of 0 (removed single quotes), precision fails on
> Firebox and Edge browsers.
> Only when I use '0', will it work for Firefox and Edge. Chrome seemed to
> work with either(?).
>
> Kevin
>
> On Sun, 13 Jan 2019 at 10:39, James Klassen <klassen.js at gmail.com> wrote:
>
>> What version are you using?
>>
>> precision should be an integer. There was a bug at one point where it
>> didn't differentiate between 0 and not set, I wonder if you hit that? In
>> that case higher integers worked, just not 0.
>>
>> Also you have an extra comma after the precision line which might trip up
>> some browsers.
>>
>> On Sat, Jan 12, 2019, 20:51 Kevin Grootendorst <kgrootendorst at gmail.com
>> wrote:
>>
>>> Thanks Jim. Had to make a slight change to make it work:
>>> var point_projections = [
>>> {
>>> label: 'UTM 17N',
>>> ref: 'EPSG:26917',
>>> precision: '0',
>>> },
>>>
>>>
>>> On Sat, 12 Jan 2019 at 21:39, James Klassen <klassen.js at gmail.com>
>>> wrote:
>>>
>>>> Already covered. Add precision to the point_projections array in
>>>> app.js.
>>>>
>>>> And probably also worth a issue to add this to the docs if it isn't in
>>>> there.
>>>>
>>>> ex:
>>>>
>>>> var point_projections = [
>>>> {
>>>> label: 'X,Y',
>>>> ref: 'EPSG:200068',
>>>> precision: 0
>>>> },
>>>>
>>>> ...
>>>>
>>>>
>>>> On Sat, Jan 12, 2019, 18:38 Kevin Grootendorst <kgrootendorst at gmail.com
>>>> wrote:
>>>>
>>>>> All,
>>>>> In the footer of my app, I'm displaying coordinates in UTM 17,
>>>>> however, it defaults to 10 decimal places. Can this be changed to 1 or 0
>>>>> decimals?
>>>>> From searching the list archives, I see that pre-v3, there was a
>>>>> coordinate_display.js or main.js that could be modified to change precision.
>>>>> I'm guessing this could be done in the app.js file in GM3, but not
>>>>> sure where/how to implement.
>>>>> Is it in the app.addProjection?
>>>>> app.addProjection({
>>>>> ref: 'EPSG:26917',
>>>>> def: '+proj=utm +zone=17 +ellps=GRS80 +datum=NAD83 +units=m
>>>>> +no_defs'
>>>>> });
>>>>>
>>>>> Cheers,
>>>>> Kevin
>>>>> _______________________________________________
>>>>> Geomoose-users mailing list
>>>>> Geomoose-users at lists.osgeo.org
>>>>> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20190113/19015eba/attachment.html>
More information about the Geomoose-users
mailing list