- Pharo-users - lists.pharo.org

Re: [Pharo-users] GPS / Longitude / Latitude library

by Sven Van Caekenberghe

Alistair, I found this page really useful http://www.movable-type.co.uk/scripts/latlong.html HTH, Sven > On 5 Dec 2018, at 11:48, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 5 Dec 2018, at 08:23, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Sven, >> >> On Tue, 4 Dec 2018 at 11:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi Alistair, >>> >>>> On 4 Dec 2018, at 10:21, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>> >>>> Hi, >>>> >>>> Does anyone know of a library for processing GPS coordinates? >>>> >>>> What I'm looking for are things like: >>>> >>>> - Parsing from and printing to various string formats (HMS, NESW, decimal) >>>> - Distance between two points >>>> - etc. >>>> >>>> Thanks, >>>> Alistair >>> >>> We've got some elementary stuff based on WGS84 coordinates as points. For example, >>> >>> T3GeoTools distanceBetween: 5.33732(a)50.926 and: 5.49705(a)50.82733. >>> T3GeoTools bearingFrom: 5.33732(a)50.926 to: 5.49705(a)50.82733. >>> T3GeoTools destinationFrom: 5.33732(a)50.926 bearing: 45 distance: 2500. >>> T3GeoTools centroidOf: { 5.48230(a)50.82249. 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. >>> T3GeoTools is: 5.33732(a)50.92601 inside: { 5.48230(a)50.82249. 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. >>> >>> This is not open source, but it is not rocket science either (just implementations of public algorithms). >> >> Right, I'll probably have a go at this a put it up on github. >> >> It looks like you've chosen to model the coordinates using the Point >> class rather than creating a Coordinate class. Can you explain why (I >> don't have a strong preference either way, so am wondering what your >> thinking is). >> >> It also looks like it is longitude @ latitude. Is that correct? (I >> guess it lines up with the point y value being vertical, which is >> latitude. But most written forms put latitude first). > > I used the simplest thing that could work, using the mathematically oriented x@y (long@lat) form. From what I am doing, it works just fine. Converting to/from HMS notation is not hard I. > > Here is an example: > > distanceBetween: firstPosition and: secondPosition > "T3GeoTools distanceBetween: 5.33732(a)50.926 and: 5.49705(a)50.82733" > > | c | > c := (firstPosition y degreeSin * secondPosition y degreeSin) > + (firstPosition y degreeCos * secondPosition y degreeCos > * (secondPosition x degreesToRadians - firstPosition x degreesToRadians) cos). > c := c >= 0 ifTrue: [ 1 min: c ] ifFalse: [ -1 max: c ]. > ^ c arcCos * 6371000 > > I would not have anything against a real object, as long as it is mathematically sound and used properly. I think that only WGS84 makes sense as internal representation though - it seems the most common thing anyway. > >> Thanks! >> Alistair

Dec. 5, 2018

Re: [Pharo-users] Voyage

by Cyril Ferlicot

On Sun, Dec 2, 2018 at 4:46 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > So we just need to change the dependency. Cool :) > > In fact the dependency was already changed by Norbert! The problem is that we need a new release of mongotalk and to update the release used by Voyage :) So I cannot help here since I'm not part of pharo-nosql. -- Cyril Ferlicot https://ferlicot.fr

Dec. 5, 2018

Re: [Pharo-users] GPS / Longitude / Latitude library

by Sven Van Caekenberghe

> On 5 Dec 2018, at 08:23, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > On Tue, 4 Dec 2018 at 11:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Alistair, >> >>> On 4 Dec 2018, at 10:21, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi, >>> >>> Does anyone know of a library for processing GPS coordinates? >>> >>> What I'm looking for are things like: >>> >>> - Parsing from and printing to various string formats (HMS, NESW, decimal) >>> - Distance between two points >>> - etc. >>> >>> Thanks, >>> Alistair >> >> We've got some elementary stuff based on WGS84 coordinates as points. For example, >> >> T3GeoTools distanceBetween: 5.33732(a)50.926 and: 5.49705(a)50.82733. >> T3GeoTools bearingFrom: 5.33732(a)50.926 to: 5.49705(a)50.82733. >> T3GeoTools destinationFrom: 5.33732(a)50.926 bearing: 45 distance: 2500. >> T3GeoTools centroidOf: { 5.48230(a)50.82249. 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. >> T3GeoTools is: 5.33732(a)50.92601 inside: { 5.48230(a)50.82249. 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. >> >> This is not open source, but it is not rocket science either (just implementations of public algorithms). > > Right, I'll probably have a go at this a put it up on github. > > It looks like you've chosen to model the coordinates using the Point > class rather than creating a Coordinate class. Can you explain why (I > don't have a strong preference either way, so am wondering what your > thinking is). > > It also looks like it is longitude @ latitude. Is that correct? (I > guess it lines up with the point y value being vertical, which is > latitude. But most written forms put latitude first). I used the simplest thing that could work, using the mathematically oriented x@y (long@lat) form. From what I am doing, it works just fine. Converting to/from HMS notation is not hard I. Here is an example: distanceBetween: firstPosition and: secondPosition "T3GeoTools distanceBetween: 5.33732(a)50.926 and: 5.49705(a)50.82733" | c | c := (firstPosition y degreeSin * secondPosition y degreeSin) + (firstPosition y degreeCos * secondPosition y degreeCos * (secondPosition x degreesToRadians - firstPosition x degreesToRadians) cos). c := c >= 0 ifTrue: [ 1 min: c ] ifFalse: [ -1 max: c ]. ^ c arcCos * 6371000 I would not have anything against a real object, as long as it is mathematically sound and used properly. I think that only WGS84 makes sense as internal representation though - it seems the most common thing anyway. > Thanks! > Alistair

Dec. 5, 2018

Re: [Pharo-users] GPS / Longitude / Latitude library

by Norbert Hartl

Just for the record. I have a GeoJSON (http://geojson.org/) package at https://github.com/noha/geo-json/ This tackles geo coordinates from yet another angle: How to model a geo position as POI (point of interest) and having a common format for it. And in the meantime geo json is the storage format for geo coordinates in mongo DB. There are point classes in there that can be used with degree/minute/second. But surely something different then your needs Norbert > Am 05.12.2018 um 08:34 schrieb Alistair Grant <akgrant0710(a)gmail.com>: > > Hi Pierce & Richard, > > Thanks for your replies. > >> On Wed, Dec 05, 2018 at 10:24:18AM +0800, Pierce Ng wrote: >>> On Tue, Dec 04, 2018 at 10:21:20AM +0100, Alistair Grant wrote: >>> Does anyone know of a library for processing GPS coordinates? >>> >>> What I'm looking for are things like: >>> >>> - Parsing from and printing to various string formats (HMS, NESW, decimal) >>> - Distance between two points >>> - etc. >> >> SQLite-based possibilities: >> >> - Spatialite: https://www.gaia-gis.it/fossil/libspatialite/index >> - R*Tree: https://sqlite.org/rtree.html >> - GeoPoly: https://sqlite.org/geopoly.html > > > >> On Wed, Dec 05, 2018 at 06:44:35PM +1300, Richard O'Keefe wrote: >> As Dershowitz and Reingold showed in their book "Calendrical Calculations", >> converting from UTC to several calendars needs latitude, longitude, and >> elevation. ISO 6709 is the relevant standard: >> https://en.wikipedia.org/wiki/ISO_6709 > > My camera uses D M S (0 deg 0' 0.00", 0 deg 0' 0.00") so I'll use that > initially, but I'll definitely add links in the comments and make sure > that support for other formats can be added. > > I'm not doing any database work at the moment (storing results in STON > files for now), but will also add the links to the class comments. > > Thanks again, > Alistair > >

Dec. 5, 2018

Re: [Pharo-users] GPS / Longitude / Latitude library

by Benoit St-Jean

Perhaps porting the R package GeoSphere to Pharo/Squeak/Smalltalk would be an option?Â It's rather complete and used a lot (at least in the R community) ! https://cran.r-project.org/web/packages/geosphere/geosphere.pdf ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) On Wednesday, December 5, 2018, 2:24:07 a.m. EST, Alistair Grant <akgrant0710(a)gmail.com> wrote: Hi Sven, On Tue, 4 Dec 2018 at 11:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Alistair, > > > On 4 Dec 2018, at 10:21, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi, > > > > Does anyone know of a library for processing GPS coordinates? > > > > What I'm looking for are things like: > > > > - Parsing from and printing to various string formats (HMS, NESW, decimal) > > - Distance between two points > > - etc. > > > > Thanks, > > Alistair > > We've got some elementary stuff based on WGS84 coordinates as points. For example, > > T3GeoTools distanceBetween: 5.33732(a)50.926 and: 5.49705(a)50.82733. > T3GeoTools bearingFrom: 5.33732(a)50.926 to: 5.49705(a)50.82733. > T3GeoTools destinationFrom: 5.33732(a)50.926 bearing: 45 distance: 2500. > T3GeoTools centroidOf: { 5.48230(a)50.82249. 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. > T3GeoTools is: 5.33732(a)50.92601 inside: { 5.48230(a)50.82249. 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. > > This is not open source, but it is not rocket science either (just implementations of public algorithms). Right, I'll probably have a go at this a put it up on github. It looks like you've chosen to model the coordinates using the Point class rather than creating a Coordinate class.Â Can you explain why (I don't have a strong preference either way, so am wondering what your thinking is). It also looks like it is longitude @ latitude.Â Is that correct?Â (I guess it lines up with the point y value being vertical, which is latitude.Â But most written forms put latitude first). Thanks! Alistair

Dec. 5, 2018

Re: [Pharo-users] GPS / Longitude / Latitude library

by Alistair Grant

Hi Pierce & Richard, Thanks for your replies. On Wed, Dec 05, 2018 at 10:24:18AM +0800, Pierce Ng wrote: > On Tue, Dec 04, 2018 at 10:21:20AM +0100, Alistair Grant wrote: > > Does anyone know of a library for processing GPS coordinates? > > > > What I'm looking for are things like: > > > > - Parsing from and printing to various string formats (HMS, NESW, decimal) > > - Distance between two points > > - etc. > > SQLite-based possibilities: > > - Spatialite: https://www.gaia-gis.it/fossil/libspatialite/index > - R*Tree: https://sqlite.org/rtree.html > - GeoPoly: https://sqlite.org/geopoly.html On Wed, Dec 05, 2018 at 06:44:35PM +1300, Richard O'Keefe wrote: > As Dershowitz and Reingold showed in their book "Calendrical Calculations", > converting from UTC to several calendars needs latitude, longitude, and > elevation. ISO 6709 is the relevant standard: > https://en.wikipedia.org/wiki/ISO_6709 My camera uses D M S (0 deg 0' 0.00", 0 deg 0' 0.00") so I'll use that initially, but I'll definitely add links in the comments and make sure that support for other formats can be added. I'm not doing any database work at the moment (storing results in STON files for now), but will also add the links to the class comments. Thanks again, Alistair

Dec. 5, 2018

Re: [Pharo-users] GPS / Longitude / Latitude library

by Alistair Grant

Hi Sven, On Tue, 4 Dec 2018 at 11:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Alistair, > > > On 4 Dec 2018, at 10:21, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi, > > > > Does anyone know of a library for processing GPS coordinates? > > > > What I'm looking for are things like: > > > > - Parsing from and printing to various string formats (HMS, NESW, decimal) > > - Distance between two points > > - etc. > > > > Thanks, > > Alistair > > We've got some elementary stuff based on WGS84 coordinates as points. For example, > > T3GeoTools distanceBetween: 5.33732(a)50.926 and: 5.49705(a)50.82733. > T3GeoTools bearingFrom: 5.33732(a)50.926 to: 5.49705(a)50.82733. > T3GeoTools destinationFrom: 5.33732(a)50.926 bearing: 45 distance: 2500. > T3GeoTools centroidOf: { 5.48230(a)50.82249. 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. > T3GeoTools is: 5.33732(a)50.92601 inside: { 5.48230(a)50.82249. 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. > > This is not open source, but it is not rocket science either (just implementations of public algorithms). Right, I'll probably have a go at this a put it up on github. It looks like you've chosen to model the coordinates using the Point class rather than creating a Coordinate class. Can you explain why (I don't have a strong preference either way, so am wondering what your thinking is). It also looks like it is longitude @ latitude. Is that correct? (I guess it lines up with the point y value being vertical, which is latitude. But most written forms put latitude first). Thanks! Alistair

Dec. 5, 2018

Re: [Pharo-users] can I avoid the nested loops

by Roelof Wobben

Dec. 5, 2018

Re: [Pharo-users] can I avoid the nested loops

by Richard O'Keefe

The data set AoC gave me for problem 3 has 1353 claims. The brute force way is to make your x->(y->count) map and then walk over it counting the number of counts > 1, n := 0. map do: [:row | row do: [:count | count > 1 ifTrue: [n := n+1]]]. On Wed, 5 Dec 2018 at 11:06, Roelof Wobben <r.wobben(a)home.nl> wrote: > Thanks I found that out already. > > Now trying to understand what they mean with this exactly > > If the Elves all proceed with their own plans, none of them will have enough fabric. How many square inches of fabric are within two or more claims? > > > They give some 13000 plans > > > Roelof > > > > > > Op 4-12-2018 om 22:55 schreef Ben Coman: > > > > On Wed, 5 Dec 2018 at 00:45, Roelof Wobben <r.wobben(a)home.nl> wrote: > >> so like this ? >> >> so first the intersect between rectangle1 and rectangle2 >> store it >> and then the intersection between the stored one and rectangle3 >> and so on >> then its time to look how I must define a rectangle when I know the >> starting point and the length and width >> >> then it time to figure out how I can define a Rectangle with the starting >> point the length and the width >> > > Use Spotter to bring up the System Browser on the Rectangle class. > Then right-click >> Class-refs > to look at how the class is used directly to create new instances. > > cheers -ben > > > >> >> Roelof >> >> >> >> Op 4-12-2018 om 17:27 schreef phil(a)highoctane.be: >> >> Use Rectangle class and intersect: method? >> >> >> >> >> On Tue, Dec 4, 2018 at 5:07 PM Roelof Wobben <r.wobben(a)home.nl> wrote: >> >>> Hello, >>> >>> For adventofCode I had to write some code that calculates the overlap >>> that multiple rectangles have. >>> >>> Fo far I have it working for 1 rectangle but I do not like the code >>> because of the nested loops. >>> >>> Can I make this more the pharo way >>> >>> Code so far : >>> >>> | item coordinates area overlap regexp line beginX endX beginY endY| >>> area := OrderedCollection new. >>> overlap := OrderedCollection new. >>> regexp := '\#(\d+) @ (\d+),(\d+)\: (\d+)x(\d+)' asRegex. >>> line := '#1 @ 1,3: 4x4'. >>> (regexp matches: line) >>> ifTrue: [ >>> beginX := (regexp subexpression: 2) asInteger + 1. >>> endX := (regexp subexpression: 5) asInteger + beginX . >>> beginY := (regexp subexpression: 4) asInteger + 1. >>> endY := (regexp subexpression: 6) asInteger + beginY. >>> beginX to: (endX - 1) do: [:a | >>> beginY to: (endY -1) do: [:b | >>> item := a asString , '*' , b asString . >>> (area includes: item) >>> ifTrue: [ overlap add: item ] >>> ifFalse: [ area add: item ]]]] . >>> ^ area. >>> >>> Thanks, >>> >>> Roelof >>> >>> >>> >> >

Dec. 5, 2018

Re: [Pharo-users] GPS / Longitude / Latitude library

by Richard O'Keefe

As Dershowitz and Reingold showed in their book "Calendrical Calculations", converting from UTC to several calendars needs latitude, longitude, and elevation. ISO 6709 is the relevant standard: https://en.wikipedia.org/wiki/ISO_6709 On Tue, 4 Dec 2018 at 23:35, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > Interesting. > > Iâm interested with such tools too. > > I ask students to do gps point collection from mobile (Cordova) and > process them in pharo to detect if they enter known places. > > I wonder if a proper gps point class would be useful. Iâd like to record > also the precision. > > Cheers, > > Cedrick > > > > > Le 4 dÃ©c. 2018 Ã 11:15, Alistair Grant <akgrant0710(a)gmail.com> a Ã©crit : > > > > Hi Sven, > > > > Thanks. This is just for me playing around with my photo collection, > > i.e. find all photos from a particular location, i.e. within a > > specified distance of a point. Also maybe add GPS coordinates to some > > photos. > > > > Thanks again, > > Alistair > > > >> On Tue, 4 Dec 2018 at 11:04, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> > >> Hi Alistair, > >> > >>> On 4 Dec 2018, at 10:21, Alistair Grant <akgrant0710(a)gmail.com> wrote: > >>> > >>> Hi, > >>> > >>> Does anyone know of a library for processing GPS coordinates? > >>> > >>> What I'm looking for are things like: > >>> > >>> - Parsing from and printing to various string formats (HMS, NESW, > decimal) > >>> - Distance between two points > >>> - etc. > >>> > >>> Thanks, > >>> Alistair > >> > >> We've got some elementary stuff based on WGS84 coordinates as points. > For example, > >> > >> T3GeoTools distanceBetween: 5.33732(a)50.926 and: 5.49705(a)50.82733. > >> T3GeoTools bearingFrom: 5.33732(a)50.926 to: 5.49705(a)50.82733. > >> T3GeoTools destinationFrom: 5.33732(a)50.926 bearing: 45 distance: 2500. > >> T3GeoTools centroidOf: { 5.48230(a)50.82249. 5.49523(a)50.81288. > 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. 5.48230(a)50.82249 }. > >> T3GeoTools is: 5.33732(a)50.92601 inside: { 5.48230(a)50.82249. > 5.49523(a)50.81288. 5.50138(a)50.82008. 5.50228(a)50.82595. 5.49265(a)50.82560. > 5.48230(a)50.82249 }. > >> > >> This is not open source, but it is not rocket science either (just > implementations of public algorithms). > >> > >> We have less need for special conversions, we do them case by case when > they occur. > >> > >> What are you planning to do ? > >> > >> Sven > >> > >> > > > >

Dec. 5, 2018