I know what you mean, but there is a problem... Facial Recognition has failed ... Personnel need to be identified through other biometric means.
Shahjahan Ahmed Publisher Web: www.seanews.co.uk Phone No: +44 (0)203 302 0097 Email: [email protected] This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -----Original Message----- From: Adam Estrada [mailto:[email protected]] Sent: 13 January 2020 11:56 To: [email protected] Subject: Re: Proposal to remove (for now) the sis-webapp module Shah, Your enthusiasm here is great but the use case isn’t really what SIS was meant to do. Have you looked at Tensorflow, Caffe or Microsoft machine learning tools for this use case? Actually, I think Facebook with their Caffe 2 implementation has a facial recognition algorithm that runs on a smart phone Adam > On Jan 13, 2020, at 6:43 AM, Shahjahan Ahmed <[email protected]> wrote: > > Ok, remove if the module is not in use. Additionally, begin building me app > for deployment to all personnel smart phones which will allow them to quickly > identify individuals through various data sources including biometric data, > such as fingerprint on smartphone and facial features. > > The app should be encrypted for use only by personnel and the app should be > registered and distribute to smart devices which are owned by personnel. > > Please develop this immediately. > > Best Wishes, > > Shah > > > Shahjahan Ahmed > Publisher > Web: www.seanews.co.uk > Phone No: +44 (0)203 302 0097 > Email: [email protected] > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. If > you have received this email in error please notify the system manager. This > message contains confidential information and is intended only for the > individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately by e-mail if you have received this e-mail by mistake and delete > this e-mail from your system. If you are not the intended recipient you are > notified that disclosing, copying, distributing or taking any action in > reliance on the contents of this information is strictly prohibited. > > > -----Original Message----- > From: Martin Desruisseaux [mailto:[email protected]] > Sent: 13 January 2020 10:21 > To: [email protected] > Subject: Re: Proposal to remove (for now) the sis-webapp module > > Hello Shahjahan > >> Le 12/01/2020 à 18:52, Shahjahan Ahmed a écrit : >> >> Before removing it. Does anyone know what the app was designed for? > > A description is available on the wiki at [1]. My understanding it that > user enters coordinates of a bounding box and the application shows > locations (maybe with additional info) of some points in that bounding > box, with GeoRSS as the source of those points. But I think it has never > been an application working "out of the box". The files in the WEB-INF > and META-INF directories are values like > "/path/to/sis-location-config.xml" [2], "/path/to/qtree/index/dir", > "/path/to/georss/xml/files/dir" [2][3], apparently expecting a developer > to edit those paths and build locally. After the paths have been set, > the application reads a list of URLs of GeoRSS sources [4]. The links > listed in this file seem dead now, so I can not check the data format. > The results were shown in a JSP page which imports CSS and JavaScript > from http://leaflet.cloudmade.com (maybe for showing the map) [5], but > the referenced resources do not seem to exist anymore. The whole Java > code is a single, relatively small Java file [6]. > > The reason why I propose to remove sis-webapp is because it is currently > the only code in SIS which use QuadTree. An issue has been raised > recently on user mailing list [7] which requires a QuadTree or RTree for > proper resolution. So I though about using the existing SIS QuadTree > [8], but it is a "Point QuadTree" (storing only points) while resolving > the issue requires a "Region QuadTree" (storing bounding boxes). I have > also other concerns with that QuadTree (e.g. it works with > latitudes/longitudes only and uses a hard-coded Earth radius) which > incited me to put a warning in Javadoc saying that this class may change > in future SIS release. Now if we want to work on this QuadTree, the task > would be a little bit easier if we do not need to preserve compatibility > with sis-webapp. > > Note: we had a Google Summer of Code project 1~2 years ago about > implementing an OGC Catalog Service for the Web (CSW). This is a > distinct sis-webapp than the one I'm proposing to remove. The result of > this GSoC project is still on a separated repository for now [9]. My > hope is still to use that GSoC work as a starting point for a new > application/sis-webapp module in the future. > > The proposal is about removing the Java code, JSP page and configuration > files, but keep sis-webapp has an empty (for now) module ready to > receive new work. The removed sis-webapp still have value as an example > of how to setup a small server using Jetty and how to configure the tests. > > Martin > > [1] https://cwiki.apache.org/confluence/display/SIS/Web+application > [2] > https://github.com/apache/sis/blob/0.8/application/sis-webapp/src/main/webapp/WEB-INF/web.xml > [3] > https://github.com/apache/sis/blob/0.8/application/sis-webapp/src/main/webapp/META-INF/context.xml > [4] > https://github.com/apache/sis/blob/0.8/application/sis-webapp/src/main/resources/sis-location-config.xml > [5] > https://github.com/apache/sis/blob/0.8/application/sis-webapp/src/main/webapp/demo.jsp > [6] > https://github.com/apache/sis/blob/0.8/application/sis-webapp/src/main/java/org/apache/sis/services/LocationServlet.java > [7] > https://lists.apache.org/thread.html/rfec61914fd6f5ce6798953aeea8c37d813408438021ec5626da40500%40%3Cuser.sis.apache.org%3E > [8] http://sis.apache.org/apidocs/org/apache/sis/index/tree/QuadTree.html > [9] https://github.com/haonguyen123/sis/tree/CSW >
