Skip to main content
November 2nd, 2023 Constraint Points are now available in PlantPredict MapBuilder We have received this request from several of our customers who are developing projects where Solar is co-located with Wind. You can now drop a Constraint Point on your map and then have a circular constraint generated based upon the setback value that you provide. The Constraint Point icon is located on the right-hand toolbar and looks like this:
Release 11 14 0 Image1 1
Just drop this onto your Map and adjust your setback.
Release 11 14 0 Image2
Constraint points also get imported from KMZ files as well, so if you have a KMZ with wind turbine locations that you would like to upload onto your map, the software will recognize these points and place them.
Release 11 14 0 Image3
These constraint points will also be exported when you Download your map data in any of the formats: KMZ, DXF or SHP.   Minor Bug Fixes and Enhancements
  • Users can upload a .KMZ backdrop to the Map Builder prediction. The system allows users to save this backdrop, eliminating the need for repeated uploads.
  • Meteonorm weather files are now being downloaded with an “Active” Status instead of “Global”, and the owner will be the user who initiated the download.
  • We restricted the ability to generate API credentials to a specific group of users who meet the following criteria:
    1. The requester must have administrative privileges.
    2. Both the requester and the user must belong to the same company, unless the requester is a super admin.
    3. Both the requester and the user must have an ‘Active’ status.
    4. Both the requester and the user must possess an active subscription for one of the following license types: Free Trial, Strategic, Education, or Enterprise.
  • We’ve enhanced support for importing large weather files. We now can import weather files containing 30 years worth of data with a 15-minute interval. The maximum size for weather file imports has been increased to 128MB.
    • If a weather file import contains more than 8,760 timestamp records (equivalent to one year of data at 60-minute intervals), the user will only see the first quarter of the data on the quality check screen. This adjustment was made to prevent errors in the API due to the size of the data.