Hi Florian, Thank you for the pointer to streampipes. As you noticed, the geocoder is really experimental ;) You are welcome to open issues on github and to improve code.
In my understanding, a “geocoder" (text to location) should not be confused with a "reverse geocoder" (location to text). Right now, we use the “geocoder” to assign a location to IP addresses based on their textual description (it usually contains the address). Antoine is currently working on ip to location. Your "reverse geocoder” looks really interesting. Our long term goal is to have a set of infrastructure component for web mapping infrastructure. The "what’s here” buttons available on many maps are probably implemented with reverse geocoders. Can your contribution to stream pipe be used outside of the context of a stream or event processor? Best, Bertil > On 30 Nov 2022, at 15:47, Florian Micklich <mickl...@apache.org> wrote: > > Hi > > during refactoring the geo processors to the 1 class method, I had a look at > the > reversegeocoder processor [1] > > Do we want to keep is this way as it is e.g. internal download from a zip > file [2]? > Should we adjust it in some way and do we want to keep it this way at all? > > This is not a really reverse geodocer ;) > > > Greetings > Florian > > [1] > https://github.com/apache/streampipes/blob/dev/streampipes-extensions/streampipes-processors-geo-jvm/src/main/resources/org.apache.streampipes.processor.geo.jvm.reversegeocoding/documentation.md > > > [2] > https://github.com/apache/streampipes/blob/dev/streampipes-extensions/streampipes-processors-geo-jvm/src/main/java/org/apache/streampipes/processors/geo/jvm/processor/revgeocoder/ReverseGeocoding.java#L36
signature.asc
Description: Message signed with OpenPGP
