Mapfiles preparation #179

New Issue

mpeltriaux · 2022-06-22T12:32:32+02:00

mpeltriaux commented

2022-06-22 12:32:32 +02:00

Status quo

All data aggregated by KSP need to be published using WMS and/or WFS on LANIS. For this, new mapfiles need to be created, which access the data stored on the database.

Mapfiles and views

The mapfiles are going to access prepared views on the database. These views will only be accessible for a certain user.

All views will return at least the following attributes:
identifier, title, geometry, report_link

Where identifier refers to the previous "Kennung", title holds the human readable title of the entry and geometry holds the geometry using the crs 25832 (default of RLP).

view_eiv_recorded

Returns all recorded interventions ("EIV"). Color scheme should follow the already known color currently used in LANIS.

view_eiv_unrecorded

Returns all unrecorded interventions ("EIV"). As discussed with LanisZ, rendering those entries would be a huge improvement especially for architects out there during planing phase: They are not really interested on details of certain entries but rather in the placement of their surfaces. Showing these 'in-progress' surfaces helps avoidance of de-facto-used areas for new projects.

Color scheme for these entries must follow: Fill color similar to view_eiv_recorded but with a obvious red touch. No border color. Fill color must be displayed using a linear-gradient, to further highlight the in-progress state of these entries.

view_kom_recorded

Returns all compensation ("KOM") of recorded interventions. Color scheme should follow the already known color currently used in LANIS.

view_kom_unrecorded

Returns all compensations ("KOM") of unrecorded interventions. As discussed with LanisZ, rendering those entries would be a huge improvement especially for architects out there during planing phase: They are not really interested on details of certain entries but rather in the placement of their surfaces. Showing these 'in-progress' surfaces helps avoidance of de-facto-used areas for new projects.

Color scheme for these entries must follow: Fill color similar to view_kom_recorded but with a obvious red touch. No border color. Fill color must be displayed using a linear-gradient, to further highlight the in-progress state of these entries.

view_oek

Returns all recorded eco accounts ("OEK"). Color scheme should follow the already known color currently used in LANIS.

There is no need to provide another view for unrecorded eco accounts

view_ema

Returns all recorded ema entries ("EMA"). Color scheme should follow the already known color currently used in LANIS.

There is no need to provide another view for unrecorded eco accounts

# Status quo All data aggregated by KSP need to be published using WMS and/or WFS on LANIS. For this, new mapfiles need to be created, which access the data stored on the database. # Mapfiles and views The mapfiles are going to access prepared views on the database. These views will only be accessible for a certain user. All views will return at least the following attributes: `identifier`, `title`, `geometry`, `report_link` Where `identifier` refers to the previous "Kennung", `title` holds the human readable title of the entry and `geometry` holds the geometry using the crs 25832 (default of RLP). ## view_eiv_recorded Returns all recorded interventions ("EIV"). Color scheme should follow the already known color currently used in LANIS. ## view_eiv_unrecorded Returns all unrecorded interventions ("EIV"). As discussed with LanisZ, rendering those entries would be a huge improvement especially for architects out there during planing phase: They are not really interested on details of certain entries but rather in the placement of their surfaces. Showing these 'in-progress' surfaces helps avoidance of de-facto-used areas for new projects. Color scheme for these entries must follow: Fill color similar to view_eiv_recorded but with a obvious red touch. No border color. Fill color must be displayed using a linear-gradient, to further highlight the in-progress state of these entries. ## view_kom_recorded Returns all compensation ("KOM") of recorded interventions. Color scheme should follow the already known color currently used in LANIS. ## view_kom_unrecorded Returns all compensations ("KOM") of unrecorded interventions. As discussed with LanisZ, rendering those entries would be a huge improvement especially for architects out there during planing phase: They are not really interested on details of certain entries but rather in the placement of their surfaces. Showing these 'in-progress' surfaces helps avoidance of de-facto-used areas for new projects. Color scheme for these entries must follow: Fill color similar to view_kom_recorded but with a obvious red touch. No border color. Fill color must be displayed using a linear-gradient, to further highlight the in-progress state of these entries. ## view_oek Returns all recorded eco accounts ("OEK"). Color scheme should follow the already known color currently used in LANIS. **There is no need to provide another view for unrecorded eco accounts** ## view_ema Returns all recorded ema entries ("EMA"). Color scheme should follow the already known color currently used in LANIS. **There is no need to provide another view for unrecorded eco accounts**

mpeltriaux added the

feature

label 2022-06-22 12:32:32 +02:00

mpeltriaux self-assigned this 2022-06-22 12:32:32 +02:00

mpeltriaux commented

2022-07-12 10:50:34 +02:00

Mapfiles have been created for dedicated service. Rendered data comes from konova.test.naturschutz.rlp.de staging server.

mpeltriaux closed this issue

2022-07-12 10:50:34 +02:00

Sign in to join this conversation.