Map View Improvements

[Greenlight88]

Hi Norm,

Hit some limitations with the map view thought I'd jot down a couple of ideas to improve, I've put the more relevant ones to us in particular first with just a couple of other thoughts last

1. Set a Pin location with syling from KTL

Use case - we have maps that show our bookings it would be good to also show where our consultants homes are located - we could only do that if the home were a booking - you might want to show other static elements against a dataset for other reasons e.g. we have labs that we occasionally have to travel to, drop off points etc

2. Style pins based on conditions

In knacks native application you can style based on just one condition, it would be great if you could combine conditions in some way to set the styling of a pin

3. Knack does not support labels for pins

4. support for k-files? I think its called a kfile - its a file of vectors and coordinates that defines a shape - if knack could do all these things

5. Better / different pin styling? Knack has jhust one style of pin as native

With thanks for consideration

[Greenlight88]

Thought of a solution for my main issue so thought I'd post - this is actually a data structure issue, we currently map different kinds of addresses in seperate tables eg for us Bookings has addresses and so does enquiries and so does consultants.

I think its ok and useful to have actual address fields within each table but if you want to map these elements together you create a new table (Sites) which is connected to these other tables and has as fields say:

Address
Multiple choice (Bookings, Enquiries & Consultant Addresses)

You could have this autocreated using a knack Submission rule (Create a connected entry)

Now you can map all elements on one map and you could change pin colour based on the Multi choice field

Now you have Bookings next to enquiries -useful for us as we can then call enquiries close to our existing bookings and say offer them a deal to book on a certain day