Hi Florian, Yes, currently you have to enter the whole URL in the adapter to get it to work. We would like to have a service for that, to evaluate the URIs and also suggest the once that are already integrated.
You can have a look in the vocabulary module [1] in the backend. There we have already integrated multiple vocabularies, but we constantly try to extend those. If you have any suggestions we can add them. Philipp [1] https://github.com/apache/incubator-streampipes/tree/dev/streampipes-vocabulary <https://github.com/apache/incubator-streampipes/tree/dev/streampipes-vocabulary> On 2020/02/19 18:46:31, Florian Micklich <[email protected]> wrote: > Hi all,> > > I would prefer to put the documentation in a wiki and not in the project > itself. So it is easier to find. Documentation in the resource folder is > something else and already provided.> > > A block post is a good idea after the story is expanded a bit with some > other basic PEs :)> > > > Thanks for the info with the Geo.lat and Geo.lng ontology. I was aware of > this functionality and I first implemented it this way. But I was not able to > add this in the adapter setting, so I switched back to numbers in my PE. I > was using the ontology therms Geo.lat and Geo.lng in the adapter setting but > this was not working.> > > Then I used the provided strings, Philipp mentioned [0].> > > http://www.w3.org/2003/01/geo/wgs84_pos#lat> > > http://www.w3.org/2003/01/geo/wgs84_pos#long> > > This way it is working! So I will implement this change in the committed > LatLngToGei PE, after a quick testrun.> > > Are there any other ontology settings worth mentioning? Not only for Geo? A > drop down list would be also a good idea .> > > Greetings> > > Florian> > > > > > Am 16.02.20 um 22:09 schrieb Philipp Zehnder:> > > Hi Florian,> > > sorry for the late reply.> > > Very cool, I tested your processors and they worked as expected and I will > merge them directly.> > Just one minor comment. Please try to avoid logging raw events to the > console. This makes it harder to find errors and exceptions in the logs when > the service runs in a docker container.> > > For domain properties (semantic types) of the latitude and longitude values > in wgs84 you can use Geo.lat / Geo.lng [0].> > If you add this to the requiredPropertyWithUnaryMapping the properties are > then already pre-selected.> > > Regarding your question in the other mail about the env file in the module > streampipes-processors-geo-jvm:> > Each module should contain an env file for development to reduce the > configuration effort for other developers. But I saw you already committed it > in your pull request.> > > Your step by step guide in this email is very good, this would also be > helpful for other developers.> > My suggestion would be to add it to our developer documentation [1]: How to > run processors in the project incubator-streampipes-extensions in IntelliJ> > What do you think?> > > Regarding your second pull request: The documentation you provided [2] is > awesome.> > My question to the other members of the community would be, where would we > best keep this documentation?> > * Wiki> > * Documentation> > * directly in the project> > * somewhere else> > > Maybe you could also write a short blogpost containing your descriptions? > This might be a good getting started for new users.> > > Thanks again for your contribution, I really look forward to all the geo > processors.> > > Cheers,> > Philipp> > > > [0] > https://github.com/apache/incubator-streampipes/blob/dev/streampipes-vocabulary/src/main/java/org/apache/streampipes/vocabulary/Geo.java > > <https://github.com/apache/incubator-streampipes/blob/dev/streampipes-vocabulary/src/main/java/org/apache/streampipes/vocabulary/Geo.java><https://github.com/apache/incubator-streampipes/blob/dev/streampipes-vocabulary/src/main/java/org/apache/streampipes/vocabulary/Geo.java>> > > [1] https://streampipes.apache.org/docs/docs/dev-guide-introduction/ > <https://streampipes.apache.org/docs/docs/dev-guide-introduction/><https://streampipes.apache.org/docs/docs/dev-guide-introduction/>> > > [2] > https://github.com/giviflo/incubator-streampipes-extensions/tree/feature/geo_jts_doc > > <https://github.com/giviflo/incubator-streampipes-extensions/tree/feature/geo_jts_doc><https://github.com/giviflo/incubator-streampipes-extensions/tree/feature/geo_jts_doc>> > > > On 2020/02/11 20:39:24, Florian Micklich <[email protected]> wrote:> > > > Hi Philipp,>> > > the incompatible pom settings didn't give me any rest this evening and I > found probably the reason why.>> > > In the first attempt I just used "open" in Intellij to load the the > "/incubator-streampipes-extensions/streampipes-processors-geo-jvm" project > path.>> > > Tonight I used "import project" option in Intellij and followed the > instruction steps:>> > > ++ Select maven project where the pom file exists --> > /incubator-streampipes-extensions/streampipes-processors-geo-jvm to impo>> > > ++ import project from external model --> maven>> > > ++ import project setup --> left all default settings as it is>> > > ++ select profile --> java8-doclint-disable in my case (don't know what this > means)>> > > ++ select maven project to import --> > org.apache.streampipes:streampipes-processors-geo-jvm:065.1-SNAPSHOT>> > > ++ SELECT SDK --> 1.8 (in my case sdkman/candidates/java/8.0.232-zulu>> > > ++ left project name and file location at it is>> > > ++ .idea folder already exists. Overwrite --> yes>> > > > ==> sources will be loaded and almost all sources are available.>> > > Only following source couldn't be found:>> > > <parent>>> > <artifactId>streampipes-extensions</artifactId>>> > <groupId>org.apache.streampipes</groupId>>> > <version>0.65.1-SNAPSHOT</version>>> > </parent>>> > > > I copied my local env file into the develop folder. Run the ./sp start > command in the installer folder and everything is running quite charming > without any problems.>> > > So I would say I close the push request and start a new one after adding my > existing work. So everything is nice and clean.>> > > Should I also add my local env file to the commit or what is recommended?>> > > > Greetings>> > > Florian>> > > > > Disy Informationssysteme GmbH>> > Florian Micklich>> > Lösungsentwickler>> > +49 721 16006 477, [email protected]<[email protected]>>> > > Firmensitz: Ludwig-Erhard-Allee 6, 76131 Karlsruhe>> > Registergericht: Amtsgericht Mannheim, HRB 107964>> > Geschäftsführer: Claus Hofmann>> > > Bitte beachten Sie folgende Informationen für Kunden, Lieferanten und > Bewerber>> > - Datenschutz: www.disy.net/datenschutz<http://www.disy.net/datenschutz>>> > - Informationspflichten: > www.disy.net/informationspflichten<http://www.disy.net/informationspflichten>>> > > > > > > Disy Informationssysteme GmbH> > Florian Micklich> > Lösungsentwickler> > +49 721 16006 477, [email protected]> > > Firmensitz: Ludwig-Erhard-Allee 6, 76131 Karlsruhe> > Registergericht: Amtsgericht Mannheim, HRB 107964> > Geschäftsführer: Claus Hofmann> > > Bitte beachten Sie folgende Informationen für Kunden, Lieferanten und > Bewerber> > - Datenschutz: www.disy.net/datenschutz> > - Informationspflichten: www.disy.net/informationspflichten> > >
