search

bcgov / smk-cli

The Command Line Interface enables users to rapidly create and edit SMK map configuration, including data consumption via OGC and Esri ReST data access services and local data files.
https://bcgov.github.io/smk-cli
Apache License 2.0
5 stars 3 forks source link

Manage Vector Layers - Not working #66

Closed franTarkenton closed 2 years ago

franTarkenton commented 3 years ago

When trying to work with some custom layers I am running into the following issue:

get an error message saying the -smk-catalog.json file does not exist.

Then when I try to import a vector layer:

After that is complete the layer does not show up in the list of vector layers. I think what is suppose to happen is the csv gets converted to geojson, and then you should be able to add that layer. Anyways after clicking through the section where you define the columns the layer never shows up anywhere.

I was eventually able to add a geojson object using the gui. I think the problem might be specific to layers that need to be transformed before they can be used.

dgboss commented 3 years ago

@franTarkenton I'm able to add a csv file with point features using the GUI and then I am able to add it to the layers I want in my map. Do you have a specific sample file you could share that demonstrates the issue? Thanks!

michaelpnelson commented 3 years ago

Hi @franTarkenton . The first issue you mention may have been addressed. Change https://github.com/bcgov/smk-cli/commit/6bfed7d4af7ab453ec50025cbc9f30f606f550e0 suppresses the "does not exist" error when the layers directory is empty. If you're seeing this error when your layers directory is not empty, please let us know and we can investigate further.

michaelpnelson commented 3 years ago

Hi @franTarkenton. I'm checking in on the CSV transformation problem you were experiencing. Are you still seeing the issue? If you are, could you send us a sample file we could use to replicate the issue? Thanks!

michaelpnelson commented 2 years ago

As part of revisiting older issues, we're closing this one. If the CSV issue is seen again, we can create a new issue.