Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 04 18:28
    mudit3774 commented #511
  • Dec 04 18:27
    mudit3774 commented #511
  • Nov 28 17:46

    tidwall on master

    Update changelog (compare)

  • Nov 28 17:43

    tidwall on 1.19.2

    (compare)

  • Nov 28 17:42

    tidwall on master

    1.19.2 (compare)

  • Nov 28 17:13

    tidwall on master

    Fixes a false negative for inte… (compare)

  • Nov 28 13:34
    tidwall commented #511
  • Nov 28 12:57
    tidwall commented #250
  • Nov 28 09:26
    garry-9590 commented #511
  • Nov 28 08:28
    garry-9590 opened #511
  • Nov 26 12:10
    naveenchlsn commented #250
  • Nov 26 12:09
    naveenchlsn commented #250
  • Nov 25 17:56
    tidwall commented #510
  • Nov 22 07:48
    zhangyonguu opened #510
  • Nov 18 22:22

    tidwall on 1.19.1

    (compare)

  • Nov 18 22:22

    tidwall on master

    1.19.1 (compare)

  • Nov 18 18:04

    tidwall on master

    Ensure build passes on test (compare)

  • Nov 18 17:56

    tidwall on master

    Update travis ci test and push (compare)

  • Nov 17 22:06
    tidwall commented #473
  • Nov 17 22:06
    tidwall closed #473
Josh Baker
@tidwall
Hi Peter, the default field value is zero. You should be able to specify "FIELD locationId 0" and the field will disappear.
Or FSET locationID 0
Peter Hulst
@phulst
ah, I just discovered that.. thx
Josh Baker
@tidwall
np
Peter Hulst
@phulst
I also noticed that if I use detect enter,inside with a WITHIN live geofence, I get two messages at once when the object enters the fence, one with detect value 'enter' and the other with value 'inside'. Is that intentional?
Josh Baker
@tidwall
Yes. The first 'inside' triggers an 'enter' event. The same for an 'outside' and 'exit'
Peter Hulst
@phulst
ok, thanks.
Josh Baker
@tidwall
you're welcome
Pavel Makarenko
@m1ome
@tidwall did you have time to see Kafka PR?
Josh Baker
@tidwall
@m1ome I began reviewing yesterday. I need some more time to familiarize myself with Kafka first. I'll keep you posted.
Pavel Makarenko
@m1ome
@tidwall awesome!
Josh Baker
@tidwall
@m1ome All set. Kafka PR is merged. !! Yay!
Pavel Makarenko
@m1ome
@tidwall finished with MQTT but need some test over it, have a strange feeling this should be tested well :)
Josh Baker
@tidwall
@m1ome ok. We'll spend a little extra time on testing and perhaps get additional feedback on best practices around MQTT and IoT.
Pavel Makarenko
@m1ome
@tidwall ok i will jump on proto geojson issue, researching it.
Pavel Makarenko
@m1ome
@tidwall in a few days i will submit PR with a geobuf support
need to write library and add some test to it :)
And we will be ready to move on geo PROTOBUF outout
*output
Josh Baker
@tidwall
@m1ome 👍 porting the geobuf library sounds like a fun.
Pavel Makarenko
@m1ome
@tidwall i will provide additional .proto i don’t port a geobuf, beacuse they use proto v2 and need’s a lot of addition to support RFC of GeoJSON
Josh Baker
@tidwall
@m1ome will it still be compatible with geobuf?
Pavel Makarenko
@m1ome
@tidwall you wanna keep compatible version to use node.js library?
@tidwall i mean, all can use any .proto file to implement what they want and i can provide node.js/js library
Josh Baker
@tidwall
@m1ome I think it might be nice to keep compatibility with geobuf format. As long as a user can pass the same geobuf blobs to Tile38 as they would to services that utilize the JS version, I'm good.
Pavel Makarenko
@m1ome
@tidwall i can provide a node.js/js library for it :)
Josh Baker
@tidwall
@m1ome Do you mean a node.js client library?
Pavel Makarenko
@m1ome
@tidwall yes
Josh Baker
@tidwall
@m1ome :+1:
Pavel Makarenko
@m1ome
@tidwall i tried .proto file from geobuf (node.js version) and it’s kinda messy
Pavel Makarenko
@m1ome
@tidwall and if we starting to change proto file we loose compatability :(
Josh Baker
@tidwall
@m1ome what do you suggest?
Pavel Makarenko
@m1ome
@tidwall bad thing about “geobuf” is:
JSON -> PROTOBUF -> JSON conversion
it’s useless if you wanna provide speed and compact protocol
i mean i will provide JSON to PROTOBUF conversion, but you can manually do this in your application using .proto file
It’s quite simple
Josh Baker
@tidwall
@m1ome I agree that we shouldn't touch JSON in the processes. It could just go straight from geobuf to the native object format that Tile38 uses today. And vice versa.
Pavel Makarenko
@m1ome
Yeah with a small interface :)
And that’s a main idea
I will prepare JSON Pack/Unpack function also for a external use
Josh Baker
@tidwall
@m1ome I think we're on the same page. :+1:
Pavel Makarenko
@m1ome
@tidwall wonderful :)
Josh Baker
@tidwall
Tile38 2.0 pre-alpha benchmarks tidwall/tile38#171
Agustin Bacigalup
@redraw
Hi! hey. promising project. I've seen latest Redis versions support spatial queries, however, concerning tile38, is it like a modified Redis with extended geo features written in Go? Is it built on top of Redis?
Josh Baker
@tidwall
Hi Agustin. It's not built on Redis. Totally custom code base. It only shares the same network protocol making it easy to use most popular Redis clients.
Agustin Bacigalup
@redraw
Great
Justin Lowery
@umpc
Hi @tidwall. I hope you’re doing well. How is Tile38 version 2 coming along?
Josh Baker
@tidwall
Hi @umpc. All is well and I'm sorry 2.0 is taking so long. The progress is slow at the moment with most of the effort going towards data structures that support new spheroid calculations. There's a few low hanging features that will improve performance which I may introduce into the codebase prior to 2.0.
Justin Lowery
@umpc
@tidwall I’m patient for it. It seems to be worth the wait!