157 geodata route

[bariela]

Description

• fixed issue with missing isochrones
• renamed staticLayers everywhere to dataLayers (expect route definition for backward compatibility)
• used specific function for getting SRID value from database table
• allow for missing projection in url queries
• leftJoin instead of innerJoin for attribute in mapLayers for layers like tile type which do not have attributeId
• allowed reserved characters in specific url query parameters
• use boxReload parameter in layerOptions

There is still issue with geometry filters in postgres queries due to unresolved SRID values in geodata routes

Motivation and Context

How has this been tested?

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• [ ] I have read the CONTRIBUTING document.
• [ ] I have checked to ensure that there aren't other open Pull Requests for the same update/change.
• [ ] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[srezacova]

Hi, should't we add allowReserved: true also to attributeId in /api/attributes and remove encode/decode from code? And for all proj, attributeId, attributeIdCategory we have in apischema.

When I run initial load on Dashboard layer throw: "APIError: Parameter 'attributeId' must be url encoded. Its value may not contain reserved characters.\n That's weird, I have feeling that this worked before for attributeId.

Maybe we should also get rid of word static in apischema, but I guess that's not important now.

Initial data upload is failing because of null value in column "geo_data_url" of relation "layer_geo_data" violates not-null constraint, if tested with demo data, but that is also in main.

In log from initial load I see [1] "[18].featureIds[0].property:"province"" is not allowed, that probably shouldn't be there.

[bariela]

Hi, should't we add allowReserved: true also to attributeId in /api/attributes and remove encode/decode from code? And for all proj, attributeId, attributeIdCategory we have in apischema.

When I run initial load on Dashboard layer throw: "APIError: Parameter 'attributeId' must be url encoded. Its value may not contain reserved characters.\n That's weird, I have feeling that this worked before for attributeId.

Maybe we should also get rid of word static in apischema, but I guess that's not important now.

Initial data upload is failing because of null value in column "geo_data_url" of relation "layer_geo_data" violates not-null constraint, if tested with demo data, but that is also in main.

In log from initial load I see [1] "[18].featureIds[0].property:"province"" is not allowed, that probably shouldn't be there.

For the parameters - yes, they should be all probably handled the same way

For the apischema I agree, not priority now The initial-data-load failing is all right, it should - there is apparently problem in data/config, not in code. The log directly says it, featureIds should be array of strings, it gets object with property 'province'