Geospatial Without Maps [blog post]
--
https://cercanasystems.com/2025/05/geospatial-without-maps/ <-- shared blog posts
--
[I will be honest, I can’t remember the last time I personally made a map…]
#GIS #spatial #mapping #mapless #AllDataIsSpatial #usecase #appliedscience #appliedtechnology #automation #coding #machinelearning #AI #maintenance #utilities #GPS #infrastructure #datasupply #dataflow #spatialdata #spatialanalysis #spatiotemporal #farming #agriculture #precisionagriculture #yield #InternetOfThings #integration #smartinfracture #earthobservation #model #modeling #routing #urban #planning #spatiallogic #proximity #zonal #statistics #geostatistics #context #systemsintegration #workflows #processmodels #spatialintelligence #decisionsystems #businessrules #efficiency

I'm not feeling the warm fuzzies about trying to do GCP Dataflow (aka Apache Beam) with Typescript. Doesn't feel fully baked.

Also doesn't feel like a lot of doc/examples nor many people using it. I don't think our org should be on the bleeding edge of something like this for a core piece of our infrastructure.

Dunno. Will keep working on it for a bit.

For many years I've observed the following in parallel:

1. General confusion (and in some cases disdain) about the notion of a #SemanticWeb

2. Steadfast effort by a community to keep the vision going, stealthily, as exemplified by the #LODCloud (#DBpedia,, #Wikidata, #Uniprot etc..) and Schema.org (#SchemaOrg)

3. #DataSilos and all the impedance they inflict on the agility of individuals and enterprises alike on the rise i.e., #DataAccess and #DataFlow are still challenging, unnecessarily.

One of the things I'll be talking about in the stream tomorrow: Understanding that https://thi.ng/rstream constructs are essentially defining a #dataflow #graph much like you'd know from a node-graph based editor (a la Blender/Houdini etc.), only obviously with the difference of actually creating such a graph programmatically rather than manually via visual editing. Personally I find this programmatic approach much more powerful, but a visual representation makes it of course much easier to debug & analyze such graph topologies, also to explain & illustrate to others how data and state changes are flowing through the app/system and/or where to attach new features/nodes or optimize/restructure the topology...

Another massive benefit: This approach makes it much easier to build features such that only the most minimal amount of work needs to be done, helping to achieve better performance...

The attached diagram was generated with #Graphviz via https://thi.ng/rstream-dot and shows the dataflow graph for the image vectorization tool mentioned in previous toots.

Full size version:
https://demo.thi.ng/umbrella/trace-bitmap/topology.html

The tool itself:
https://demo.thi.ng/umbrella/trace-bitmap/

The second image shows the minimal code required to generate the #visualization source file...

#Dataflow #computing is a really cool paradigm and now #arcan has shown it's working on it too !

https://arcan-fe.com/2021/04/12/introducing-pipeworld/