fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.8K
active users

#rspatial

2 posts2 participants0 posts today
Replied in thread

@mdsumner Thanks! This is basically just me trying to understand the current landscape before I dive deeper into the cutting edge stuff from @kylebarron, @paleolimbot and @bdon. Wearing goggles while learning some javascript on the ride. I haven't really looked into raster stuff so far, but if all goes well, I will soon enough, though coming from a climate/atmospheric modelling perspective.

On the left is a standard median S2 composite. On the right is a geomedoid (cell with the smallest distance to the geomedian). It aint quick but this is what I've been working towards for a while now so I'm amped. Better compositing coming to vrtility 📦 soon.

Felt the need to provide students with a visual summary of spatial regression models. Effective? Correct?
#rspatial

Grateful for the great resources: r-spatial.org/book/17-Economet and ruettenauer.github.io/Geodata_

Interestingly I had to use sf and st_intersection before I could make a "CMY set" type plot and color its different pieces...
github.com/geocaruso/MAGEO1642

"Spatial Data Science Languages: commonalities and needs" - that a preprint 11(!) of us wrote together as one of many outcomes of two workshops held in Münster (2023) and in Prague (2024). It summarised where we are, what we share between R, Python and Julia, what are the common challenges, lessons and recommendations - arxiv.org/abs/2503.16686

Big thanks belongs especially to @edzer who kickstarted the whole initiative! And to all the others who participated!

arXiv.orgSpatial Data Science Languages: commonalities and needsRecent workshops brought together several developers, educators and users of software packages extending popular languages for spatial data handling, with a primary focus on R, Python and Julia. Common challenges discussed included handling of spatial or spatio-temporal support, geodetic coordinates, in-memory vector data formats, data cubes, inter-package dependencies, packaging upstream libraries, differences in habits or conventions between the GIS and physical modelling communities, and statistical models. The following set of insights have been formulated: (i) considering software problems across data science language silos helps to understand and standardise analysis approaches, also outside the domain of formal standardisation bodies; (ii) whether attribute variables have block or point support, and whether they are spatially intensive or extensive has consequences for permitted operations, and hence for software implementing those; (iii) handling geometries on the sphere rather than on the flat plane requires modifications to the logic of {\em simple features}, (iv) managing communities and fostering diversity is a necessary, on-going effort, and (v) tools for cross-language development need more attention and support.

@rshean.bsky.social You can avoid running the query on buildings if you check that the city_border is actually a polygon (or more precisely not a POINT): 𝚒𝚏(!𝚜𝚝_𝚐𝚎𝚘𝚖𝚎𝚝𝚛𝚢_𝚝𝚢𝚙𝚎(𝚌𝚒𝚝𝚢_𝚋𝚘𝚛𝚍𝚎𝚛) == "𝙿𝙾𝙸𝙽𝚃"){   𝚙𝚛𝚒𝚗𝚝("𝚌𝚘𝚘𝚕") } 𝚎𝚕𝚜𝚎 {   𝚙𝚛𝚒𝚗𝚝(𝚜𝚝_𝚐𝚎𝚘𝚖𝚎𝚝𝚛𝚢_𝚝𝚢𝚙𝚎(𝚌𝚒𝚝𝚢_𝚋𝚘𝚛𝚍𝚎𝚛)) } #rspatial

Bluesky SocialRussell Shean (@rshean.bsky.social)Independent freelance consultant | data scientist | data engineer | software developer #rstats #python #pydata #bash #databs #azure python tools for #powerbi DMs about freelance projects, collaborations, or just to chat welcome 😁