Cartodb: Invite to georeference proactively when detecting non-georeferenced data.

[carlostallon]

Context

When you enter non georeferenced data, we are adding a new enhancement to avoid a user could end up not seeing anything on the map and not knowing he must georeference the data, which
would end up in a blocker

Step by step mockups

Design ready

Sketch archive here: Dropbox / CartoDB / Projects / 01-webapp / 03-Map-editor / 02-mockups / 3.x / _issues / 465 proactive georeference

Related design issue

https://github.com/CartoDB/design/issues/465

[xavijam]

Oido cocina!

[saleiva]

While fixing this, we should also fix another issue which is that when not having georeferenced data, we shouldn't let people to add widgets from that layer.

[xavijam]

But it is possible that the user wants to connect a widget to that "node", where at the same time, it is connected to another node by an analysis. Make sense?

[saleiva]

I don't think widgets work without georef data...

[xavijam]

Arg, you are right, I was blind by the data stats.

[matallo]

already started working on this, on top of the work done for the onboarding, I have some doubts, though

• Shouldn't we show this screen once the user has entered the layer?

It could be hard to approach the case where several layers have non-georeferenced data. Also, once the user enters the layer that tab (style) would be the one selected. I think this will be more consistent with the rest of the onboardings, like analysis, and easier to handle (Maybe I'm a bit biased).

• The same case happens with the warning box, I'm used to see them inside the layer.

• The placeholder image beside the georeference button looks weird to me, it looks like a layer block, but you are already inside the layer.

Finally, is this the final copywriting?

Thanks!

[saleiva]

cc/ @CartoDB/design

[matallo]

wip on this issue has been done in the next branch https://github.com/CartoDB/cartodb/tree/11316-georeference

[arianaescobar]

Let me try to give a bit more of information:

The message _à la onboarding_ will only be shown the first time ever you add a non-georeferenced layer to a map on your account. After marking that message on the "Don't show me this again", the next time you add a non-georeferenced layer to a new map (and ONLY if it's the first non-georeferenced layer of that map), we'll show you the notification + icon.

So we'll only give this information once per map because it's possible that our users might like to add a non-georeferenced layer to use on an analysis without needing it to be georeferenced and we don't want to bother anyone with the same message over and over again.

That's why we want those messages to appear on the layer list, instead of inside the layer itself. If we show it inside the layer, we might also have issues when mixing the layer onboarding with that first initial message, so that's another reason in favor of doing it on the layer list.

I didn't understand this part:

"The placeholder image beside the georeference button looks weird to me, it looks like a layer block, but you are already inside the layer"

Could you elaborate on it? @matallo

Regarding the copywriting being final, yes it is. It was already reviewed by @brittanymicek and approved by Design. Are you seeing anything strange that we should take a look at?

I hope this solves your doubts :)

[matallo]

Sure, that was the case when you are in the layer view, and you are presented with a card whith a resemblance to the layer card i.e.

that reminds me of the layers view cards

which look weird to me, since in my mental model you are already in the layer view, and you are presented with the layer card, being the georeference an analysis, I'd go with the same style than analysis placeholder, but idk

---

OK to the rest of comments, and thanks for the extensive explanation

[arianaescobar]

Oh, got it! You are right, let us take a look and we'll get back at you on that.

[arianaescobar]

Ok, green light on making it look like the analysis placeholder instead of the layer one. Great catch @matallo :)

[xavijam]

:clap:

On 20 February 2017 at 12:02, Ariana Escobar [e-mail]
wrote:

Ok, green light on making it look like the analysis placeholder instead of
the layer one. Great catch @matallo https://github.com/matallo :)

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/issues/11316#issuecomment-281050340,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIEMnwj5BPrDIXd0Agdf8HD-Razi-i6ks5reXLTgaJpZM4LpOrk
.

[matallo]

Coming back to this, what happens when the user hasn't gone through the builder onboarding? I break down the steps below:

1. User enters in her newly created account
2. add a non georeferenced dataset from dashboard
3. goes through builder onboarding
4. goes through georeference data onboarding ?

I'll stick to the design but I just wanted to bring up this quite common case, where the user has to go through two consecutive onboardings

[matallo]

Also there's still the point about how to approach the case where several layers have non-georeferenced data, as the user can select several dataset at the moment of create the map in the dashboard.

What has to be shown in the onboarding, then?

[arianaescobar]

After discussing it with the team...

To your first doubt, yes, the Georeference "onboarding" would appear after Builder's main onboarding.

To your second doubt, the onboarding would show the information of the first non-georeferenced layer and the main button will take you to georeference that layer.

[matallo]

Advanced with this, this is looking good 🙂

btw, I'm just showing it in case there are rows (it makes no sense to georeference an empty dataset, despite it will say it has no geometry 🙈 I will elaborate on this in the PR, but maybe you'd like to think in another onboarding to add rows to an empty dataset 😬 )

thanks for bearing with me!

[xavijam]

Back to development again (and hopefully the last one). We will tackle last small details on monday and then, 🚀 .

[xavijam]

Ready to be deployed! 🎉 🎉 🎉

[matallo]

:_)

[xavijam]

Annnnddddddddd DEPLOYED!

[saleiva]

Is this finally instrumented? @noguerol