June 2020 - Pharo-users - lists.pharo.org

Re: [Pharo-users] GIS support for Pharo

by Serge Stinckwich

On Thu, Jun 4, 2020 at 4:11 PM Norbert Hartl <norbert(a)hartl.name> wrote: > I started this initiative for our company because we are in the mobility > bubsiness where maps and geo centric things are important. It is not > elaborate as a real GIS support but a start. So here my secret plan: > > Thank you Norbert for your interest on that topic. I put Etienne Delay because he is not ont the pharo-users mailing-list and I'm working with him on GIS issues for CORMAS. - GeoJSON [1] was done because web services came up with that format to > exchange geo shape information. Furthermore database like MongoDB changed > their internal support for 2d/2dsphere indexes also to GeoJSON. There is a > package GeoJSON-Voyage which is start of a helper to easily store Geo data > in voyage-mongo. > > - I started to do a KML Reader [2] because besides GeoJSON that is a > widely used format. And this can be used in Google Earth which is the best > free Geo editor that I know. > > - As KML and GeoJSON use a similar model for representing geo shapes and > POIs I started to factor out that into the Geography package [3]. > > - At the moment in the Geography package there is only a 2D point class > GGPoint to have something to hold geo coordinates (there is also a 3D > variant). In the past I used Point as the class for these things but came > to the conclusion that there is a distinction between a point and geo point > when it comes to things like distance etc. So it is better to have them > separate. Into this model I want to morph the classes for LineStrings, > LinearRings, Polygons etc. from GeoJSON and KML to have a common foundation > for the basic geo shapes lines, multi-lines, closed multi-lines (=polygons) > etc. > > - As GGPoint is distinct to Point this is just the context where you use > it. The Geography package should be a companion to the Geometry package [4] > which I forked from TelescopeSt to make it a community package which is > good for this plan but also for roassal which uses the Geometry package. To > me the geoX model should be switched between Geometry and Geography > regarding to the context you want to work in being planar or spherical. > > - In my tools that I build this model classes have also gt-inspector > extension so the shapes can be viewed just by inspecting them. I'm fighting > with the roassal team to make it possible for geo coordinates which > conflicts at the moment with their defined thresholds. But with the > factoring the shapes into Geography I will move those extension to the > Geography package as well > > - I also implemented a polygon intersection algorithm (Weiler and > Atherton) which I will then incorporate in any of the GeoX packages > > You have done a lot of work. And we add all the work done by Hernan on supporting ESRI shapefiles, we have already a good start. Etienne also mention the OpenGIS model in this issue: https://github.com/cormas/cormas/issues/139 >From what I understood, OpenGIS model crosscut many points of the Geography package: http://portal.opengeospatial.org/files/?artifact_id=25355 So these are the pieces that are there. The plan in text is: > > - Have a incarnation of a "point" and make that switch context from planar > to spherical > - Use planar treatment with the Geometry package (intersections etc.) > - Use this "point" to generate shapes either geometric or geographic > - Be able to read and write in common formats like GeoJSON and KML > - Make shapes be composable and inspectable with the existing tools > > I think GIS needs more but what we have is more than just a start. The > projection system with the current code is WGS84 for sure. If there are > other needs we need to think about this early. > > For everything else I'm open ears. Even for the idea of having a pharo-gis > github project to collect those things to a common place. But I like to > discuss GIS and not if it makes sense to have a all of these github repos. > We can try to do an online meeting to discuss about that with Etienne and other people interested by this topic. We are mostly interested to have GIS support on CORMAS, so having a common repository will definitively help us. At the moment we are using Roassal2 for CORMAS visualisatin and we are moving towards Roassal3. Regards, -- Serge Stinckwic h https://twitter.com/SergeStinckwich

June 4, 2020

Re: [Pharo-users] GIS support for Pharo

by CÃ©drick BÃ©ler

Looks great and all information in the thread. â¦. > - I started to do a KML Reader [2] because besides GeoJSON that is a widely used format. And this can be used in Google Earth which is the best free Geo editor that I know. <Slighty OT>, What do you think of Mapbox ? I try to de-google as much as I can :) Just to contextualize: my mid-term goal is to have a mean to build simple Â« digital twin Â» that are integrated in Mapbox/Leaflet/OSM, using a priori three.js. Spatiality is a bit tricky as not default in three.js and the three.js plugin of Mapbox is a bit limited as far a I understand it right now (Iâm trying stuff on that especially with the reytracing possibility so as to augment 3D models). There is a lib called maptalks where I put the demo here. http://o0o.io/three/maptalks/ https://maptalks.org => https://github.com/maptalks/maptalks.js This is the building block for interactive geospatial 3D model I experiment with the help of students. </sligthy OT> The "digital twin Â» might be OT from the GIS related effort that is discussed here but I find it very related. If you want a digital twin, it has to be geolocalized. Tell me if other have such kind of interest. > > - As KML and GeoJSON use a similar model for representing geo shapes and POIs I started to factor out that into the Geography package [3]. Cool :) > > - At the moment in the Geography package there is only a 2D point class GGPoint to have something to hold geo coordinates (there is also a 3D variant). In the past I used Point as the class for these things but came to the conclusion that there is a distinction between a point and geo point when it comes to things like distance etc. So it is better to have them separate. Into this model I want to morph the classes for LineStrings, LinearRings, Polygons etc. from GeoJSON and KML to have a common foundation for the basic geo shapes lines, multi-lines, closed multi-lines (=polygons) etc. ... > > - As GGPoint is distinct to Point this is just the context where you use it. The Geography package should be a companion to the Geometry package [4] which I forked from TelescopeSt to make it a community package which is good for this plan but also for roassal which uses the Geometry package. To me the geoX model should be switched between Geometry and Geography regarding to the context you want to work in being planar or spherical. > > - In my tools that I build this model classes have also gt-inspector extension so the shapes can be viewed just by inspecting them. I'm fighting with the roassal team to make it possible for geo coordinates which conflicts at the moment with their defined thresholds. But with the factoring the shapes into Geography I will move those extension to the Geography package as well > > - I also implemented a polygon intersection algorithm (Weiler and Atherton) which I will then incorporate in any of the GeoX packages Great :) > > So these are the pieces that are there. The plan in text is: > > - Have a incarnation of a "point" and make that switch context from planar to spherical > - Use planar treatment with the Geometry package (intersections etc.) > - Use this "point" to generate shapes either geometric or geographic > - Be able to read and write in common formats like GeoJSON and KML > - Make shapes be composable and inspectable with the existing tools > > I think GIS needs more but what we have is more than just a start. The projection system with the current code is WGS84 for sure. If there are other needs we need to think about this early. I think the projection system is one of the hard difficulties with GIS but also important. Itâs out of my knowledge but probably people like Etienne can give their impression on that ? Cheers and thanks again for all the efforts, CÃ©drick > > For everything else I'm open ears. Even for the idea of having a pharo-gis github project to collect those things to a common place. But I like to discuss GIS and not if it makes sense to have a all of these github repos. > > Norbert > > [1] https://github.com/zweidenker/GeoJSON <https://github.com/zweidenker/GeoJSON> > [2] https://github.com/zweidenker/KML <https://github.com/zweidenker/KML> > [3] https://github.com/zweidenker/Geography <https://github.com/zweidenker/Geography> > [4] https://github.com/pharo-contributions/Geometry <https://github.com/pharo-contributions/Geometry> > >> Am 04.06.2020 um 05:31 schrieb Serge Stinckwich <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>>:

June 4, 2020

Re: [Pharo-users] ESRI ASCII raster format

by Serge Stinckwich

On Thu, Jun 4, 2020 at 4:08 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> - >> >> It was fun. >> My implementation could be more robust but for 2 hours coding. >> It was a fun kata. >> > > Would you want to share your work during our next CORMAS meeting, Friday? > > > > If you want now cormas can use it, fork it, expand,â¦. > I did it for you as an exercise for me. > > Ok, this is great. We will definitively reused it for CORMAS. Regards -- Serge Stinckwic h https://twitter.com/SergeStinckwich

June 4, 2020

Re: [Pharo-users] GIS support for Pharo

by Baveco, Hans

Would be an interesting project.. An old link to possibly still useful code: http://wiki.squeak.org/squeak/3317 Btw the shapefile support, from the ESRI spec, was done by me and is still available on http://www.squeaksource.com/@CUT95k_uXmPU4uXY/HCmgtrop. I use it daily. I may have some fixes/additions, but in general the code as provided works well (I suppose the code at smalltalkhub is still mostly the same). Some shapefile formats are still missing, mostly because I never encountered them.. To read a complete shapefile one also needs to read dbf files. This was another substantial effort http://www.squeaksource.com/@Y4HhnL90iyA2TmAb/X0sPqshM; luckily there was an older implementation.available to build upon. Not sure whether nowadays there are other ways to read/write files old DBASE format files... Cheers, Hans Baveco From: Serge Stinckwich <serge.stinckwich(a)gmail.com> Sent: donderdag 4 juni 2020 5:32 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] GIS support for Pharo Dear all, there was already some discussion in the list about GIS support for Pharo previously. Working on CORMAS multi-agent simulation platform: https://github.com/cormas/cormas some developers feel the need to have more GIS support for Pharo. I know of existing GIS software: - GeoJSON by Zweidenker: https://github.com/zweidenker/GeoJSON - ESRI ascii raster, done by Stephane recently: https://github.com/Ducasse/ESRI-ASCII-Raster - shapefile support by Hernan: http://smalltalkhub.com/#!/~hernan/Shapes (to be moved to github) - I found this project also: http://www.squeaksource.com/gekon.html I know that Etienne Delay is also interested by GIS support and propose to implement OpenGIS model support: https://github.com/cormas/cormas/issues/139 Can we try to unite and maybe create a pharo-GIS organization on github to federate our efforts? Cheers, -- Serge Stinckwic h https://twitter.com/SergeStinckwich

June 4, 2020

Re: [Pharo-users] GIS support for Pharo

by Norbert Hartl

Forgot to say. I also started to do an OSM renderer two years ago. I tried to do in Bloc but got no support and it got stuck. A few weeks ago I put this again on my list. Talking to Stef I saw that I might not need to interaction support etc. at the beginning and can do this on top of Athens. FYI, Norbert > Am 04.06.2020 um 10:11 schrieb Norbert Hartl <norbert(a)hartl.name>: > > I started this initiative for our company because we are in the mobility bubsiness where maps and geo centric things are important. It is not elaborate as a real GIS support but a start. So here my secret plan: > > - GeoJSON [1] was done because web services came up with that format to exchange geo shape information. Furthermore database like MongoDB changed their internal support for 2d/2dsphere indexes also to GeoJSON. There is a package GeoJSON-Voyage which is start of a helper to easily store Geo data in voyage-mongo. > > - I started to do a KML Reader [2] because besides GeoJSON that is a widely used format. And this can be used in Google Earth which is the best free Geo editor that I know. > > - As KML and GeoJSON use a similar model for representing geo shapes and POIs I started to factor out that into the Geography package [3]. > > - At the moment in the Geography package there is only a 2D point class GGPoint to have something to hold geo coordinates (there is also a 3D variant). In the past I used Point as the class for these things but came to the conclusion that there is a distinction between a point and geo point when it comes to things like distance etc. So it is better to have them separate. Into this model I want to morph the classes for LineStrings, LinearRings, Polygons etc. from GeoJSON and KML to have a common foundation for the basic geo shapes lines, multi-lines, closed multi-lines (=polygons) etc. > > - As GGPoint is distinct to Point this is just the context where you use it. The Geography package should be a companion to the Geometry package [4] which I forked from TelescopeSt to make it a community package which is good for this plan but also for roassal which uses the Geometry package. To me the geoX model should be switched between Geometry and Geography regarding to the context you want to work in being planar or spherical. > > - In my tools that I build this model classes have also gt-inspector extension so the shapes can be viewed just by inspecting them. I'm fighting with the roassal team to make it possible for geo coordinates which conflicts at the moment with their defined thresholds. But with the factoring the shapes into Geography I will move those extension to the Geography package as well > > - I also implemented a polygon intersection algorithm (Weiler and Atherton) which I will then incorporate in any of the GeoX packages > > So these are the pieces that are there. The plan in text is: > > - Have a incarnation of a "point" and make that switch context from planar to spherical > - Use planar treatment with the Geometry package (intersections etc.) > - Use this "point" to generate shapes either geometric or geographic > - Be able to read and write in common formats like GeoJSON and KML > - Make shapes be composable and inspectable with the existing tools > > I think GIS needs more but what we have is more than just a start. The projection system with the current code is WGS84 for sure. If there are other needs we need to think about this early. > > For everything else I'm open ears. Even for the idea of having a pharo-gis github project to collect those things to a common place. But I like to discuss GIS and not if it makes sense to have a all of these github repos. > > Norbert > > [1] https://github.com/zweidenker/GeoJSON <https://github.com/zweidenker/GeoJSON> > [2] https://github.com/zweidenker/KML <https://github.com/zweidenker/KML> > [3] https://github.com/zweidenker/Geography <https://github.com/zweidenker/Geography> > [4] https://github.com/pharo-contributions/Geometry <https://github.com/pharo-contributions/Geometry> > >> Am 04.06.2020 um 05:31 schrieb Serge Stinckwich <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>>: >> >> Dear all, >> >> there was already some discussion in the list about GIS support for Pharo previously. >> >> Working on CORMAS multi-agent simulation platform: https://github.com/cormas/cormas <https://github.com/cormas/cormas> some developers feel the need to have more GIS support for Pharo. >> >> I know of existing GIS software: >> - GeoJSON by Zweidenker: https://github.com/zweidenker/GeoJSON <https://github.com/zweidenker/GeoJSON> >> - ESRI ascii raster, done by Stephane recently: https://github.com/Ducasse/ESRI-ASCII-Raster <https://github.com/Ducasse/ESRI-ASCII-Raster> >> - shapefile support by Hernan: http://smalltalkhub.com/#!/~hernan/Shapes <http://smalltalkhub.com/#!/~hernan/Shapes> >> (to be moved to github) >> - I found this project also: http://www.squeaksource.com/gekon.html <http://www.squeaksource.com/gekon.html> >> >> I know that Etienne Delay is also interested by GIS support and propose to implement OpenGIS model support: https://github.com/cormas/cormas/issues/139 <https://github.com/cormas/cormas/issues/139> >> >> Can we try to unite and maybe create a pharo-GIS organization on github to federate our efforts? >> >> Cheers, >> -- >> Serge Stinckwich >> https://twitter.com/SergeStinckwich <https://twitter.com/SergeStinckwich> >

June 4, 2020

Re: [Pharo-users] GIS support for Pharo

by Norbert Hartl

I started this initiative for our company because we are in the mobility bubsiness where maps and geo centric things are important. It is not elaborate as a real GIS support but a start. So here my secret plan: - GeoJSON [1] was done because web services came up with that format to exchange geo shape information. Furthermore database like MongoDB changed their internal support for 2d/2dsphere indexes also to GeoJSON. There is a package GeoJSON-Voyage which is start of a helper to easily store Geo data in voyage-mongo. - I started to do a KML Reader [2] because besides GeoJSON that is a widely used format. And this can be used in Google Earth which is the best free Geo editor that I know. - As KML and GeoJSON use a similar model for representing geo shapes and POIs I started to factor out that into the Geography package [3]. - At the moment in the Geography package there is only a 2D point class GGPoint to have something to hold geo coordinates (there is also a 3D variant). In the past I used Point as the class for these things but came to the conclusion that there is a distinction between a point and geo point when it comes to things like distance etc. So it is better to have them separate. Into this model I want to morph the classes for LineStrings, LinearRings, Polygons etc. from GeoJSON and KML to have a common foundation for the basic geo shapes lines, multi-lines, closed multi-lines (=polygons) etc. - As GGPoint is distinct to Point this is just the context where you use it. The Geography package should be a companion to the Geometry package [4] which I forked from TelescopeSt to make it a community package which is good for this plan but also for roassal which uses the Geometry package. To me the geoX model should be switched between Geometry and Geography regarding to the context you want to work in being planar or spherical. - In my tools that I build this model classes have also gt-inspector extension so the shapes can be viewed just by inspecting them. I'm fighting with the roassal team to make it possible for geo coordinates which conflicts at the moment with their defined thresholds. But with the factoring the shapes into Geography I will move those extension to the Geography package as well - I also implemented a polygon intersection algorithm (Weiler and Atherton) which I will then incorporate in any of the GeoX packages So these are the pieces that are there. The plan in text is: - Have a incarnation of a "point" and make that switch context from planar to spherical - Use planar treatment with the Geometry package (intersections etc.) - Use this "point" to generate shapes either geometric or geographic - Be able to read and write in common formats like GeoJSON and KML - Make shapes be composable and inspectable with the existing tools I think GIS needs more but what we have is more than just a start. The projection system with the current code is WGS84 for sure. If there are other needs we need to think about this early. For everything else I'm open ears. Even for the idea of having a pharo-gis github project to collect those things to a common place. But I like to discuss GIS and not if it makes sense to have a all of these github repos. Norbert [1] https://github.com/zweidenker/GeoJSON <https://github.com/zweidenker/GeoJSON> [2] https://github.com/zweidenker/KML <https://github.com/zweidenker/KML> [3] https://github.com/zweidenker/Geography <https://github.com/zweidenker/Geography> [4] https://github.com/pharo-contributions/Geometry <https://github.com/pharo-contributions/Geometry> > Am 04.06.2020 um 05:31 schrieb Serge Stinckwich <serge.stinckwich(a)gmail.com>: > > Dear all, > > there was already some discussion in the list about GIS support for Pharo previously. > > Working on CORMAS multi-agent simulation platform: https://github.com/cormas/cormas <https://github.com/cormas/cormas> some developers feel the need to have more GIS support for Pharo. > > I know of existing GIS software: > - GeoJSON by Zweidenker: https://github.com/zweidenker/GeoJSON <https://github.com/zweidenker/GeoJSON> > - ESRI ascii raster, done by Stephane recently: https://github.com/Ducasse/ESRI-ASCII-Raster <https://github.com/Ducasse/ESRI-ASCII-Raster> > - shapefile support by Hernan: http://smalltalkhub.com/#!/~hernan/Shapes <http://smalltalkhub.com/#!/~hernan/Shapes> > (to be moved to github) > - I found this project also: http://www.squeaksource.com/gekon.html <http://www.squeaksource.com/gekon.html> > > I know that Etienne Delay is also interested by GIS support and propose to implement OpenGIS model support: https://github.com/cormas/cormas/issues/139 <https://github.com/cormas/cormas/issues/139> > > Can we try to unite and maybe create a pharo-GIS organization on github to federate our efforts? > > Cheers, > -- > Serge Stinckwich > https://twitter.com/SergeStinckwich <https://twitter.com/SergeStinckwich>

June 4, 2020

Re: [Pharo-users] Moose install

by StÃ©phane Ducasse

I do not think that Moose should be loaded like that. you can obtain a build from the launcher and all the code should be hosted on github now. S. > On 3 Jun 2020, at 22:52, Michael Burns <michaelburns(a)mac.com> wrote: > > > From: Michael Burns <michaelburns(a)mac.com> > Subject: Moose install > Date: 3 June 2020 at 22:52:10 CEST > To: "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> > > > Pharo 8 on Mac. > > I used Pharo Project Catalog to install Moose. > > > But, it looks like there were maybe some errors. > When I search for Moose in the system browser I find these packages: > > ConfigurationOfMoose > ConfigurationOfMooseAlgos > Moose-Algos-Graph > Mose-Algos-Graph-Tests > > However, in the Transcript I found a number of <ClassName> is Undeclared. >> And at the end: Error: Cannot resolve symbolic version #release1 > > On the positive side, testRunner says that all Moose*-Tests test cases pass. > > Am I good? > Or is there something else to do here? > On the MooseTechnology page it seems to indicate that the latest version they have runs on Pharo 7. > > ...finished 1.0 > Fetched -> ConfigurationOfMoose-TudorGirba.364 --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ > Loaded -> ConfigurationOfMoose-TudorGirba.364 --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ > Loading 5.0 of ConfigurationOfMoose... > Fetched -> ConfigurationOfPastell-TorstenBergmann.13 --- http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ --- http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ > Loaded -> ConfigurationOfPastell-TorstenBergmann.13 --- http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ --- http://smalltalkhub.com/mc/PharoExtras/Pastell/main/ > Fetched -> ConfigurationOfPetitParser-AndreiChis.82 --- http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- http://smalltalkhub.com/mc/Moose/PetitParser/main/ > Loaded -> ConfigurationOfPetitParser-AndreiChis.82 --- http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfMetanool-GeorgeGanea.21 --- http://smalltalkhub.com/mc/Moose/Metanool/main/ --- http://smalltalkhub.com/mc/Moose/Metanool/main/ > Loaded -> ConfigurationOfMetanool-GeorgeGanea.21 --- http://smalltalkhub.com/mc/Moose/Metanool/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfGlamour-TudorGirba.225 --- http://smalltalkhub.com/mc/Moose/Glamour/main/ --- http://smalltalkhub.com/mc/Moose/Glamour/main/ > Loaded -> ConfigurationOfGlamour-TudorGirba.225 --- http://smalltalkhub.com/mc/Moose/Glamour/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfGToolkit-GeorgeGanea.97 --- http://smalltalkhub.com/mc/Moose/GToolkit/main/ --- http://smalltalkhub.com/mc/Moose/GToolkit/main/ > Loaded -> ConfigurationOfGToolkit-GeorgeGanea.97 --- http://smalltalkhub.com/mc/Moose/GToolkit/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfXMLParser-monty.353 --- http://smalltalkhub.com/mc/PharoExtras/XMLParser/main/ --- http://smalltalkhub.com/mc/PharoExtras/XMLParser/main/ > ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (DTDCachingExternalEntityResolver is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLAbstractFactory is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLFileHandle is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLParserLimits is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLStreamConverter is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLClassFinder is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline297 (XMLClassFinder is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (DTDCachingExternalEntityResolver is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLAbstractFactory is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLFileHandle is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLParserLimits is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLStatelessStreamConverter is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLStreamConverter is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLClassFinder is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline312 (XMLClassFinder is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (DTDCachingExternalEntityResolver is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLAbstractFactory is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLFileHandle is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLParserLimits is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLStatelessStreamConverter is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLStreamConverter is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLClassFinder is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline321 (XMLTokenizerState is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline332 (DTDCachingExternalEntityResolver is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline332 (XMLAbstractFactory is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline332 (XMLFileHandle is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline332 (XMLParserLimits is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline332 (XMLStreamConverter is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline332 (XMLStatelessStreamConverter is Undeclared) > ConfigurationOfXMLParser>>initializeClassesForGSBaseline332 (XMLTokenizerState is Undeclared) > Loaded -> ConfigurationOfXMLParser-monty.353 --- http://smalltalkhub.com/mc/PharoExtras/XMLParser/main/ --- http://smalltalkhub.com/mc/PharoExtras/XMLParser/main/ > Fetched -> ConfigurationOfPetitSQLParser-GeorgeGanea.34 --- http://smalltalkhub.com/mc/Moose/PetitSQLParser/main/ --- http://smalltalkhub.com/mc/Moose/PetitSQLParser/main/ > Loaded -> ConfigurationOfPetitSQLParser-GeorgeGanea.34 --- http://smalltalkhub.com/mc/Moose/PetitSQLParser/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfMooseAlgos-AndreiChis.60 --- http://smalltalkhub.com/mc/Moose/MooseAlgos/main/ --- http://smalltalkhub.com/mc/Moose/MooseAlgos/main/ > Loaded -> ConfigurationOfMooseAlgos-AndreiChis.60 --- http://smalltalkhub.com/mc/Moose/MooseAlgos/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfOSProcess-ThierryGoubier.41 --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ > Loaded -> ConfigurationOfOSProcess-ThierryGoubier.41 --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfMerlin-GeorgeGanea.48 --- http://smalltalkhub.com/mc/Moose/Merlin/main/ --- http://smalltalkhub.com/mc/Moose/Merlin/main/ > Loaded -> ConfigurationOfMerlin-GeorgeGanea.48 --- http://smalltalkhub.com/mc/Moose/Merlin/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfRoelTyper-StephaneDucasse.3 --- http://smalltalkhub.com/mc/RMoD/RoelTyper/main/ --- http://smalltalkhub.com/mc/RMoD/RoelTyper/main/ > Loaded -> ConfigurationOfRoelTyper-StephaneDucasse.3 --- http://smalltalkhub.com/mc/RMoD/RoelTyper/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfFame-CyrilFerlicot.40 --- http://smalltalkhub.com/mc/Moose/Fame/main/ --- http://smalltalkhub.com/mc/Moose/Fame/main/ > Loaded -> ConfigurationOfFame-CyrilFerlicot.40 --- http://smalltalkhub.com/mc/Moose/Fame/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfSmallDude-GeorgeGanea.41 --- http://smalltalkhub.com/mc/Moose/SmallDude/main/ --- http://smalltalkhub.com/mc/Moose/SmallDude/main/ > Loaded -> ConfigurationOfSmallDude-GeorgeGanea.41 --- http://smalltalkhub.com/mc/Moose/SmallDude/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> ConfigurationOfRoassal2-AlexandreBergel.144 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Loaded -> ConfigurationOfRoassal2-AlexandreBergel.144 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Fetched -> Moose-Help-TudorGirba.5 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Famix-Specifications-TudorGirba.7 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-HismoImporter-gl.12 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-Test-HismoImporter-StephanEggermont.5 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Arki-Reporter-Core-AndreHora.21 --- http://smalltalkhub.com/mc/Moose/Arki/main/ --- http://smalltalkhub.com/mc/Moose/Arki/main/ > Fetched -> Arki-Tests-Reporter-TudorGirba.9 --- http://smalltalkhub.com/mc/Moose/Arki/main/ --- http://smalltalkhub.com/mc/Moose/Arki/main/ > Fetched -> Famix-Tests-C-AndreHora.6 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Famix-Tests-Extensions-TudorGirba.25 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Dynamix-Tests-Core-TudorGirba.17 --- http://smalltalkhub.com/mc/Moose/DynaMoose/main/ --- http://smalltalkhub.com/mc/Moose/DynaMoose/main/ > Fetched -> Moose-TestResources-Reference-Core-TudorGirba.3 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-Reference-PackageOne-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-LAN-AndreHora.7 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-LCOM-AndreHora.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P4FullInteracted-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P6InteractedReferee-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P5FullReferee-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P1FullReferencer-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P2InteractedReferencerReferee-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P3InteractedReferencer-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P7ReferencerReferee-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P8FullReferencer-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P9FullReferencer-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P10InteractedReferee-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P11FullReferee-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P12FullReferencer-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P13FullReferencer-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-P14FullReferee-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-KGB-PExtensions-tg.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-PackageBlueprint-P1-NicolasAnquetil.2 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-PackageBlueprint-P2-JeanRemyFalleri.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-PackageBlueprint-P3-JeanRemyFalleri.1 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-TestResources-PackageBlueprint-P4-JeanRemyFalleri.3 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Fetched -> Moose-Tests-MonticelloImporter-AndreHora.6 --- http://smalltalkhub.com/mc/Moose/Moose/main/ --- http://smalltalkhub.com/mc/Moose/Moose/main/ > Project: Metanool stable > [1.2] > Fetched -> ConfigurationOfMagritte3-AndreiChis.128 --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ > Loaded -> ConfigurationOfMagritte3-AndreiChis.128 --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ --- /Users/Michael/Documents/Pharo/images/Pharo 8.0 - 64bit (stable)/pharo-local/package-cache > Project: Magritte3 stable > [3.5.2] > Fetched -> ConfigurationOfGrease-CyrilFerlicot.349 --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ > Loaded -> ConfigurationOfGrease-CyrilFerlicot.349 --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ > Error: Cannot resolve symbolic version #release1 > > > > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

June 4, 2020

Re: [Pharo-users] ESRI ASCII raster format

by StÃ©phane Ducasse

> > It was fun. > My implementation could be more robust but for 2 hours coding. > It was a fun kata. > > Would you want to share your work during our next CORMAS meeting, Friday? If you want now cormas can use it, fork it, expand,â¦. I did it for you as an exercise for me. S.

June 4, 2020

GIS support for Pharo

by Serge Stinckwich

Dear all, there was already some discussion in the list about GIS support for Pharo previously. Working on CORMAS multi-agent simulation platform: https://github.com/cormas/cormas some developers feel the need to have more GIS support for Pharo. I know of existing GIS software: - GeoJSON by Zweidenker: https://github.com/zweidenker/GeoJSON - ESRI ascii raster, done by Stephane recently: https://github.com/Ducasse/ESRI-ASCII-Raster - shapefile support by Hernan: http://smalltalkhub.com/#!/~hernan/Shapes (to be moved to github) - I found this project also: http://www.squeaksource.com/gekon.html I know that Etienne Delay is also interested by GIS support and propose to implement OpenGIS model support: https://github.com/cormas/cormas/issues/139 Can we try to unite and maybe create a pharo-GIS organization on github to federate our efforts? Cheers, -- Serge Stinckwic h https://twitter.com/SergeStinckwich

June 4, 2020

Re: [Pharo-users] ESRI ASCII raster format

by Serge Stinckwich

On Thu, Jun 4, 2020 at 5:16 AM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I did it as a kata as fast as I could â¦ > > https://github.com/Ducasse/ESRI-ASCII-Raster > > I found the spec a bit strange > yes this is a very old format ... > > The header information is followed by cell value information specified in > space-delimited row-major order, with each row separated by a carriage > return. > and > > - No carriage returns are necessary at the end of each row in the > raster. The number of columns in the header determines when a new row > begins. > > O_o > > so I followed the example on wikipedia > > It was fun. > My implementation could be more robust but for 2 hours coding. > It was a fun kata. > Would you want to share your work during our next CORMAS meeting, Friday? Regards, -- Serge Stinckwic h https://twitter.com/SergeStinckwich

June 4, 2020