Conversation
…reusable function
…d ELASTIC_KEYWORDS as exported const
…to camelCase interface
…to camelCase CommonRequestParameters infered type
…et_grid-and-version-are-missing-in-geocodingqueryobject-in-the-response-mapco-4784
| "files": { | ||
| "__name": "S3_FILES_DATA", | ||
| "__format": "json" | ||
| } |
There was a problem hiding this comment.
This is supposed to be a large file, don't we want to provide it in another way?
There was a problem hiding this comment.
This is the config and metadata for the files that are being stores in S3.
This way the service knows what bucket and file's name to pull.
| "node": "http://control_elastic:9200", | ||
| "auth": { | ||
| "username": "control", | ||
| "password": "password" | ||
| "username": "elastic", | ||
| "password": "changeme" |
There was a problem hiding this comment.
This should stay as default values. These seem to be actual credentials (even if for local work).
There was a problem hiding this comment.
elastic and changeme are the default Elasticsearch credentials.
control_elastic is just the placeholder. for local env, you need to change it to localhost if you are running it locally.
| "node": "http://geotext_elastic:9200", | ||
| "auth": { | ||
| "username": "geotext", | ||
| "password": "password" | ||
| "username": "elastic", | ||
| "password": "changeme" |
| "controlObjectDisplayNamePrefixes": { | ||
| "TILE": "Tile", | ||
| "SUB_TILE": "Sub Tile", | ||
| "ROUTE": "Route", | ||
| "ITEM": "Item", | ||
| "CONTROL_POINT": "Control Point" | ||
| }, |
There was a problem hiding this comment.
Is this really needed? You could do the same as you do with snake to camel and vice versa and seperate by spaces.
There was a problem hiding this comment.
This is a dictionary to the feature's generated display name.
I'll change the config's name to a better name
| "F_CODE": 8754111, | ||
| "F_ATT": 951111, | ||
| "ENTITY_HEB": "control point", | ||
| "LAYER_NAME": "CONTROL_GIL_GDB.CTR_CONTROL_POINT_CROSS_N", |
There was a problem hiding this comment.
We need to make sure the namings are ok.
| /* eslint-disable @typescript-eslint/no-unsafe-assignment */ | ||
| /* eslint-disable @typescript-eslint/naming-convention */ | ||
| /* eslint-disable @typescript-eslint/no-unsafe-member-access */ | ||
| import crypto from 'crypto'; |
There was a problem hiding this comment.
It seems that this package is deprecated.
Maybe we can use uuid instead?
There was a problem hiding this comment.
This is dev-scripts. But, will change to node:crypto
| - x-api-key: [] | ||
| x-user-id: [] | ||
|
|
||
| /search/control/tiles: |
There was a problem hiding this comment.
I suggest splitting endpoints for querying tile and mgrs so we could have clearer and simpler API handling.
There was a problem hiding this comment.
This route enables search Control Tiles via providing a MGRS Tile. It will result with all of the tiles that intersects with our Control Tiles.
|
|
||
| const LAST_ELEMENT_INDEX = -1; | ||
|
|
||
| const generateDisplayName = <T extends Tile | Item | Route>( |
There was a problem hiding this comment.
Please create an enum for the common used strings representing types and other entities.
There was a problem hiding this comment.
I would like you to elaborate :)
6cd8d64 to
2577db4
Compare
… feat/feedback-api-redis
…rid-and-version-are-missing-in-geocodingqueryobject-in-the-response-mapco-4784 fix: added missing target_grid and version to the response
Feat/feedback api redis
This is the implementation of the new architecture of Geocoding API. It includes Control grid search and location search.