esri / featureservice2trigger Goto Github PK

We can generate a token with the provided client id and secret. With that we should be abel to access FeatureServices the user owns.

Resolve #2 and #3.

we tried several times to import public features service but everytime it appear the following error (see the text from the shell)

Sorry we are novices but any help is appreciated.
thanx
enico & luca
....................
C:\temp>
C:\temp>
C:\temp>featureservice2trigger --clientId=1AtftFpnFgrW1ONi --clientSecret=19d290
6d9f58442f8f21b6e50beecb37 --tag=bacini --tag=idro --serviceUrl="http://webgis.a
rpa.piemonte.it/ags101free/rest/services/acqua/qualita_acque_balneazione_WM/Feat
ureServer/0" --buffer=300 --notificationTemplate="Welcome to {{DESCRIZION}}"
Getting metadata for http://webgis.arpa.piemonte.it/ags101free/rest/services/acq
ua/qualita_acque_balneazione_WM/FeatureServer/0
Success! Got metadata for http://webgis.arpa.piemonte.it/ags101free/rest/service
s/acqua/qualita_acque_balneazione_WM/FeatureServer/0

Requesting Features...

stream.js:94
throw er; // Unhandled stream error in pipe.
^
Error: Unexpected "!" at position 1 in state START
at Parser.proto.charError (C:\Users\enribona\AppData\Roaming\npm\node_module
s\featureservice2trigger\node_modules\JSONStream\node_modules\jsonparse\jsonpars
e.js:84:16)
at Parser.proto.write (C:\Users\enribona\AppData\Roaming\npm\node_modules\fe
atureservice2trigger\node_modules\JSONStream\node_modules\jsonparse\jsonparse.js
:112:23)
at Stream. (C:\Users\enribona\AppData\Roaming\npm\node_modules\fe
atureservice2trigger\node_modules\JSONStream\index.js:27:12)
at Stream.stream.write (C:\Users\enribona\AppData\Roaming\npm\node_modules\f
eatureservice2trigger\node_modules\JSONStream\node_modules\through\index.js:26:1
1)
at Request.ondata (stream.js:51:26)
at Request.EventEmitter.emit (events.js:95:17)
at IncomingMessage. (C:\Users\enribona\AppData\Roaming\npm\node_m
odules\featureservice2trigger\node_modules\request\request.js:820:12)
at IncomingMessage.EventEmitter.emit (events.js:95:17)
at IncomingMessage. (_stream_readable.js:746:14)
at IncomingMessage.EventEmitter.emit (events.js:92:17)

Lots of discussion on how to do this here Esri/geoservices-js#35

Under Options/notificationTemplate. As far as I know this is the only place where this needs to be fixed.