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

RFC108 - Heatmap/Interpolation Layer creation #4857

Merged
merged 1 commit into from Feb 13, 2014
Merged

RFC108 - Heatmap/Interpolation Layer creation #4857

merged 1 commit into from Feb 13, 2014

Conversation

tbonfort
Copy link
Member

This issue tracks the development of RFC-108: http://mapserver.org/development/rfc/ms-rfc-108.html

@sdlime
Copy link
Member

sdlime commented Jan 30, 2014

Awesome addition! Now I can ditch some hacks I dropped into GDAL years ago and a processing chain that also included imagemagick. Got any samples? --Steve


From: Thomas Bonfort [notifications@github.com]
Sent: Thursday, January 30, 2014 9:30 AM
To: mapserver/mapserver
Subject: [mapserver] RFC108 - Heatmap/Interpolation Layer creation (#4857)

This issue tracks the development of RFC-108: http://mapserver.org/development/rfc/ms-rfc-108.html


You can merge this Pull Request by running

git pull https://github.com/tbonfort/mapserver heatmaps

Or view, comment on, or merge it at:

#4857

Commit Summary

  • scafolding for heatmap support
  • some more
  • wip
  • wip
  • fix hsl2rgb
  • wip interpolation maps
  • add options
  • correct projection, configurable attribute

File Changes

Patch Links:


Reply to this email directly or view it on GitHubhttps://github.com//pull/4857.


free(values);
char ds_string [1024];
snprintf(ds_string,1024,"MEM:::DATAPOINTER=%p,PIXELS=%u,LINES=%u,BANDS=1,DATATYPE=Byte,PIXELOFFSET=1,LINEOFFSET=%u",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rouault could you please give a quick yes/no answer as to whether it is correct to use this method to create a GDAL datasource. i.e. can/should I be using the GDAL C api to create this datasource rather than making it parse this string ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is valid. But when you create a MEM dataset this way, you remain the owner of the buffer. It is your responsibility to you to destroy it after the MEM dataset has been destroyed (the MEM dataset wouldn't know with which method to use to free the buffer).

If you want the MEM dataset to manage the buffer, then you should use GDALCreate().

also adds:
 - rfc86 scaletoken substitutions for PROCESSING entries
 - proj fastpaths for 3857->4326 reprojections
@tbonfort tbonfort merged commit 6676cea into MapServer:master Feb 13, 2014
tbonfort added a commit to MapServer/msautotest_DEPRECATED that referenced this pull request Sep 23, 2014
@hlherrera
Copy link
Contributor

It works!!!

@Yogurt4
Copy link

Yogurt4 commented Jun 28, 2015

Hi. I was just wondering if this feature could be used to plot a data grid. (And if not, whether it could be developed.)
We have various distribution maps. However, instead of colouring by density of scattered points, we have measurement points on a rectangular grid. The values can come from soil chemistry, air pollution, humidity, etc.
What we need is an interpolation between the measurement points, like the isothermal or isobar plot in the weather forecast.

Or, imagine the SRTM (Surface Radar Terrain Model) data from NASA. It is also a rectangular grid of elevation data. Using this data one could draw an elevation map in MapServer.

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

Successfully merging this pull request may close these issues.

None yet

5 participants