GPS World

Tag: web services

  • Comment sought on OGC API standard for geospatial web processing

    Comment sought on OGC API standard for geospatial web processing

    New process simplifies task of computational geospatial processing accessible via web services

    OGC logoThe Open Geospatial Consortium (OGC) seeks public comment on a new draft OGC API standard: OGC API – Processes – Part 1: Core. Comments are due by Oct. 19.

    The draft OGC API – Processes Standard specifies a Web API that enables the execution of computing processes and the retrieval of metadata describing their purpose and functionality. For example, these processes could combine raster, vector, coverage and/or point cloud data with well-defined algorithms to produce new raster, vector, coverage and/or point cloud information.

    The draft OGC API – Processes Standard builds on the Web Processing Service (WPS) 2.0 standard and defines the processing standards to communicate in a RESTful manner using JSON encodings. This API is a newer and more modern way of programming and interacting with resources over the web while allowing better integration into existing software packages.

    In many cases, location data, including data from sensors, must be processed before the information can be effectively used. OGC API – Processes, just like the OGC WPS Interface Standard, provides a standard interface that simplifies the task of making simple or complex computational geospatial processing services accessible via web services.

    Such services include well-known processes found in GIS software as well as specialized processes for 2D/3D/4D modeling and simulation. The API also makes it easy for developers to implement microservices that can handle location data.

    The draft OGC API – Processes Standard provides a similarly robust, interoperable, and versatile protocol for process execution across the Web. OGC API – Processes supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time-consuming tasks.

    As with other OGC APIs, OGC API – Processes consists of optional parts that each provide extra functionality. This specification, Part 1: Core, is intended to be a minimal useful API for the execution of processes from the geospatial domain. There are no constraints on the types of processes that can be published through the API. Examples of processes that have been demonstrated during the development of the draft API standard include routing, contour generation, buffering, coverage processing and several others. The API is therefore expected to be applicable to several domains.

    The candidate OGC API – Processes – Part 1: Core standard is available for review and comment on the OGC Portal. Comments are due by October 19, 2020, and should be submitted via the method outlined on the OGC API – Processes – Part 1: Core draft Standard’s public comment request page.

  • June 30 Leap Second Worries Markets, Internet

    June 30 Leap Second Worries Markets, Internet

    London time - canon t2i
    (Photo credit: @Doug88888, used under CC BY-NC-SA 2.0 license.)

    The coming leap second on June 30 sounds as scary as the (turns out not-so-scary) Y2K bug. But the world has experienced leap second issues before, and most affected industries are taking steps to prepare.

    The world’s clocks will be adjusted by one second on June 30, when a leap second will be inserted into Coordinated Universal Time (UTC), the standard international time scale. In theory, all UTC clocks should insert a second labeled 23h 59m 60s (the leap second) following one labeled 23h 59m 59s UTC. This is equivalent to having all of the clocks in the world stop for one second at that time, as explained in May’s Expert Advice column.

    A problem with some GPS receivers implementing the extra second caused the U.S. Civil GPS Service Interface Committee (CGSIC) to issue a notice in February. But GPS receivers aren’t the only thing that could be affected.

    The Wall Street Journal is reporting that financial regulators and market participants are worried enough about the leap second that they’re planning for potential disruptions. The adjustment could present technical difficulties for traders and exchanges, as some computers might not be programmed to account for the adjustment, according to a Dow Jones report.

    “These guys are agonizing over it,” Steve Allen, a programmer-analyst at the University of California’s Lick Observatory, told Dow Jones. “It is definitely a hassle.”

    “The problem with the extra second is that it’s difficult to gauge how computer systems will react,” according to Journal writer Brian Hershberg.

    A U.S. Commodity Futures Trading Commission spokeswoman said that “For the most part, we’re not too worried,” told Dow Jones. “But of course as the regulator, we do need to ensure folks are ready.”

    The last leap second occurred on June 30, 2012, and that leap second caused technical problems for websites and computing systems — including Reddit, Mozilla, Gawker, FourSquare, Yelp and LinkedIn.

    Google had prepared ahead of time and was unaffected. Google gradually adds a couple of milliseconds to its servers’ clocks throughout the day when a leap second is to occur. According to a 2011 Google blog, “We modified our internal NTP servers to gradually add a couple of milliseconds to every update, varying over a time window before the moment when the leap second actually happens. This meant that when it became time to add an extra second at midnight, our clocks had already taken this into account, by skewing the time over the course of the day.”

    But many web services didn’t follow Google’s lead in 2012 and experienced disruptions. Qantas‘ computer system went down for hours, forcing employees to check in passengers by hand. For background on the 2012 event, and a good explanation on the reason for a leap second, read “Time to Get in Sync” by Richard Langley, GPS World Innovation editor.

    Amazon Web Services said it plans to “implement alternative solutions to avoid the ‘:60’ leap second. This means that AWS clocks will be slightly different from the standard civil time for a short period of time.”

    In the U.S., stock exchanges such as the New York Stock Exchange and Nasdaq are working around the leap-second time (8 p.m. in the U.S.) by closing its after-hours trading a half-hour early, which is scheduled for 8 p.m.

    The Hong Kong Observatory is advising stakeholders and operators in information technology, telecommunication, transport, and finance to review whether systems under their management can handle leap seconds properly, and if necessary, consider testing and adjusting their systems to ensure normal operation during and after the introduction of the leap second.

    Time and frequency company EndRun Technologies is offering leap-second information on its website, and Cisco is offering its customers guidance on how to deal with it.

    Racelogic, who make the LabSat simulator, will be recording the Leap Second as it happens and will then have the scenarios available for customers to replay. A variety of recordings will be taken: GPS, GLONASS, and BeiDou constellations will each be captured as a single channel, and also as a simultaneous triple-constellation recording. These will then be available to use with the LabSat.