> 
> What would be the novel aspect(s) of your GIS app?
> 
Metadata is my main concern, and it's important in GIS and could be improved 
upon there -- IMHO. I get the impression from my research that the future of 
serious metadata is rooted in type theory and graph databasing, i.e, being able 
to jump out of a hierarchy. I watched a long video called The Semantic 
Representation of Mathematical Knowledge (https://youtu.be/psSyM1zp82k), and 
these brainiacs gave me the impression that good metadata (for something as 
difficult as math) must be based in type theory.

A while back I worked at a county assessor's office, and we had an ancient 
mainframe that kept track of the county's thousands of land parcels. Typically, 
assessors deal with parcels being split or merged -- or at least changing 
hands. If the lines did in fact change, our system would simply create a new 
state, old state gone, old lines forgotten. I was brought in to do GIS, one 
task being to create a history of land use/parcel changes. Neither my ESRI rig 
or the mainframe had a way to do this -- and all my suggestions made 
bureaucrats nervous... Functional -- at least in theory -- should allow this 
sort of bifurcation and, as I call it, "parallel universing". Maybe I'm getting 
"too far afield," but a never-ending recursion (e.g. infinity mirror) is what 
land/land use is about -- at least if you want to avoid what our mainframe was 
doing. I don't fully grok the whole bitcoin blockchain, but my initial 
understanding is that this is sort of giant recursion too ... but perhaps I'm 
straying off into the weeds a bit.

I'm still green, but what I hear about metaprogramming would also be a benefit 
to GIS, although types and metaprogramming probably don't mix?

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to