Development of a software framework for Planning Support Systems (PSS)
Development of a software framework for Planning Support Systems (PSS)
0 0
pgr-conf-2016
On Github gisvlasta / pgr-conf-2016
Development of a software framework for Planning Support Systems (PSS)
Vasilis Vlastaras * @gisvlastaTopographer
GIS software developer
Research Assistant
. . .
?
Software Development
Planning
Topic: PSS
Planning Support Systems
What are Planning Support Systems ?
What kind of PSS have been developed?
Taxonomy
Attributes Areas of Application Type of softwareCharacteristics
Desktop (90s) Standalone applications Based on existing GIS Developed as modules in existing programs Made for specific purposes Web (00s) Public Participation Solving very specific problemsKlosterman's ascertainment
Lack of integrated solutions comparable to GIS softwareKlosterman's proposal.
Capture actors (planners, stakeholders, government) Reflect processes Provide models Answer what if scenarios Provide models... all in an integrated way
However such systems have not been developed so far ...
... why ?
Reasons for not having integrated PSS solutions
Small user base ? Complicated processes (that change over time) A lot of actors that increase complexity Different planning processes in each country...
Technical reasons
Most of PSS have been developed against a specific database Most of Desktop PSS can be extended using specific programming languages / technologies All web solutions can not be extended. Models provided can not be reused by different systems. Most systems target specific technical audiencesAs a conclusion, existing systems are mostly closed black boxes difficult to extend once you come from another technical background
Can this be changed?
Proposal: PSS Application Framework
Systems built for a previous generation should be replaced with something of our era
What is our era?
Devices Interconnectivity Data Explosion Transition from web of pages to the web of data and applicationsHistory of the web
Interlinked static hypertext pages (forming a web)
Introduction of client scipting -> Interactive web pages
Server side scripting + databases -> Dynamic web pages
Web Applications
Future of the web
From web of pages -> Web of Data
Explosion of Data Open Data Technologies to access and query distributed data (SPARQL, RDF, OWL)Semantic Web -> Pages have machine readable meaning
How is the web transforming?
Web becomes a distributed Universal computational platform Services start talk to each other Data start living remotely and can be accessible remotelyWhat can a PSS do in such a web?
A PSS can become a central consumer of remote models and services Can access data remotely Can run remote processes Can mashup the results in the form of reports and visualizations Can present data stories Can help colaborate on a common platformMore specifically (technical details of framework)
Universal development platform. (The web). Plugin architecture. (Plugins discoverable and installed though the web. Node - npm). Ability to run local or remote processes. Built with JavaScript in mind and extended with a language of developer's choice. JavaScript allows the integration of software libraries built for the web. Database agnostic. Big Data might not be able to be moved locally. So the system should query them remotely (SPARQL). Models should be installed localy or be able to be run remotely. Results should be able to be saved localy or remotely and be presented in the form of visualizations.Not building one more PSS but a framework for models and processes to be developed, we promote the creation of a common technical language of understanding which enables us to create reusable components, discover the things we need to take decisions and have a solid base from where we can start building solutions