sos4R - 52° North Innovation Price Presentation
•
1 gefällt mir•463 views
Final presentation of the winning project of the 52° North Innovation Price sos4R - Accessing a Sensor Observation Service from R.
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie sos4R - 52° North Innovation Price Presentation
Ähnlich wie sos4R - 52° North Innovation Price Presentation (20)
Mehr von Daniel Nüst
Mehr von Daniel Nüst (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
sos4R - 52° North Innovation Price Presentation
- 4. motivation?
- 5. open data!
- 10. based on... XML RCurl getting sos and r to work together...
- 11. … No automatic class creation – like XMLBeans …
- 12. … O&M is extremely flexible, especially when linking to GML …
- 13. features
- 14. POST requests: GET requests: http
- 15. core operations profile GetCapabilities DescribeSensor GetObservation GetObservationById
- 16. exchangeability
- 17. … the parser of every of these elements can easily be changed …
- 18. myParseSensorML <- function(obj) { root <- xmlRoot(obj) return(xmlName(root)) } mysos = SOS( url = "http://www.sos.de/sos", parsers = SosParsingFunctions( "DescribeSensor" = myParseSensorML) ) … example of replacing a parsing function. Here the parsing for the response to a describesensor operation …
- 19. filters?
- 20. filters!
- 21. read.sos info.sos read.table read.csv ... User survey!
- 22. Question! … what vocabulary should be used?
- 23. … demo time …
- 24. … sos4R is not (!) for exploring, find the desired stations using the ThinSWEClient …
- 25. Water level for example buoy in northern sea near Hamburg
- 27. … beta testers wanted …
- 28. Roadmap and tasks 1 week: beta RELEASE and end user documentation including use cases, 2 weeks: developer documentation and todo list compilation
- 29. blog: www.nordholmen.net/sos4r community: http://52north.org/geostatistics/ thanks! questions?
Hinweis der Redaktion
- Last year WPS, this year SOS
- Good that I am first, before the shiny easy user interface for normal people This is what I consider a good user interface... but I don't target normal people, not at all, I target... people like us - Researchers, statisticians, geostatisticians like that! People like R
- Png screenshot, blown up, some strange artefacts of the compression Almost like a galaxy, something from outer space, weird, foreign, maybe (!) fascinating, but not really explainable – that is what normal people must think when they use R for the first time My target audience are people who work with R. Not „normal people“, but as the Google chief analyst puts it: The people with the sexiest job in the next ten years!
- Personal motivation Something that should be done /is worth starting. A project that is of great use to other people and might actually be used by others Don't want to implement/work with standards for the standards sake only, but use what I learned for interdisciplinary purposes Enable „real“ analysis by real statisticans The power of R (plots, analysis) – > R
- Governments organisations
- R is a free software environment for statistical computing and graphics. Several platforms, Open Source Statistical modesl, tests, time-series analysis, classification, … you name it! Extensible via packages NO BLACK BOX
- SOS 1.0.0 A standardized data storage service for observations made by sensors... Do I even need to explain? It comes with en entourage...
- O&M Sampling (SA) OGC Common What is used where? Don't need to read those top to bottom, but good to know what they are about! Capsule this from a user!
- What is needed to get R and SOS together? Client and Service Client XML decoding XML encoding KVP encoding XML Rcurl (libcurl)
- No XML Beans , some code generating feature in package XML, but couldn't get it to run properly with all the features I need Some design choices in representation of XML in R classes
- Flexibility of O&M Some work on simple profile, but disgarded (too big a project to solve „on the side“) Especially: hierachical orderings, optional elements and attributes, GML types with a huge amount of optional metadata attributes DECISION TIME: 52N SOS O&M Profile, not well defined but constructable from code inspection
- Interactive encoding of requests and automatic decoding/parsing of responses to R objects for subsequent analysis Never be able to handle all options, so what is the „main feature“?
- Transfer method and encoding? Support profile of 52N SOS Interactive creation of GET and POST request Get request as defined by OOSTethys Best Practice We are a community of software developers and marine scientists who develop open source tools to integrate ocean observing systems. Our goal is to dramatically reduce the time it takes to install, adopt and update standards-compliant Web services.
- Exchangeability in the code for Parsers , Encoders , Converters Using R feature that methods can be passed as parameter values
- Filters not complete! All possible with manual construction... Spatial operators: lacking the encoders for GmlFeatures and construction functions for the features
- Filters not complete! All possible with manual construction... Spatial operators: lacking the encoders for GmlFeatures and construction functions for the features Ok so far on the encoding side, BUT I CAN NEVER HANDLE ALL POSSIBILITIES IN A SOS...
- R has read.table, read.csv, read... convenience/helping function s Based on user survey Access parts of capabilities
- Question for all : Do or do not use SWE/SOS terms??? PRO USING THEM : possible confusing later on, or for experienced users, everybody comes from a certain domain anyway, these are flexible... CON USING THEM : learning threshold, a little bit „unusual“, maybe only for non-native speakers?
- Examples! Important to say: Sos4R is NOT for exploration! Non-R users might not get everything From the moment the data frame is given, it's only R !
- Bake Z plot(r1clean$Time, r1clean$Wasserstand, type = &quot;l&quot;, ylim=c(200,800))
- Based on weathersos
- (BETA-) TESTERS WANTED! What is tested? Time series, simple plots What is not tested? Spatial stuff, requests, spatial analysis Support will be given!
- Roadmap 1 week: beta RELEASE end user documentation including more tests for coercion and use cases 2 weeks: developer documentation (wiki) and todo list compilation