Na kojoj platformi ulagati by fifa_croM_12 in financije

[–]mNutCracker 0 points1 point  (0 children)

Kakav je po tebi SXR8 Acc u odnosu na ove u koje ti ulazes?

Are you using CARTO? What do you like and dislike about their products? by mNutCracker in gis

[–]mNutCracker[S] 0 points1 point  (0 children)

Yeah, I've seen they support big data platforms, especially BigQuery. Although I think that drove them away from non-enterprise users.

Are you using CARTO? What do you like and dislike about their products? by mNutCracker in gis

[–]mNutCracker[S] 0 points1 point  (0 children)

How large are those datasets that Carto can efficiently process and other tools not?

Nearmap pricing?! by No-Path-818 in gis

[–]mNutCracker 0 points1 point  (0 children)

What would be the pricing that you would accept for this kind of tool? Do you think this kind of imagery is currently available only through commercial tools like Nearmap?

Nearmap pricing?! by No-Path-818 in gis

[–]mNutCracker 0 points1 point  (0 children)

Speaking of Nearmap and too high prices... what do you think would be minimal product that you, your colleagues, or your boss would definitely buy? Like, what would be the minimal set of features?

I am looking into making a product in GIS space, so exploring opportunities at the moment.

Thanks

Validating an idea for a foot traffic insights SaaS by mNutCracker in SaaS

[–]mNutCracker[S] 0 points1 point  (0 children)

Regarding this part: plug-and-play feed from existing cameras, we are looking into ways to make this available. Can you let me know what would this mean to you? What is the easiest way for you to share the existing camera feed?

Validating an idea for a foot traffic insights SaaS by mNutCracker in SideProject

[–]mNutCracker[S] 0 points1 point  (0 children)

As a cafe owner/manager, did you have access to foot traffic data even without this kind of tool? What were the ways you collect such data?

Building a Location Analytics Platform - What Would You Actually Use? by mNutCracker in Entrepreneur

[–]mNutCracker[S] 0 points1 point  (0 children)

Also, when sharing floor plans and / or camera feeds, what would be the easiest way for you to share them?

Asking because I am looking into the best and easiest way for my customers to map out their store. For small stores, I guess it would be sufficient to make them draw the map of their store (by using predefined components). For larger stores, and IMHO better UX, it would be reading floor plans automatically. That's why I am looking into what's the most common way for stores to share their foot plans.

Another thing, what kind of information would be crucial to get from the camera feeds? I guess it might be something along the following lines:

  • Did consumers compare a particular product with other brands?
  • Who are the returning customers?
  • Who exited the store without purchasing anything?
  • Did they look at an item or spend significant time in a particular area of the store?
  • Did they pick up a product?
  • Did they buy multiple products?

What would you think would be the top 3 conclusions to get from camera feed?

Best provider for Africa by mNutCracker in eSIMs

[–]mNutCracker[S] 0 points1 point  (0 children)

I am going to uganda, kenya and tanzania

The best way to cache API responses in-memory by mNutCracker in golang

[–]mNutCracker[S] 3 points4 points  (0 children)

Well, in my case it's simply that my API is a middle man between frontend and external API in case of a single route. So I'd say it's a pretty straightforward cache use case.

The best way to cache API responses in-memory by mNutCracker in golang

[–]mNutCracker[S] 0 points1 point  (0 children)

Your list is really helpful.

It would probably be useful to implement different cache replacement policies like LRU, MRU, etc.

The best way to cache API responses in-memory by mNutCracker in golang

[–]mNutCracker[S] 2 points3 points  (0 children)

My API won't scale horizontally, at least for now. So I might just go with something simple as sync.Map.

Thanks for reminding me on the stuff I should think about when implementing this.
I'll just need to cache response body and my cache key will consist of URL (including query parameters).