Problem loading JSON file indoor EILLocation


I have problem loading EILLocation.drawlocation() as shown in Image 2. In Image 1 I have shown how I load the the location though JSON file. I couldn’t figure what wrong here but I believe its something wrong with the library.

Meanwhile, I do believe that Swift and Indoor SDK has updated in the way of how to access the library but the dev note are not up to date. Please update your dev doc.

For your references about not updated dev doc.
SwiftEstimoteIndoor’s example project Class References using starting from EST while the new Class References are using Class References starting with EIL. Its kinda confusing me.

Image 1


Image 2

Why not fetch the location from Estimote Cloud instead? (:

We’ve sort of deprecated the old JSON approach—to much fiddling with adding the JSON file to the bundle, keeping it up to date, etc.

As for the SwiftEstimoteIndoor example, that’s not ours, so we can’t update it. You can find our example here:

1 Like

I have the same problem like Ambiga, I guess the solution propose by you might help. I still trying.

I want to build a prototype mobile based navigation system using Estimote IndoorSDK, do you think I can build the apps just within 3 beacon?

If it is possible to build the prototype within 3 beacon, here is my logic. As you can see from the picture below, I will consider not to place the beacon number 1 and 3 since the mapping can be done using Estimote cloud instead. The navigation will be done using the idea of ranging beacon. The user will be navigate from beacon 2 to beacon 4 , then the beacon number 5 will notificate the user you have reach your destination.

If you only want to guide the user from beacon to beacon, then you can use as many or as few beacons as you like/need.

Indoor Location in its “Normal” mode requires a pretty dense beacon setup, because it gives you fine-grained (x,y) position of the user. You can however use Indoor Location in the “Light” mode (read more about it here and here), which uses a different, less precise algorithm, but as a result you can use it with any number of beacons. (Precision will simply be better around the beacons.)

And of course, you can always use plain ranging as you said, then you can also do beacon-to-beacon navigation with any number of them (:

1 Like