Welcome to Planet OSGeo

November 20, 2024

November 19, 2024

News item: FOSS4G Europe 2024 Tartu final press release - OSGeo
November 2024

Dear OSGeo community,

it has now been some months since FOSS4G Europe 2024 in Tartu, Estonia.

We, the LOC would like to thank you all for your participation, either on site or via the interwebs, for your proposals for presentations and workshops - you helped us put together this amazing event in our hometown. You've helped us create something that will always have a very special place in our hearts.

The final press-release for FOSS4G Europe 2024 is - finally :slight_smile: - ready and can be accessed under the foundation news at osgeo.org [1]. Further links to photos, presentation videos on TIB-AV portal and YouTube, and to the academic track proceedings are all in there.

We hope you enjoyed your time in Tartu, and in the surrounding areas if you had time to explore a bit more.

So one last time - on behalf of the FOSS4G Europe 2024 LOC, thank you and see you very soon.

Tõnis Kärdi
FOSS4G Europe 2024 chair

[1] - FOSS4G Europe 2024 Tartu final press release - OSGeo

About FOSS4G Europe
--------------------------------
The FOSS4GE conference, a European extension of the Open Source Geospatial Foundation (OSGeo) annual FOSS4G event, connects professionals in the geoinformation software realm. FOSS4G Europe 2024 in Tartu was the eastern and northernmost (and as it turned out - largest) ever FOSS4G Europe conference to date.

About OSGeo
-------------------
The Open Source Geospatial Foundation (OSGeo) is a non-profit
organization dedicated to the development and promotion of open-source
geospatial technologies and data. OSGeo serves as an umbrella
organization for the collaborative development of open source
geospatial software, and provides financial, organizational, and legal
support to the broader geospatial community.

_______________________________________________
Announce mailing list
Announce@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/announce

1 post - 1 participant

Read full topic

by Astrid_Emde_OSGeo at November 19, 2024 09:05 PM

News item: Welcoming our new OSGeo Charter Members 2024 - OSGeo
November 2024

OSGeo would like to welcome our new OSGeo Charter Members 2024.

We are happy to announce that the following people were accepted as OSGeo Charter Members:

     Alberto Vavassori from Italy
     Caitlin Haedrich from United States of America
     Cholena Smart from Australia
     Claudio Iacopino from Italy
     Dave Barter from United Kingdom
     Felipe Matas from Chile
     Gresa Neziri from Kosovo
     Hamidreza Ostadabbas from Iran
     Mathieu Pellerin from Cambodia
     Matthias Daues from Germany
     Maxime Collombin from Switzerland
     Petr Sevcik from Czech Republic
     Ponciano da Costa de Jesus from Timor-Leste
     Sami Mäkinen from Finland
     Scott McHale from Canada
     Tobias Wendorff from Germany
     Vasil Yordanov from Bulgaria
     Vincent Sarago from France
     William Dollins from United States of America
     Youssef Harby from Egypt

You are welcome to find out about our new members at the following page New Member Nominations 2024 - OSGeo

In 2024, we had 21 valid nominations and all were accepted.
This year 300 charter members casted their vote.
The board approved the new members in November 2024.

OSGeo has 580 charter members

  - from 74 countries
  - 11 are retired

Thanks a lot to Luís Moreira de Sousa, Iván Sánchez Ortega, Vicky Vergara (2024 OSGeo Elections CROs) for organizing the OSGeo Election 2024.
Share this

See the full list of the OSGeo Charters member and find a link to every profile page there https://www.osgeo.org/about/charter-members/

About OSGeo
-------------------
The Open Source Geospatial Foundation (OSGeo) is a non-profit
organization dedicated to the development and promotion of open-source
geospatial technologies and data. OSGeo serves as an umbrella
organization for the collaborative development of open source
geospatial software, and provides financial, organizational, and legal
support to the broader geospatial community.

_______________________________________________
Announce mailing list
Announce@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/announce

1 post - 1 participant

Read full topic

by Astrid_Emde_OSGeo at November 19, 2024 07:51 PM

November 18, 2024

This is why I've been hesitant to add type hints to Fiona, Rasterio, and Shapely. David Lord on missteps and misgivings:

I want a "start over" tool for type annotating a Python library. I started with Flask as untyped code, then added annotations until mypy stopped complaining. But this didn't mean the annotations were _correct_. Over time I've fixed various reported issues. I feel like if I could start from scratch again, I'd probably get closer to correct with the experience I've gained. But removing all existing annotations and ignores is too time consuming on its own. #python

by Sean Gillies at November 18, 2024 02:16 AM

GeoServer 2.26.1 release is now available with downloads (bin, war, windows), along with docs and extensions.

This is a stable release of GeoServer recommended for production use. GeoServer 2.26.1 is made in conjunction with GeoTools 32.1, and GeoWebCache 1.26.1.

Thanks to Peter Smythe (AfriGIS) for making this release.

Security Considerations

This release addresses security vulnerabilities and is considered an important upgrade for production systems.

  • GEOS-11557 CVE-2024-45748 High. The details will be released later.

See project security policy for more information on how security vulnerabilities are managed.

Release notes

Improvement:

Bug:

  • GEOS-11524 csw: default queryables mapping not generated
  • GEOS-11543 Unable to use propertyName to filter properties in a GetFeature request when service is not set
  • GEOS-11553 SLD Style: Empty SE Rotationelement throws RuntimeException (QGIS generated SLD)
  • GEOS-11556 NullPointerException when GWC disk quota monitoring is disabled
  • GEOS-11559 The customized attributes editor is prone to setting the wrong attribute source
  • GEOS-11573 TileLayer preview doesn’t work anymore

Task:

For the complete list see 2.26.1 release notes.

Community Updates

Community module development:

  • GEOS-11107 Open search for EO community module: packaging missing gt-cql-json-xx.x.jar
  • GEOS-11517 Using various OGC APIs results in service enabled check related WARN logs
  • GEOS-11560 OGC API modules lack cql2-json in assembly
  • GEOS-11563 Allow configuring a DGGS resolution offset on a layer basis
  • GEOS-11565 Allow configuring the minimum and maximum DGGS resolution for a layer
  • GEOS-11579 DGGS modules prevent GeoServer startup if JEP is not installed

Community modules are shared as source code to encourage collaboration. If a topic being explored is of interest to you, please contact the module developer to make contact and offer assistance, even if it is just to say that it works for you.

About GeoServer 2.26 Series

Additional information on GeoServer 2.26 series:

Release notes: ( 2.26.1 | 2.26.0 | 2.26-M0 )

by Peter Smythe at November 18, 2024 12:00 AM

November 17, 2024

This is a tutorial about Remotior Sensus, a Python package that allows for the processing of remote sensing images and GIS data.
In particular, this tutorial illustrates how to create a high resolution jpg image from a Sentinel-2 image. Of course, this tutorial could be extended to other satellite images such as Landsat.
Following the video of this tutorial.

Read more »

by Luca Congedo (noreply@blogger.com) at November 17, 2024 12:57 PM

November 16, 2024

November 15, 2024

Un año más de excelentes proyectos desarrollados por estudiantes de todo el país que han decidido animarse y experimentar con el uso de las Tecnologías de Información Geográfica. Y una vez más estos estudiantes nos sorprenden con el nivel y la calidad de sus trabajos, logrados en apenas 3 meses, debiendo además atender todas sus otras responsabilidades que el estudio les exige.

Ya son más de 1000 docentes y estudiantes (no sólo de Uruguay, sino que también de México -en 2022- y Colombia -en 2023-) que han participado de esta iniciativa que nació en 2017 y que se realiza anualmente desde entonces, solamente interrumpiéndose en 2020, especialmente por la pandemia del COVID-19.

Este año nos acompañaron como tutores de los equipos concursantes:

  • Romel Vázquez, Universidad Central «Marta Abreu» de Las Villas (Cuba)
  • Ramon Alejandro Claro Torres, Universidad Central «Marta Abreu» de Las Villas (Cuba)
  • Williams Luis Morales Moya, Universidad Central «Marta Abreu» de Las Villas (Cuba)
  • Neftalí Sillero, Faculdade de Ciências da Universidade do Porto (Portugal
  • Carlos Lara, Facultad de Ciencias de la Universidad Católica de la Santísima Concepción (Chile)
  • A/P Nadia Chaer, Comunidad gvSIG Uruguay (Uruguay)
  • Lic. Maximiliano Olivera, profesor de Geografìa, CeRP del Litoral  (Uruguay)
  • Antoni Pérez Navarro, profesor de los Estudios de Informática, Multimedia y Telecomunicación, Universitat Oberta de Catalunya (España)
  • Agustín Reyna, Dirección Nacional de Topografía (Uruguay)

El jurado estuvo integrado por:

  • por el Ministerio de Transporte y Obras Públicas: Arq. Sergio Acosta y Lara
  • por la Dirección General de Educación Secundaria: Insp. Mónica Canaveris
  • por Ceibal: Mag. Lic. Sofía García
  • por la Dirección de Educación Técnico Profesional: Prof. Julio A. Rodríguez
  • por la Universidad Politécnica de Madrid: Dr. Luis Manuel Vilches Blázquez
  • por la Asociación Nacional de Profesores de Geografía: Prof. Irene Lucía Knecht Santana
  • Por la Universidad Central «Marta Abreu» de Las Villas: Dr. Mikel Moreno Hernández

A continuación, los videos de los proyectos ganadores:

proyecto ganador

proyecto finalista

proyecto finalista

Una vez más debemos agradecer a todas y todos los que han hecho posible que esto sucediera: al equipo del MTOP; a las y los tutores; a los integrantes del jurado; a todas y todos los colaboradores en el Plan Ceibal (gracias por su invalorable asistencia); a toda la Asociación gvSIG (gracias a su incansable apoyo es que este proyecto es posible); a la ANEP, en especial a la Dirección General de Educación Secundaria pero también a la Dirección General de Educación Técnico Profesional; a la Universidad Politécnica de Madrid; a las instituciones que este año nos han apoyado: Universidad Central Marta Abreu de Las Villas y la Asociación Nacional de Profesores de Geografía; y a todas las autoridades de las instituciones involucradas que han decidido continuar apoyando esta iniciativa, la que continúa creciendo.

Nos vemos el año que viene

by gvsigbatovi at November 15, 2024 07:36 PM

November 14, 2024

The pgRouting Team is pleased to announce the release of pgRouting version 3.7.0
The latest release is available at [1]
For discussions on the release, go to [2]

To see all issues & pull requests closed by this release see the Git closed milestone for 3.7.0 on Github. [3]

*Support*

  * #2656 Stop support of PostgreSQL12 on pgrouting v3.7
      o Stopping support of PostgreSQL 12
      o CI does not test for PostgreSQL 12

*New experimental functions*

  * Metrics
      o pgr_betweennessCentrality

*Official function changes*

  * #2605 Standarize spanning tree functions output
      o Functions:
          + pgr_kruskalDD
          + pgr_kruskalDFS
          + pgr_kruskalBFS
          + pgr_primDD
          + pgr_primDFS
          + pgr_primBFS
      o Standarizing output columns to (seq, depth, start_vid, pred,
        node, edge, cost, agg_cost)
          + Added pred result columns.

*Experimental promoted to proposed*

  * #2635 pgr_LineGraph ignores directed flag and use negative values
    for identifiers.
      o pgr_lineGraph
          + Promoted to proposed signature.
          + Works for directed and undirected graphs.

*Code enhancement*

  * #2599 Driving distance cleanup
  * #2607 Read postgresql data on C++
  * #2614 Clang tidy does not work

*To update your database*

Download the packaged version from your operating system, and use this command in the database:
ALTER EXTENSION pgrouting UPDATE TO "3.7.0";

[1]. Release v3.7.0 · pgRouting/pgrouting · GitHub
[2]. v3.7.0 · pgRouting/pgrouting · Discussion #2677 · GitHub
[3]. Issues · pgRouting/pgrouting · GitHub

1 post - 1 participant

Read full topic

by jsanz at November 14, 2024 10:25 AM

November 13, 2024

I saw a physical therapist yesterday. I had a virtual visit with my physician today. I had a 2 mile hike in the sun around a local reservoir. Now I'm listening to the Glenn Branca Orchestra on The Frow Show and my take on my health is: let's go!

The expert consensus is that I did not injure my spine, but that muscles in the left side of my hip have clamped down on a nerve. I'm going to proceed as if that is true, foam rolling, walking, and running through the pain, and not worrying about my spine cracking in pieces. I do have a little bit of numbness in my upper left leg and so I will not directly dive into long technical downhill runs. I expect that I'll resolve that soon.

by Sean Gillies at November 13, 2024 02:16 AM

November 12, 2024

I've taken a momentary break from our (admittedly) glacial pace of MapGuide development to put out another release of mapguide-rest 

This release includes the following changes:

  • Fix missing reverse routing on selection overview
  • Fix bad feature query preparation when querying against watermarked layers
  • Relax strict-typing on MgReaderToGeoJsonWriter::FeatureToGeoJson() so that it can work with MgPaginatedFeatureReader allowing pagination to work again
  • Added missing properties parameter to swagger defn for session-based feature selection route

We now return to regularly-scheduled programming of trying to get MapGuide Open Source 4.0 to the finish line.

As for mapguide-rest, I envision at least once more major RC *after* the final release of MapGuide Open Source 4.0 before finally wrapping things up on development work and pulling the trigger on the mapguide-rest 1.0 final release. Enough of this RC-after-RC business!

by Jackie Ng (noreply@blogger.com) at November 12, 2024 01:46 PM

It was great to attend FOSS4G:UK South West 2024 in Bristol on 12th Nov, at OSGeo:UK’s now regular Bristol Venue, The Engine Shed. The event was a sell out and we had 62 people in the Engine Shed’s main room.

This was the first time in a while that I have been to a FOSS4G:UK as an attendee rather than as an organiser - and it made a nice difference! We had 14 great presentations, covering a whole range of topics including digitalization of railways, reproducible science, real time vessel monitoring, landscape heritage, open source funding, cloud native web apps and a whole variety of useful open source tools.

Unfortunately I missed the first presentation - thanks Great Western Railways! - but one common theme that cropped up a lot was how social media as a tool for open source projects has changed dramatically. James Milner said that social media used to be a great way to promote his program, Terra Draw, but know he gets no where near the same impact from using social media. It’s now a bit of a big unknown, and I particularly liked how he summarised this:

Interestingly, I sent out a number of social media posts to Twitter (X), Mastodon and LinkedIn, and LinkedIn got the most response, so make of that what you will! Although I think it’s fair to say LinkedIn is not universally loved, as it was memorably described as “Grindr for Business” by Andrew Bailey!

The presenters have also mastered the use of memes, with Matt Travis hitting home with some of the perils of waiting for large data sets to load:

and of course also

It was also fantastic to get FAIR Open Science and FAIR workflows mentioned in the presentation by Richard Conway & Garin Smith from Telespazio, who are in the process of developing an exploration platform that allows researchers both to share their data, code and their methods in a reproducible form.

I also had the opportunity to speak about GoFundGeo and talk about how OSGeo:UK is funding a range of open source geospatial projects that will have an impact in the UK. Join the OSGeo:UK mailing list or check the website to find out more.

Nick presenting GoFundGeo, thanks to Sam Franklin for the photo

Finally, as ever, it was great to meet new people and network again with old friends at these events. I know of at least one contract opportunity, as well a number of potential ones and also I think some new volunteers for OSGeo:UK!

Thanks very much to all the organisers - Pascal Coulon, Alastair Graham, Sam Franklin, Dan Ormsby, Illya Sparkes-Santos, Ant Scott, as well as everyone who came along and took part.

If you want help or advice on any open source geospatial tool, or are interested in Introductory or Advanced GIS training in QGIS or R, please do contact me.

by Nick Bearman at November 12, 2024 12:00 AM

November 11, 2024

GeoSpatial Techno is a startup focused on geospatial information that is providing e-learning courses to enhance the knowledge of geospatial information users, students, and other startups. The main approach of this startup is providing quality, valid specialized training in the field of geospatial information.

( YouTube | LinkedIn | Facebook | X )


Exploring CQL and ECQL Filtering in GeoServer

In this session, we want to talk about the Using CQL/ECQL Filters in GeoServer in detail. If you want to access the complete tutorial, click on the link.

Introduction

Contextual Query Language (CQL) is a text-based query for search/retrieval adopted by the OGC for the Catalogue Web Services specification. Unlike the XML-based Filter Encoding language, CQL is more readable and easier for manual authoring. However, it has limitations, such as not being able to encode ID filters and requiring the attribute to be on the left side of comparison operators.

To overcome these limitations, GeoServer offers an extended version called ECQL, which closely resembles SQL and provides greater flexibility. ECQL allows users to define filters for querying data in GeoServer using attribute comparisons, logical operators, and spatial predicates. It is compatible with GeoServer’s REST API and can be used for WMS and WFS requests to retrieve filtered data.

Note. This video was recorded on GeoServer 2.22.4, which is not the most up-to-date version. Currently, versions 2.25.x and 2.26.x are supported. To ensure you have the latest release, please visit this link and avoid using older versions of GeoServer.

Note. Future version of GeoServer will include support for CQL2 which provides both a text and a JSON representation.

Comparison operators

To compare attribute values or other numeric and text values in your CQL / ECQL (Extended Common Query Language) expressions, you can utilize comparison operators.

In the Layer Preview section, first click on the OpenLayers option for the topp:states layer. Next, locate and click on the Toggle options toolbar in the top left corner to access the advanced options.

In the CQL filter box within this toolbar, enter the filter expression STATE_NAME = 'Texas', and then press the Apply button. This filter will retrieve and display the data for the state of Texas.

By reviewing the following examples using the Toggle options toolbar from the LayerPreview page, you will learn how to effectively understand and apply comparison operators using CQL/ECQL expressions:

  • ‘PropertyIsGreaterThanOrEqualTo’ filter

This filter shows the states that have more than or equal to 5 million inhabitants.

PERSONS >= 5000000
  • ‘PropertyIsLike’ filter

This filter shows the states whose names, contain the letters ‘ing’ like Washington and Wyoming.

STATE_NAME like '%ing%'
  • ‘PropertyIsBetween’ filter

This filter shows the states with a population of 5 million to 10 million.

PERSONS between 5000000 and 10000000

Spatial operators

These operators enable you to perform spatial queries and filter data, based on various relationships between geometries. Here are the explanations for some commonly used spatial operators:

  • ‘Intersect’ filter

This filter allows you to query spatial data in GeoServer based on geometric intersection relationships. This filter returns all features that have any spatial intersection or overlap.

The syntax for the Intersect filter in CQL is as follows:

Intersects(the_geom,Point(-90 40))
  • ‘Within’ filter

The Within filter checks if a spatial object is completely within another spatial object. This filter retrieves all features that are located within the boundaries of a specified geometric shape, using spatial relationships.

Within(the_geom,Polygon((-100 30,-100 45,-80 45,-80 30,-100 30)))
  • ‘Contains’ filter

This filter is the inverse of the “Within” filter. It checks if a spatial object completely contains another spatial object and helps you retrieve features that fully enclose the specified geometry.

CONTAINS(the_geom,LINESTRING(-73.9 43.5,-77.76 42.56))

Bounding Box operators

The Bounding Box operator is used to filter data based on a specified bounding box. The “bbox” filter in CQL allows you to query spatial data in GeoServer based on a bounding box or a rectangular area.

CQL filters can also be utilized with the GET method. To use the bbox filter using the GET method, enter the following code in the URL address bar of your browser:

http://localhost:8080/geoserver/topp/wms?service=WMS&version=1.1.0&request=GetMap&layers=topp:states&bbox=-124.73142200000001,24.955967,-66.969849,49.371735&width=768&height=330&srs=EPSG:4326&format=application/openlayers&CQL_FILTER=BBOX(the_geom,-110,41,-95,45)

This filter enables you to retrieve all features that intersect, or are contained within the specified bounding box.


In this session, we took a brief journey through the “CQL filtering in GeoServer”. If you want to access the complete tutorial, click on the link.

by Nima Ghasemloo at November 11, 2024 12:00 AM

November 10, 2024

November 09, 2024

Even Rouault has proposed a new, modern, and more coherent command line interface (CLI) for the GDAL/OGR project. I think it's a good idea and a good time to do it. I've wanted a better one for about 15 years. Even credits Rasterio for inspiration, and that's gratifying to see. I started writing Rasterio 10 years ago in part because I wanted a better CLI for GDAL.

What I wanted in a GDAL CLI were the following features:

  • A root command and a few subcommands, one namespace for everything.

  • Uniform arguments and options with predictable ordering and naming.

  • Good documentation of arguments and options.

  • More subcommands with fewer options each. Making gdal_translate into 3-4 commands, for example.

  • Input and output that favor stdin/stdout and JSON.

  • Ease of installation. For example, with pip instead of an OS package manager.

I estimated in 2013-2014 that it was not feasible for me to achieve those goals within the GDAL project itself. GDAL and its community had no funding for this kind of work at the time. I found the GDAL project's tests somewhat inscrutable and frustrating. A hefty legacy of documentation and folk wisdom about the old ways would have to be updated. Mostly by me, certainly. And the GDAL user community largely did not care. Free software that was fast and effective (and, most of all, free!) was already more than most people had dreamed of. A GIS analyst had so many business and organizational problems to deal with already that the rough edges of gdalinfo and gdal_translate didn't even crack her top 20. Software polish wasn't a big concern in the second decade of FOSS4G. I think it's still a hard thing to sell. Individual consumers will pay money for slick, well-designed software that makes them feel good. Organizations value polish less. And neither GDAL nor Rasterio sell anything to individual consumers.

Overhauling gdal_translate, ogr2ogr, and friends within the GDAL project looked like a non-starter to me. Pushing a herd of boulders up a hill, by myself, for free, for a community that was largely content with working around and stepping over these boulders. I think I made the right choice for myself. I got to start from scratch, move fast, and use a modern CLI framework. I made a command line interface for Rasterio that, while not perfect, met most of my goals. And I didn't go broke or burn out while doing it.

Today, thanks to years of fundraising work by Howard Butler, Paul Ramsey, Kristian Evers, and Even, the GDAL project does have funding to overhaul its command line interface as an aspect of overall project health and maintenance. Multiple developers can be paid to work on it. They won't have to donate their time to it as I would have. Rasterio's command line interface can't be adopted by GDAL, or be forked to become GDAL's because it doesn't have all the features of existing GDAL programs (or even of gdal_translate and ogr2ogr for that matter), and my decision to have more subcommands with fewer options is kind of against the grain of GDAL. But the new GDAL CLI can adopt the demonstrably useful features and design of Rasterio's. JSON output, for example, is something that GDAL has already picked up from Rasterio.

Rasterio will certainly fade a little if the new GDAL CLI is designed and executed well. But that's in the nature of software and software communities. Rasterio has always depended on GDAL and benefited from being built on a technically solid and well loved foundation. And I didn't invent CLI subcommands and JSON output, not at all. It's not unfair. If you succeed in open source, if you move the needle, you will be emulated. In this case, I think we can call it progress. I'm content.

In the long run, I stand to get half of what I originally wanted from a GDAL CLI, the first three of the six features I listed above. And there's probably still room for a suite of Unix style programs with different opinions and design decisions, especially if it and GDAL agree on basic concepts, arguments, options, and flags.

by Sean Gillies at November 09, 2024 04:54 PM

I stopped using Twitter a while ago. Then it was rebranded as "X". I dithered about deleting my account. Would it be taken over by crypto scammers or an 18 year-old Russian army private or contractor? I've come to the conclusion that I don't care anymore. They can have it if they want. I've downloaded my archive and clicked "deactivate your account".

If you see a post from an @sgillies on X, it isn't me.

by Sean Gillies at November 09, 2024 04:03 AM

November 08, 2024

A maior promoção de 2024 começa hoje, dia 08 e vai até o dia 10 de novembro.

✅ Essa é a sua chance de adquirir nossos cursos com descontos imperdíveis nessa Black Friday.

Cursos que estão com desconto:

📍Combo: PostgreSQL, PostGIS e GeoServer (EAD Videoaula com 38h/aula)
💰50% de desconto
🗓 Acesso por 24 meses

📍Combo: PostgreSQL, PostGIS, GeoServer e OpenLayers 4 (EAD Videoaula com 53h/aula)
💰60% de desconto
🗓 Acesso por 24 meses

👉🏻 Os cupons de desconto estão sendo informados no nosso Grupo VIP, basta você clicar no link abaixo :

👉🏻 https://geocursos.com.br/blackfriday

by Fernando Quadro at November 08, 2024 11:00 AM

Saturday, I reported that I was laid up with a back injury. I'm feeling better today. The pain is manageable and I've been able to spend about half of my time awake upright, standing or sitting on my bed, with regular breaks to touch my toes and do the yoga half lift to stretch my back. I even managed to run a little bit yesterday while helping a guy who was the victim of a hit-and-run incident. Car on car, to be specific. No one was injured, as far as I could tell.

Ban cars. Ban injuries.

by Sean Gillies at November 08, 2024 03:54 AM

November 07, 2024

November 06, 2024

November 05, 2024

If you're not already using pytest's tmp_path fixture, you really should. The fixture provides a temporary directory for testing use. A directory that you can't reference from other test runs or from other test functions in the same run, but that isn't immediately deleted when your tests finish. The directory is created in your account temporary location and is eventually cleaned up by your computer's operating system. Until then, you can open the directories and their files in other applications.

I've been making assertions on datasets in Rasterio's tests and also dragging them into QGIS for a closer look after the tests finish.

https://live.staticflickr.com/65535/54120218694_cd56609f30_b.jpg

by Sean Gillies at November 05, 2024 11:56 PM

No mundo do Geomarketing, a precisão é a chave para o sucesso. E uma das etapas cruciais para garantir essa precisão é a coleta de dados em campo.

🔍 Validação Realista: Enquanto os dados de mapas e bases de dados são valiosos, nada supera a validação realista que a coleta de dados em campo oferece. Verificar pessoalmente as informações nos permite confirmar sua precisão e atualidade.

📈 Refinamento Estratégico: Ao mergulhar nas nuances de uma área específica, podemos descobrir insights que simples análises de dados remotos podem negligenciar. Detalhes sobre padrões de tráfego, comportamento do consumidor e características locais podem refinar nossas estratégias de marketing de maneiras surpreendentes.

🗣 Feedback Direto: Interagir com os residentes locais, consumidores e outras partes interessadas nos dá acesso a um feedback valioso e em tempo real. Esse feedback é uma mina de ouro para ajustar nossas estratégias e adaptá-las às necessidades locais.

📊 Personalização Efetiva: Compreender profundamente as características locais nos permite personalizar nossas estratégias de marketing de maneira mais eficaz. Não se trata apenas de atingir o público certo, mas de atingi-lo da maneira certa, levando em conta as particularidades de cada região.

Em suma, a coleta de dados em campo não é apenas uma etapa em um estudo de geomarketing, mas sim o alicerce sobre o qual construímos estratégias eficazes e impactantes. É o que nos permite transformar dados em insights acionáveis e conquistar resultados tangíveis. 🚀🌍

Fonte: Marcio T. Mendonça

by Fernando Quadro at November 05, 2024 12:00 PM