Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: setting a different unit for Y-axis, i.e., for translation --> elevation #77

Open
prasanjitdash opened this issue Mar 26, 2020 · 1 comment

Comments

@prasanjitdash
Copy link

Is there a setting to change the unit of the elevation w/o changing the source code?

In my case, I'm customizing this to display ocean front gradient values and the unit is K/100km or some variant. A sample data file is attached (rename to .js to include in the file header)
test.txt

Thank you

@prasanjitdash
Copy link
Author

I am also struggling to figure out how to insert 'properties' in FeatureCollection. The example .js file provided with the plugin is not a valid geoJSON (fair enough) and properties cannot be specified for a FeatureCollection but only for features. When I read a geojson data dynamically, need to append the following leading and trailing blocks:

{
    "type": "FeatureCollection",
    "features": [
      **<<insert A valid geojson feature>>**
	],
    "properties": {
        "Creator": "https://www.star.nesdis.noaa.gov/star/socd_index.php",
        "records": 1,
        "summary": "steepness"
    }
}

My question is, can the 2nd set of properties at the bottom be specified externally to the plugin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant