-
Notifications
You must be signed in to change notification settings - Fork 1
HERE Developer
This document will outline possible integrations with HERE Developer solutions.
Add crud adaptor integrated with typescript sdk for layer data.
Convert panel page form to layer / protobuf to be used to define a a layer / schema. Investigate how this could be achieved.
Installation options for existing AWS account (dev and prod).
Example reques.
Create near locality search demo.
Browse is probably the primary end-point for our current purposes.
Also auto suggest possibly for quickly finding categories.
I'm interested in seeing places around a marker by (lat and long or address).
Lookup location - flag on map Easily add queries with flags for queries against location. For example find all walmarts, safeways relative to this hotel.
I need hotel - geo code - Use lat and long to plugin to query
sandwhich places near this hotel
fastfood places near this hotel
chains near this hotel.
-- click mark and get details including walkable distance.
future can add map and click create walkable route directions.
save searches and recreate views easily - come back to later. Create view groups for a certain area or "trip".
Example of geo code:
This requires the exact address. However, it would be useful to implement beta auto COMPLETE
Find a place based on location context.
What I can currently do is probably pop an address into a field. Feed that address into a geocode query. Grab the first item - need conditional? if met continue. Maybe not.
At the top of the page is an input address. In the left panel results show up. User can select location(s) from results. When location selected it becomes search context. I don't really think its going to be possible to do multiple searches.
each item in search can be broken up into separate nested panels panels.
or better yet each item in a collection
When result is clicked goes into collection -
browse:at accepts ONE location context via lat,lng
Therefore, each top level location selected requires new query.
The map style needs to somehow know where to get its data from.
Each result will be nested. Therefore, the map style would need to have configuration to allow multiple sets on one map from multiple nested panels. Otherwside it would not be possible to combine. Either that or a map can be cumaltive and doesn't erase data even if the panes no longer exist. There could be an option for a style to not redraw. For now that could be implemnted into the map. Where changes in data don't redraw the entire panel. For now it could just be implemented with a redraw with plans to implement something later as this develops.
Location Explorer - name of demo
address_form
- formly input or auto suggest.-- that could work. - select - use location id. - use auto complete - easy
- would be cool to allow multiple locations to be selected -- these become main land markers on map.
- currenrly this just requires some additional code to do repeating fields that is already in a test/demo page.
- the locations that are selected can probably just be displayed inline - like tags.
- You could feed it all the ids via querystring input to regenrate the selections - if we want that. or by saved search possibly. This would save to idb currently.
- It would neat if autocomplete had a way to pass in an alternative view using a panel binding. Right now its strictly limited to using tokens. Probably not critical but would be nice and has other useful methods.
- I think the value for the auto complete or its ID will need to be the combination of lan,lng just like what will be passed into browse query.
- Data model becomes array of strings ie. ['-12.0000,98.00000', '-1.77888,9.00000']
- I think I can add a datasource that is a context to the form. Than have that context bind to a select transform of the array of location selections.
- form needs to be able to be use as context.