<div dir="ltr">Hei!<div><br></div><div>I got my answers. Thanks guys!</div><div><br></div><div>Sander</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 9, 2022 at 12:35 PM Jörg Thomsen (WhereGroup) <<a href="mailto:joerg.thomsen@wheregroup.com">joerg.thomsen@wheregroup.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>
    <div>Hello Sander,</div>
    <div><br>
    </div>
    <div>
      <blockquote type="cite">
        <ol>
          <li>Had issues with 4326 to 3301 transformation,the extent and
            all that. (OpenLayers could manage but QGIS couldnt).
            Previously only had ows_extent. <br>
            Is ows_extent even a thing? This only shows wms_extent <a href="https://mapserver.org/ogc/wms_server.html#layer-object-metadata" target="_blank">https://mapserver.org/ogc/wms_server.html#layer-object-metadata</a><br>
            Should you use wfs_extent and wms_extent instead?<br>
          </li>
        </ol>
      </blockquote>
      the wms_ / wfs_ / ows_ / oga_ (coming in MapServer 8)
      Metadata-entry are aiming on your output. So, if you only want to
      serve wms, you only need the wms_*.</div>
    <div>wfs_* conigures your WFS-server. If you
      want to serv wms and wfs and the parameters are the same, you can
      use ows_ instead.<br>
      <blockquote type="cite">
        <ol>
          <li>My layer is doing an OGR connection directly to the API
            URL. Works fine. My question is, the API renews itself every
            2 minutes (new data).<br>
            How does Mapserver handle the request with that connection?
            I move the map (openlayers), there's a new Mapserver request
            - does Mapserver make a new request to the API endpoint and
            get a new json?<br>
            Or is there some sort of cache?</li>
        </ol>
      </blockquote>
      No cache by default. MapServer requests the data source every time
      mapserver gets itself a getmap or get feature info request (or
      getfeature when serving wfs). So your WMS serves the actual data
      any time. If you want a cache, you have to configure mapcache or
      mapproxy separately.<br>
    </div>
    <div><br>
      <blockquote type="cite">
        <ol>
          <li>Am I missing something else from the Metadata that I
            should consider? </li>
        </ol>
      </blockquote>
      I don't see anything missing</div>
    <div><br>
    </div>
    <div>Jörg<br>
    </div>
    <div><br>
    </div>
    <div>Am 09.02.22 um 10:26 schrieb Sander
      Pukk:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">Hi there!
        <div><br>
        </div>
        <div>Trying to use a geojson output from API directly in
          Mapserver layer.</div>
        <div>Geojson is per standard, 4326, but my Mapserver and OL (the
          client) is configured to 3301.</div>
        <div>We have hundreds of layers (mostly from Postgres) at the
          same time and the system works.</div>
        <div>No other direct API ones.</div>
        <div><br>
        </div>
        <div>The current MAP file's WEB part looks like this:</div>
        <div><br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> 
          WEB<br>
                METADATA<br>
                  "wfs_title"                     "title"<br>
                  "wfs_enable_request"            "*"<br>
                  "wms_enable_request"            "*"<br>
                  "wfs_encoding"                  "UTF-8"<br>
                  "wms_title"                     "title"<br>
                  "wms_encoding"                  "UTF-8"<br>
                  "wms_onlineresource"          
           "url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"<br>
                  "wfs_onlineresource"          
           "url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"<br>
                  "ows_srs"                            "EPSG:3301
          EPSG:3857 EPSG:4326"<br>
                  "ows_enable_request"            "*"<br>
                  "wfs_getfeature_formatlist"     "gml,geojson"<br>
                  "wms_feature_info_mime_type"  
           "application/json,application/json;
          subtype=geojson,application/vnd.ogc.gml,text/plain"<br>
                END<br>
            END</blockquote>
        <div> </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> 
          PROJECTION<br>
                "init=epsg:3301"<br>
            END</blockquote>
        <div> </div>
        <div> </div>
        <div>And the layer:</div>
        <div><br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> 
            PROJECTION<br>
                  "init=epsg:4326"<br>
              END<br>
             <br>
              METADATA<br>
                  "wfs_srs"               "EPSG:3301"<br>
                  "gml_msGeometry_type" "line" </blockquote>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><i> 
                   #"ows_extent" "40500 5993000 1064500 7017000" copy
            paste lon and lat from these 3301 coordinates from other
            layer's capabilites</i><br>
                  "ows_extent" "14.9318705986602 53.7681633673032
          35.1060366818735 63.2747817924556"       <br>
                  "wfs_extent"        "14.9318705986602 53.7681633673032
          35.1060366818735 63.2747817924556"<br>
                  "wms_extent"        "14.9318705986602 53.7681633673032
          35.1060366818735 63.2747817924556"<br>
                  "ows_title" "road_restrictions"<br>
                  "ows_abstract" "road_restrictions"<br>
                  "ows_keywordlist" "road_restrictions"<br>
                  "ows_include_items" "all"<br>
                  "gml_include_items" "all"<br>
                  "ows_featureid" "id"<br>
                  "gml_exclude_items"         "edges,geometry"<br>
                  "ows_exclude_items"         "edges,geometry"<br>
              END   </blockquote>
        <div><br>
        </div>
        <div><br>
        </div>
        <div> Couple of questions I have which I didnt really find
          answers for:</div>
        <div><br>
        </div>
        <div>
          <ol>
            <li>Had issues with 4326 to 3301 transformation,the extent
              and all that. (OpenLayers could manage but QGIS couldnt).
              Previously only had ows_extent. <br>
              Is ows_extent even a thing? This only shows wms_extent <a href="https://mapserver.org/ogc/wms_server.html#layer-object-metadata" target="_blank">https://mapserver.org/ogc/wms_server.html#layer-object-metadata</a><br>
              Should you use wfs_extent and wms_extent instead?<br>
            </li>
            <li>My layer is doing an OGR connection directly to the API
              URL. Works fine. My question is, the API renews itself
              every 2 minutes (new data).<br>
              How does Mapserver handle the request with that
              connection? I move the map (openlayers), there's a new
              Mapserver request - does Mapserver make a new request to
              the API endpoint and get a new json?<br>
              Or is there some sort of cache?</li>
            <li>Am I missing something else from the Metadata that I
              should consider? <br>
              <br>
            </li>
          </ol>
          <div>With kind regards,</div>
        </div>
        <div>Sander</div>
      </div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
MapServer-users mailing list
<a href="mailto:MapServer-users@lists.osgeo.org" target="_blank">MapServer-users@lists.osgeo.org</a>
<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-users</a>
</pre>
    </blockquote>
    <p><br>
    </p>
    <pre cols="72">-- 
Viele Grüße,
Jörg Thomsen

 ---------------------------------------------
 Schon gewusst?

 In unserem Blog geben wir Tipps & Tricks zu
 Open-Source-GIS-Software 
 und berichten aus unserem Experten-Alltag:
 <a href="https://wheregroup.com/blog/" target="_blank">https://wheregroup.com/blog/</a>
 ---------------------------------------------

Jörg Thomsen
WhereGroup GmbH
Bundesallee 23
10717 Berlin
Germany

Tel: +49 (0)30 / 5130 278 74
Fax: +49 (0)30 / 5130 278 11    

<a href="mailto:joerg.thomsen@wheregroup.com" target="_blank">joerg.thomsen@wheregroup.com</a>
<a href="http://www.wheregroup.com" target="_blank">www.wheregroup.com</a>

Geschäftsführer:
Olaf Knopp, Peter Stamm
Amtsgericht Bonn, HRB 9885

-------------------------------
Folgen Sie der WhereGroup auf twitter: <a href="http://twitter.com/WhereGroup_com" target="_blank">http://twitter.com/WhereGroup_com</a></pre>
  </div>

_______________________________________________<br>
MapServer-users mailing list<br>
<a href="mailto:MapServer-users@lists.osgeo.org" target="_blank">MapServer-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
</blockquote></div>